apm-5-check-reports

Scans APM Report Buses and processes pending Task Reports for Manager review.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill apm-5-check-reports-zk-theory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apm-5-check-reports
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/apm-5-check-reports
Command: npx skills add https://github.com/ZK-Theory/TDL --skill apm-5-check-reports-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In an APM (Agentic Project Management) workflow, Workers deliver Task Reports to file-based Report Buses, and the Manager needs a reliable way to discover, read, and process all pending reports without manually checking each bus directory. ## Core Features & Use Cases - Targeted Bus Checks: Accepts optional agent-id arguments to check specific Workers' Report Buses, resolving agent IDs per the APM communication skill. - Full Bus Scan: Without arguments, scans all Report Buses in a single terminal invocation, flags unexpected content from non-dispatched Workers, and reports when no pending reports exist. - Stage Reconciliation: Before treating a final report as Stage-completing, reconciles every Plan Task and milestone gate against accepted, deferred, superseded, or removed work, blocking Stage collapse on unresolved scope. - Use Case: A Manager agent finishes dispatching three Workers and invokes this command to batch-read their Report Buses, process each Task Report per the task review procedure, and verify the Stage is truly complete. ## Quick Start Invoke the check-reports command as the APM Manager, optionally passing Worker agent IDs, to scan the Report Buses and process any pending Task Reports.

Frequently Asked Questions about apm-5-check-reports

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

FAQPage Schema
How do I check pending Task Reports in an APM workflow?

Invoke the check-reports command as the Manager agent. Without arguments it scans all Report Buses under .apm/bus in one terminal invocation; with agent-id arguments it reads only those Workers' report.md files.

What happens when check-reports is run with no arguments?

It scans every Report Bus, reads non-empty ones with path markers, and cross-references them against active dispatches. Unexpected content from non-dispatched Workers is flagged to the User, and empty buses produce a no-pending-reports notice.

Can non-Manager agents use the check-reports command?

No. Planners, Workers, and other non-APM agents must concisely decline and take no action. The command is restricted to the APM Manager role.

Why does check-reports block Stage completion?

It blocks Stage collapse when Plan Tasks or milestone gates lack an accepted, deferred, superseded, or removed state. Absence from the Tracker or Task Logs counts as unresolved scope, not removal, so the User is informed instead.

How are agent IDs resolved when checking specific Workers?

Each agent-id argument is resolved per section 4.2 Agent ID Resolution in the apm-communication skill, then all targeted Report Buses are batch-read in a single terminal invocation.