specify: Goal → Requirements via Systematic Interview

Overview

Transform a vague goal into structured, traceable requirements through: 0. WHERE Grounding — establish project type, situation, ambition, and risk modifiers 0.5. Context Research (brownfield only) — scan existing codebase before asking the user

Interview — systematic Q&A across Business/Interaction/Tech axes (depth-calibrated by WHERE)
Extract — parallel requirements extraction by domain experts
Cross-check — conflict/gap/duplicate detection
Confirmation — user accepts assumptions + final requirements.md committed in cli format

Handoff contract

The final deliverable is <spec_dir>/requirements.md in the format that /blueprint consumes:

Frontmatter: type (greenfield|feature|refactor|bugfix), goal, non_goals[]
Body: flat list of ## R-X<num>: parent requirements, each with nested #### R-X<num>.Y: sub-requirements carrying given/when/then
X in the ID is axis code: B=Business, U=Interaction (user), T=Tech
Optional ## Open Decisions section with ### OD-N: blocks