status-update

Generate audience-specific project status updates from a single data source.

33|10|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/andreaswasita/copilot-cowork-dojo --skill status-update-andreaswasita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status-update
Source: https://github.com/andreaswasita/copilot-cowork-dojo/tree/main/skills/status-update
Command: npx skills add https://github.com/andreaswasita/copilot-cowork-dojo --skill status-update-andreaswasita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams spend hours drafting separate status updates for executives, the team, and sponsors, often duplicating data and missing context. This Skill automates audience-specific progress reporting to save time and improve clarity.

Core Features & Use Cases

  • Audience-tuned updates: generate distinct updates for exec, team, and stakeholders.
  • Diff-driven reporting: pull last-week data and surface only the changes.
  • Clear asks and outcomes: always include a concrete ask and highlight progress, blockers, and risks.

Quick Start

Provide last week's status data and key metrics to generate three audience-specific updates.

Frequently Asked Questions about status-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate project status updates for executives and stakeholders?

Diff-based status updates extract changes from last week's project data to surface only relevant progress, blockers, and risks. This mechanism prevents duplicating data and ensures stakeholders receive concise, audience-tailored updates without manual comparison.

How do I prepare steerco status updates quickly from a single data source?

Audience-tuned status updates produce three distinct drafts from a single data source, individually structured for executives, team members, and stakeholders. This approach enforces a structured workflow with audience-specific templates, diff-based updates, and a mandatory ask.

Can I generate separate project updates for my team and sponsors without duplicating data?

Generating audience-tuned status updates requires providing last week's status data and key metrics as input. The process requires no external dependencies or components, using this single data source to automatically produce the three audience-specific drafts.

What is the best way to include a mandatory ask in stakeholder communications?

Audience-tuned updates distinguish themselves from standard project reporting by applying diff-driven analysis to surface only recent changes and enforcing a mandatory ask in every draft. This structured workflow produces three tailored narratives from a single data source.

Does automated status reporting work for monthly cadences and sponsor communications?

Automated status reporting requires a single data source containing last week's status data and key metrics to function correctly. Without this baseline input, the diff-analysis mechanism cannot surface changes or generate the three audience-tuned drafts.