| name | spike-wrap-up |
| description | Package findings from a completed spike into a durable, project-local skill that auto-loads on future similar work. Reads the most recent `.gsd/workflows/spikes/` directory, interviews the user briefly on what's reusable, then writes `.claude/skills/<name>/SKILL.md`. Use when asked to "wrap up the spike", "package this as a skill", "make this reusable", "turn findings into a skill", or at the end of the synthesize phase of `/gsd start spike`. Closes the parity gap with GSD v1's `/gsd-spike-wrap-up`. |
Convert the output of a research spike (`SCOPE.md`, `research/*.md`, `RECOMMENDATION.md`) into a project-local skill under `.claude/skills/` so that the next time a similar task comes up, the agent loads the skill automatically. This is how throwaway spikes become durable capital.
GSD's spike workflow (`src/resources/extensions/gsd/workflow-templates/spike.md`) produces documents in `.gsd/workflows/spikes//`. Those documents are useful once and then forgotten unless something packages them for reuse.
GSD already watches .claude/skills/ (and .agents/skills/) at both user and project levels — see src/resources/extensions/gsd/skill-discovery.ts. Any skill written there is picked up on the next session without further wiring. This skill is the bridge from "spike done" to "skill available."
Invocation points:
- End of Phase 3 (synthesize) in
/gsd start spike — prompt suggests running this skill
- User has a spike directory and wants to harvest it
- Pre-existing
RECOMMENDATION.md that deserves a permanent home
<core_principle>
NOT EVERY SPIKE DESERVES A SKILL. If the recommendation was "don't do X," there may be no reusable guidance. Ask the user first; exit without writing if the answer is no.
PROJECT-LOCAL, NOT USER-GLOBAL. Write to .claude/skills/ in the repo, not ~/.claude/skills/. The skill encodes project-specific choices that should not leak into unrelated projects.
