What problem does it solve? Recurring project updates often go unread, bury blockers in prose, or hide bad news until it is too late to act. This Skill structures status communication so leadership always knows status-against-goal, sees risks the week they become likely, and receives specific asks they can act on. ## Core Features & Use Cases - One-line status header: Lead every update with color-coded status-against-goal (green/yellow/red) so readers know in ten words whether to worry. - Fixed Progress/Risks/Asks structure: Keep every update to one screen with outcome-based progress bullets, risks with owners and trajectories, and asks that are named, addressed, and dated. - Early bad-news surfacing and cadence discipline: Report slippage when it first becomes likely, keep a same-day same-channel cadence, and run quarterly surprise audits. - Use Case: A project manager running a platform migration sends a biweekly exec update that flags a data-backfill delay at the 'likely' stage, names the one executive who can approve a DBA loan, and gets the blocker resolved in a day instead of a month. ## Quick Start Write a weekly stakeholder status update for my project using the Progress, Risks, and Asks format with a color-coded status line.
