sp80/.opencode/commands/gsd/gsd-discuss-phase.md

name, description, argument-hint, permissions

name	description	argument-hint	permissions
gsd-discuss-phase	Gather phase context through adaptive questioning before planning	<phase> [--auto]	read write bash glob grep question task mcp__context7__resolve-library-id mcp__context7__query-docs true true true true true true true true true

Extract implementation decisions that downstream agents need — researcher and planner will use CONTEXT.md to know what to investigate and what choices are locked.

How it works:

1. Load prior context (PROJECT.md, REQUIREMENTS.md, STATE.md, prior CONTEXT.md files)
2. Scout codebase for reusable assets and patterns
3. Analyze phase — skip gray areas already decided in prior phases
4. Present remaining gray areas — user selects which to discuss
5. Deep-dive each selected area until satisfied
6. Create CONTEXT.md with decisions that guide research and planning

Output: {phase_num}-CONTEXT.md — decisions clear enough that downstream agents can act without asking the user again

<execution_context> @./.opencode/get-shit-done/workflows/discuss-phase.md @./.opencode/get-shit-done/templates/context.md </execution_context>

Phase number: $ARGUMENTS (required)

Context files are resolved in-workflow using init phase-op and roadmap/state tool calls.

1. Validate phase number (error if missing or not in roadmap) 2. Check if CONTEXT.md exists (offer update/view/skip if yes) 3. **Load prior context** — read PROJECT.md, REQUIREMENTS.md, STATE.md, and all prior CONTEXT.md files 4. **Scout codebase** — Find reusable assets, patterns, and integration points 5. **Analyze phase** — Check prior decisions, skip already-decided areas, generate remaining gray areas 6. **Present gray areas** — Multi-select: which to discuss? Annotate with prior decisions + code context 7. **Deep-dive each area** — 4 questions per area, code-informed options, Context7 for library choices 8. **write CONTEXT.md** — Sections match areas discussed + code_context section 9. Offer next steps (research or plan)

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 (OpenCode handles these):

• Technical implementation
• Architecture choices
• Performance concerns
• Scope expansion

<success_criteria>

• Prior context loaded and applied (no re-asking decided questions)
• 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 </success_criteria>