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 it is confirmed or out of scope. An explicit default is allowed only for a nonmaterial uncertainty.
Boundary
Receive a feature request, an earlier exploration, and repository facts. Produce .ai-workflow/work/<feature-slug>/decision-record.md with status draft while the interview is open and ready-for-prd when the frontier is empty.
Read shared/references/workflow-stage-routing.md before the interview. It names the few broad lenses that can change an early question. Use one relevant broad lens at a time when it changes a decision. Run another only when the first result exposes a necessary later decision. Use security-gate for an exposed security surface. Use to-prototype only when running code is the smallest reversible move that can settle a decision.
Do not call design-gate, test-lens, a practice skill, a panel, a runner, or models-consensus. If the user explicitly wants additional opinions, direct them to invoke models-consensus; its own workflow presents the proposed seats for user approval before it runs.
This step ends at the decision record. to-prd writes the draft PRD. Do not plan files, create tasks, or implement code.
Work
-
Ground the interview in the relevant code, tests, domain glossary, and earlier architecture decisions. Existing decisions are already decided. Bring repository facts to the user instead of asking questions that exploration can answer. The user's time is the bottleneck.
-
Build the design tree. The frontier contains only user decisions whose prerequisites are settled. Cover actors and access, user outcomes and failure cases, data and integrations, explicit scope limits, rollout or rollback, and broad design choices that change the product shape. Security questions count as frontier questions.