Agent skill · magnus919
implementation-planning
Plan the implementation of an approved requirement or specification: produce an executable, dependency-aware delivery plan covering work breakdown, dependency mapping, critical path, ownership, parallelism and sequencing, rollout strategy, rollback and recovery paths, and verification against the original requirement. Supports cross-team, cross-repository, migration, and staged-rollout scenarios. Do not use for pre-approval discovery or needs-finding, authoring a specification from scratch, coding or implementation, the neckbeard issue-to-PR delivery flow itself, or any work whose prerequisite decision has not been approved — planning unapproved work is an explicit stop condition.
What it needs
About 6k tokens when loaded.
What this skill does
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" When not to use Pre-approval discovery or needs-finding — the input is not yet an approved requirement. Route to product-discovery. Authoring a specification from scratch — no approved spec exists yet. Route to spec-driven-development. Coding, implementation, or architecture design — the plan is done, now execute. Route to backend-engineering, frontend-engineering, or software-architecture-analysis. The neckbeard issue-to-PR delivery flow — this skill plans work, it does not execute the neckbeard lifecycle gates, delivery-packet sequencing, or phase orchestration. Delivery execution is a separate concern. The prerequisite decision is not approved — if the requirement or specification has not been approved, stop. Planning unapproved work is an explicit stop condition. Record the missing approval and escalate; do not produce a plan. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/implementation-planning