msd-core/commands/gsd/plan-phase.md at bb5b0da78ebc1dbe3afa8fa951ffc54f0432930e

Files

Lex Christopherson 194d1d88bb refactor: slim principles.md and load in core commands

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>

2026-01-14 23:48:44 -06:00

2.3 KiB

Raw Blame History

name, description, argument-hint, allowed-tools

name

description

argument-hint

allowed-tools

gsd:plan-phase

Create detailed execution plan for a phase (PLAN.md)

[phase]

Read

Bash

Write

Glob

Grep

AskUserQuestion

WebFetch

mcp__context7__*

Create executable phase prompt with discovery, context injection, and task breakdown.

Purpose: Break down roadmap phases into concrete, executable PLAN.md files that Claude can execute. Output: One or more PLAN.md files in the phase directory (.planning/phases/XX-name/{phase}-{plan}-PLAN.md)

<execution_context> @~~/.claude/get-shit-done/references/principles.md @~~/.claude/get-shit-done/workflows/plan-phase.md @~~/.claude/get-shit-done/templates/phase-prompt.md @~~/.claude/get-shit-done/references/plan-format.md @~~/.claude/get-shit-done/references/scope-estimation.md @~~/.claude/get-shit-done/references/checkpoints.md @~/.claude/get-shit-done/references/tdd.md </execution_context>

Phase number: $ARGUMENTS (optional - auto-detects next unplanned phase if not provided)

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

Load roadmap: @.planning/ROADMAP.md

Load phase context if exists (created by /gsd:discuss-phase): Check for and read .planning/phases/XX-name/{phase}-CONTEXT.md - contains research findings, clarifications, and decisions from phase discussion.

Load codebase context if exists: Check for .planning/codebase/ and load relevant documents based on phase type.

1. Check .planning/ directory exists (error if not - user should run /gsd:new-project) 2. If phase number provided via $ARGUMENTS, validate it exists in roadmap 3. If no phase number, detect next unplanned phase from roadmap 4. Follow plan-phase.md workflow: - Load project state and accumulated decisions - Perform mandatory discovery (Level 0-3 as appropriate) - Read project history (prior decisions, issues, concerns) - Break phase into tasks - Estimate scope and split into multiple plans if needed - Create PLAN.md file(s) with executable structure

<success_criteria>

One or more PLAN.md files created in .planning/phases/XX-name/
Each plan has: objective, execution_context, context, tasks, verification, success_criteria, output
Tasks are specific enough for Claude to execute
User knows next steps (execute plan or review/adjust) </success_criteria>

2.3 KiB Raw Blame History

2.3 KiB

Raw Blame History