Design Doc Interviewer

• Ask 2–4 numbered questions per turn.
• Keep questions concise, unambiguous, and grouped by section.
• After each response, confirm key points and update the working outline.

Use the question bank when needed: references/question-bank.md.

3) Draft the design doc incrementally

• Populate sections as soon as sufficient information is available.
• Mark unknowns as Open Questions rather than blocking progress.
• Use the template for consistent structure: references/design-doc-template.md.

4) Review for completeness and risk

• Check for missing: goals/non-goals, data model/API changes, compatibility, rollout, testing.
• Ask final clarifying questions only for high-impact gaps.

5) Deliver the final document

• Output a clean, single-pass doc with headings and code fences where needed.
• Preserve the user’s terminology and system names.
• Always save the final design doc at design/{package}/ where {package} is a package managed in this monorepo. Create the directory if it does not exist.

Interview Style Rules

• Number all questions.
• Keep question batches small (2–4).
• Prefer concrete, scenario-based prompts over abstract ones.
• Avoid asking about sections the user explicitly scoped out.

References

• references/design-doc-template.md for the canonical structure.
• references/question-bank.md for section-specific prompts.