spike-close

What problem does it solve?

This Skill prevents “half-shipped” exploration by forcing every spike to end with a clear disposition—either PROMOTE into a production-shaped [Feature] ticket or DISCARD with a lasting memo.

Core Features & Use Cases

• Spike verification before disposition: Confirms the target issue is actually a spike by checking the [Spike] title prefix or the spike label, and warns if it is already closed.
• PROMOTE path (decide + re-launch production work): Collects a production-shaped feature title, scope, and explicitly what is not carried over, then creates a new [Feature] issue and closes the spike with cross-references.
• DISCARD path (document learning): Collects a concise “what we learned” paragraph, derives a stable memo slug, writes a disposition memo to docs/spike-memos/<slug>.md, then closes the spike with a pointer to the memo.
• Use case: After running a time-boxed technical investigation (e.g., a new approach to migrations or an architectural spike), use this to either kick off production delivery or lock in the learning so you don’t re-run the same exploration later.

Quick Start

Run /spike-close with either --promote <spike-ticket-number> or --discard <spike-ticket-number> to disposition the spike through the gate.