| name | pmo-delivery |
| description | Use for delivery planning, handoff, task source of truth, and engineering sequencing. |
pmo-delivery
Purpose
Translate approved scope/design into executable work items and handoff notes.
Trigger
Use when creating or reviewing DELIVERY.md, sequencing work, assigning owners, or checking task-source consistency.
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.
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 for mode, status, review-stage, task-source, strict-trigger, and sentinel values. Use pmo-config/artifact-policy.json to decide whether DELIVERY.md is required, conditional, or replaceable by GitHub Issues for the active mode and gate.
Execution Steps
- Confirm task source of truth: file or GitHub.
- Create work items with mode, strict trigger, requirement ref, design ref, status, review stage, evidence, and labels.
- Check enum values against runtime policy.
- Flag missing blockers or client decisions.
Output Contract
Return work-item changes, dependency notes, owner gaps, and validation result.
Approval Rules
Mode escalation and high-risk work require human confirmation before delivery starts.
Validation Command
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/validate-project.ps1 -ProjectPath <project> -Mode <mode> -Gate Scope
Prohibited Actions
Do not create hidden task systems, duplicate source of truth, hardcode mode/gate matrices, or add features outside scope.
Completion Criteria
Every work item references an existing requirement/business rule and has valid mode, status, and review stage.