What problem does it solve? Spike investigations often end ambiguously — the experiment succeeded but nobody decides what happens to the code, leaving half-shipped exploration in the main branch. This Skill forces every spike to close with an explicit disposition: either PROMOTE the findings into a production-shaped feature ticket, or DISCARD the work with a written memo so the same ground is never re-explored. ## Core Features & Use Cases - Disposition gate: Enforces exactly two outcomes — --promote files a fresh [Feature] follow-up ticket, --discard writes a memo to omnigrid-docs/spike-memos/<slug>.md. - Spike verification: Confirms the ticket is actually a spike (via [Spike] title prefix or spike label) using gh issue view before proceeding, and refuses non-spike tickets. - Cross-referenced closure: Closes the spike with a comment linking to the new feature ticket or memo path, so future archaeology always finds the trail. - Use Case: After a timeboxed spike confirms that a caching approach works, run /spike-close --promote 142 to file the production feature ticket and close the spike without lifting prototype code into production. ## Quick Start Ask the assistant to close spike ticket number 142 with the promote option so a follow-up feature ticket is filed and the spike is closed with a cross-reference.
