subagent-progress-report

Coordinate sub-agent progress reporting via shared session roots and agent.log files.

13|6|Updated Feb 19, 2025
One-click install
npx skills add https://github.com/Tairitsua/Monica --skill subagent-progress-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-progress-report
Source: https://github.com/Tairitsua/Monica/tree/main/.claude/skills/subagent-progress-report
Command: npx skills add https://github.com/Tairitsua/Monica --skill subagent-progress-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Coordinate progress reporting and supervision between a main agent and spawned sub-agents so the main agent can verify bootstrap, monitor ongoing progress, and recover from quiet or unresponsive children without editing child logs.

Core Features & Use Cases

  • Creates and reuses a single shared session root under the project temporary directory and enforces one per-agent child folder ownership model.
  • Provides scripts to initialize main and sub-agent sessions, prepend timestamped agent.log entries, verify bootstrap, wait for new prepended log entries with exponential backoff, collect summarized status across agents, and mark closed sessions for archival.
  • Use when delegating scoped tasks to sub-agents in runtimes that support spawn/wait/send_input, when you require active frequent logging from children, need non-invasive monitoring, or must follow a patient two-round recovery flow instead of immediate redelegation.

Quick Start

Initialize a shared session root, delegate a sub-agent with a stable agent name that requires subagent-progress-report, have the sub-agent initialize its folder and write its first agent.log entry immediately, and run the included bootstrap checker to confirm readiness.

Frequently Asked Questions about subagent-progress-report

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

FAQPage Schema
How do I monitor sub-agent progress and recovery without editing child logs?

A shared session root with per-agent agent.log files enables non-invasive sub-agent monitoring. Sub-agents prepend timestamped entries while the main agent verifies bootstrap and collects summarized status without editing child logs.

How do I bootstrap spawned sub-agents and verify they are ready?

Initialize a shared session root and require each spawned sub-agent to create a per-agent folder with an initial agent.log entry. Run a bootstrap checker to verify readiness before delegating further tasks.

What is the best way to handle unresponsive sub-agents during task orchestration?

Handle unresponsive sub-agents using a patient two-round recovery flow with exponential backoff waiting for new prepended log entries. This avoids immediate redelegation while monitoring quiet children.

Does sub-agent progress reporting work with standard Python orchestration runtimes?

Sub-agent progress reporting works with runtimes that support spawn, wait, and send_input operations. It requires runtimes capable of supervising spawned sub-agents for delegated tasks and active frequent logging.

How do I archive closed sub-agent sessions after task completion?

Mark completed sessions for archival within the shared .tmp/<timestamp>-agent-session root. The workflow renames closed per-agent directories to preserve task records and finalize the orchestration.