sprint-status

Reports running, idle, crashed, or completed states of dev-team sessions across registered repos.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/apireno/agent-workflow-template --skill sprint-status-apireno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-status
Source: https://github.com/apireno/agent-workflow-template/tree/main/.claude/skills/sprint-status
Command: npx skills add https://github.com/apireno/agent-workflow-template --skill sprint-status-apireno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When orchestrating multiple AI dev-team sessions across a fleet of repositories, it is hard to know which sessions are still running, which have crashed, and which have finished without manually inspecting each repo. This Skill aggregates per-repo Phase 2 session state into a single at-a-glance status table. ## Core Features & Use Cases - Fleet Registry Parsing: Reads the active repo registry at .cto/projects.yaml and lists every active repository with its path. - Session State Detection: Classifies each repo as RUNNING, IDLE, CRASHED, COMPLETE, or no-session by inspecting .claude session marker files and JSONL transcript activity timestamps. - Actionable Summary: Flags crashed repos with a /resume-dev-team suggestion, stalled idle sessions, and completed repos ready for sprint acceptance. - Use Case: A CTO agent is asked "how are the dev teams doing?" mid-sprint; the Skill scans all registered repos and returns a table showing two repos running, one crashed, and one complete, along with recommended next commands. ## Quick Start Ask the agent "what's the sprint status across my dev-team repos?" to get a fleet-wide session snapshot.

Frequently Asked Questions about sprint-status

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

FAQPage Schema
How do I check the status of multiple AI dev-team sessions at once?

Run the sprint-status skill, which reads the fleet registry at .cto/projects.yaml and inspects each repo's .claude session markers. It prints a table classifying every repo as RUNNING, IDLE, CRASHED, COMPLETE, or no-session.

How does the skill detect a crashed dev-team session?

It checks for a CRASHED marker file inside the repo's .claude directory. When present, the repo is reported as CRASHED with a note suggesting /resume-dev-team to recover the session.

What does the skill need to find the fleet registry?

It resolves a CTO home directory containing .cto/projects.yaml by checking CTO_HOME, CTO_REPO, CLAUDE_PROJECT_DIR, walking up from the working directory, and reading ~/.cto/home. If none validate, it fails with a diagnostic naming the rejected candidates.

Why does sprint-status report no-session for a repo?

A repo shows no-session when it lacks a .claude/current-session.id file, meaning no Phase 2 dev-team session has been tracked there. This is normal between sprints or before rollout.

Can I use this with repos not listed in the registry?

No. Only repos marked active in .cto/projects.yaml are scanned. Unregistered or inactive repos are skipped, so add them to the registry first if you want them monitored.