What problem does it solve? Preparing for a Sprint Review ceremony means manually pulling completed issues, checking Definition of Done compliance, auditing mid-sprint scope creep, and formatting an agenda or release notes — repetitive administrative work this Skill automates against the Jira REST and Agile APIs. ## Core Features & Use Cases - Sprint data compilation: Fetches sprint metadata and all issues (paginated, with changelog) and normalizes them into a JSON document classifying done vs. open work via localization-safe status categories. - Scope creep audit: Detects issues added to the sprint after its start date by inspecting changelog events, and reports committed vs. mid-sprint velocity separately. - DoD compliance check: Flags Done issues missing a resolution or QA approval with inline warnings, without blocking the agenda. - Two output formats: Renders the same data as a three-section sprint review agenda or as stakeholder-facing release notes. - Use Case: Before your sprint review, ask the agent to prepare the agenda — it resolves the active sprint, compiles the data, and produces a markdown agenda with velocity metrics, shipped increments, uncompleted work, and a scope creep audit. ## Quick Start Ask the agent to prepare the sprint review agenda for the active sprint on your Jira board, or pass a specific sprint ID to generate release notes instead.
