skills.rest
dazzaji
dazzajiCOMMUNITY
Explore all skills by this author →
Website𝕏@dazzagreenwoodGitHub

sprint-overseer

Automate periodic sprint health checks and log progress to an overseer log.

9|Updated Apr 2, 2026
Search Tags:#logging#multi-agent#tmux#sprint#progress#overseer#nudges
One-click install
npx skills add https://github.com/dazzaji/interlateral_agents --skill sprint-overseer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-overseer
Source: https://github.com/dazzaji/interlateral_agents/tree/main/.claude/skills/sprint-overseer
Command: npx skills add https://github.com/dazzaji/interlateral_agents --skill sprint-overseer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Periodically inspect sprint health by monitoring a sprint lead and worker sessions, classify progress, and log results beside the sprint file.

Core Features & Use Cases

  • Periodic health checks of sprint work and evidence files.
  • Contextual nudges to the sprint lead when stalls are detected.
  • Joint coordination for final closeout when the team signals completion.

Quick Start

Start the sprint overseer by providing the sprint file path and initial configuration.

Frequently Asked Questions about sprint-overseer

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

FAQPage Schema
How do I automate sprint health checks for multi-agent sessions?▼

Set up a periodic health check by providing a sprint file path and configuration, which monitors worker sessions and evidence artifacts to determine on-track or stalled status and logs results beside the sprint file.

How do I get contextual nudges when a multi-agent sprint stalls?▼

Contextual nudges are sent to the sprint lead when the periodic health check detects stalled progress in worker sessions or missing evidence artifacts during the sprint.

Can I coordinate sprint closeout with a team using tmux?▼

Yes, joint coordination for final closeout is triggered when the team signals completion using configured stop or done markers within the sprint directory.

What do I need to start monitoring long-running sprints?▼

You need a sprint file path to start monitoring, with optional manager session and stop or done markers to track worker sessions and evidence artifacts.

When should I avoid using an automated sprint overseer?▼

Avoid using an automated sprint overseer for short-lived or single-agent tasks, as it is designed for long-running multi-agent sprints requiring periodic progress classification.

Related Skills

Explore More Product & Management Skills→
thavirak-svaythavirak-svay
1

bmad-sprint-planning

Parse epic files to generate and maintain sprint-status.yaml tracking.

Community
Intermediate
jackspacejackspace
16

cloudflare-images

Upload, store, and transform images via the Cloudflare Images API.

Community
Advanced
mistakeknotmistakeknot
3

intermux

Monitor tmux sessions for agent status, health, and activity logs.

Community
Intermediate
MichaelSolatiMichaelSolati

sprint-status

Reads sprint plans and story files to compile sprint progress metrics.

Community
Intermediate