delivery
Deliver a change through an approved design contract, sequential implementation, independent review and exact-HEAD release. Use for any Bounded or Architectural change — including a small, one-line behavioral fix, which is the canonical Bounded case — so it gets design approval and independent review. Not for a Spike, which investigates and recommends without starting a delivery run.
hieuphung97 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add hieuphung97/dely --skill delivery技能说明
name: delivery description: Deliver a change through an approved design contract, sequential implementation, independent review and exact-HEAD release. Use for any Bounded or Architectural change — including a small, one-line behavioral fix, which is the canonical Bounded case — so it gets design approval and independent review. Not for a Spike, which investigates and recommends without starting a delivery run.
Delivery
Dely accepts a request that may still be vague, brings it to an approved design contract, then automates sequential implementation, independent review, and pull-request preparation. It is a thin control protocol, not an orchestrator, SDLC framework, or second source of Git state.
Read AGENTS.md in the repository for this project's gate commands, artifact
paths, default branch, and per-phase harness/model/effort pins. This skill
never names them.
Two human gates
- Approve the design contract before candidate mutation.
- Merge or publish after Dely has prepared the reviewed pull request.
Dely pauses outside those gates only for a scope or architecture change, a destructive action, new authority, replan, or an unavailable required runtime.
The control session
The current interactive session is Control. It owns the approval invariant, task boundaries, exception handling, dispatch supervision, and release. It does not implement or review the candidate.
Control does not prescribe question count, order, format, or skill-selection precedence. Dely owns the design outcome and approval boundary, not a universal interview or planning method. The user, project, and harness determine which design skills and native modes are active.
Native Plan Mode governs its enforced action constraints, question and plan surfaces, artifact representation, and mode transitions. Compatible active design skills may refine exploration and design methodology within those constraints. When more than one applies, normal harness instruction and tool precedence governs. One explicit approval satisfies Dely's boundary for the same design scope; a material scope change requires renewed approval. Dely does not select, activate, configure, emulate, or compose either mechanism.
Neither one owns or can bypass the approval invariant: before candidate mutation, Control must obtain explicit human approval of a design contract. Plan Mode is defense in depth, not proof that requirements are clear or that no mutation is possible.
Control surfaces unresolved uncertainty that could materially change intent, acceptance, authority, public contract, architecture, or consequential risk. The active design method may resolve other details from repository evidence and convention, but material assumptions must be explicit.
Shape: Spike, Bounded, Architectural
Use the smallest contract that safely holds the change. Risk may promote an otherwise small change; diff size never demotes data-loss, security, permission, or public-compatibility risk.
| Shape | Use | Artifact | Review |
|---|---|---|---|
| Spike | Investigation only; no candidate is delivered | Approved probe and recommendation; no delivery run | none |
| Bounded | Small change, clear behaviour and ownership | Approved in-chat design and short execution envelope | one whole-change review |
| Architectural | Multiple behaviours, public-contract change, architecture decision, or promoted risk | Approved decision record, task plan, execution envelope | task review per task, then one integration review |
An approved design contract states intent and success criteria; scope and authority; affected public contract or architecture; consequential risks and material assumptions; and a plausible counterexample or failure mode that distinguishes correct behaviour from a present-but-wrong implementation. If no executable instrument can discriminate the requirement, the contract names the manual inspection and its limit.
Architectural work uses templates/decision-record.md (durable) and
templates/plan.md (transient, deleted in the release commit, before
the release-binding review). Commit both before implementation begins
— that commit is the review baseline.
Acceptance
One table: each requirement, the instrument that proves it, the plausible wrong implementation that instrument rejects, and where that rejection was observed.
An acceptance row is invalid until you have settled that its instrument discriminates. A row whose instrument passes both before and after the change proves nothing and will be found at review. Baseline-red is insufficient by itself: an instrument observed red only because the feature is absent says nothing about whether it can catch an implementation that is present, runs, returns a pass, and is wrong.
Each row names a plausible wrong implementation its instrument rejects — one that exists, runs, and returns a pass. "The feature is absent" does not satisfy Counterexample. Where no counterexample exists, the row says so and says a human reads the diff.
Record what the available instruments cannot observe. Prefer the simplest instrument that proves the contract.
Any claim about extent — an allowed scope, a count, a set of call sites — states the command that produced it. Naming the command is not the measurement: the command must have been run, and the claim reports its output. Where the claim is a count or a scope, the instrument enumerates rather than samples.
Execution envelope
Before mutation, Control resolves deployment preferences against the live harness surface, starts Orca and verifies its required capabilities, records the dirty baseline and exact-path ownership, and creates a feature branch when starting on the default branch.
The envelope freezes owned scope and paths; protected pre-existing dirty paths; acceptance criteria, counterexample, and focused instruments; branch, base, remote, and pull-request target; resolved harness, model, and effort for dispatched roles; and authority
阅读完整来源 ↗