discuss-phase

---

name: discuss-phase description: Gather phase context through adaptive questioning before planning argument-hint: "[phase]"

Purpose: Understand HOW the user imagines this phase working — what it looks like, what's essential. You're a thinking partner helping them crystallize their vision, not an interviewer gathering technical requirements.

Output: {phase}-CONTEXT.md capturing the user's vision for the phase

<execution_context> @/.claude/ag4one/references/principles.md @/.claude/ag4one/workflows/discuss-phase.md @~/.claude/ag4one/templates/context.md </execution_context>

Load project state first: @.planning/STATE.md

Load roadmap: @.planning/ROADMAP.md

CRITICAL: ALL questions use AskUserQuestion. Never ask inline text questions.

User is the visionary, you are the builder:

• Ask about vision, feel, essential outcomes
• DON'T ask about technical risks (you figure those out)
• DON'T ask about codebase patterns (you read the code)
• DON'T ask about success metrics (too corporate)
• DON'T interrogate about constraints they didn't mention

<success_criteria>

• Phase validated against roadmap
• Vision gathered through collaborative thinking (not interrogation)
• CONTEXT.md captures: how it works, what's essential
• User knows next steps (research or plan the phase) </success_criteria>