Files
msd-core/commands/gsd/discuss-milestone.md
Lex Christopherson 508e0c86cd fix: remove enterprise language from help and discuss-milestone
Update user-facing descriptions to reflect vision-focused workflow:
- discuss-phase: captures vision, not constraints/risks
- list-phase-assumptions: see Claude's plan, course-correct vision
- discuss-milestone: features first, not scope/constraints

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-16 08:12:02 -06:00

1.3 KiB

description
description
Gather context for next milestone through adaptive questioning
Help you figure out what to build in the next milestone through collaborative thinking.

Purpose: After completing a milestone, explore what features you want to add, improve, or fix. Features first — scope and phases derive from what you want to build. Output: Context gathered, then routes to /gsd:new-milestone

<execution_context> @~/.claude/get-shit-done/workflows/discuss-milestone.md </execution_context>

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

Load roadmap: @.planning/ROADMAP.md

Load milestones (if exists): @.planning/MILESTONES.md

1. Verify previous milestone complete (or acknowledge active milestone) 2. Present context from previous milestone (accomplishments, phase count) 3. Follow discuss-milestone.md workflow: - Ask: "What do you want to add, improve, or fix?" - Dig into features they mention - Help them articulate what matters most - Present decision gate (ready / ask more / let me add context) 4. Hand off to /gsd:new-milestone with gathered context

<success_criteria>

  • Project state loaded and presented
  • Previous milestone context summarized
  • Milestone scope gathered through adaptive questioning
  • Context handed off to /gsd:new-milestone </success_criteria>