gsd-spike-wrap-up

Package spike findings by curating experiment results into a persistent project skill with YAML frontmatter, outputting the final artifact to a project-local directory under .qwen/skills for future auto-loading. This enables project-wide spike curation and versioning across development cycles.

A project skill for spike curation is a persistent artifact that groups experimental findings by theme for traceability. You need it when you want to make spike knowledge available across multiple builds and teams for faster decision making and reproducibility.

Maintain an audit trail of spike experiments by recording a project history summary during the packaging process. This enforces traceability of decisions and spikes alongside the generated skill artifact in the project-local directory.

Yes, you can auto-load packaged spike knowledge within Claude-based build workflows by outputting the skill to a project-local directory under .qwen/skills. This enables project-wide reuse across development cycles without manual reconfiguration.

Yes, the spike wrap-up skill enforces YAML frontmatter naming conventions when packaging findings. This ensures the generated project skill adheres to required metadata standards for reproducibility and versioning within the .qwen/skills directory.

The limitation of using a project skill for spike curation is that outputs are restricted to a project-local directory under .qwen/skills. This means the packaged knowledge is scoped to the specific project context rather than being globally portable across separate repositories.