get-shit-done/commands/gsd/discuss-phase.md at a7249ebe83dfed8a2fcb08970fe2f6b3fdf11766

mirror of https://github.com/glittercowboy/get-shit-done synced 2026-04-25 17:25:23 +02:00

Files

Lex Christopherson a7249ebe83 feat(discuss-phase): intelligent gray area analysis with scope guardrails

- Analyze phase to identify gray areas by category (UI, UX, Behavior, etc.)
- Present multi-select for user to choose which areas to discuss
- Deep-dive each selected area with focused questioning loop
- Explicit scope guardrail: clarify HOW, never expand WHAT
- Capture deferred ideas without acting on them
- Downstream awareness: CONTEXT.md feeds researcher and planner agents
- Template restructured for decisions (domain, decisions, discretion, deferred)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-16 10:11:17 -06:00

2.7 KiB

Raw Blame History

name, description, argument-hint, allowed-tools

name

description

argument-hint

allowed-tools

gsd:discuss-phase

Gather phase context through adaptive questioning before planning

<phase>

Read

Write

Bash

Glob

Grep

AskUserQuestion

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:

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

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

Phase number: $ARGUMENTS (required)

Load project state: @.planning/STATE.md

Load roadmap: @.planning/ROADMAP.md

1. Validate phase number (error if missing or not in roadmap) 2. Check if CONTEXT.md exists (offer update/view/skip if yes) 3. **Analyze phase** — Identify domain boundary and gray areas by category 4. **Present gray areas** — Multi-select AskUserQuestion: which to discuss? 5. **Deep-dive each area** — Loop per area until user says "move on" 6. **Write CONTEXT.md** — Structured by decisions made 7. 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

Gray area categories (use what's relevant):

UI — Layout, visual presentation, information density
UX — Interactions, flows, feedback
Behavior — Runtime behavior, state changes
Empty/Edge States — What shows in unusual situations
Content — What information is shown/hidden

Do NOT ask about (downstream agents handle these):

Technical implementation (researcher investigates)
Architecture choices (planner decides)
Performance concerns (researcher/planner handle)
Scope expansion (roadmap defines scope)

<success_criteria>

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>

2.7 KiB Raw Blame History

2.7 KiB

Raw Blame History