Skill

amoa-progress-monitoring

Monitors AI agent progress on GitHub issues via state transitions, detects stalls, sends reminders, escalates unresponsive tasks, handles blockers, and verifies completions.

Github

monitoring

git-workflow

npx claudepluginhub emasoft/ai-maestro-orchestrator-agent

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Monitors agent progress via state transitions, detects stalls, and escalates issues.

Supporting Assets

references/blocker-handling-protocol.mdreferences/escalation-and-messaging.mdreferences/monitoring-examples.mdreferences/op-detect-agent-state.mdreferences/op-handle-blocker-report.mdreferences/op-handle-reassignment.mdreferences/op-query-progress-dashboard.mdreferences/op-resolve-blocker.mdreferences/op-send-first-reminder.mdreferences/op-send-urgent-reminder.mdreferences/op-verify-task-completion.md

SKILL.md

Similar Skills

amoa-task-distribution

Distributes GitHub tasks to AI agents by priority, dependencies, availability, skills, and load using labels and AI Maestro messaging. For task assignment requests.

14 files

ai-maestro-orchestrator-agent

status

342

Renders AgentOps workflow dashboard via /status, showing ratchet/task status, epics, learnings count, git state, recent activity, inbox, and session signals. Use for quick project overviews.

1 file4 tools

agentops

check-team-worldai-workstreams

Checks status of worldai-workstreams team agents across workstreams 1-5, reports done/running/stuck agents, new git commits, and sqlite beads created.

claude-commands

Stats

Stars10

Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Progress Monitoring Skill

Overview

Monitors agent progress via state transitions, detects stalls, and escalates issues.

Prerequisites

Requires AGENT_OPERATIONS.md, amoa-label-taxonomy, amoa-messaging-templates, AI Maestro API, GitHub CLI.

Instructions

States: Acknowledged, No ACK, Active, No Progress, Stale, Unresponsive, Blocked, Complete. Transitions: Assigned→Acknowledged→Active→Complete. Stalls: No Progress→Stale→Unresponsive.

Query status:in-progress issues; determine each agent's state via timestamps
No ACK/No Progress/Stale → send reminder or status request
Unresponsive → escalate; Blocked → create type:blocker issue, notify user
Complete → verify PR, tests, review, docs; update labels

Copy this checklist and track your progress:

Query in-progress issues and determine agent states
Send reminders/escalate as needed per state
Verify completions and update labels

Output

State report table (task, agent, state, last update) + escalation messages + blocker issues.

Examples

Error Handling

Escalate: reminder→urgent→reassignment. Blockers→type:blocker issues. See references/monitoring-examples.md.

Resources

references/blocker-handling-protocol.md
- Iron Rule for Blockers
- Comprehensive Blocker Definition
- Blocker Response Protocol
- Update Labels and Create Blocker Issue
- Resolution
- When Blocker Resolved
- Blocker Lifecycle Checklist
references/escalation-and-messaging.md
- Escalation Order
- First Reminder
- Urgent Reminder
- Reassignment Decision
- Progress Report Format
  - Status Update
  - Completion Report
  - Blocker Report
- Completion Verification
  - Verification Checklist
  - If Verification Passes
  - If Verification Fails
references/monitoring-examples.md
- Example 1: Query Agent State via AI Maestro
- Example 2: Send First Reminder
- Example 3: Escalate to Urgent
- Example 4: Handle Blocker Report
- Example 5: Verify Completion
- Dashboard Queries
- Error Handling