planning

vumichien's avatarfrom vumichien

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

⭐0stars🔀0forks📁View on GitHub🕐Updated Nov 13, 2025⬇️2downloads
[Architecture Design]

When & Why to Use This Skill

This Claude skill facilitates comprehensive technical planning and architecture design for software engineering projects. It enables developers to create scalable, secure, and maintainable implementation roadmaps through deep codebase analysis, research-driven solution design, and detailed task breakdowns, ensuring project success and structural integrity before the coding phase begins.

Use Cases

  • Architecting new system features by analyzing existing codebases and designing scalable, future-proof solutions.
  • Evaluating technical trade-offs between different frameworks or libraries to ensure long-term maintainability and performance.
  • Creating detailed implementation roadmaps and granular task breakdowns for complex engineering projects to guide development teams.
  • Assessing security and performance implications of proposed technical changes to mitigate risks during the design phase.
  • Generating comprehensive technical documentation and system design specifications for stakeholder review and 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

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

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.