Use team-status-report

Write a weekly team status report from tracker data (Jira, Linear or GitHub Projects, via CSV, JSON or an MCP tool)

Write a weekly team status report from tracker data (Jira, Linear or GitHub Projects, via CSV, JSON or an MCP tool) — shipped, in progress, blocked with the blocker and owner, slipped against plan, risks and asks — with every number computed from the data by a stdlib script, never estimated, and a RAG status that states the rule that set it.

Reach for it when the user wants a weekly status update, sprint report or stakeholder update from the tracker, or says "write this week's status report", "are we on track?".

Install it

npx skilldrop-cli install team-status-report                 # Claude Code, your user folder
npx skilldrop-cli install team-status-report --project       # Claude Code, this repo
npx skilldrop-cli install team-status-report --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the Trackers pack: --pack trackers installs it with its neighbours.

It ships scripts, so it needs Python 3 (standard library only, nothing to install). What they may touch is declared in its manifest.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "Write this week's status report for the checkout team from the Jira export"
• "Are we on track this sprint? Here's our Linear cycle export, give me shipped, blocked and slipped with a RAG"
• "Turn our GitHub project board into a weekly stakeholder update with risks and asks"
• "End-of-sprint report against what we committed: what shipped, what slipped, who's blocked"

Requests like these belong to a different skill, so it shouldn't answer them:

• "Summarise this 30-page design doc into one page for the exec team"
• "Find the duplicates and stale tickets in our backlog export"
• "Record that we decided to delay Klarna to Q1, with the options we considered"

If another skill answers instead, ask for this one by name: "use team-status-report".

Check what you get

A good result:

• Every number is computed from the data, by the script or a stated count. No "about", no "roughly half", no velocity the data can't support.
• The RAG names its rule and the number that triggered it. Green with no plan says so.
• Blocked items name the blocker and the owner, or say "not recorded".
• Slipped is measured against a stated plan, and unplanned work is shown separately, not folded into completion.
• Facts from outside the tracker are attributed: "3 Oct (security team, per user)".
• Each ask has a who, a what and a when, and points at the item it unblocks.
• Nothing is invented: no dates, causes, owners or blockers the export and the user didn't give.

See a worked example

• northwind weekly status

Use something else when

• Condensing a long document into a one-page summary for executives; use exec-summary
• Cleaning up the backlog itself (duplicates, stale items, ordering); use backlog-triage
• Recording a decision and its rationale; use decision-log

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: backlog-triage, decision-log, exec-summary

Edit this page on GitHub · View source