
gsd-plan-phase
Create detailed phase plan (PLAN.md) with verification loop
- Installs
- 146
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/shoootyou/get-shit-done-multi --skill gsd-plan-phase- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads gsd-plan-phase automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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>FAQ
What does the gsd-plan-phase skill do?
Create detailed phase plan (PLAN.md) with verification loop
How do I install gsd-plan-phase?
Run npx skills add https://github.com/shoootyou/get-shit-done-multi --skill gsd-plan-phase in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/gsd-plan-phase/ (personal) or .claude/skills/gsd-plan-phase/ (project).
Which AI agents can use gsd-plan-phase?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is gsd-plan-phase safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains gsd-plan-phase?
It is published by shoootyou in shoootyou/get-shit-done-multi. It has 146 recorded installs.
More from shoootyou/get-shit-done-multi
get-shit-done
shoootyou/get-shit-done-multi
Structured spec-driven workflow for planning and executing software projects with Claude Code.
gsd-new-project
shoootyou/get-shit-done-multi
Initialize a new project with deep context gathering and PROJECT.md
gsd-audit-milestone
shoootyou/get-shit-done-multi
Audit milestone completion against original intent before archiving
gsd-execute-phase
shoootyou/get-shit-done-multi
Execute all plans in a phase with wave-based parallelization
gsd-map-codebase
shoootyou/get-shit-done-multi
Analyze codebase with parallel mapper agents to produce .planning codebase documents
gsd-verify-work
shoootyou/get-shit-done-multi
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.