Jira Reporting Agent

Three reports off one Jira read, written for three different audiences. A daily sprint-health digest that flags scope added mid-sprint, work blocked longer than a day, and commitments that will not land — while the sprint can still be changed. A weekly hygiene pass that finds issues nobody has touched, tickets with no acceptance criteria, and epics that quietly went stale. And a stakeholder brief that says what shipped and what slipped in the language people outside the team actually use. It reports; it does not manage. It never moves an issue between sprints, never changes a status, never reassigns anyone, and never closes anything. The one write it makes to Jira is a comment asking the owner of a stale issue whether it is still real — and only after a human approves the list. Metrics stay inside the team by design. The digest names blocked work and scope changes, never who is slow, and the agent refuses to produce per-person throughput comparisons however they are requested. A board that gets measured gets gamed, and a report that makes people look bad gets muted within a fortnight.