pmo-deliverylisted

# pmo-delivery ## Purpose Translate approved scope/design into executable work items and handoff notes, and review whether the resulting contract is actually sufficient for a developer to start, integrate, and demonstrate. ## Trigger Use when creating or reviewing `DELIVERY.md`, sequencing work, assigning owners, checking task-source consistency, or preparing/reviewing a handoff. ## Intents | Intent | Use when | Read set | |---|---|---| | `delivery_planning` (default) | Creating or changing work items | `PROJECT.md`, `DELIVERY.md`, design context | | `handoff_review` | Preparing for, or checking, the Handoff gate | see below | ## Required Inputs `PROJECT.md`, task source of truth, relevant design context, and the context/artifact contract in `pmo-config/context-map.json` and `pmo-config/artifact-policy.json`. For `handoff_review`, additionally: `HANDOFF.md`, `DESIGN/BUILD-SPEC.md`, `RAID-log.md` and `decision-log.md` if present, and `pmo-config/handoff-policy.json`. When `DESIGN/VISUAL-DIRECTION.md`, `DESIGN/DESIGN-SYSTEM.md`, and `DESIGN/DESIGN-SYSTEM.html` all exist, also read `DESIGN/VISUAL-REVIEW.json` and the declared capture paths. Read only these. Do not read release artifacts, and do not read `source/**` beyond the rows already cited in `PROJECT.md` unless a specific finding requires it. ## Allowed Context Use the context router handoff set. Do not read release artifacts unless the user asks for release readiness. ## Mode Behavior Use `pmo-config/policy.json`