| name | neo-delivery |
| description | Convert approved Neo context and design into thin vertical implementation slices with focused verifiers, compatibility, rollout, rollback, and replan conditions. Use only with a delivery-stage handoff generated by $neo. Do not use directly, create horizontal layer batches, or implement the slices. |
Structure Delivery
Work only on the active Neo delivery stage.
Use the <neo-cli> already resolved by the active $neo router. If it is not
present in the handoff context, resolve scripts/neo.py
from the installed neo skill's source location.
- Validate the handoff with
neo.py handoff <slug> --expect delivery.
- Load all approved required-stage artifacts.
- Read
interaction.md and
delivery.md.
- Divide work into thin vertical behaviors. For each slice state:
- behavior or risk proved;
- minimum cross-boundary changes;
- prerequisites and non-goals;
- focused automated verifier;
- real-interface or operational evidence;
- compatibility, rollout, rollback, and documentation needs; and
- stop or replan condition.
- Put the highest-value uncertainty early while leaving the system coherent
after every slice.
- Present only granularity, verifier, sequencing, and dependency decisions for
approval. Record consequential choices.
- Write
.neo/tasks/<slug>/delivery.md and gate it with
neo.py gate <slug> --stage delivery --artifact <path>.
If no user input is required, return control to $neo to continue finalization
in this context. Do not implement a slice.
