clairem0 Interview
Clarify the decisions needed to choose a direction or create the next artifact.
- Read relevant context first. Investigate anything answerable from files, code, history, or prior decisions instead of asking the user.
- Ask one decision-driving question at a time. Include your recommended answer and why.
- Pressure-test assumptions that drive scope or complexity. Surface contradictions, stale guidance, reusable seams, and simpler directions.
- Reflect decisions back as they settle. Continue until remaining ambiguity would not materially change the next step.
- End with a concise decision recap. If requested, capture it in the natural PRD, work plan, or specification without replacing useful existing context. Before writing sensitive context, verify that the destination is private or explicitly approved.