← ClaudeAtlas

deliverlisted

Take a feature from scoping to its PRs in one session: run `/scope` with `--intent=continue` and then `/execute` on the PLAN it produces, merging (when the repository's own rules allow it) unless run with `--no-merge`. Use it when the author wants a topic done end to end without re-invoking anything between the two -- "scope and build this", "deliver the plugin-system feature", "take this from idea to PR" -- and to pick such a topic up again, since every invocation re-enters through `/scope`, which knows where the topic stopped. Do NOT use it to write only the documents (`/scope`), to run a PLAN that already exists and needs no re-scoping (`/execute`), or to fix one known issue (`/work-on`).
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh deliver 2>&1 || true` # Deliver `/deliver <topic>` runs `/scope <topic> --intent=continue` and then `/execute docs/plans/PLAN-<topic>.md` in one session, without the author re-invoking anything. It passes `--merge` to `/execute` unless `--no-merge` is given, so a run ends `merged` wherever the repository's protection lets `/execute` merge, and in a named, resumable state everywhere else. `/deliver` is a koto workflow, and it is thin in behaviour: it writes nothing to the repository itself. `/scope` and `/execute` do all of that, as the same root sessions (`scope-<topic>`, `execute-<topic>`) a person running them directly would get. What `/deliver` adds is the sequence and the checks between the two, and those live in its template, `skills/deliver/koto-templates/deliver.md`, not in this file. ## How the Run Is Held Together Each invocation opens a fresh `deliver-<topic>` session and a fresh koto request with two legs, `scope` and `execute`. Each child joins its leg through its own `--koto-leg=<request-id>:<leg>` flag and reports through its terminal result, which koto records on the leg. `/deliver` reads each leg only through a `request-leg` gate in its template. It never parses what a child printed, and nothing you submit can stand in for a child's result. A child's word never moves the run forward on its own. Every forward step is re-checked against durable state first: the PLAN tracked and the scoping PR recordin