Gsd Plan Phase
- 121 installs
- 21 repo stars
- Updated March 20, 2026
- shoootyou/get-shit-done-multi
gsd-plan-phase is a Get Shit Done Multi agent skill that breaks project phases into atomic PLAN.md execution files for developers practicing spec-driven AI-assisted planning.
About
gsd-plan-phase is a slash command skill in get-shit-done-multi (v2.0.3) that follows optional /gsd-research-phase domain investigation. The gsd-planner agent reads ROADMAP.md, RESEARCH.md, and STATE.md, then decomposes a phase into numbered PLAN.md files (e.g., 01-01-PLAN.md) with YAML frontmatter specifying phase, plan number, wave, depends_on, files_modified, and autonomous flags. Each plan contains an objective and XML task blocks with files, action, verify, and done elements. The installer ships 29 skills and 13 agents to Claude Code, GitHub Copilot CLI, and Codex CLI platforms. Developers run /gsd-plan-phase <phase> after research, review generated plans, then hand off to /gsd-execute-phase for atomic-commit implementation. The repository is archived with upstream migration to gsd-build/get-shit-done.
- gsd-planner reads ROADMAP.md, RESEARCH.md, and STATE.md before task breakdown
- Outputs numbered PLAN.md files with wave, depends_on, and autonomous YAML frontmatter
- Each plan uses XML task blocks: files, action, verify, done elements
- Identifies parallelization via wave grouping and dependency edges between plans
- Part of get-shit-done-multi with 29 skills and 13 agents across 3 AI platforms
Gsd Plan Phase by the numbers
- 121 all-time installs (skills.sh)
- +2 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #1,286 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 27, 2026 (Skillselion catalog sync)
npx skills add https://github.com/shoootyou/get-shit-done-multi --skill gsd-plan-phaseAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 121 |
|---|---|
| repo stars | ★ 21 |
| Last updated | March 20, 2026 |
| Repository | shoootyou/get-shit-done-multi ↗ |
How do you break a project phase into AI-executable plans?
Run /gsd-plan-phase to generate numbered PLAN.md files with wave dependencies from ROADMAP.md and RESEARCH.md.
Who is it for?
Developers using GSD Multi who completed research and need atomic, reviewable task plans before AI execution.
Skip if: Unstructured brainstorming without ROADMAP.md context or teams skipping human plan review before execution.
When should I use this skill?
A developer runs /gsd-plan-phase after research to create executable task plans for an upcoming implementation phase.
What you get
Numbered PLAN.md files with YAML frontmatter, XML task definitions, wave dependency graph, and files_modified lists per plan.
- Numbered PLAN.md files
- Wave dependency graph
- Task XML with verify and done criteria
By the numbers
- get-shit-done-multi v2.0.3 ships 29 skills and 13 specialized agents
- PLAN.md files use YAML frontmatter with wave and depends_on fields for parallel execution
Files
<objective> Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification.
Default flow: Research (if needed) → Plan → Verify → Done
Orchestrator role: Parse arguments, validate phase, research domain (unless skipped), spawn gsd-planner, verify with gsd-plan-checker, iterate until pass or max iterations, present results. </objective>
<execution_context> @{{PLATFORM_ROOT}}/get-shit-done/workflows/plan-phase.md @{{PLATFORM_ROOT}}/get-shit-done/references/ui-brand.md </execution_context>
<context> Phase number: $ARGUMENTS (optional — auto-detects next unplanned phase if omitted)
Flags:
--research— Force re-research even if RESEARCH.md exists--skip-research— Skip research, go straight to planning--gaps— Gap closure mode (reads VERIFICATION.md, skips research)--skip-verify— Skip verification loop--prd <file>— Use a PRD/acceptance criteria file instead of discuss-phase. Parses requirements into CONTEXT.md automatically. Skips discuss-phase entirely.
Normalize phase input in step 2 before any directory lookups. </context>
<process> Execute the plan-phase workflow from @{{PLATFORM_ROOT}}/get-shit-done/workflows/plan-phase.md end-to-end. Preserve all workflow gates (validation, research, planning, verification loop, routing). </process>
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Use gsd-plan-phase for structured phase decomposition; skip to execution only when tasks are already atomic and documented.
FAQ
What inputs does gsd-plan-phase require?
gsd-plan-phase expects ROADMAP.md with phase goals, optionally RESEARCH.md from /gsd-research-phase, and STATE.md tracking current progress. The gsd-planner agent decomposes the requested phase into multiple PLAN.md files.
What is inside a GSD PLAN.md file?
Each PLAN.md has YAML frontmatter with phase, plan number, wave, depends_on, files_modified, and autonomous flags. The body defines an objective and XML task elements containing files to modify, action steps, verify checks, and done criteria.