dev.exec-plan_skill

Overview

This skill creates structured, file-based execution plans for complex development tasks that need persistent documentation and clear technical direction. It is tailored for architectural decisions, multi-phase implementations, integration work, and any request that explicitly asks for a documented execution plan. The output is organized so teams can track milestones, decisions, dependencies, and risks over the lifetime of the project.

How this skill works

The skill generates a markdown execution plan in a designated directory (default: docs/project/specs/active) using a standard template. It assembles Goal, Context, Technical Approach, Steps, Dependencies, Risks & Mitigations, and Questions, and optionally suggests a branch name if the user requests a new branch. After creation, the skill reviews the plan for simplification opportunities and records any simplifications in the plan notes.

When to use it

• When architectural or design decisions must be recorded and justified
• For projects with multiple phases, milestones, or long timelines
• When external APIs, services, or integrations require research and documentation
• If the user explicitly requests a documented execution or project plan
• When task complexity exceeds a simple 3–5 step todo list

Best practices

• Place plan files in docs/project/specs/active following {YYYY-MM-DD}-{title-in-kebab-case}.md naming
• Break work into clear milestones and list dependencies between steps
• Document unanswered questions and require user confirmation before proceeding with implementation
• Keep plans concise and update them as decisions are made or scope changes
• If the plan is very complex, split it into related sub-plans and cross-reference them

Example use cases

• Designing a new microservice with API contracts, data schema, and deployment strategy
• Planning a phased migration to a third-party service that requires credential setup and testing
• Creating an integration plan for an external payment gateway with fallback and monitoring requirements
• Preparing a multi-release feature rollout with toggles, DB migrations, and backward compatibility checks