Skip to content

Skills · trackers

team-status-report

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. Use 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?".

Pack trackersTier standardJob Explain it to decision makersv0.1.4

npx skilldrop-cli install team-status-report
Other ways to install

With the sibling skills it hands off to:

npx skilldrop-cli install team-status-report --with-related

The whole pack it belongs to:

npx skilldrop-cli install --pack trackers

By hand, from a clone of the repo:

cp -R packs/trackers/skills/team-status-report ~/.claude/skills/

In Claude Code, with the trackers plugin installed, invoke it as:

/trackers:team-status-report

Try it

A realistic prompt from the skill's acceptance evals:

Weekly status for the Northwind checkout team, 24-30 Sept, for our head of e-commerce. Export is examples/northwind-week-40.csv. SEC-88 is the security team's pen-test report; they say it lands 3 Oct. API-412 is the platform team's endpoint, no date yet.

What a good result looks like

Example output

Example: Northwind checkout, week ending 30 September · the skill's own worked example, source

Worked example

The user's message:

Weekly status for the checkout team, 24–30 Sept, for Dana (head of e-commerce) and the payments steering group. Export attached: northwind-week-40.csv. Context the export doesn't have: SEC-88 is the security team's pen-test report, which the PCI questionnaire needs; they told us it lands 3 Oct. API-412 is the platform team's paginated order-history endpoint, no date yet. Black Friday code freeze is 6 Nov.

The export is northwind-week-40.csv: 15 Jira issues with Resolved, Due date and Inward issue link (Blocks) columns. There's no sprint file, so the plan is "items due in the period".

Step 1: run the script

python3 scripts/status_counts.py examples/northwind-week-40.csv \
  --from 2026-09-24 --to 2026-09-30 -o status-numbers.md --json status-numbers.json

Step 2: the script's output, unedited

# Status numbers: 2026-09-24 to 2026-09-30

Source: northwind-week-40.csv · 15 items · plan: items due between 2026-09-24 and 2026-09-30
Columns used: key='Issue key', title='Summary', status='Status', owner='Assignee', priority='Priority', created='Created', updated='Updated', resolved='Resolved', due='Due date', blocker='Inward issue link (Blocks)', labels='Labels'

## Suggested RAG: Red

Rule: Red if plan completion < 60% or >= 2 planned items blocked; Amber if completion < 85%, any planned item blocked, or a High-or-above planned item slipped; otherwise Green.
- Red: plan completion 50% is below 60%
- Amber: 1 planned item is blocked
- Amber: 3 High-or-above planned item(s) slipped: CHK-102, CHK-107, CHK-119

| Measure | Count |
|---|---:|
| Shipped in period | 5 |
| In progress | 4 |
| Blocked | 2 |
| Planned to finish by 2026-09-30 | 8 |
| Planned and done | 4 (50%) |
| Slipped (planned, not done) | 4 |
| Shipped but not in plan | 1 |

## Shipped

| Key | Title | Owner | Done |
|---|---|---|---|
| CHK-103 | Apple Pay button missing on Safari 17 | Lena Fischer | 2026-09-29 |
| CHK-105 | Show delivery date estimate on the cart page | Lena Fischer | 2026-09-26 |
| CHK-113 | Add fraud score to order admin view | Tom Okafor | 2026-09-25 |
| CHK-121 | Discount line rounds to wrong penny on mixed-VAT carts | Marco Rossi | 2026-09-24 |
| CHK-122 | Rotate PSP API keys | Tom Okafor | 2026-09-28 |

## In progress

| Key | Title | Owner | Status |
|---|---|---|---|
| CHK-102 | Save card for future purchases | Tom Okafor | In Review |
| CHK-112 | One-click reorder from order history | Aisha Bello | In Progress |
| CHK-116 | Persist cart across devices for signed-in users | Lena Fischer | In Progress |
| CHK-125 | Load test checkout for Black Friday | Marco Rossi | In Progress |

## Blocked

| Key | Title | Owner | Blocker | Last update |
|---|---|---|---|---|
| CHK-107 | Update PCI self-assessment questionnaire | Aisha Bello | SEC-88 | 2026-09-30 |
| CHK-123 | Order history pagination | Marco Rossi | API-412 | 2026-09-22 |

## Slipped (planned, not done by 2026-09-30)

| Key | Title | Owner | Status | Priority | Due |
|---|---|---|---|---|---|
| CHK-102 | Save card for future purchases | Tom Okafor | In Review | High | 2026-09-30 |
| CHK-107 | Update PCI self-assessment questionnaire | Aisha Bello | Blocked | Highest | 2026-09-30 |
| CHK-116 | Persist cart across devices for signed-in users | Lena Fischer | In Progress | Medium | 2026-09-30 |
| CHK-119 | Accessibility fixes on the payment form | (none) | To Do | High | 2026-09-30 |

## Risk candidates

- CHK-107 (Update PCI self-assessment questionnaire): planned for this period and blocked
- CHK-119 (Accessibility fixes on the payment form): planned for this period with no owner
- CHK-114 (Klarna pay-later option): top priority (Highest) and not started

## Work in progress by owner (in progress + blocked)

| Owner | Items |
|---|---:|
| Aisha Bello | 2 |
| Marco Rossi | 2 |
| Lena Fischer | 1 |
| Tom Okafor | 1 |

