agent-progress

To track multi-agent pipeline progress across step transitions, you enforce the creation of standardized status files at a fixed location. This exposes per-step readiness and outcomes to improve debugging and enable reliable recovery after failures.

Standardized statuses for agent pipeline monitoring include PENDING, IN_PROGRESS, COMPLETE, SKIPPED, FAILED, BLOCKED, and RETRYING. Using this defined set ensures consistent data formatting for easy integration with monitoring and observability tools.

Automated pipelines stall without observability because there is no structured tracking to trace behavior or understand delays. Writing per-step progress files at defined locations makes it possible to audit progress, identify stalled runs, and resume work.

To debug stalled multi-agent workflows, you enforce per-step progress files at each step transition. This provides observability across the pipeline, allowing you to trace agent behavior, understand delays, and coordinate recovery.

Yes, you need to create the `.claude/specs/[feature]/agent-status/` directory. Enforcing a fixed file location for your status files ensures consistent data formatting and easy integration with your existing monitoring tools.

Yes, writing structured status files at each step transition enables reliable recovery in automated pipelines. By exposing per-step outcomes with defined statuses like FAILED or BLOCKED, you can trace behavior and resume work after failures.