spike-wrap-up

To wrap up spike findings into a reusable skill, package repeatable guidance into a project-local SKILL.md file. This process records the originating spike and updates the decision log to ensure future sessions automatically discover and load the packaged knowledge.

Convert a spike into a project-local skill when the spike findings include repeatable guidance that should be loaded automatically for future similar work across OTTO workflows, ensuring durable knowledge reuse rather than one-time documentation.

Spike wrap-up creates a persistent skill file at .claude/skills/<name>/SKILL.md from spike outputs. It also updates .otto/workflow/DECISIONS.md to record a traceable decision referencing the originating spike.

Packaging spike outputs into a durable skill enables automatic discovery by storing repeatable guidance in a project-local SKILL.md file, which future similar work sessions across OTTO workflows can automatically load and reference.

Yes, you need existing spike outputs such as SCOPE.md and RECOMMENDATION.md files. The wrap-up process packages these conclusions into a reusable skill, so the originating spike must conclude with repeatable guidance before triggering the task.

Manually documenting spike findings lacks automatic loading and traceability. Packaging findings into a project-local skill ensures future similar work auto-loads the guidance, while updating the decision log maintains a clear link to the originating spike.