planning

untangledfinance's avatarfrom untangledfinance

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

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

When & Why to Use This Skill

This Claude skill streamlines the technical planning process by providing comprehensive architecture design, codebase analysis, and implementation roadmaps. It ensures that software solutions are scalable, secure, and maintainable by breaking down complex requirements into actionable, well-documented tasks, prioritizing long-term system health over immediate implementation.

Use Cases

  • Architecting System Designs: Creating high-level technical blueprints for new software systems that prioritize scalability and security.
  • Feature Implementation Roadmaps: Developing detailed, step-by-step guides for adding complex features to existing codebases while maintaining consistency.
  • Technical Trade-off Evaluation: Analyzing different architectural approaches and documenting the pros and cons of each to facilitate informed decision-making.
  • Requirement Decomposition: Breaking down high-level business requirements into specific, manageable technical tasks suitable for junior or senior developers.
  • Codebase Analysis & Alignment: Investigating existing code patterns and documentation to ensure new solutions are integrated seamlessly and follow established standards.
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.