mcpField
P
planning

planning

github.com/samhvw8Development11109 installsUpdated 49w ago
Repository

About planning

A skill for creating technical implementation plans through research, codebase analysis, solution design, and documentation. It is intended for developers evaluating approaches or breaking complex requirements into actionable work, without implementing code.

Key features

  1. 01Research technical approaches
  2. 02Analyze the existing codebase
  3. 03Design solution architectures
  4. 04Organize implementation plans
  5. 05Break work into tasks
  6. 06Document trade-offs and context

Use cases

  1. 01Planning a new feature
  2. 02Comparing technical approaches
  3. 03Designing a system architecture
  4. 04Turning complex requirements into a roadmap

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/samhvw8/dot-claude --skill planning

After installing, type/planningin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
codebase-understanding.md
output-standards.md
plan-organization.md
research-phase.md
solution-design.md

Details

From the project README

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.

Comments

Markdown supported