project-pulse-brief_skill

Overview

This skill curates stakeholder-ready pulse briefs that summarize project portfolio updates, risks, and next steps. It provides a lightweight, repeatable playbook and an editable template you can copy into any document or knowledge base. The focus is on clarity, brevity, and making briefs skimmable for executives.

How this skill works

Collect weekly status inputs from project leads via your project email thread and shared Drive folders. Use the included markdown template to capture highlights, watchlist items, risks, owners, and next steps, then validate completeness with a short checklist. Publish the brief through your normal communication channel and track follow-up actions in a shared tracker.

When to use it

• Weekly or biweekly portfolio status cycles when sponsors need a concise update
• Before executive reviews or steering committee meetings
• When consolidating multiple project updates into a single executive summary
• To capture decision points and required support requests from stakeholders
• When you need a repeatable, low-overhead reporting cadence without integrations

Best practices

• Keep the brief under two pages and limit each section to five items
• List owner, status, recent wins, blockers, and next steps for every project
• Use neutral, objective language and avoid speculation without data
• Validate missing or conflicting information with a quick reply-all or short huddle
• Link to supporting documents for deep dives instead of expanding the brief

Example use cases

• Prepare a one-page portfolio snapshot for a weekly executive email
• Summarize program risks and mitigation owners ahead of a sponsor meeting
• Turn disparate project updates from Drive and email into a single brief
• Provide a concise handout for steering committee decks with links to artifacts
• Create a living brief that tracks follow-up actions across reporting cycles