planning

Tietve's avatarfrom Tietve

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

⭐0stars🔀0forks📁View on GitHub🕐Updated Nov 15, 2025
[Architecture Design]

When & Why to Use This Skill

This Claude skill streamlines technical planning by providing a structured framework for architecting scalable, secure, and maintainable software solutions. It facilitates deep codebase analysis, research-driven design, and the creation of comprehensive implementation roadmaps, ensuring that complex requirements are broken down into actionable, high-quality technical documentation to guide successful development.

Use Cases

  • Architecting new system designs for complex features to ensure long-term scalability and security compliance.
  • Evaluating multiple technical approaches and performing trade-off analysis to identify the most efficient solution before coding begins.
  • Creating detailed implementation roadmaps and granular task breakdowns that provide clear direction for development teams.
  • Conducting deep codebase research and analysis to ensure new solutions align with existing architectural patterns and principles.
  • Generating comprehensive technical documentation including research reports, design specifications, and pseudocode for better project alignment.
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

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.