| name | deliver |
| description | Take one shaped Gradient docs/schema/profile task to merge-ready. Composes
/shape, /implement, /code-review, /ci, /qa, /demo, and /refactor as needed.
Stops before merge. Trigger: /deliver.
|
| argument-hint | [task|context-packet] |
/deliver
Deliver one coherent public-safe change. In this repo, merge-ready means the
change strengthens a named lifecycle stage, respects module boundaries, and has
evidence for the current manual gate.
Procedure
- Confirm the shaped goal and non-goals.
- For substantial or ambiguous work, use the planner to clarify the context
packet before implementation.
- Make the smallest docs/schema/profile/harness change that satisfies it. When
using the triad, this is the executor step, and the executor also gathers the
requested evidence.
- Run
/code-review against public-safe, lifecycle, and profile semantics.
When using the triad, this is the critic step; blocking critique loops back
to planning or execution before proceeding.
- Run
/ci for the current gate.
- Run
/qa for changed artifact inspection.
- Use
/demo when a reviewer needs a transcript, fixture, or walkthrough.
- Run
/refactor only to simplify the changed surface; do not broaden scope.
- The lead agent/operator decides whether the evidence is sufficient to stop,
loop, or hand off for shipping.
Triad Use
Use the planner/executor/critic triad when the task changes a module contract,
schema, profile, harness primitive, generated repo guidance, policy/context
surface, or user-facing workflow. Skip it for tiny documentation fixes,
mechanical moves, and one-command checks.
The planner packet must name the objective, non-goals, authority order, repo
anchors, executor ownership boundary, and executable evidence. The executor
must stay inside that boundary and report changed files. The critic must review
cold against the packet and fail on missing evidence, unnecessary complexity,
module-boundary drift, or unapproved scope growth. The lead agent/operator
integrates the result and owns the final decision.
Gate
The load-bearing ship gate is ./scripts/validate.sh, plus reviewer
judgment for lifecycle semantics in docs/architecture.md and
docs/module-contracts.md when docs change.
Receipt
Report changed files, lifecycle stage strengthened, evidence gathered, and
remaining unverified paths.
