planning

Use when you need to plan technical solutions that are scalable, secure, and maintainable.

⭐2stars🔀131forks📁View on GitHub🕐Updated Nov 26, 2025⬇️9downloads

When & Why to Use This Skill

This Claude skill facilitates the creation of robust, scalable, and maintainable technical implementation plans. It bridges the gap between high-level requirements and execution by providing comprehensive system architecture designs, deep codebase analysis, and detailed development roadmaps. By adhering to industry-standard principles like YAGNI, KISS, and DRY, it ensures that technical solutions are optimized for long-term stability and performance.

Use Cases

  • Architecting System Designs: Designing scalable and secure infrastructure for new features or entire software systems.
  • Technical Feasibility & Trade-offs: Evaluating multiple technical approaches and providing a detailed analysis of their pros, cons, and long-term implications.
  • Development Roadmapping: Breaking down complex business requirements into actionable, step-by-step technical tasks and documentation for engineering teams.
  • Codebase Integration Planning: Analyzing existing code patterns and dependencies to ensure new solutions are consistent and maintainable.
  • Security & Performance Auditing: Researching and planning technical solutions that specifically address high-load performance requirements and security vulnerabilities.
nameplanning
descriptionUse when you need to plan technical solutions that are scalable, secure, and maintainable.
licenseMIT

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.