planning

The planning skill acts as an architectural design and strategic roadmap engine for technical teams. It is designed for developers and system architects who need to navigate complex requirements, perform deep codebase analysis, and ensure that new implementations align with existing architectural patterns and long-term project goals. By adhering to YAGNI, KISS, and DRY principles, the skill ensures that proposed technical solutions prioritize simplicity, security, and maintainability over unnecessary complexity.

• Performs automated codebase analysis and research via researcher and scout sub-agents.

• Facilitates systematic solution design, including architecture diagrams, API schemas, and component breakdown.

• Maintains project consistency by referencing defined development rules and project-specific technical documentation.

• Integrates with local file systems to track active plan states and ensure version control for planning artifacts.

• Generates comprehensive documentation in standardized directories, including research reports, phase-specific implementation steps, and architectural trade-off assessments.

• Users should provide initial requirements, existing codebase context, and specific constraints to generate optimal plans.

• The output includes structured plan directories containing research, design, and step-by-step implementation roadmaps.

• Avoids code implementation; instead, it provides detailed pseudocode, logic flows, and task breakdowns ready for developer execution.

• Always check for existing active plans in the project root to prevent configuration drift and version proliferation.

• Leverages project-specific tools, such as indices and rule files (e.g., development-rules.md), to ensure plans remain strictly within project standards.

• Highly effective for feature development, system refactoring, technical debt reduction, and evaluating the impact of new dependencies or framework migrations.