How it works:
- Analyze the phase to identify gray areas (UI, UX, behavior, etc.)
- Present gray areas — user selects which to discuss
- Deep-dive each selected area until satisfied
- Create CONTEXT.md with decisions that guide research and planning
Output: {phase}-CONTEXT.md — decisions clear enough that downstream agents can act without asking the user again
Load project state:
@.planning/STATE.md
Load roadmap:
@.planning/ROADMAP.md
CRITICAL: Scope guardrail
- Phase boundary from ROADMAP.md is FIXED
- Discussion clarifies HOW to implement, not WHETHER to add more
- If user suggests new capabilities: "That's its own phase. I'll note it for later."
- Capture deferred ideas — don't lose them, don't act on them
Domain-aware gray areas:
Gray areas depend on what's being built. Analyze the phase goal:
- Something users SEE → layout, density, interactions, states
- Something users CALL → responses, errors, auth, versioning
- Something users RUN → output format, flags, modes, error handling
- Something users READ → structure, tone, depth, flow
- Something being ORGANIZED → criteria, grouping, naming, exceptions
Generate 3-4 phase-specific gray areas, not generic categories.
Probing depth:
- Ask 4 questions per area before checking
- "More questions about [area], or move to next?"
- If more → ask 4 more, check again
- After all areas → "Ready to create context?"
Do NOT ask about (Claude handles these):
- Technical implementation
- Architecture choices
- Performance concerns
- Scope expansion
- Gray areas identified through intelligent analysis
- User chose which areas to discuss
- Each selected area explored until satisfied
- Scope creep redirected to deferred ideas
- CONTEXT.md captures decisions, not vague vision
- User knows next steps
1---2name: kata-discuss-phase3description: Gather phase context through adaptive questioning before planning, clarifying implementation decisions, or exploring gray areas for a phase. Triggers include "discuss phase", "clarify phase", "gather context", "what are the gray areas", and "phase discussion".4---56<objective>7Extract implementation decisions that downstream agents need — researcher and planner will use CONTEXT.md to know what to investigate and what choices are locked.89**How it works:**10111. Analyze the phase to identify gray areas (UI, UX, behavior, etc.)122. Present gray areas — user selects which to discuss133. Deep-dive each selected area until satisfied144. Create CONTEXT.md with decisions that guide research and planning1516**Output:** `{phase}-CONTEXT.md` — decisions clear enough that downstream agents can act without asking the user again17</objective>1819<execution_context>20@./references/phase-discuss.md21@./references/context-template.md22</execution_context>2324<context>25Phase number: $ARGUMENTS (required)2627**Load project state:**28@.planning/STATE.md2930**Load roadmap:**31@.planning/ROADMAP.md32</context>3334<process>351. Validate phase number (error if missing or not in roadmap)362. Check if CONTEXT.md exists (offer update/view/skip if yes)373. **Analyze phase** — Identify domain and generate phase-specific gray areas384. **Present gray areas** — Multi-select: which to discuss? (NO skip option)395. **Deep-dive each area** — 4 questions per area, then offer more/next406. **Write CONTEXT.md** — Sections match areas discussed417. Offer next steps (research or plan)4243**CRITICAL: Scope guardrail**4445- Phase boundary from ROADMAP.md is FIXED46- Discussion clarifies HOW to implement, not WHETHER to add more47- If user suggests new capabilities: "That's its own phase. I'll note it for later."48- Capture deferred ideas — don't lose them, don't act on them4950**Domain-aware gray areas:**51Gray areas depend on what's being built. Analyze the phase goal:5253- Something users SEE → layout, density, interactions, states54- Something users CALL → responses, errors, auth, versioning55- Something users RUN → output format, flags, modes, error handling56- Something users READ → structure, tone, depth, flow57- Something being ORGANIZED → criteria, grouping, naming, exceptions5859Generate 3-4 **phase-specific** gray areas, not generic categories.6061**Probing depth:**6263- Ask 4 questions per area before checking64- "More questions about [area], or move to next?"65- If more → ask 4 more, check again66- After all areas → "Ready to create context?"6768**Do NOT ask about (Claude handles these):**6970- Technical implementation71- Architecture choices72- Performance concerns73- Scope expansion74 </process>7576<success_criteria>7778- Gray areas identified through intelligent analysis79- User chose which areas to discuss80- Each selected area explored until satisfied81- Scope creep redirected to deferred ideas82- CONTEXT.md captures decisions, not vague vision83- User knows next steps84 </success_criteria>
gannonh