Team Status Reporting

Your agent queries the tracker and produces status reports, dashboards, bottleneck findings and retrospective metrics, showing its counts and saying when data is missing.

Used by our operations team

What It Does

Produces four reports from live tracker data: a team status report, a cross-team dashboard, a bottleneck analysis and a sprint retrospective. Each metric has a stated method. Bottlenecks come from days in stage and blocker age. Retrospective numbers come from sprint tags, creation and completion dates, and the blocking notes. When the data needed for a number is missing, the report says so instead of estimating.

It only reads. It never changes a task.

Who Uses It

Team leads for daily and weekly status, coordinators for the cross-team view, and everyone at the end of a sprint.

Setup

1. Install and set up task-ops first. This skill requires it. Follow its backend/SETUP.md.
2. Copy the skill/ folder into your agent's skills folder as reporting-ops, for example .claude/skills/reporting-ops/. Or fetch it through the Thinqmesh MCP server.
3. In task-ops, edit references/team-config.md: teams, capacity and the stale and stuck thresholds.
4. Make sure TASK_OPS_URL and TASK_OPS_KEY are set, as described in the task-ops setup.
5. For retrospectives, tag sprint tasks with Sprint: <id> in notes and record blockers as Blocked <date>: <reason> and Unblocked <date>. sprint-ops and task-ops do this for you.

Example Result

Bottleneck Report, 2026-03-09

Stage congestion
  Test      6 tasks, average 7.5 days in stage   <- likely bottleneck
  Build     4 tasks, average 3 days in stage

Overloaded teams
  Design    active 11, capacity 10, ratio 1.1

Long blockers
  Engineering #12, blocked 6 days (waiting on sandbox keys)

Recommendations
  Add a second reviewer for Test, or move two Build tasks to next sprint.

How to Adapt

• Change the stale and stuck thresholds and the capacity figures in task-ops's references/team-config.md.
• Add or remove report types in SKILL.md. Each one is a query plus a grouping.
• Change the cadence table to your meeting rhythm.