Research

Deeply understand a problem, its context, and its constraints before thinking about solutions. The output is a structured RESEARCH.md that becomes the primary input for create-prd and create-technical-design.

Rule: Do not propose solutions. Do not sketch architectures. Do not evaluate options. This phase is about understanding — not deciding.

Routing

• Turn research into requirements → /create-prd
• Turn research into architecture → /create-technical-design
• Propose and decide between options → /create-rfc

Process

Step 1 — Intake Interview

Do not read any code or fetch any URLs yet.

Use AskUserQuestion to gather what the user already knows about the problem space. Capture intent from what they have already shared — only ask for what is genuinely missing. Cover: