/silver:ship-readiness

Catalog-backed reusable workflow component (WF-SHIP-READINESS) for the final delivery gate — branch hygiene, completion audit, and ship authorization. Composed at the end of delivery workflows after quality gates pass.

Overview

/silver:ship-readiness documents WF-SHIP-READINESS, a reusable workflow component in the v0.48.3 APO catalog. It is the terminal gate chain that proves a branch is ready for PR creation, merge, or deploy.

Catalog slug: ship-readiness. Type: reusable_component. Allowed dynamic operations: loop (re-audit after fixes before ship authorization).

BRANCH_FINISH → COMPLETION_AUDIT → SHIP

Individual atomic flows are invokable via /silver:branch-finish, /silver:completion-audit, and /silver:ship, but the ship-readiness chain only runs as an ordered composition inside parent workflows.

Reusable component: Unlike top-level composer workflows such as /silver:feature, this chain is composed automatically after pre-ship QUALITY_GATE passes. Individual atomic flows remain invokable directly via their own routes.

Catalog Composition

Atomic flowSlugCommandWork product
AF-BRANCH-FINISHBRANCH_FINISH/silver:branch-finishBranch hygiene, commit readiness, and traceability evidence
AF-COMPLETION-AUDITCOMPLETION_AUDIT/silver:completion-auditRequired-skill audit proving catalog composition was followed
AF-SHIPSHIP/silver:shipShip authorization and delivery handoff evidence

Where it is composed

WF-SHIP-READINESS is the final segment of the post-execution sequence in delivery workflows:

… → VERIFY (verify-tests) → SECURE (VALIDATE as needed) → QUALITY_GATE (pre-ship) → BRANCH_FINISH → COMPLETION_AUDIT → SHIP

Parent workflows that include this component:

WF-SILVER-FAST ends at VERIFY and does not include ship readiness — bounded changes use the lightweight fast path.

Atomic Flow Execution

AF-BRANCH-FINISH — Branch hygiene

Invoke /silver:branch-finish. Ensure commits are atomic, messages are traceable, branch is rebased or merged cleanly, and no WIP artifacts remain. Produces ART-BRANCH_FINISH.

AF-COMPLETION-AUDIT — Prove workflow compliance

Invoke /silver:completion-audit. Audit that all required skills from .silver-bullet.json were invoked and recorded in session state. This is the hook-enforced gate that blocks git commit/git push (planning skills) and gh pr create/deploy (full deploy list).

AF-SHIP — Authorize delivery

Invoke /silver:ship. Confirm ship readiness: PR description completeness, traceability to spec/UAT, and delivery handoff evidence. Produces ART-SHIP before gh pr create or deploy commands proceed.

Hook enforcement

Ship readiness is not advisory — hooks enforce it at the Bash tool boundary:

  • Intermediate commits (git commit, git push) — require required_planning skills only
  • Final delivery (gh pr create, gh release create, deploy) — require the full required_deploy list from .silver-bullet.json
Two-tier model: Execution subagents can make atomic commits mid-workflow with planning skills only. The full ship-readiness chain must complete before PR creation or deploy — completion-audit.sh and stop-check.sh enforce this at runtime.