1fe3fa427e
- 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>
2.0 KiB
2.0 KiB
description, argument-hint, allowed-tools
| description | argument-hint | allowed-tools | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Create detailed execution plan for a phase (PLAN.md) | [phase] |
|
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/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/cli-automation.md
</execution_context>
Load project state first: @.planning/STATE.md
Load roadmap: @.planning/ROADMAP.md
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>