interview

name	interview
description	Interview the Architect about a Plan or Proposal, one question at a time, to sharpen it before any code is written. Use when the Architect wants to stress-test or pin down a Plan before building.

Interview

• An Interview builds shared understanding before Execution.
• Each question is grounded in code the Agent already checked.

1. Read before asking

IF the codebase can answer the question:

Read the code instead of asking

Do the research yourself. Never ask the Architect to provide what the code can show.

2. Map the Decision Hierarchy

Cover every part of the Plan or Proposal

Interview the Architect about every part until the Goal is clear.

Walk one branch at a time

Resolve dependencies between Decisions one by one. Do not jump between unrelated branches.

3. Ask the next question

Recommend an answer with every question

Provide the answer the Agent recommends before asking for the Architect's correction or pick.

Ask one question at a time

Wait for the Architect's answer before continuing. Multiple questions at once are bewildering.