track-status
Skill1 starsChanged 3 months agoMITView on GitHub
Produce a status report — RAG health with reason and action, progress, velocity/burndown, milestone status, and an updated RAID log. Use for regular reporting or an on-demand health check. Dispatches delivery-monitor then comms-lead. Supports optional tool sync.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-business-caseSkill
- build-roadmapSkill
- capture-feedbackSkill
- close-projectSkill
- coordinate-programSkill
- define-metricsSkill
- define-strategySkill
- design-dashboardSkill
- elicit-requirementsSkill
- groom-backlogSkill
- make-deliverableSkill
- manage-changeSkill
- manage-resourcesSkill
- plan-capacitySkill
- plan-launchSkill
- plan-portfolio-automationSkill
- plan-projectSkill
- plan-sprintSkill
- powerbiSkill
- prioritizeSkill
- review-okrsSkill
- review-portfolio-intakeSkill
- run-ceremonySkill
- run-discoverySkill
- run-gate-reviewSkill
- setup-pmoSkill
- track-financialsSkill
- track-portfolioSkill
- write-prdSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
Start from templates/status-report.md.
- Very specific: line 41
If knowledge/integrations.md configures Slack/Notion, offer to post the formatted status there.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
/track-status — Where things stand
When to use
Regular status cadence, or an on-demand "how are we doing?" health check.
Dispatches
delivery-monitor (gather + analyze) → comms-lead (format for the audience).
Inputs
Project/sprint plans, knowledge/backlog.md, knowledge/roadmap.md, knowledge/raid-log.md,
knowledge/cadence.md, knowledge/financials.md (cost baseline and actuals),
knowledge/change-log.md (approved scope changes), knowledge/governance.md (escalation thresholds),
velocity history.
Steps
- Roll up progress: milestone/sprint status, velocity trend, burndown/burnup, scope changes. Where a cost
baseline exists in
knowledge/financials.md, add earned-value indices (SPI/CPI) for an objective read on progress; where it doesn't, say "earned value unavailable — no cost baseline" rather than approximating one. - Compute RAG per workstream with a reason and an action — never a bare color.
- Detect anomalies/emerging risks (slipping critical path, rising burnup ceiling, stalled items); update
knowledge/raid-log.mdwith owners, respecting the ownership rule stated in that file — add entries and update Score/Status, but never overwrite an owner's Response. Escalate perknowledge/governance.md. - Have
comms-leadformat the report for the target audience (lead with decisions/help needed).
Methods
knowledge/methods/project-management.md, knowledge/methods/agile-scrum-mechanics.md,
standards/communication-standards.md (RAG discipline, status template).
Output
Start from templates/status-report.md. Save to
knowledge/status/YYYY-MM-DD-<project-or-team>-status.md, with an updated knowledge/raid-log.md. Where the
report is circulated to stakeholders, the formatted version goes to knowledge/deliverables/. Follow
standards/document-standards.md and standards/communication-standards.md.
Optional sync
If knowledge/integrations.md configures Slack/Notion, offer to post the formatted status there. Files
remain source of truth; skip if not configured.
Created by Colin Beck<br>
LinkedIn: https://www.linkedin.com/in/beckcolin/<br>
GitHub: https://github.com/link7373
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.