Step 3: the report

Every number is from the output above. The blocker descriptions and dates come from the user's message, and are marked where the export didn't have them.

# Checkout team status: 24–30 September 2026

**Status: Red.** Rule: plan completion below 60% is Red. We finished 4 of the 8 items due this
week (50%). One of the four that slipped is blocked; three are High or Highest priority.

## Shipped (5)

- CHK-113 Fraud score in the order admin view (Tom Okafor), 25 Sep
- CHK-105 Delivery date estimate on the cart page (Lena Fischer), 26 Sep
- CHK-122 Rotated PSP API keys (Tom Okafor), 28 Sep
- CHK-103 Apple Pay button fixed on Safari 17 (Lena Fischer), 29 Sep
- CHK-121 Discount rounding fix on mixed-VAT carts (Marco Rossi), 24 Sep. Unplanned: came in
  as a bug on 23 Sep.

## Slipped against plan (4 of 8 due)

| Item | Owner | Where it is | Priority |
|---|---|---|---|
| CHK-107 PCI self-assessment questionnaire | Aisha Bello | Blocked by SEC-88 | Highest |
| CHK-102 Save card for future purchases | Tom Okafor | In review | High |
| CHK-119 Accessibility fixes on the payment form | No owner | Not started | High |
| CHK-116 Persist cart across devices | Lena Fischer | In progress | Medium |

No new dates are given here: the export has none, and the owners haven't supplied them.

## Blocked (2)

| Item | Owner | Blocked by | Expected |
|---|---|---|---|
| CHK-107 PCI questionnaire | Aisha Bello | SEC-88, the security team's pen-test report | 3 Oct (security team, per user) |
| CHK-123 Order history pagination | Marco Rossi | API-412, the platform team's paginated endpoint; no update since 22 Sep | No date |

## In progress (4)

CHK-102 Save card (in review), CHK-112 One-click reorder, CHK-116 Persist cart, CHK-125
Black Friday load test (due 16 Oct).

## Risks

- **CHK-119 accessibility fixes have no owner and were due this week.** It's High priority
  and hasn't started.
- **CHK-114 Klarna is Highest priority and not started,** with no owner.
- **The Black Friday code freeze is 6 Nov** (per user). CHK-125's load test is due 16 Oct, which
  leaves three weeks to act on what it finds.

## Asks

1. **Security team:** confirm SEC-88 lands on 3 Oct, so CHK-107 can be finished.
2. **Platform team:** a date for API-412. CHK-123 has been waiting since 22 Sep.
3. **Dana:** name an owner for CHK-119 this week.
4. **Dana:** confirm CHK-114 Klarna is still Highest. Nobody is assigned to it.

What the report left out: a "% on track" or velocity figure (the export can't support one), a reason for CHK-102 sitting in review (not in the data), and new dates for the slipped items (none given).

How it's checked

Measured against plain Claude Code (2026-10-23): it met 83% of its checks, against 42% without it, and a blind judge preferred it. How skills are checked

27 assertions across 4 acceptance evals, and 7 trigger queries. Every skill's checks

What the output must do
  • Every count (shipped, in progress, blocked, planned, slipped) matches the script's output for the export, not an estimate
  • States a RAG colour together with the rule and the number that set it
  • Each blocked item names its blocker and its owner
  • Slipped items are measured against a stated plan source (here, items due in the period)
  • Unplanned shipped work (CHK-121) is shown separately and not counted toward plan completion
  • Attributes the 3 Oct date to the security team via the user rather than presenting it as tracker data
  • Each ask names who, what and by when
  • Does not invent new dates, causes or blockers not in the export or the prompt
  • Notices there is no plan source and asks for one (a key list or milestone) or states that slipped vs plan cannot be computed
  • Does not present a Green status as 'on track' when there is no plan; says the status reflects blockers only
  • Counts shipped from closedAt within the period
  • Writes 'blocker not recorded' or asks, rather than guessing what blocks an item
  • Does not invent velocity or percentage-complete figures
  • Reports 8 items shipped in 12-16 Oct, not 9, because LP-307 was resolved on 9 Oct
  • Separates the 2 unplanned items (LP-309, LP-314) from the planned work, with 6 of the 11 Wk42 items done
  • Reports the five items due this week and not done (LP-303, LP-305, LP-306, LP-310, LP-312)
  • Names the typesetting pass (LP-310) as what blocks LP-305, and says no blocker is recorded for LP-306 rather than guessing one
  • Attributes the 30 Oct printer date to Tomasz rather than the tracker, and notes that the tracker still shows 23 Oct
  • Does not give a velocity comparison or any figure that cannot be computed from the export, and says the data does not cover last month
  • Stays under 250 words
  • Is three or four sentences long
  • Reports the raffle prizes as 6 of 15 and the cake rota as half filled, without changing the numbers
  • Says the hall booking is stuck waiting on the caretaker
  • Says the float money has not been started
  • Does not invent dates, names or numbers, such as the fair date or who is doing what
  • Uses plain wording for a volunteer committee, with no project-management jargon
  • Delivers the update without asking questions first
When it should and shouldn't activate

Should activate:

  • 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

Should leave to another skill:

  • 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

Related skills

backlog-triage, decision-log, exec-summary

Source

SKILL.md · the whole folder on GitHub.