Contextualize

Reach shared understanding with the user of the problem and its surroundings, then record that understanding so create-prd, create-technical-design, and create-implementation-plan can consume it without re-interviewing. The output is a structured CONTEXT.md file.

Shared understanding means: if you and the user were each asked separately to describe the problem, the constraints, and what already exists, your accounts would match. The interview is not over until that is true.

Rule: gather understanding, not decisions. Do not define success, propose solutions, sketch architectures, prioritize, or set scope — those belong to downstream skills. Capture the world as it is, not what it should become.

Routing

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

Interview Discipline

Interview the user relentlessly until you reach shared understanding. There is no pre-defined script — at every turn you decide what to ask next based on what is still unclear. Apply the five rules below throughout.