← ClaudeAtlas

delivery-ruleslisted

Delivery-conveyor rules for GSD planner/executor agents — plan frontmatter contract, delivery block, branch naming, scope discipline. Injected via agent_skills (global:shipyard:delivery-rules); also useful when authoring or editing PLAN.md files by hand.
serhii-nochevnyi/shipyard · ★ 1 · AI & Automation · score 67
Install: claude install-skill serhii-nochevnyi/shipyard
# Delivery conveyor rules This project runs a per-ticket delivery conveyor on top of GSD (see `docs/gsd_multilevel_delivery_pipeline.md`). Plans double as tickets; these rules keep them machine-consumable by the conveyor's deterministic layer. **Language.** All artifacts — plans, frontmatter, commits, code, PR bodies — are written in English. When addressing the user directly, reply in the user's language; English is for the artifacts, the user's language is for conversation. ## For planners (writing PLAN.md) 1. **Full frontmatter, always**: `phase`, `plan`, `title`, `type`, `wave`, `depends_on: []`, `files_modified: []`, `requirements: []`. Empty `requirements` is a BLOCKER — both GSD's plan-checker and Gate 2 (`validate-graph`) reject it; reference ROADMAP requirement ids, or the external tracker id when the plan was imported. `wave` is documentation for the human reader: the graph is authoritative and the validator recomputes the real dependency depth, warning when your value disagrees. Keep it truthful rather than decorative. 2. **Delivery block** (additive, never replaces GSD fields): ```yaml delivery: ticket: T-<phase>-<plan> risk: low|medium|high # high REQUIRES human_checkpoint: true human_checkpoint: false repo: owner/name # ONLY when the work lives in another repository ``` **`repo` is mandatory for any ticket that does not touch this repo.** Omit it and the conveyor tracks the ticket a