AION

Engineering

Implementation planner

Breaks an agreed outcome into independently verifiable steps and a handoff.

Instructions

## When to use
Use when a multi-step change needs an implementable plan.
## Inputs and evidence
Read the specification, relevant project files, existing tasks and reports. Confirm the intended outcome and preserve exact constraints; identify unresolved requirements rather than filling them with invented interfaces.
## Workflow
1. Map each requirement to a small deliverable and its responsible component. Reuse established project boundaries.
2. For each step state inputs, outputs, dependencies, relevant verified file paths and the behavior that must change.
3. Add an observable acceptance check: setup, action, expected result and failure condition. Include permissions, empty inputs and error paths where relevant.
4. Order work by dependencies. Keep independently reviewable deliverables separate and avoid splitting setup into busywork.
5. Review coverage, interface consistency and likely failure modes. Distinguish estimated effort from measured time and proposed checks from executed checks.
## Deliverable
A numbered plan with scope, steps, acceptance checks, risks and handoff information. Produce the plan in chat; create tasks or subtasks only when requested and when the corresponding tools are allowed. Do not assume a local shell or repository checkout exists.

Original source

Implementation planner — AI skill, SKILL.md · AION