Files
get-shit-done/commands/gsd/discuss-phase.md
Lex Christopherson 1fe3fa427e Initial commit: Get Shit Done - meta-prompting system for Claude Code
- NPX install: npx get-shit-done-cc
- Slash commands for project management
- Context engineering templates and workflows

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-15 07:44:41 -06:00

1.6 KiB

description, argument-hint
description argument-hint
Gather phase context through adaptive questioning before planning [phase]
Use adaptive questioning to gather comprehensive phase context before planning.

Purpose: Build deep understanding of objectives, constraints, risks, success indicators, and codebase state through structured intake flow. Creates CONTEXT.md file that informs high-quality planning. Output: {phase}-CONTEXT.md in phase directory with complete context documentation

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

Phase number: $ARGUMENTS (required)

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

Load roadmap: @.planning/ROADMAP.md

1. Validate phase number argument (error if missing or invalid) 2. Check if phase exists in roadmap 3. Check if CONTEXT.md already exists (offer to update if yes) 4. Follow discuss-phase.md workflow: - Present initial context from roadmap - Analyze gaps in: objectives, constraints, risks, success indicators, codebase context - Ask 2-4 questions about genuine gaps (skip what roadmap provides) - Present decision gate (ready / ask more / let me add context) - Create CONTEXT.md using template 5. Offer next steps (typically: plan the phase)

<success_criteria>

  • Phase validated against roadmap
  • Context gathered through adaptive questioning
  • CONTEXT.md created in phase directory
  • User knows next steps (plan phase, review context, or done) </success_criteria>