status-reporting
Skill11 starsChanged 50 days agoApache-2.0View on GitHub
Generates program status reports for stakeholders. Use for weekly updates, executive summaries, or milestone reviews.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- fabioc-aloha/Alex_ACT_Editiontheir own version, first seen Oct 13, 2026
- fabioc-aloha/alex-cognitive-architecturetheir own version, first seen Apr 26, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- fabioc-aloha/Alex_ACT_Edition★ 0same name
- fabioc-aloha/alex-cognitive-architecture★ 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 repository83 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- about-konductorSkill
- adr-generatorSkill
- adversarial-code-review-pass-integritySkill
- adversarial-code-review-pass-schemaSkill
- adversarial-code-review-pass-securitySkill
- adversarial-code-reviewSkill
- adversarial-design-reviewSkill
- agents-md-authoringSkill
- app-discoverySkill
- architecture-advisorSkill
- architecture-diagram-generationSkill
- argumentation-referenceSkill
- asana-sprint-planningSkill
- asdlc-aspect-reviewSkill
- asdlc-code-simplifierSkill
- aws-service-validatorSkill
- backend-developmentSkill
- backend-reviewSkill
- claude-teams-behaviorSkill
- cmux-dispatchSkill
- code-reviewSkill
- constraintsSkill
- cost-estimationSkill
- cypress-test-implementationSkill
- decision-researchSkill
- decision-writingSkill
- delegation-protocolSkill
- deliberation-panelSkill
- design-doc-guidelinesSkill
- design-evaluationSkill
- design-impact-reviewSkill
- design-quality-checkSkill
- doc-accuracy-analyzerSkill
- document-formatsSkill
- dom-inspectionSkill
- dynamodb-designSkill
- dynamodb-validationSkill
- e2e-test-strategySkill
- external-researchSkill
- find-aws-skillsSkill
- frontend-developmentSkill
- frontend-reviewSkill
- git-mergeSkill
- git-workflowSkill
- historical-issues-registrySkill
- humanize-writingSkill
- iam-policy-designSkill
- infra-validationSkill
- kiro-design-generationSkill
- kiro-requirements-generationSkill
- kiro-task-generationSkill
- legacy-to-agentic-estimateSkill
- mux-dispatchSkill
- non-functional-requirementsSkill
- persistent-memorySkill
- plan-reviewSkill
- playwright-test-implementationSkill
- policy-validationSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 16
Use this skill when:
- Distinctive: line 67
No metrics or progress indicators
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Status Reporting
Overview
Generates program status reports in two formats: executive summary (1-page) for leadership and detailed report for program teams. Covers RAG status per workstream, accomplishments, upcoming milestones, blockers, and action items. Pulls data from available project management tools when configured.
Usage
Use this skill when:
- Producing weekly program status updates
- Preparing executive summaries for leadership reviews
- Reporting on milestone completion at phase gates
- Consolidating status across multiple workstreams
Core Concepts
RAG Status
Rate each workstream: Green (on track, no risks), Amber (at risk, mitigation in progress), Red (off track, escalation needed). RAG must be justified — include the specific reason for Amber/Red and the mitigation or escalation action.
Two Report Formats
Executive Summary (1-page): Overall RAG, 3 key accomplishments, 3 upcoming milestones, top blockers, ask/escalation. No detail — decisions only. Detailed Report: Per-workstream RAG, task-level progress, metrics (velocity, burn-down), full blocker list, action items with owners and due dates.
Data Sources
Pull from available project management tools (Asana MCP if configured): task completion %, sprint velocity, overdue items, blocker tickets. If unavailable, prompt user for: completed items this period, planned items next period, blockers, and risks.
Output Format — Executive Summary
- Program Name & Date — report period
- Overall RAG — single status with one-line justification
- Key Accomplishments — 3-5 bullet points, outcome-focused
- Upcoming Milestones — next 2 weeks, with dates and owners
- Blockers & Risks — top items with owner and mitigation
- Ask / Escalation — what you need from leadership (or "None")
Output Format — Detailed Report
- Workstream Status Table — columns: Workstream, RAG, % Complete, Key Update, Next Milestone, Blocker
- Accomplishments — per workstream, with links to artifacts/PRs
- Metrics — sprint velocity, burn-down trend, scope changes
- Action Items Table — columns: Action, Owner, Due Date, Status, Notes
- Risks & Issues — link to RAID log (risk-management skill)
- Next Period Plan — key deliverables for next reporting period
Quality Gate
CRITICAL (must fix):
- RAG status without justification
- Blockers listed without owner or mitigation
- Report period or date missing
IMPORTANT (should fix):
- Action items missing due dates
- No metrics or progress indicators
- Accomplishments describe activities not outcomes
SUGGESTION:
- Could add trend arrows (improving/stable/declining) per workstream
- Could include week-over-week RAG comparison
Present findings as: CRITICAL → IMPORTANT → SUGGESTION. Ask: "Fix these issues? [y/n]" — unless scope_confirmed is true, in which case report all the findings and leave fixing to the caller, without asking.
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.

