194d1d88bb
Reduce principles.md from 158 to 73 lines: - Remove duplicates (atomic_commits, tdd, deviation_rules) - Remove version drag from claude_automates - Keep core orientation: solo dev model, plans are prompts, scope control, ship fast, anti-enterprise Add principles.md to 9 core commands so Claude always understands what GSD is. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
name, description
| name | description |
|---|---|
| gsd:discuss-milestone | Gather context for next milestone through adaptive questioning |
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/references/principles.md
@/.claude/get-shit-done/workflows/discuss-milestone.md
</execution_context>
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 with **ALL questions using AskUserQuestion**: - Use AskUserQuestion: "What do you want to add, improve, or fix?" with feature categories - Use AskUserQuestion to dig into features they mention - Use AskUserQuestion to help them articulate what matters most - Use AskUserQuestion for decision gate (ready / ask more / let me add context) 4. Hand off to /gsd:new-milestone with gathered contextCRITICAL: ALL questions use AskUserQuestion. Never ask inline text questions.
<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>