status-reporting
Skill0 starsChanged 11 days agoMITView on GitHub
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.
4 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- fludo/pm-claude-kittheir own version, first seen Nov 16, 2026
- fabioc-aloha/Alex_ACT_Editionedited, first seen Oct 13, 2026
- aws-solutions/konductortheir own version, first seen Sep 23, 2026
- fabioc-aloha/alex-cognitive-architectureedited, first seen Apr 26, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- fabioc-aloha/Alex_ACT_Edition★ 091% same
- fabioc-aloha/alex-cognitive-architecture★ 085% same
Wrote their own version · 2
- aws-solutions/konductor★ 12same name
- fludo/pm-claude-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/bootstrap-project/resources/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/bootstrap-project/resources/CLAUDE.mdCLAUDE.md
- act-tenetsSkill
- adversarial-reviewSkill
- annotate-screenshotSkill
- anti-hallucinationSkill
- ascii-chartSkill
- assess-brainSkill
- big-ideaSkill
- bootstrap-coreSkill
- bootstrap-projectSkill
- browser-toolsSkill
- chart-big-ideaSkill
- chart-interpretationSkill
- chart-vocabularySkill
- code-reviewSkill
- communication-craftSkill
- compile-brainSkill
- convertSkill
- corpus-qa-sweepSkill
- critical-thinkingSkill
- deep-reviewSkill
- doc-hygieneSkill
- docs-shellSkill
- docx-to-mdSkill
- ethical-reasoningSkill
- evaluate-before-adoptingSkill
- figure-generatorSkill
- flint-chartSkill
- flint-interactionsSkill
- flint-themeSkill
- git-workflowSkill
- html-to-mdSkill
- humanizerSkill
- install-visual-companionsSkill
- lint-clean-markdownSkill
- markdown-mermaidSkill
- markdown-sanitization-chainSkill
- md-to-emlSkill
- md-to-htmlSkill
- md-to-txtSkill
- md-to-wordSkill
- meditationSkill
- mutation-testingSkill
- planSkill
- platform-awarenessSkill
- print-svg-style-guideSkill
- proactive-awarenessSkill
- problem-framing-auditSkill
- project-capability-authoringSkill
- project-statusSkill
- render-chartSkill
- render-verifySkill
- rich-emailSkill
- risk-analysisSkill
- security-and-hardeningSkill
- setup-dependenciesSkill
- setup-enterprise-stackSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 203
If a number cannot be produced by a query, script, or formula, leave the field blank or mark it "not tracked" instead of estimating it.
- Distinctive: line 210
Use consistent formatting across reports
- Distinctive: line 219
Use jargon with non-technical audiences
- Distinctive: line 233
Draft report: Use appropriate template
- Distinctive: line 259
Completeness: All sections filled appropriately
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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]/5Audience 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)
Numbers Come From the Tracker, Not From Counting
Every metric that fills a template field (bugs open/closed, velocity, coverage %) comes from the issue tracker's own count or query output, or from a script run over a tracker export. Quote the returned value. Never tally issues, cards, or commits by eye to fill a field.
Derived values are computed the same way, by a script or spreadsheet formula over the tracker data, never worked out in prose:
- Carry-over = planned − completed (the [Z] in the Sprint Retrospective template)
- % complete = completed ÷ planned × 100
- Timeline impact (days ahead / behind) = the difference between the scheduled date and the forecast date held by the tracker or project plan
If a number cannot be produced by a query, script, or formula, leave the field blank or mark it "not tracked" instead of estimating it.
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-one status → Generate session status
/alex-act-one status weekly → Weekly team update
/alex-act-one status exec → Executive summary
/alex-act-one status email [name] → Stakeholder email draftIntegration 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 if any of the following fires:
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

