pm-delivery

Router skill for project/delivery management. Resolve topic, Read EXACTLY ONE playbook from routes:, then execute it. Never load the whole cluster. [EXPLICIT]

When to use

PM/delivery questions on budgets, estimation, capacity, roadmaps, OKRs, risk, stakeholders, SLAs, team design, vendors, or retros. NOT for: discovery, architecture, or coding — route those to their own skills. [INFERENCE]

Inputs / Outputs

• In: topic (one of 11 enums) + depth (quick|deep). [EXPLICIT]
• Out: the playbook's deliverable (matrix, register, estimate, plan), every non-trivial claim carrying an evidence tag. [EXPLICIT]

Procedure

1. Infer topic from the request; if two topics fit, ask one disambiguating question — do NOT guess. [EXPLICIT]
2. Read the single matching playbook. Stop if the path is missing. [EXPLICIT]
3. quick → essentials only; deep → apply exhaustively with verification at each step. [EXPLICIT]
4. Run the spine: Discover → Analyze → Execute → Validate. [EXPLICIT]

Acceptance gate (all must hold)

• Exactly one playbook loaded; output matches its template. [EXPLICIT]
• Every claim tagged [EXPLICIT] / [INFERENCE] / [ASSUMPTION]. [EXPLICIT]
• No raw prices anywhere — cost work uses FTE-months + disclaimers. [EXPLICIT]
• Constitution v6.0.0 enforcement + script-first rule satisfied. [EXPLICIT]
• Gate verified against assets/ (rubric + checklist) — see assets/README.md. [EXPLICIT]

Self-correction triggers

• Loaded >1 playbook, or summarized from memory instead of reading → restart at step 1. [EXPLICIT]
• A price slipped into a cost/budget/vendor output → convert to FTE-months. [EXPLICIT]
• Output skips the Discover/Validate ends of the spine → redo those steps. [INFERENCE]

Anti-patterns

• Pre-reading or merging multiple playbooks "for context." [EXPLICIT]
• Inventing topics outside the enum, or renaming routes. [EXPLICIT]
• Green-as-success theater: never report a gate passed without evidence. [EXPLICIT]