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
/status → Generate session status
/status weekly → Weekly team update
/status exec → Executive summary
/status email [name] → Stakeholder email draft
Integration Points
With Other Skills
- proactive-assistance: Offer status prep at end of day
- scope-management: Include scope health in reports
- alex-effort-estimation: Include timeline projections
- project-management: Pull from project tracking
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
Related Skills
- proactive-assistance — Trigger status prep proactively
- scope-management — Include scope health
- project-management — Project tracking context
- executive-storytelling — Advanced narrative techniques
Good status reports build trust. Great ones prevent surprise.
1---2name: "status-reporting"3description: "Create stakeholder-friendly project status updates and progress reports"4tier: standard5applyTo: '**/*status*,**/*report*,**/*update*'6currency: 2026-04-227metadata:8 source: https://skillmd.com/skills/fabioc-aloha/status-reporting9---1011# Status Reporting Skill1213Generate clear, audience-appropriate project status updates. Transform technical progress into stakeholder-friendly communication.1415## Core Philosophy1617> "Stakeholders don't need to know HOW you did it — they need to know WHAT it means for them."1819Status reports serve different audiences with different needs:20- **Executives**: Impact, risk, timeline21- **Managers**: Progress, blockers, resources22- **Teams**: Details, dependencies, next steps23- **Customers**: Value delivered, what's coming2425## Report Templates2627### Executive Summary (30 seconds)2829```markdown30## Project Status: [Project Name]31**Date**: [Date] | **Status**: 🟢 On Track / 🟡 At Risk / 🔴 Blocked3233### One-Line Summary34[Single sentence: what happened and what it means]3536### Key Metrics37| Metric | Current | Target | Trend |38|--------|---------|--------|-------|39| [Metric 1] | [Value] | [Goal] | ↑/↓/→ |40| [Metric 2] | [Value] | [Goal] | ↑/↓/→ |4142### Decisions Needed43- [ ] [Decision 1 with deadline]4445### Timeline Impact46[On schedule / X days ahead / X days behind — why]47```4849### Weekly Team Update5051```markdown52## Week of [Date Range]5354### Completed ✅55- [Achievement 1] — [impact]56- [Achievement 2] — [impact]5758### In Progress 🔄59- [Task 1] — [% complete, ETA]60- [Task 2] — [% complete, ETA]6162### Blocked 🚫63- [Blocker] — need [resolution] from [who] by [when]6465### Next Week Focus661. [Priority 1]672. [Priority 2]683. [Priority 3]6970### Metrics71- Velocity: [X] story points72- Bugs: [X] open, [Y] closed73- Coverage: [X]%7475### Risks & Mitigations76| Risk | Likelihood | Impact | Mitigation |77|------|------------|--------|------------|78| [Risk] | H/M/L | H/M/L | [Action] |79```8081### Stakeholder Email8283```markdown84Subject: [Project] Status — [Date] — [Status Emoji]8586Hi [Name],8788**Quick Summary**: [One sentence on where we are]8990**This Week's Wins**:91• [Win 1 — business impact]92• [Win 2 — business impact]9394**Coming Up**:95• [Next milestone] — [Date]96• [Key deliverable] — [Date]9798**Need Your Input On**:99• [Decision needed] — [Context, options, recommendation]100101Happy to jump on a call if you have questions.102103[Sign-off]104```105106### Sprint Retrospective Summary107108```markdown109## Sprint [N] Retrospective110111### What Went Well 🎉112- [Positive 1]113- [Positive 2]114115### What Could Improve 🔧116- [Improvement 1]117- [Improvement 2]118119### Action Items120| Action | Owner | Due |121|--------|-------|-----|122| [Action] | [Who] | [When] |123124### Sprint Metrics125- Planned: [X] points | Completed: [Y] points126- Carry-over: [Z] items127- Team satisfaction: [Score]/5128```129130## Audience Adaptation131132### Language Translation133134| Technical Term | Executive Translation |135|----------------|----------------------|136| "Refactored the authentication module" | "Improved security and login reliability" |137| "Reduced technical debt" | "Reduced maintenance costs and risk" |138| "Implemented CI/CD pipeline" | "Automated our release process — faster, safer updates" |139| "Fixed race condition" | "Resolved intermittent bug causing data issues" |140| "Migrated to microservices" | "Made the system more scalable and reliable" |141142### Detail Levels143144| Audience | Detail Level | Focus On |145|----------|--------------|----------|146| **C-Suite** | Minimal | Business impact, risks, decisions |147| **VP/Director** | Summary | Progress, resources, timeline |148| **Manager** | Moderate | Tasks, blockers, team health |149| **Team** | Detailed | Technical specifics, dependencies |150| **Customer** | Outcome | Value delivered, what's next |151152## Status Indicators153154### Traffic Light System155156| Status | Symbol | Meaning | Action |157|--------|--------|---------|--------|158| **Green** | 🟢 | On track, no issues | Continue |159| **Yellow** | 🟡 | At risk, needs attention | Monitor closely |160| **Red** | 🔴 | Blocked, needs escalation | Immediate action |161| **Blue** | 🔵 | Complete | Celebrate |162| **Gray** | ⚪ | Not started | Plan |163164### Trend Indicators165166| Symbol | Meaning |167|--------|---------|168| ↑ | Improving |169| ↓ | Declining |170| → | Stable |171| ⚠️ | Needs attention |172173## Automation Triggers174175### When to Generate Status176177| Trigger | Report Type |178|---------|-------------|179| End of day Friday | Weekly summary |180| Sprint end | Sprint report |181| Before stakeholder meeting | Executive summary |182| Milestone completion | Achievement update |183| Blocker encountered | Escalation notice |184| User asks "what did we do" | Session/period summary |185186### Data Sources187188Pull information from:189- 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 ✅198- Lead with the most important information199- Use consistent formatting across reports200- Include specific dates and numbers201- Highlight decisions needed202- Acknowledge blockers honestly203- Show progress, not just activity204205### DON'T ❌206- Bury bad news207- Use jargon with non-technical audiences208- Include unnecessary detail209- Report activity without outcomes210- Over-promise on timelines211- Skip risk assessment212213## Session Protocol214215### Generating a Status Report2162171. **Clarify audience**: Who will read this?2182. **Determine scope**: What period? What project?2193. **Gather data**: Commits, issues, conversations2204. **Identify highlights**: What matters most?2215. **Draft report**: Use appropriate template2226. **Adapt language**: Match audience level2237. **Review for clarity**: Can a newcomer understand?224225### Quick Status Commands226227```228/status → Generate session status229/status weekly → Weekly team update230/status exec → Executive summary231/status email [name] → Stakeholder email draft232```233234## Integration Points235236### With Other Skills237- **proactive-assistance**: Offer status prep at end of day238- **scope-management**: Include scope health in reports239- **alex-effort-estimation**: Include timeline projections240- **project-management**: Pull from project tracking241242### Triggers for This Skill243- "status update", "status report"244- "what did we accomplish", "summarize progress"245- "stakeholder update", "email to [stakeholder]"246- "sprint report", "weekly summary"247- End of day/week (proactive)248249## Metrics250251- **Clarity score**: Can reader understand in 30 seconds?252- **Completeness**: All sections filled appropriately253- **Accuracy**: Numbers and dates verified254- **Audience fit**: Language matches recipient255256---257258## Related Skills259260- [proactive-assistance](..\proactive-assistance/SKILL.md) — Trigger status prep proactively261- [scope-management](..\scope-management/SKILL.md) — Include scope health262- [project-management](..\project-management/SKILL.md) — Project tracking context263- [executive-storytelling](..\executive-storytelling/SKILL.md) — Advanced narrative techniques264265---266267*Good status reports build trust. Great ones prevent surprise.*