spec-plan

Interview the user relentlessly about every aspect of a plan until reaching shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one.

When to Use

• User wants to stress-test a plan or design
• User says "grill me" or "poke holes in this"
• Before running issue-to-prd — spec-plan resolves ambiguity, issue-to-prd structures the output
• Complex feature with many interacting decisions that need to be resolved sequentially

When NOT to Use

• Requirements are already clear and documented — go straight to issue-to-prd
• User just wants a quick opinion, not a deep interview
• Implementation is already underway