project-management

Stand up the predictive plan of record — a project charter (objective, success criteria, sponsor, high-level scope, assumptions/constraints), a scope statement + WBS decomposed to single-owner work packages, and the scope/schedule/cost baseline that change control is measured against. Reach for this at project initiation, a reset, or before any earned-value reporting. Used by `delivery-lead` (primary).

Build or refresh a decision-grade RAID register — risks framed cause→event→consequence and scored against a stated rubric (qualitative probability×impact, quantified/EMV where the stakes justify it), each with a response and a single owner; plus issue triage, assumptions, and dependency tracking. Reach for this when a RAID stub needs to become a real register, a risk needs quantifying, or issues need triaging to action. Used by `risk-and-raid-analyst` (primary).

Plan a sprint from a backlog — set a single sprint goal, size the commitment to demonstrated capacity (not aspiration), attach acceptance criteria + a single owner to every committed item, and make carry-over explicit. Reach for this when a team is starting a sprint, replanning mid-flight, or diagnosing erratic velocity. Used by `scrum-master` (primary).

Build and maintain a stakeholder register with power/interest mapping, design a tailored communications plan, prepare steering packs and executive status reports, and handle escalation memos — ensuring the right message reaches the right stakeholder at the right depth every cycle.

Package delivery + risk data into audience-ready communication — a narrative-first status (RAG that explains itself and never contradicts the numbers), a steering-committee pack, and an escalation memo that is a decision request. Reach for this for recurring status, an exec/board update, or an escalation under pressure. Used by `stakeholder-comms-lead` (primary).