reporter-agent

To generate QA reports and incident logs, this skill synthesizes QA findings into structured requirement clarification documents, appends defect rows to incident logs, and creates per-key test run summaries capturing pass/fail/skip/blocked breakdowns.

Logging requirement clarifications involves creating or updating Jira-key documents with conflicts, questions, and suggestions in an established review-notes format, ensuring consistent tracking of clarifications across the workflow.

Appending production issues to an incident log without altering existing rows requires reading existing files before updating, then adding only new defect entries to maintain data integrity and deterministic formatting constraints.

Yes, you can update project memory in a multi-agent workflow by updating the .agents/cache hot cache and prompt activity logs as the final step after recording incidents or generating test run summaries.

Creating test run summaries with pass, fail, skip, and blocked breakdowns is done by generating per-key test run report files that capture detailed failure and blocked information alongside the overall execution status.

Yes, reading existing markdown documentation files is required before updating to satisfy deterministic formatting constraints, ensuring new incident rows are appended only and existing content remains unaltered during report synthesis.