Implementation Planning
Create an executable plan that another engineer can follow without reopening material design decisions.
Read specification synthesis when multiple evidence sources must become one behavioral contract. Read work packages when the plan needs independently reviewable units. Read decision map when unresolved choices or multiple sessions control sequencing.
Workflow
- Confirm the approved problem, desired outcome, scope, non-goals, and decision owner.
- Inspect the current repository and relevant external authority before naming files, interfaces, or commands.
- Describe the target behavior and every public interface, data contract, state transition, or compatibility promise that changes.
- Break work into ordered, reviewable steps with exact locations and dependencies.
- Define tests by risk: unit, integration, contract, migration, end-to-end, property, and manual observation as applicable.
- Specify rollout, monitoring, compatibility, rollback, and data-recovery behavior.
- Add checkpoints where evidence must be reviewed before proceeding.
- State stopping conditions for missing authority, unexpected scope, failing safety gates, or invalidated assumptions.
Quality rules
- Resolve discoverable facts from the repository instead of delegating discovery to the implementer.
- Distinguish proposed changes from ratified decisions.
- Name uncertainty directly; do not hide it inside vague steps.
- Do not perform implementation, publication, deployment, or merge unless separately authorized.
Output
Return Objective, Current evidence, Interfaces, Implementation steps, Test strategy, Rollout and rollback, Checkpoints, Risks, and Stopping conditions.
1---2name: implementation-planning3description: Produce a decision-complete implementation plan grounded in repository and platform evidence. Use when a change needs concrete interfaces, ordered steps, tests, rollout controls, checkpoints, and stopping conditions before work begins.4license: MIT5---67# Implementation Planning89Create an executable plan that another engineer can follow without reopening material design decisions.1011Read [specification synthesis](references/specification-synthesis.md) when multiple evidence sources must become one behavioral contract. Read [work packages](references/work-packages.md) when the plan needs independently reviewable units. Read [decision map](references/decision-map.md) when unresolved choices or multiple sessions control sequencing.1213## Workflow14151. Confirm the approved problem, desired outcome, scope, non-goals, and decision owner.162. Inspect the current repository and relevant external authority before naming files, interfaces, or commands.173. Describe the target behavior and every public interface, data contract, state transition, or compatibility promise that changes.184. Break work into ordered, reviewable steps with exact locations and dependencies.195. Define tests by risk: unit, integration, contract, migration, end-to-end, property, and manual observation as applicable.206. Specify rollout, monitoring, compatibility, rollback, and data-recovery behavior.217. Add checkpoints where evidence must be reviewed before proceeding.228. State stopping conditions for missing authority, unexpected scope, failing safety gates, or invalidated assumptions.2324## Quality rules2526- Resolve discoverable facts from the repository instead of delegating discovery to the implementer.27- Distinguish proposed changes from ratified decisions.28- Name uncertainty directly; do not hide it inside vague steps.29- Do not perform implementation, publication, deployment, or merge unless separately authorized.3031## Output3233Return `Objective`, `Current evidence`, `Interfaces`, `Implementation steps`, `Test strategy`, `Rollout and rollback`, `Checkpoints`, `Risks`, and `Stopping conditions`.
JovaniPink