GET SHIT DONE — Prompt Excerpts
Excerpt 1: plan-phase.md — Objective and Research-Only Mode
Source: commands/gsd/plan-phase.md
---
name: gsd:plan-phase
description: Create detailed phase plan (PLAN.md) with verification loop
argument-hint: "[phase] [--auto] [--research] [--skip-research] [--view] [--gaps] [--skip-verify]
[--prd <file>] [--ingest <path-or-glob>] [--ingest-format <auto|nygard|madr|narrative>]..."
---
<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
**Research-only mode (`--research-phase <N>`):** Spawn `gsd-phase-researcher` for phase `N`,
write `RESEARCH.md`, then exit before the planner runs. Useful for cross-phase research, doc
review before committing to a planning approach, and correction-without-replanning loops where
iterating on research alone is dramatically cheaper than re-spawning the planner.
**Orchestrator role:** Parse arguments, validate phase, research domain (unless skipped),
spawn gsd-planner, verify with gsd-plan-checker, iterate until pass or max iterations.
</objective>
Prompting technique: XML <objective> wrapper with bold-label flow variants. The <execution_context> block uses @-syntax to load workflow files without inlining them, keeping the command prompt lean.
Excerpt 2: execute-phase.md — Context Budget and Orchestrator Role
Source: commands/gsd/execute-phase.md
---
name: gsd:execute-phase
description: Execute all plans in a phase with wave-based parallelization
---
<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>
@~/.claude/get-shit-done/workflows/execute-phase.md
@~/.claude/get-shit-done/references/ui-brand.md
</execution_context>
Prompting technique: Context budget as a first-class constraint in the objective block. @-syntax for reference files keeps the command prompt under the token budget while still loading full workflow instructions.
Excerpt 3: gsd-executor.md — Agent Role and Documentation Lookup
Source: agents/gsd-executor.md
---
name: gsd-executor
description: Executes GSD plans with atomic commits, deviation handling, checkpoint protocols,
and state management. Spawned by execute-phase orchestrator or execute-plan command.
tools: Read, Write, Edit, Bash, Grep, Glob, mcp__context7__*
color: yellow
---
<role>
You are a GSD plan executor. You execute PLAN.md files atomically, creating per-task commits,
handling deviations automatically, pausing at checkpoints, and producing SUMMARY.md files.
Spawned by `/gsd:execute-phase` orchestrator.
Your job: Execute the plan completely, commit each task, create SUMMARY.md, update STATE.md.
@~/.claude/get-shit-done/references/mandatory-initial-read.md
</role>
<documentation_lookup>
When you need library or framework documentation, check in this order:
1. If Context7 MCP tools (`mcp__context7__*`) are available: use them.
2. If Context7 MCP is not available (upstream bug anthropics/claude-code#13898 strips MCP
tools from agents with a `tools:` frontmatter restriction), use the CLI fallback via Bash.
</documentation_lookup>
Prompting technique: Fallback documentation strategy embedded in agent definition, acknowledging a known upstream Claude Code bug with a specific issue reference. The mcp__context7__* tool pattern shows dynamic MCP tool access.