coder-xieshijie/dev-skills / skills/deliver
deliver
VerifiedOne owner implements a requirement and delivers a mergeable MR/PR. Use after spec.md and verify.md are confirmed and frozen.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 24.3 KB |
| agents/openai.yaml | config | 154 B |
| references/milestone-check.md | markdown | 1.8 KB |
| references/plan-format.md | markdown | 4.8 KB |
| references/verifier-brief.md | markdown | 7.7 KB |
| scripts/check-delivery.mjs | script | 12.0 KB |
| scripts/check-delivery.test.mjs | script | 12.2 KB |
| scripts/ci-watch.mjs | script | 12.1 KB |
| scripts/ci-watch.test.mjs | script | 12.9 KB |
| scripts/stall-guard.mjs | script | 4.6 KB |
| scripts/stall-guard.test.mjs | script | 2.9 KB |
references/plan-format.md
View on GitHub# plan.md format
Based on OpenAI's ExecPlan ([Using PLANS.md for multi-hour problem solving](https://cookbook.openai.com/articles/codex_exec_plans)). The owner writes plan.md, revises it while working, and commits it with the code; plan.md changes are pushed together with code, never alone (see "MR" in SKILL.md). It has two readers: a new session taking over after an interruption, which must be able to continue from only plan.md and the git history; and the user before merging, who reads the decision list first.
spec.md and verify.md are frozen and committed on the feature branch. plan.md refers to them and does not restate the requirements or scenarios; acceptance follows verify.md.
## Sections
Write them in the order below. Sections marked "kept up to date" are updated at every stopping point and after each milestone; when you change course, revise all affected sections together, not only by appending at the end.
### Decision list (kept up to date)
Put it first, ordered from largest to smallest impact. Each entry is one top-level list item:
```text
- Decision: <the choice you made>
- Rationale: <basis and evidence>
- Other family: <the model you asked and its opinion; if you did not ask, write "Not asked; affects implementation only">
- If overturned: <what must change; which scenarios to rerun>
```
For what goes in it, see "Decision list" in SKILL.md. If there are no decisions, write "None". The decision list at the top of the MR description is copied from here.
### Frozen inputs
```text
- handoff: <MR link> <feature branch> @ <handoff commit>
- spec: <path in the repository>
- verify: <path in the repository>
- baseline: <target branch> @ <commit>
```
The owner model is not written here: you pass it to `check-delivery.mjs` as `--owner`, which uses it to confirm that the independent verifier is from another family. When only local paths were handed over, write "local" on the handoff line, and on the spec and verify lines write the absolute path and the sha256 the user gave (`- spec: <absolute path> sha256=<value>`); a session taking over uses them to run `check-delivery.mjs --spec <path>@<sha256> --verify <path>@<sha256>`.
### Purpose / Big Picture
One or two sentences: what the user can do once this is done, and how to see it working. Taken from the spec's purpose.
### Progress (kept up to date)
A checklist, one line per step: what was done, which scenarios passed, commit. The commit carries the time; write a clock time only when you read it from a command. Write an unfinished step as "completed: X; remaining: Y".
```text
- [x] M1 add read-only quota query; S01 passes; milestone check found no problems; a1b2c3d
- [ ] M2 quota-exhausted boundary (completed: UI entry point S02; remaining: command-line entry point S03)
```
### Surprises & Discoveries (kept up to date)
Facts that differed from what you expected and shaped your approach, for example a library that lacks support for something, an interface that behaves differently, or a baseline failure unrelated to this change. For each, write the observation and brief evidence.
### Outcomes & Retrospective (kept up to date)
What was achieved, what remains, the result compared against the purpose, and the repository gaps this work exposed (missing verification capabilities, docs or lint).
### Context and Orientation
Files and modules relevant to this task (full paths), non-obvious conventions, and the terms you will use; link to existing docs, and do not restate the implementation.
### Milestones
One paragraph per milestone, starting with its number (M1, M2, ...): the scope, what will exist at the end that did not exist before, which scenarios and coverage blind spots in verify it covers, which quality commands to run, and which later milestones build on it (when any do, it gets a milestone check before the first of them starts). A scenario that depends on a verification capability is placed after the capability is added.
### Validation and Acceptance
How to start the app and run the smoke set; how to drive each scenario from its entry point, with the actual commands, including those marked "bind command after implementation" in verify. Verdicts follow the checkpoints in verify.md. This section is given to the independent verifier for running the scenarios.
### Interfaces and Dependencies
The libraries, modules and services used, and why; parts the spec does not prescribe are the owner's choice and may change when the approach changes.
## Size
For evidence, write a one-sentence conclusion; the output stays in the evidence directory outside the repository, so plan.md does not link to it. When Progress grows so long that reading plan.md at every start takes real time, you may move it to `progress.md` in the same directory and leave a link in plan.md; the decision list and frozen inputs stay in plan.md.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |