Implementation Planning

Produce deep technical implementation plans for complex engineering work.

This skill is primarily for the planner agent after it has already gathered enough context to plan responsibly. It is not the default planning path for every task. Small and medium tasks should usually stay inside the planner's normal workflow without invoking this heavier protocol.

Outputs

• A complexity decision: stay with normal planning or enter a deep implementation-planning pass
• A scoped planning contract: goal, constraints, non-goals, assumptions, and success criteria
• A scope-challenge pass that checks whether the current ask is too large, too vague, or more complex than it needs to be
• A structured implementation plan with phases, dependencies, touched files or components, verification, risks, and rollback or containment notes
• A concise handoff summary for the next execution step

When Not To Use