gsd-spike-wrap-up

To save spike findings for future Claude conversations, this skill curates post-spike analysis into a persistent project skill, making the results auto-loadable in subsequent build sessions.

Packaging spike results works by consolidating ad-hoc analysis into a reusable project-local artifact under .claude/skills/spike-findings-[project]/, while simultaneously writing a concise summary to .planning/spikes/ to preserve project history.

The best way to manage ad-hoc spike findings is to standardize them into a durable record using an automated workflow, which prevents error-prone manual tracking and ensures decisions remain accessible project-wide.

Yes, you need matching execute-context workflows to run the spike-wrap-up process, as it integrates directly with that workflow to extract and package the latest spike findings into the reusable project skill.

Yes, you can use this skill to write a planning summary for completed spikes, as it automatically generates a concise historical record under the .planning/spikes/ directory during the packaging process.

You should not rely on manual notes for post-spike analysis because managing ad-hoc findings without a durable record is error-prone, whereas a persistent project skill ensures standardized, auto-loadable access.