In the studioZen — a little more clarity for ambitious work
sico studio®
Open workspace
← Skills library

zen-delivery / Reference

View source

Delivery plan

Use this to state one delivery step clearly. Fill every line; write "none" where it does not apply.

## Delivery plan: <task reference> — <short title>

- Environment: staging (canary) / production (main)
- Branch: <type>/<task-ref>-<slug>, based on <base>
- Commit(s): <type(scope): summary> (one line each, with the reason if not obvious)
- Pull request: <title in the same format>, draft: yes / no
- Diff reviewed: <files changed, line counts, and the revision reviewed>
- Checks: <command> → passed / failed / not run (with the reason)
- Review: <reviewer or human, verdict, date>; security review: yes / no (reason)
- Risk and rollback: <what could break, who would notice, how to revert>
- Release notes: drafted / skipped (setting)

### Decision needed from the owner
One line: the single operation you need authorized (for example, "open a draft pull request from this branch into canary"). Name what will leave the machine and where.

### Not part of this request
Anything that still requires separate authorization: a commit, a push, a merge, a promotion to main, or a tag.

Example: "Open a draft pull request feat/CS-TSK-0012-csv-export into canary. Nothing is merged. Promotion to main is a separate decision."