team-status

Generates a read-only snapshot of agent team health, releases, and escalations.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/witwave-ai/witwave --skill team-status-witwave-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-status
Source: https://github.com/witwave-ai/witwave/tree/main/.agents/self/zora/.claude/skills/team-status
Command: npx skills add https://github.com/witwave-ai/witwave --skill team-status-witwave-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running a multi-agent autonomous development team, it is hard to quickly answer "what is the team doing right now?" without manually checking git logs, CI runs, and each agent's memory files. This Skill aggregates all of that state into a single structured status report on demand. ## Core Features & Use Cases - Per-peer health summary: Reports each peer agent's status, last fired skill, open backlog count, and any escalations. - Release state tracking: Shows the latest tag, commits since tag, CI status on main, and the last release pipeline conclusion. - Escalation and decision visibility: Lists recent dispatch decisions with rationales and any open escalations, plus hard-cap usage for dispatches, releases, and batch-reverts. - Use Case: A human operator asks "what's the team doing?" and receives a structured markdown snapshot covering release state, peer activity, recent decisions, and open escalations without triggering any dispatches or state changes. ## Quick Start Ask the agent "give me a team status report" to receive a read-only snapshot of peer health, release state, and open escalations.

Frequently Asked Questions about team-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the status of an autonomous agent team?▼

Invoke the team-status skill by asking for a team status report. It reads git history, CI workflow runs, each peer's memory index, and the decision log, then returns a structured markdown snapshot of the team's current state.

What information does a team status report include?▼

The report covers release state (latest tag, commits since tag, CI status), a per-peer table with last activity and backlog counts, the last six dispatch decisions with rationales, open escalations, and hard-cap usage for dispatches and releases.

Does the team status check dispatch agents or change state?▼

No, the skill is strictly read-only. It does not dispatch peers, modify memory files, or invoke other skills. Dispatching is handled separately by the dispatch-team skill during heartbeat ticks.

When should I use team-status instead of dispatch-team?▼

Use team-status when a human asks for a report on team activity, such as "what's the team doing?" Use dispatch-team from the heartbeat when the system needs to evaluate state and actually assign work to peers.

What data sources does the status snapshot read from?▼

It reads git log for commits and tags, gh run list for recent CI workflow runs, each peer's MEMORY.md index and deferred-findings backlog, the orchestrator's decision_log.md, and pause_mode.flag to report observation-only mode.