mcpField
G
gsd-discuss-phase

gsd-discuss-phase

github.com/shoootyouAgent workflows22120 installsUpdated 32w ago
Repository

About gsd-discuss-phase

gsd-discuss-phase guides a user through clarifying a roadmap phase and records implementation decisions in a CONTEXT.md file for downstream research and planning agents. It keeps discussion within the phase’s fixed scope and captures deferred ideas separately.

Key features

  1. 01Phase-specific gray-area analysis
  2. 02User-selected discussion topics
  3. 03Four-question deep dives per topic
  4. 04Writes a phase CONTEXT.md
  5. 05Records out-of-scope ideas for later

Use cases

  1. 01Clarifying UI or behavior decisions before planning
  2. 02Preparing a phase for downstream research
  3. 03Updating an existing phase context file

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/shoootyou/get-shit-done-multi --skill gsd-discuss-phase

After installing, type/gsd-discuss-phasein Claude Code to confirm it loaded.

Details

From the project README
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. Analyze the phase to identify gray areas (UI, UX, behavior, etc.)
  2. Present gray areas — user selects which to discuss
  3. Deep-dive each selected area until satisfied
  4. 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> @{{PLATFORM_ROOT}}/get-shit-done/workflows/discuss-phase.md @{{PLATFORM_ROOT}}/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. **Analyze phase** — Identify domain and generate phase-specific gray areas 4. **Present gray areas** — Multi-select: which to discuss? (NO skip option) 5. **Deep-dive each area** — 4 questions per area, then offer more/next 6. **Write CONTEXT.md** — Sections match areas discussed 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

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

<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>

Comments

Markdown supported