Planning

What it does

This skill generates detailed, actionable technical implementation plans to achieve complex goals. It leverages research, codebase analysis, solution design, and comprehensive documentation to create these plans, always adhering to YAGNI, KISS, and DRY principles. The output is a plan file path accompanied by a summary, ensuring the plan is self-contained with necessary context and potentially including code snippets or pseudocode for clarification.

When to use it

This skill is helpful when:

• Planning new feature implementations
• Architecting system designs
• Evaluating technical approaches
• Creating implementation roadmaps
• Breaking down complex requirements
• Assessing technical trade-offs

Key capabilities

• Research and Analysis: Conducts research and analysis, optionally using provided reports.
• Codebase Understanding: Analyzes existing codebases, potentially leveraging pre-existing "scout" reports.
• Solution Design: Creates architectural and implementation designs.
• Plan Organization: Organizes plans with a specific directory structure including research, reports, scout information, the main plan document (plan.md), and phase-specific documents.
• Output Standards: Adheres to defined output standards for clarity and actionability.
• Active Plan Management: Tracks and manages active vs. suggested plans using session state.

Example prompts

• "Create a plan for implementing user authentication."
• "Generate an implementation roadmap for migrating our database."
• "What's the best approach to integrating with the new payment gateway? Create a plan outlining the steps."

Tips & gotchas

• The skill does not implement code; it only creates plans.
• Pay attention to the "Plan:" or "Suggested:" context injected into prompts, as this indicates whether an existing plan should be used or if a new one needs to be created.
• Reports are stored in specific locations depending on whether they relate to an active or suggested plan.