interview-me
Interview Me
Turn a raw request into a spec-ready decision record that to-prd can turn into a PRD without reopening requirements. A material decision is spec-ready only when the user confirmed it, --auto settled it from supplied scope and evidence, or it is out of scope. A default may settle only a nonmaterial uncertainty.
The output is .ai-workflow/work/<feature-slug>/decision-record.md: status draft while the interview is open, ready-for-prd when the frontier is empty. Reuse an existing slug.
Modes
Manual mode is the default: you ask the user, and no other model runs. --auto is opt-in; silence does not select it. It runs an interviewer and a respondent on other models, as references/auto-mode.md describes. models-consensus runs only on an explicit request, never as a routine escalation.
Work
- Ground the interview in the relevant code, tests, glossary, and earlier ADRs. Existing decisions are already decided. Bring repository facts to the user rather than asking what exploration can answer: the user's time is the bottleneck.
- Build the design tree. The frontier holds only decisions whose prerequisites are settled. Cover actors and access, user outcomes and failure cases, data and integrations, scope limits, rollout and rollback, and broad design choices that change the product's shape. Security questions are frontier questions; use
security-gatefor an exposed surface. When a broad lens can change a frontier decision, apply it here asshared/references/workflow-stage-routing.mddescribes. - Ask one round. Ask five independent frontier questions when five exist, in one numbered plain-text batch if a question tool allows fewer; ask fewer only when fewer exist. Never more than five, and never a second request in the same turn. Each question carries its repository basis and a recommended answer. A dependent question waits for the next round.
- Record on settle. Give each decision a stable ID (
D1,D2, …) that survives into the PRD and tasks, and write each answer, default, or descoped item into the record as it settles. When a term becomes canonical, update the glossary. For an architectural decision apply all three or no ADR: hard to reverse, surprising without context, and a real trade-off. Write a qualifying ADR fromarchitecture-lens/references/adr-template.md, matching any existingdocs/adr/naming. - Recompute the frontier after every answer batch. When only running code can settle a decision that changes the PRD, use
to-prototypeand record its answer. Never prototype a fact the repository already answers. - Finish when every branch ends in a confirmed decision, an evidence-based automatic answer, a nonmaterial default, or an explicit out-of-scope line.