implementation-planning
Installation
SKILL.md
Implementation Planning
Turn an approved requirement or specification into an executable delivery plan. This skill is a planning discipline — it produces a plan, not code, not a spec, and not a lifecycle orchestration.
When to load this skill
Load when the input is an approved requirement, specification, or decision and the task is to produce a concrete delivery plan that accounts for dependencies, sequencing, risk, and verification.
| Trigger | Example |
|---|---|
| An approved SPEC.md or product brief needs a delivery plan | "Plan the implementation for the payments checkout spec" |
| A cross-team or multi-repo feature needs work coordination | "Plan the rollout for the identity-migration change across three services" |
| A data migration needs a staged execution plan | "Plan the schema migration with rollback stages" |
| A risky or high-stakes change needs a rollout strategy | "Plan the staged rollout for the auth-provider replacement" |
| Multiple workstreams need dependency mapping and critical-path analysis | "Map dependencies and critical path for the platform upgrade" |