Stakeholder Brief

The problem

Stakeholders are often buried under status novels and multi-page reports that obscure the actual request. Developers and PMs waste time formatting weekly updates when they only need to signal a critical change or secure a specific approval.

What it does

• Extracts a single, verb-based ask from messy meeting notes or data dumps.
• Distills complex project updates into exactly one page for one specific audience.
• Identifies operational risks and hard deadlines with strict source citations.
• Enforces a rigid format including change bullets, risks, and ISO-dated dues.
• Flags contradictions or missing data as blocking issues rather than inventing placeholders.

Frameworks & tools

This skill is framework-agnostic. It operates on any environment capable of reading and writing Markdown files, such as Claude Code, Cursor, or local file systems.

Why this beats prompting it yourself

Generic prompts often hallucinate dates, soften asks into "FYIs," or include irrelevant status padding like capacity hours and stalled tasks. This skill uses a strict procedure to strip "house" formatting, reject sister-skill artifacts like SOPs or weekly reviews, and ensure no data is invented or leaked from memory.

Use cases

• Briefing an owner on a critical architectural shift and the required approval.
• Summarizing a project risk for a lead after a disruptive technical discovery.
• Creating a one-pager for a specific stakeholder that requires a single decision by a fixed date.

Known limitations

Does not support multi-audience recaps or multiple asks per brief. It requires ISO dates and will not resolve relative terms like EOD or ASAP without a source.