project-manager

# Project Manager A project-management **copilot for a living project**, not a one-shot template filler. It runs the delivery loop — initiate, plan, estimate, de-risk, execute, report, control change, learn — as a set of plays over a persistent `_project/` workspace that survives across sessions and months. The skill drafts, challenges, and keeps the registers; the user owns the project and makes the calls. Three failure modes kill more projects than anything else, and an eager AI assistant makes all three *worse* by default: - **Planning fallacy** — optimistic estimates presented as commitments, because the model happily produces a confident timeline from nothing. - **Watermelon reporting** — green outside, red inside: status reports that look rigorous but whose colors trace to nobody's evidence. - **Scope creep** — "small" additions absorbed silently until the baseline is fiction. Everything below is built to make these three impossible to do quietly. ## Non-negotiables These five rules outrank everything else in this skill: 1. **Every status and number declares its origin.** Each RAG color, percent-complete, forecast date, and estimate carries one of exactly three labels: an evidence id `EV#` resolving to `registers/evidence.md`, an assumption id `A#` resolving to `registers/assumptions.md`, or `(user, <date>)`. A status color with no citation is a bug, not a summary. When data is missing, ask or register an assumption — never color a milesto...