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>
2.2 KiB
2.2 KiB
name, description, argument-hint
| name | description | argument-hint |
|---|---|---|
| gsd:discuss-phase | Gather phase context through adaptive questioning before planning | [phase] |
Purpose: Understand HOW the user imagines this phase working — what it looks like, what's essential. You're a thinking partner helping them crystallize their vision, not an interviewer gathering technical requirements.
Output: {phase}-CONTEXT.md capturing the user's vision for the phase
<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>
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 with **ALL questions using AskUserQuestion**: - Present phase from roadmap - Use AskUserQuestion: "How do you imagine this working?" with interpretation options - Use AskUserQuestion to follow their thread — probe what excites them - Use AskUserQuestion to sharpen the core — what's essential for THIS phase - Use AskUserQuestion for decision gate (ready / ask more / let me add context) - Create CONTEXT.md capturing their vision 5. Offer next steps (research or plan the phase)CRITICAL: ALL questions use AskUserQuestion. Never ask inline text questions.
User is the visionary, you are the builder:
- Ask about vision, feel, essential outcomes
- DON'T ask about technical risks (you figure those out)
- DON'T ask about codebase patterns (you read the code)
- DON'T ask about success metrics (too corporate)
- DON'T interrogate about constraints they didn't mention
<success_criteria>
- Phase validated against roadmap
- Vision gathered through collaborative thinking (not interrogation)
- CONTEXT.md captures: how it works, what's essential
- User knows next steps (research or plan the phase) </success_criteria>