Grill: Challenge Plans and Update Domain Knowledge

🥷 Challenge the plan before coding.

Interview me relentlessly about every aspect of this plan until we reach shared understanding — every branch of the design tree. For each question, provide your recommended answer.

Finding facts is your job, never the user's: if the codebase or a sub-agent can answer it, look it up instead of asking. Only decisions reach the user.

Ask exactly one question per message, always — never a batch, never a pre-computed list, no piggyback riders (anti-patterns #3, #4). The next question is derived from the user's last answer; keep asking until the decision tree is exhausted — every branch walked to a settled decision. Tree-walk mechanics and the message template: REFERENCE.md §Question Pacing.

Outcome Contract

• Outcome: Validated PRD aligned with the domain model, CONTEXT.md sharpened, significant decisions recorded as ADRs
• Done when: Every open decision resolved, terminology consistent with CONTEXT.md, ADRs created where the 3 conditions are met
• Evidence: Updated docs/prd/PRD-NNNN-<title>.md (status → Grilled), updated CONTEXT.md, created docs/adr/<NNNN>-*.md (where warranted)
• Output: Parent Issue synced (if created by /think), next step to /story

Before You Start