planning · samhvw8 — Claude Code skill: implementation plans and setup
The planning skill examines a codebase and drafts a technical plan with architecture, phases, and task breakdowns. Use it before building a feature or changing a system.
MIT 109 installs ★ 12 updated 2025-12-09
npx skills add samhvw8/dot-claude --skill planning -a claude-codeWhat planning does
The skill studies the project, investigates possible approaches, and writes an implementation plan. Depending on the task, the document can include architecture, work phases, pseudocode, and trade-offs. It does not implement changes; it returns the plan file path and a summary.
Its workflow moves from context gathering and research to synthesis, design, and review. Instructions for these stages live under references/, while plans go in plans/. Existing researcher or scout reports let the skill skip the matching research or codebase review stage.
Plans must follow ./docs/development-rules.md and fit existing codebase patterns. Make sure that file is available from the repository root before asking for a plan.
What it helps with
- turn feature requirements into implementation phases
- weigh technical approaches and their trade-offs
- outline an architecture for a new component
- map work against an existing codebase
Example prompts for the agent
- Draft an implementation plan for a new feature in this project and save it under
plans/. - Review the codebase and propose an architecture for a new component without editing files.
- Break these requirements into phases and compare the available approaches.
How to install planning
1Skills CLI (Vercel)
npx skills add samhvw8/dot-claude --skill planning -a claude-code2Manually: put the files in place
~/.claude/skills/planning/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/planning/
1Skills CLI (Vercel)
npx skills add samhvw8/dot-claude --skill planning -a codex2Manually: put the files in place
.agents/skills/planning/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add samhvw8/dot-claude --skill planning -a cursor2Manually: put the files in place
.cursor/skills/planning/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install samhvw8/dot-claude skills/planning2Manually: put the files in place
.github/skills/planning/SKILL.md1Skills CLI (Vercel)
npx skills add samhvw8/dot-claude --skill planning -a gemini-cli2Platform CLI
gemini skills install https://github.com/samhvw8/dot-claude --path skills/planningManually: put the files in place
.devin/skills/planning/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add samhvw8/dot-claude --skill planning -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about planning
How do I install planning in Claude Code?
Run npx skills add samhvw8/dot-claude --skill planning -a claude-code. The skill file is available at ~/.claude/skills/planning/SKILL.md.
What does the planning skill do?
It examines a project, evaluates possible solutions, and produces a detailed implementation plan. It does not write the implementation.
Does planning account for project-specific development rules?
Yes. Its plans must respect ./docs/development-rules.md and follow patterns found in the codebase.
Source text
SKILL.md · MIT
---
name: planning
description: "Technical implementation planning and architecture design. Capabilities: feature planning, system architecture, technical evaluation, implementation roadmaps, requirement breakdown, trade-off analysis, codebase analysis, solution design. Actions: plan, architect, design, evaluate, breakdown technical solutions. Keywords: implementation plan, technical design, architecture, system design, roadmap, requirements analysis, trade-offs, technical evaluation, feature planning, solution design, scalability, security, maintainability, sprint planning, task breakdown. Use when: planning new features, designing system architecture, evaluating technical approaches, creating implementation roadmaps, breaking down complex requirements, assessing technical trade-offs."
license: MIT
---
# Planning
Create detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.
## When to Use
Use this skill when:
- Planning new feature implementations
- Architecting system designs
- Evaluating technical approaches
- Creating implementation roadmaps
- Breaking down complex requirements
- Assessing technical trade-offs
## Core Responsibilities & Rules
Always honoring **YAGNI**, **KISS**, and **DRY** principles.
**Be honest, be brutal, straight to the point, and be concise.**
### 1. Research & Analysis
Load: `references/research-phase.md`
**Skip if:** Provided with researcher reports
### 2. Codebase Understanding
Load: `references/codebase-understanding.md`
**Skip if:** Provided with scout reports
### 3. Solution Design
Load: `references/solution-design.md`
### 4. Plan Creation & Organization
Load: `references/plan-organization.md`
### 5. Task Breakdown & Output Standards
Load: `references/output-standards.md`
## Workflow Process
1. **Initial Analysis** → Read codebase docs, understand context
2. **Research Phase** → Spawn researchers, investigate approaches
3. **Synthesis** → Analyze reports, identify optimal solution
4. **Design Phase** → Create architecture, implementation design
5. **Plan Documentation** → Write comprehensive plan
6. **Review & Refine** → Ensure completeness, clarity, actionability
## Output Requirements
- DO NOT implement code - only create plans
- Respond with plan file path and summary
- Ensure self-contained plans with necessary context
- Include code snippets/pseudocode when clarifying
- Provide multiple options with trade-offs when appropriate
- Fully respect the `./docs/development-rules.md` file.
**Plan Directory Structure**
```
plans/
└── YYYYMMDD-HHmm-plan-name/
├── research/
│ ├── researcher-XX-report.md
│ └── ...
├── reports/
│ ├── XX-report.md
│ └── ...
├── scout/
│ ├── scout-XX-report.md
│ └── ...
├── plan.md
├── phase-XX-phase-name-here.md
└── ...
```
## Quality Standards
- Be thorough and specific
- Consider long-term maintainability
- Research thoroughly when uncertain
- Address security and performance concerns
- Make plans detailed enough for junior developers
- Validate against existing codebase patterns
**Remember:** Plan quality determines implementation success. Be comprehensive and consider all solution aspects.
© samhvw8 · MIT · samhvw8/dot-claude
Similar skills
All skills for Agent setup: memory, context, orchestration →planning by other authors comes first.