Skip to content

Packs

Trackers

When to use it
For leads and PMs who run work in Jira, Linear or GitHub Projects: load a PRD into the tracker, triage the backlog, write the weekly status report, and check the tracker still matches the doc, all from an export or an MCP tool, with the numbers computed rather than estimated.
Covers
Build and review software (2), Explain it to decision makers (1)
Where you decide
No gated loop of its own; the skills run one at a time.
Size
8 skills · 0 loops
About 20 minutes for the import, then 10 to 15 minutes a week a session
npx skilldrop-cli install --pack trackers

Installs 8 skills, including core.

Other ways to install

The pack's loops too, each as an invokable skill:

npx skilldrop-cli install --loop --pack trackers

In Claude Code, as a plugin (after /plugin marketplace add sananthanarayan/skilldrop):

/plugin install trackers@skilldrop

Into Cursor, Kiro or another IDE:

npx skilldrop-cli install --pack trackers --ide cursor

Start here: Triage your backlog before the next refinement session

Paste this into your agent:

Here's our backlog exported from Jira: ./backlog.csv. Refinement is Thursday. Find the duplicates, tell me what isn't ready to pull and why, and propose an order for what we take next. Anything without an update in 30 days counts as stale.
Before you start
  • A CSV or JSON export of your backlog from Jira, Linear or GitHub, or a tracker MCP tool installed
  • Python 3.9 or later, for the counting scripts
How to tell it worked
backlog-triage runs its script and reports exact counts (duplicate pairs, items with no owner or no acceptance criteria, stale and oversized items), names each duplicate pair with why they match, gives a reason for every position in the ordering, and ends with a change list you can apply.
If nothing happens
If the counts say "n/a", the script didn't find a column: rerun it with --map, e.g. --map owner="Team Lead". If backlog-triage doesn't activate, ask for it by name ("use backlog-triage").

A typical session

When: A PRD has been agreed and the work is about to live in the tracker for weeks, and you want the tracker, the backlog and the weekly update to stay honest. About About 20 minutes for the import, then 10 to 15 minutes a week.

You bring:

  1. tracker-brief-sync
    You
    Hand over the PRD and name your tracker.
    You get
    A checked import file (Jira CSV, mapped CSV or gh commands) with one epic per goal and one story per requirement, each with acceptance criteria and a link back to its section.
    You decide
    Import as is, or adjust the mapping first.
  2. backlog-triage
    You
    Before refinement, give it a fresh export of the backlog.
    You get
    Exact counts, confirmed duplicate pairs, what isn't ready and why, priority conflicts, a reasoned ordering and a change list.
    You decide
    Which changes to apply, and who owns the unowned items.
  3. team-status-report
    You
    Each week, give it the export, the period, the plan, and anything the tracker doesn't show about blockers.
    You get
    A one-screen report: shipped, in progress, blocked with blocker and owner, slipped against plan, risks and asks, with a RAG status and the rule that set it.
  4. tracker-brief-sync
    You
    Mid-build or before launch, give it the PRD and a fresh export.
    You get
    A drift report: requirements with no issue, issues with no requirement, issues pointing at removed sections, and issues for Won't-have items, each with both ways to resolve it.
    You decide
    Change the tracker, or change the doc.

You end with: A tracker that traces back to the PRD, a groomed backlog, a weekly report built from counted numbers, and a record of where the plan and the work have drifted apart.

Compare Trackers with another pack

Skills in this pack (3)

Included from core (5)