---
name: team-status-report
description: Generate a status/standup report for the data team from the shared task list, recent PRs, and QA verdicts — shipped, in-flight, blocked, and QA-pending — as a Markdown digest, optionally posted to ClickUp or Slack. Operates on work items only, no client data.
disable-model-invocation: true
argument-hint: "[scope, e.g. 'today' | 'this sprint' | repo path]"
---

# Team status report

Produce a concise progress digest for the data team — what shipped, what's in flight, what's blocked, what's waiting on QA — from the signals the team already produces: the shared task list, recent PRs, and the QA gate's verdicts. Useful as a standup, a sprint check-in, or a client-facing update (after a human pass).

`$ARGUMENTS` may name the scope (e.g. `today`, `this sprint`, `since last report`) and/or the repo.

Run this from the **lead / main session** if you want to post the digest to ClickUp/Slack (that needs credentials). Generating the Markdown itself needs no credentials.

## What it reads

- **Shared task list** (`TaskList` / `TaskGet`) — task subjects, discipline tags, status, owners, dependency edges, `prio:`/`due:` tags, and any `QA-PASS:` tokens.
- **Recent PRs** (`gh pr list`, `gh pr view`) — open/merged in scope, their review state, and the originating ticket links.
- **QA verdicts** — `QA-PASS:` tokens on tasks and the `qa-auditor`'s findings; tasks lacking sign-off are "QA-pending".

This skill reports on **work items**, not data — it never reads or echoes client data, query results, or note content. It's safe on either connection.

## Output

A Markdown digest with these sections (omit any that are empty):

- **Shipped** — tasks completed / PRs merged in scope, grouped by discipline (`de`/`ae`/`da`/`ds`), each with its ticket + PR link.
- **In flight** — in-progress tasks with owner and current PR state.
- **Blocked** — tasks whose dependency is still open, naming the blocker; plus anything explicitly flagged blocked.
- **QA-pending** — work done but not yet `QA-PASS:`-signed, or blocked by the connection-mode gate (off-Bedrock).
- **Up next** — the lead's sequenced top of the backlog (dependency → `prio:` → `due:`), so readers see what's coming.
- **Risks / needs a decision** — `prio:unset` tickets, overdue `due:` dates, anything awaiting a user call.

Keep it scannable: short bullets, links over prose, counts in the section headers (e.g. `## Shipped (4)`).

## Steps

1. Resolve scope from `$ARGUMENTS` (default: since the last report, or today).
2. Pull the task list and recent PRs; join PRs to tasks via the ticket link.
3. Bucket each item into the sections above using status, review state, and QA tokens.
4. Render the Markdown digest.
5. **Optionally post it** — if the user asks, post to the configured ClickUp doc/Slack channel (lead-only, tool-agnostic). Otherwise just print it for the user to copy.

## Boundaries

- **Work items only** — no client data, query results, or raw note content in the report.
- **Don't fabricate progress** — if a task's state is ambiguous, say so; report what the task list and PRs actually show.
- **Posting is opt-in and lead-only** — generating the digest is always safe; posting needs the main session's credentials.
- **Secrets policy** — never read, request, or echo credential values.