Agent skill
gsd-plan
Create a phased execution plan with fresh-context architecture
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/gsd-plan
SKILL.md
GSD Plan -- Phased Execution Planning
Create a structured, phased plan inspired by GSD (Get Shit Done). Each phase runs in a fresh agent context to prevent context rot.
What To Do
-
Analyze the feature request: Break into atomic phases completable in a single agent session.
-
Create phased plan using TodoWrite with clear inputs/outputs/verification per phase.
-
Write plan files:
.planning/ PROJECT.md -- Feature vision and scope REQUIREMENTS.md -- Acceptance criteria ROADMAP.md -- Phased plan with waves STATE.md -- Progress and decisions -
Plan structure (XML-optimized for Claude):
xml<phase number="1" name="Data Models"> <task type="auto"> <name>Create CandidateProfile model</name> <files>src/backend/Models/CandidateProfile.cs</files> <action>Create domain model with GDPR compliance</action> <verify>dotnet build succeeds</verify> <done>Model compiles with all required properties</done> </task> </phase> -
Wave parallelism: Independent tasks in the same wave run in parallel via Task tool.
Context Rot Prevention
- Each phase executes in a FRESH agent context (via Task tool)
- Orchestrator stays lean -- only tracks STATE.md
- Main context stays under 40% utilization
Arguments
<feature-description>: What to build (natural language)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?