agent-reporter

Automate progress reporting by reading internal pipeline state from a progress.md file and applying predefined templates to format user-facing updates. The system extracts milestone and subtask status to deliver real-time reports after each pipeline stage.

Blocker escalation in automated reporting is handled by immediately surfacing blockers when detected during state reads. The system prioritizes critical blockers over standard milestone updates to ensure users are alerted without waiting for pipeline completion.

Yes, a progress.md file is required to generate real-time pipeline updates. The reporting system reads this file to extract current milestone and subtask statuses before formatting and delivering the user-facing progress report.

Generate end-of-pipeline summaries by invoking the reporting agent after pipeline completion. It reads the final state from progress.md and produces a concise summary of all milestones, subtasks, and resolved blockers.

Yes, you can use predefined templates to ensure consistent formatting across multiple agents. The reporting system applies these templates automatically when reading progress state to standardize user-facing updates.

Avoid using an automated progress reporting agent if your workflow lacks a progress.md state file or does not follow a milestone-driven pipeline. The system requires structured internal state data to format updates and escalate blockers.