Status Reporting Skill
Generate clear, audience-appropriate project status updates. Transform technical progress into stakeholder-friendly communication.
Core Philosophy
"Stakeholders don't need to know HOW you did it — they need to know WHAT it means for them."
Status reports serve different audiences with different needs:
- Executives: Impact, risk, timeline
- Managers: Progress, blockers, resources
- Teams: Details, dependencies, next steps
- Customers: Value delivered, what's coming
Report Templates
Executive Summary (30 seconds)
## Project Status: [Project Name]
**Date**: [Date] | **Status**: 🟢 On Track / 🟡 At Risk / 🔴 Blocked
### One-Line Summary
[Single sentence: what happened and what it means]
### Key Metrics
| Metric | Current | Target | Trend |
|--------|---------|--------|-------|
| [Metric 1] | [Value] | [Goal] | ↑/↓/→ |
| [Metric 2] | [Value] | [Goal] | ↑/↓/→ |
### Decisions Needed
- [ ] [Decision 1 with deadline]
### Timeline Impact
[On schedule / X days ahead / X days behind — why]
Weekly Team Update
## Week of [Date Range]
### Completed ✅
- [Achievement 1] — [impact]
- [Achievement 2] — [impact]
### In Progress 🔄
- [Task 1] — [% complete, ETA]
- [Task 2] — [% complete, ETA]
### Blocked 🚫
- [Blocker] — need [resolution] from [who] by [when]
### Next Week Focus
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
### Metrics
- Velocity: [X] story points
- Bugs: [X] open, [Y] closed
- Coverage: [X]%
### Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| [Risk] | H/M/L | H/M/L | [Action] |
Stakeholder Email
Subject: [Project] Status — [Date] — [Status Emoji]
Hi [Name],
**Quick Summary**: [One sentence on where we are]
**This Week's Wins**:
• [Win 1 — business impact]
• [Win 2 — business impact]
**Coming Up**:
• [Next milestone] — [Date]
• [Key deliverable] — [Date]
**Need Your Input On**:
• [Decision needed] — [Context, options, recommendation]
Happy to jump on a call if you have questions.
[Sign-off]
Sprint Retrospective Summary
## Sprint [N] Retrospective
### What Went Well 🎉
- [Positive 1]
- [Positive 2]
### What Could Improve 🔧
- [Improvement 1]
- [Improvement 2]
### Action Items
| Action | Owner | Due |
|--------|-------|-----|
| [Action] | [Who] | [When] |
### Sprint Metrics
- Planned: [X] points | Completed: [Y] points
- Carry-over: [Z] items
- Team satisfaction: [Score]/5
Audience Adaptation
Language Translation
| Technical Term |
Executive Translation |
| "Refactored the authentication module" |
"Improved security and login reliability" |
| "Reduced technical debt" |
"Reduced maintenance costs and risk" |
| "Implemented CI/CD pipeline" |
"Automated our release process — faster, safer updates" |
| "Fixed race condition" |
"Resolved intermittent bug causing data issues" |
| "Migrated to microservices" |
"Made the system more scalable and reliable" |
Detail Levels
| Audience |
Detail Level |
Focus On |
| C-Suite |
Minimal |
Business impact, risks, decisions |
| VP/Director |
Summary |
Progress, resources, timeline |
| Manager |
Moderate |
Tasks, blockers, team health |
| Team |
Detailed |
Technical specifics, dependencies |
| Customer |
Outcome |
Value delivered, what's next |
Status Indicators
Traffic Light System
| Status |
Symbol |
Meaning |
Action |
| Green |
🟢 |
On track, no issues |
Continue |
| Yellow |
🟡 |
At risk, needs attention |
Monitor closely |
| Red |
🔴 |
Blocked, needs escalation |
Immediate action |
| Blue |
🔵 |
Complete |
Celebrate |
| Gray |
⚪ |
Not started |
Plan |
Trend Indicators
| Symbol |
Meaning |
| ↑ |
Improving |
| ↓ |
Declining |
| → |
Stable |
| ⚠️ |
Needs attention |
Automation Triggers
When to Generate Status
| Trigger |
Report Type |
| End of day Friday |
Weekly summary |
| Sprint end |
Sprint report |
| Before stakeholder meeting |
Executive summary |
| Milestone completion |
Achievement update |
| Blocker encountered |
Escalation notice |
| User asks "what did we do" |
Session/period summary |
Data Sources
Pull information from:
- Git commits and PR descriptions
- Issue tracker (completed, in-progress, blocked)
- Calendar (milestones, deadlines)
- Session history (what we worked on)
- Metrics dashboards (if available)
Best Practices
DO ✅
- Lead with the most important information
- Use consistent formatting across reports
- Include specific dates and numbers
- Highlight decisions needed
- Acknowledge blockers honestly
- Show progress, not just activity
DON'T ❌
- Bury bad news
- Use jargon with non-technical audiences
- Include unnecessary detail
- Report activity without outcomes
- Over-promise on timelines
- Skip risk assessment
Session Protocol
Generating a Status Report
- Clarify audience: Who will read this?
- Determine scope: What period? What project?
- Gather data: Commits, issues, conversations
- Identify highlights: What matters most?
- Draft report: Use appropriate template
- Adapt language: Match audience level
- Review for clarity: Can a newcomer understand?
Quick Status Commands
/alex-act-core status → Generate session status
/alex-act-core status weekly → Weekly team update
/alex-act-core status exec → Executive summary
/alex-act-core status email [name] → Stakeholder email draft
Integration Points
Triggers for This Skill
- "status update", "status report"
- "what did we accomplish", "summarize progress"
- "stakeholder update", "email to [stakeholder]"
- "sprint report", "weekly summary"
- End of day/week (proactive)
Metrics
- Clarity score: Can reader understand in 30 seconds?
- Completeness: All sections filled appropriately
- Accuracy: Numbers and dates verified
- Audience fit: Language matches recipient
Would Revise If
Revisit this skill by 2026-08-26 (90 days) or sooner if any of the following fires:
- Stakeholder feedback reports the templates as unclear, jargon-heavy, or missing decisions-needed sections ≥3 times within a quarter
- The audience-adaptation table produces tone mismatches when applied verbatim ≥2 times in observed reports
- Reports generated via these templates consistently bury bad news or miss escalation triggers that surface later as preventable surprises
Good status reports build trust. Great ones prevent surprise.
1---2name: status-reporting-43description: "Create stakeholder-friendly project status updates and progress reports. Use when writing a status update, progress report, weekly or milestone recap, release summary, or any stakeholder-facing account of where work stands."4lastReviewed: 2026-05-265metadata:6 source: https://skillmd.com/skills/fabioc-aloha/status-reporting-47---89# Status Reporting Skill1011Generate clear, audience-appropriate project status updates. Transform technical progress into stakeholder-friendly communication.1213## Core Philosophy1415> "Stakeholders don't need to know HOW you did it — they need to know WHAT it means for them."1617Status reports serve different audiences with different needs:1819- **Executives**: Impact, risk, timeline20- **Managers**: Progress, blockers, resources21- **Teams**: Details, dependencies, next steps22- **Customers**: Value delivered, what's coming2324## Report Templates2526### Executive Summary (30 seconds)2728```markdown29## Project Status: [Project Name]30**Date**: [Date] | **Status**: 🟢 On Track / 🟡 At Risk / 🔴 Blocked3132### One-Line Summary33[Single sentence: what happened and what it means]3435### Key Metrics36| Metric | Current | Target | Trend |37|--------|---------|--------|-------|38| [Metric 1] | [Value] | [Goal] | ↑/↓/→ |39| [Metric 2] | [Value] | [Goal] | ↑/↓/→ |4041### Decisions Needed42- [ ] [Decision 1 with deadline]4344### Timeline Impact45[On schedule / X days ahead / X days behind — why]46```4748### Weekly Team Update4950```markdown51## Week of [Date Range]5253### Completed ✅54- [Achievement 1] — [impact]55- [Achievement 2] — [impact]5657### In Progress 🔄58- [Task 1] — [% complete, ETA]59- [Task 2] — [% complete, ETA]6061### Blocked 🚫62- [Blocker] — need [resolution] from [who] by [when]6364### Next Week Focus651. [Priority 1]662. [Priority 2]673. [Priority 3]6869### Metrics70- Velocity: [X] story points71- Bugs: [X] open, [Y] closed72- Coverage: [X]%7374### Risks & Mitigations75| Risk | Likelihood | Impact | Mitigation |76|------|------------|--------|------------|77| [Risk] | H/M/L | H/M/L | [Action] |78```7980### Stakeholder Email8182```markdown83Subject: [Project] Status — [Date] — [Status Emoji]8485Hi [Name],8687**Quick Summary**: [One sentence on where we are]8889**This Week's Wins**:90• [Win 1 — business impact]91• [Win 2 — business impact]9293**Coming Up**:94• [Next milestone] — [Date]95• [Key deliverable] — [Date]9697**Need Your Input On**:98• [Decision needed] — [Context, options, recommendation]99100Happy to jump on a call if you have questions.101102[Sign-off]103```104105### Sprint Retrospective Summary106107```markdown108## Sprint [N] Retrospective109110### What Went Well 🎉111- [Positive 1]112- [Positive 2]113114### What Could Improve 🔧115- [Improvement 1]116- [Improvement 2]117118### Action Items119| Action | Owner | Due |120|--------|-------|-----|121| [Action] | [Who] | [When] |122123### Sprint Metrics124- Planned: [X] points | Completed: [Y] points125- Carry-over: [Z] items126- Team satisfaction: [Score]/5127```128129## Audience Adaptation130131### Language Translation132133| Technical Term | Executive Translation |134|----------------|----------------------|135| "Refactored the authentication module" | "Improved security and login reliability" |136| "Reduced technical debt" | "Reduced maintenance costs and risk" |137| "Implemented CI/CD pipeline" | "Automated our release process — faster, safer updates" |138| "Fixed race condition" | "Resolved intermittent bug causing data issues" |139| "Migrated to microservices" | "Made the system more scalable and reliable" |140141### Detail Levels142143| Audience | Detail Level | Focus On |144|----------|--------------|----------|145| **C-Suite** | Minimal | Business impact, risks, decisions |146| **VP/Director** | Summary | Progress, resources, timeline |147| **Manager** | Moderate | Tasks, blockers, team health |148| **Team** | Detailed | Technical specifics, dependencies |149| **Customer** | Outcome | Value delivered, what's next |150151## Status Indicators152153### Traffic Light System154155| Status | Symbol | Meaning | Action |156|--------|--------|---------|--------|157| **Green** | 🟢 | On track, no issues | Continue |158| **Yellow** | 🟡 | At risk, needs attention | Monitor closely |159| **Red** | 🔴 | Blocked, needs escalation | Immediate action |160| **Blue** | 🔵 | Complete | Celebrate |161| **Gray** | ⚪ | Not started | Plan |162163### Trend Indicators164165| Symbol | Meaning |166|--------|---------|167| ↑ | Improving |168| ↓ | Declining |169| → | Stable |170| ⚠️ | Needs attention |171172## Automation Triggers173174### When to Generate Status175176| Trigger | Report Type |177|---------|-------------|178| End of day Friday | Weekly summary |179| Sprint end | Sprint report |180| Before stakeholder meeting | Executive summary |181| Milestone completion | Achievement update |182| Blocker encountered | Escalation notice |183| User asks "what did we do" | Session/period summary |184185### Data Sources186187Pull information from:188189- Git commits and PR descriptions190- Issue tracker (completed, in-progress, blocked)191- Calendar (milestones, deadlines)192- Session history (what we worked on)193- Metrics dashboards (if available)194195## Best Practices196197### DO ✅198199- Lead with the most important information200- Use consistent formatting across reports201- Include specific dates and numbers202- Highlight decisions needed203- Acknowledge blockers honestly204- Show progress, not just activity205206### DON'T ❌207208- Bury bad news209- Use jargon with non-technical audiences210- Include unnecessary detail211- Report activity without outcomes212- Over-promise on timelines213- Skip risk assessment214215## Session Protocol216217### Generating a Status Report2182191. **Clarify audience**: Who will read this?2202. **Determine scope**: What period? What project?2213. **Gather data**: Commits, issues, conversations2224. **Identify highlights**: What matters most?2235. **Draft report**: Use appropriate template2246. **Adapt language**: Match audience level2257. **Review for clarity**: Can a newcomer understand?226227### Quick Status Commands228229```230/alex-act-core status → Generate session status231/alex-act-core status weekly → Weekly team update232/alex-act-core status exec → Executive summary233/alex-act-core status email [name] → Stakeholder email draft234```235236## Integration Points237238### Triggers for This Skill239240- "status update", "status report"241- "what did we accomplish", "summarize progress"242- "stakeholder update", "email to [stakeholder]"243- "sprint report", "weekly summary"244- End of day/week (proactive)245246## Metrics247248- **Clarity score**: Can reader understand in 30 seconds?249- **Completeness**: All sections filled appropriately250- **Accuracy**: Numbers and dates verified251- **Audience fit**: Language matches recipient252253## Would Revise If254255Revisit this skill by **2026-08-26** (90 days) or sooner if any of the following fires:256257- Stakeholder feedback reports the templates as unclear, jargon-heavy, or missing decisions-needed sections ≥3 times within a quarter258- The audience-adaptation table produces tone mismatches when applied verbatim ≥2 times in observed reports259- Reports generated via these templates consistently bury bad news or miss escalation triggers that surface later as preventable surprises260261---262263*Good status reports build trust. Great ones prevent surprise.*