What problem does it solve? Teams running ICEA-driven development accumulate audit files, trackers, and ledgers per story, but have no consolidated view of quality trends, revision depth, or recurring issues across a release. This Skill aggregates those scattered artefacts into two shareable reports. ## Core Features & Use Cases - Dual-format reporting: Produces a Markdown report with Mermaid diagrams for repos and wikis, plus a self-contained HTML report with inline Chart.js for offline stakeholder sharing. - Per-story and aggregate metrics: Parses ai-audit.md, tracker.md, icea.md, and code-review/security ledgers to compute revision counts, phase durations, follow-ups, build issues, rework rate, and optional token usage. - Trend and lessons analysis: Compares against previous release reports for trend deltas and synthesizes recurring lessons-learned themes into a Pareto chart. - Use Case: After completing Release 3, run the metrics command to get an executive summary table, quality radar, and lessons mindmap covering all ADOs in the release. ## Quick Start Ask the assistant to generate release metrics by saying "METRICS RELEASE-3" or request lessons learned for a specific release and sprint.
