Deliver spec
Core principle
Deliver one approved outcome with proportional validation and independent final
review. The lead owns architecture, integration and delivery, and implements
tightly coupled or sequential work directly by default. Delegate only when
independent work, isolation or specialist investigation justifies the
overhead; available worker capacity alone does not. Preserve explicit ownership,
external-action permissions, execution budgets and invocation-specific merge
authority. Never select work from a Project queue.
Select the mode
For an active run-github-project controller's verified ticket handoff, read
Project controller handoff and apply its
procedure instead of the standalone approval, merge, and timeout rules below.
The Project controller retains all shared state and merge authority.
For a direct named-spec request, use the standalone procedure below; if a
Project run already owns that issue, return it to that controller.
Procedure
- Resolve the named source, repository, approved contract, and any existing
branch or PR from fresh state. On resume, reconcile the PR, exact head,
checks, feedback, and authority before acting. For integration amendments,
use Evidence and review to verify the
installed planner contract and retained work before consuming any delta.
- Plan: reuse a current
to-plan plan; otherwise invoke to-plan
(conversation mode for a local source) and honor its readiness and
publication gates. A source qualifying for the fast path
applies it instead. For a GitHub issue missing ready-for-agent, first use
triage and wait for its approved outcome; do not change labels yourself.
Local sources skip triage but need explicit stakeholder approval. For an
approved local source with no plan that does not qualify for the fast path,
name conversation-mode to-plan as the initial route, including when
answering a resume question.
When presenting a plan for approval, include a concise high-level overview
in the response: the intended outcome, main implementation steps and
validation approach. Link the detailed plan when available, then ask for
approval of that scope.
Approval covers the accepted contract and only the live qualification
allowances it explicitly records; do not infer extra attempts or authority.
- Verify scope and boundaries once. A verified handoff authorizes continuing
in-scope implementation, testing and repairs in the isolated checkout;
require no per-file or per-stage permission packets. Reuse valid plans,
reviews and checks. Require earlier independent review only for a concrete
risk that must be settled before proceeding, such as freezing experimental
labels before observing outputs; build work independent of it, such as
tooling, in parallel rather than after. Keep required deliverables and data-handling and spend limits;
build no unrequested general infrastructure. Establish reviewer capability from runtime
metadata, never by spawning a capability-only reviewer. If final review
cannot run, report that delivery blocker without waiving review.
- Follow the bundled implementation procedure
for solo or delegated work, ownership, isolation and recovery. Implement
sequential or tightly coupled slices as the lead, not through a worker. Follow the stated repository or user testing policy.
Reconcile retained work before implementing; never redo accepted work for
routing.
Follow Evidence and review for testing,
corrections and the single reusable delivery record. When the source requires
asynchronous or persistent live qualification, apply
Live qualification and failure recovery
before attempts and resumes; do not add it to ordinary offline work.
- Self-review the integrated candidate, run affected local and required
pre-push checks, then give one independent read-only reviewer per delivery
PR the approved source, repository standards, the exact clean candidate head
and its validation evidence. Use a fresh agent that makes no
writes and has no inherited implementation context. Reuse valid
independent coverage; do not duplicate a plan or implementation review.
Require evidence-backed findings and a
ship, fix-first, or rethink
verdict. Honor explicitly invoked provider contracts and report missing
coverage. Return findings to the implementation owner; at the repaired head,
renew affected checks and review changed ranges and interactions. Broaden only when impact cannot
be bounded or an explicit requirement demands it. Confirm combined coverage
of the final clean head before pushing. If finished, verified work leaves
the final diff empty, report no-change; a starting empty diff is not
no-change. Otherwise create one draft PR, or reuse the existing PR, and
verify its head is the reviewed head. Apply
PR review timing: start applicable external review
while CI runs, using verified draft support or earlier PR readiness when
permitted. Keep delivery pending until all final-head gates pass. Use
closing links only for verified GitHub issues.
shepherd owns CI, feedback and every PR operation. Keep repairs with their
implementation owner; renew affected checks and focused review at the
repaired head before pushing. Routine implementation or fixture corrections preserving
requirements, coverage, architecture and authority proceed under the existing
approval; record them briefly. Material changes require the appropriate
decision and replan before affected work continues. Weakened qualification
or expanded permissions are material. Merge only with explicit authority
valid for this invocation. After about 30 minutes of pending gates, hand back
the exact pending checks, feedback, PR and head for later resume.
Finish gate
Report ready only when the final head passes required checks and reviews
with findings resolved and evidence applicable to that clean head;
merged only after authorized merge readback;
no-change only when implementation and verification finish with an empty
final diff; pending with exact outstanding gates; otherwise blocked with the
needed decision or capability. Preserve the PR and source pointers on pending
or blocked runs. Do not report a prior head as the reviewed result.
1---2name: deliver-spec3description: Use when explicitly asked to deliver an approved GitHub or local spec through a reviewed pull request, or when a Project controller delegates one claimed implementation ticket.4compatibility: "Solo or delegated implementation uses the bundled procedure; triage is conditional. Never installs providers."5metadata:6 source: https://skillmd.com/skills/tuyv/deliver-spec7---89# Deliver spec1011## Core principle1213Deliver one approved outcome with proportional validation and independent final14review. The lead owns architecture, integration and delivery, and implements15tightly coupled or sequential work directly by default. Delegate only when16independent work, isolation or specialist investigation justifies the17overhead; available worker capacity alone does not. Preserve explicit ownership,18external-action permissions, execution budgets and invocation-specific merge19authority. Never select work from a Project queue.2021## Select the mode2223For an active `run-github-project` controller's verified ticket handoff, read24[Project controller handoff](references/project-handoff.md) and apply its25procedure instead of the standalone approval, merge, and timeout rules below.26The Project controller retains all shared state and merge authority.27For a direct named-spec request, use the standalone procedure below; if a28Project run already owns that issue, return it to that controller.2930## Procedure31321. Resolve the named source, repository, approved contract, and any existing33 branch or PR from fresh state. On resume, reconcile the PR, exact head,34 checks, feedback, and authority before acting. For integration amendments,35 use [Evidence and review](references/evidence-and-review.md) to verify the36 installed planner contract and retained work before consuming any delta.372. Plan: reuse a current `to-plan` plan; otherwise invoke `to-plan`38 (conversation mode for a local source) and honor its readiness and39 publication gates. A source qualifying for the [fast path](references/fast-path.md)40 applies it instead. For a GitHub issue missing `ready-for-agent`, first use41 `triage` and wait for its approved outcome; do not change labels yourself.42 Local sources skip triage but need explicit stakeholder approval. For an43 approved local source with no plan that does not qualify for the fast path,44 name conversation-mode `to-plan` as the initial route, including when45 answering a resume question.46 When presenting a plan for approval, include a concise high-level overview47 in the response: the intended outcome, main implementation steps and48 validation approach. Link the detailed plan when available, then ask for49 approval of that scope.50 Approval covers the accepted contract and only the live qualification51 allowances it explicitly records; do not infer extra attempts or authority.523. Verify scope and boundaries once. A verified handoff authorizes continuing53 in-scope implementation, testing and repairs in the isolated checkout;54 require no per-file or per-stage permission packets. Reuse valid plans,55 reviews and checks. Require earlier independent review only for a concrete56 risk that must be settled before proceeding, such as freezing experimental57 labels before observing outputs; build work independent of it, such as58 tooling, in parallel rather than after. Keep required deliverables and data-handling and spend limits;59 build no unrequested general infrastructure. Establish reviewer capability from runtime60 metadata, never by spawning a capability-only reviewer. If final review61 cannot run, report that delivery blocker without waiving review.624. Follow the bundled [implementation procedure](references/implementation-mode.md)63 for solo or delegated work, ownership, isolation and recovery. Implement64 sequential or tightly coupled slices as the lead, not through a worker. Follow the stated repository or user testing policy.65 Reconcile retained work before implementing; never redo accepted work for66 routing.67 Follow [Evidence and review](references/evidence-and-review.md) for testing,68 corrections and the single reusable delivery record. When the source requires69 asynchronous or persistent live qualification, apply70 [Live qualification and failure recovery](references/qualification-failure.md)71 before attempts and resumes; do not add it to ordinary offline work.725. Self-review the integrated candidate, run affected local and required73 pre-push checks, then give one independent read-only reviewer per delivery74 PR the approved source, repository standards, the exact clean candidate head75 and its validation evidence. Use a fresh agent that makes no76 writes and has no inherited implementation context. Reuse valid77 independent coverage; do not duplicate a plan or implementation review.78 Require evidence-backed findings and a `ship`, `fix-first`, or `rethink`79 verdict. Honor explicitly invoked provider contracts and report missing80 coverage. Return findings to the implementation owner; at the repaired head,81 renew affected checks and review changed ranges and interactions. Broaden only when impact cannot82 be bounded or an explicit requirement demands it. Confirm combined coverage83 of the final clean head before pushing. If finished, verified work leaves84 the final diff empty, report `no-change`; a starting empty diff is not85 `no-change`. Otherwise create one draft PR, or reuse the existing PR, and86 verify its head is the reviewed head. Apply87 [PR review timing](references/pr-review-timing.md): start applicable external review88 while CI runs, using verified draft support or earlier PR readiness when89 permitted. Keep delivery `pending` until all final-head gates pass. Use90 closing links only for verified GitHub issues.916. `shepherd` owns CI, feedback and every PR operation. Keep repairs with their92 implementation owner; renew affected checks and focused review at the93 repaired head before pushing. Routine implementation or fixture corrections preserving94 requirements, coverage, architecture and authority proceed under the existing95 approval; record them briefly. Material changes require the appropriate96 decision and replan before affected work continues. Weakened qualification97 or expanded permissions are material. Merge only with explicit authority98 valid for this invocation. After about 30 minutes of pending gates, hand back99 the exact pending checks, feedback, PR and head for later resume.100101## Finish gate102103Report `ready` only when the final head passes required checks and reviews104with findings resolved and evidence applicable to that clean head;105`merged` only after authorized merge readback;106`no-change` only when implementation and verification finish with an empty107final diff; `pending` with exact outstanding gates; otherwise `blocked` with the108needed decision or capability. Preserve the PR and source pointers on pending109or blocked runs. Do not report a prior head as the reviewed result.