Gsd Execute Phase
- 105 installs
- 21 repo stars
- Updated March 20, 2026
- shoootyou/get-shit-done-multi
gsd-execute-phase is a Get Shit Done Multi agent skill that executes approved PLAN.md task files with atomic git commits and fresh context for developers running spec-driven AI-assisted implementation.
About
gsd-execute-phase is a slash command skill in get-shit-done-multi (v2.0.3), part of an installer deploying 29 skills and 13 agents across Claude Code, GitHub Copilot CLI, and Codex CLI. After /gsd-plan-phase produces PLAN.md files with YAML frontmatter (phase, plan, wave, depends_on, autonomous flags), gsd-execute-phase spawns gsd-executor agents that follow task XML blocks precisely, make atomic git commits per task, and create SUMMARY.md when each plan finishes. Plans in the same wave execute in parallel; dependency edges enforce order. Human verification and decision checkpoints pause execution until approved. Developers invoke /gsd-execute-phase <phase> once plans are reviewed, producing code changes plus SUMMARY.md artifacts before /gsd-verify-phase goal-backward checking. Note: the fork is archived with features merged upstream to gsd-build/get-shit-done.
- Executes PLAN.md files spawned by gsd-executor with atomic git commits per task
- Runs parallel plan waves based on depends_on YAML frontmatter fields
- Writes SUMMARY.md after each completed plan in .planning/ phase directories
- Pauses at human verification and decision checkpoints during execution
- Part of get-shit-done-multi deploying 29 skills and 13 agents (v2.0.3)
Gsd Execute Phase by the numbers
- 105 all-time installs (skills.sh)
- +1 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #1,341 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-execute-phaseAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 105 |
|---|---|
| repo stars | ★ 21 |
| Last updated | March 20, 2026 |
| Repository | shoootyou/get-shit-done-multi ↗ |
How do you execute AI coding plans with atomic commits?
Run /gsd-execute-phase to implement PLAN.md tasks with atomic git commits and SUMMARY.md reports in a spec-driven project.
Who is it for?
Developers using GSD Multi who have approved PLAN.md files and want autonomous per-plan execution with clean git history.
Skip if: Ad-hoc coding without a ROADMAP.md and PLAN.md structure, or teams not using the GSD spec-driven workflow.
When should I use this skill?
A developer runs /gsd-execute-phase after planning is approved and wants executor agents to implement tasks with atomic commits.
What you get
Implemented code changes, per-task git commits, SUMMARY.md files per plan, and checkpoint pauses for human verification.
- Code implementation
- Atomic git commits
- SUMMARY.md per plan
By the numbers
- get-shit-done-multi v2.0.3 deploys 29 skills and 13 specialized agents
- Requires Node.js 20+; supports Claude Code, GitHub Copilot CLI, and Codex CLI
Files
<objective> Execute all plans in a phase using wave-based parallel execution.
Orchestrator stays lean: discover plans, analyze dependencies, group into waves, spawn subagents, collect results. Each subagent loads the full execute-plan context and handles its own plan.
Context budget: ~15% orchestrator, 100% fresh per subagent. </objective>
<execution_context> @{{PLATFORM_ROOT}}/get-shit-done/workflows/execute-phase.md @{{PLATFORM_ROOT}}/get-shit-done/references/ui-brand.md </execution_context>
<context> Phase: $ARGUMENTS
Flags:
--gaps-only— Execute only gap closure plans (plans withgap_closure: truein frontmatter). Use after verify-work creates fix plans.
Context files are resolved inside the workflow via gsd-tools init execute-phase and per-subagent <files_to_read> blocks. </context>
<process> Execute the execute-phase workflow from @{{PLATFORM_ROOT}}/get-shit-done/workflows/execute-phase.md end-to-end. Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, 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-execute-phase after gsd-plan-phase for structured execution; avoid it for unstructured one-off coding without PLAN.md artifacts.
FAQ
What does gsd-execute-phase produce after running?
gsd-execute-phase produces code changes with atomic git commits per task, plus SUMMARY.md files documenting what each plan built. Execution respects wave dependencies in PLAN.md YAML frontmatter and pauses at human checkpoints.
Can gsd-execute-phase run plans in parallel?
gsd-execute-phase runs plans in the same wave in parallel when depends_on is empty or satisfied. The gsd-executor agent handles one PLAN.md at a time, following task XML with files, action, verify, and done blocks.