HE Spike
Run a focused, time-boxed investigation to reduce uncertainty before planning.
When to Use
- •Feasibility is uncertain (new technology, unfamiliar API, unclear constraints)
- •Multiple valid approaches exist and the tradeoffs aren't clear without hands-on exploration
- •The intake spec recommends a spike (fuzzy-idea loop outcome)
- •Risk is high enough that building a throwaway prototype is cheaper than guessing wrong
Inputs
- •
docs/specs/<slug>.md(the intake spec that triggered the spike) - •Specific questions to answer or hypotheses to validate
Spike Contract
- •Define a clear question or hypothesis to validate.
- •Set a time box (default: 2 hours of focused work).
- •Build the minimum throwaway prototype or investigation needed.
- •Document findings — not the prototype code.
- •Spike code is disposable and must not be merged into the main codebase.
When comparing multiple approaches, launch one subagent per approach to explore them concurrently. Each subagent prototypes or researches one option and returns findings. This maximizes coverage within the time box.
Output
- •
docs/specs/<slug>-spike.mdwith:- •Question: What we set out to learn
- •Approach: What we built or investigated
- •Findings: What we learned (with evidence)
- •Recommendation: Which approach to take and why
- •Remaining unknowns: What we still don't know
- •Time spent: Actual vs. budgeted
Exit Gate
- •Spike findings document exists at
docs/specs/<slug>-spike.md - •Original question is answered or explicitly marked as still-unknown with next steps
- •Recommendation is actionable (feeds directly into planning)
- •Docs commit gate passes
Transition Options
Present 2-3 explicit next-step options with a recommended default. Use request_user_input (Codex) or AskUserQuestion (Claude Code) in Plan mode; otherwise ask in chat. Wait for user selection before proceeding.
At least one option must be Next step: he-plan.