leadership-summary·reporting·active
Leadership Summary
Renders the final report in three formats: 30-second exec brief, 5-minute manager read, full engineering deep-dive — without rewriting content.
ARIAtrigger · agent
Leadership Summary
Renders the final report in three formats: 30-second exec brief, 5-minute manager read, and full engineering deep-dive — without rewriting content.
When this skill fires
·ARIA finishes synthesis, trends, and recommendations
·A user explicitly requests a specific format:
aria report --format=exec·A scheduled report fires (e.g. end-of-sprint)
The three formats
30-second exec brief
For board members, founders, executive sponsors. Three lines:
·Verdict (one sentence:"Quality is steady; one critical action required this sprint")
·Top action (one sentence with owner + effort)
·Trend (improving / stable / degrading + the dominant signal)
That's the entire format. No tables, no charts, no metrics. The brief either compels a 5-minute read or doesn't.
5-minute manager read
For engineering managers, VP eng, product leads. Adds:
·The 3–5 prioritized signals fromCross-Agent Synthesizer
·Each recommendation fromRecommendation Drafter with effort + impact
·A trend chart per top-level metric
·Open questions that need a manager decision (resourcing, scope tradeoffs)
This is the version that drives sprint-planning and 1:1 conversations.
Full engineering deep-dive
For engineers acting on the report. Adds:
·Every finding with full evidence (viaEvidence Capture)
·Per-test, per-endpoint, per-finding tables
·Raw metric time-series for the relevant window
·Direct links to runs, scenarios, code lines, tracker tickets
This is the artifact engineering reads when actually fixing things.
Same content, different rendering
→ARIA does not write the report three times. It writes it once, with structured data, andLeadership Summary picks the right slices for each audience.
This matters because:
·The exec brief and the deep-dive say the same thing — what differs is depth, not direction
·An engineer drilling from the exec brief to the deep-dive sees thesame finding, just with more detail
·Updates propagate automatically when underlying data changes
Format conventions
Exec brief
·Plain prose, no bullets
·One color (no severity heatmaps; the prose carries severity)
·Maximum 80 words
Manager read
·Headed sections
·Bullets for prioritized signals
·Compact charts; no chart sprawl
·Always 1 page printed
Deep-dive
·Hierarchical
·Direct links to source data
·Code snippets where relevant
·Length unbounded but indexed
What it produces
Three rendered documents in the chosen format (Markdown, HTML, or PDF), all tied back to the same underlying ARIA run ID. A reader of any version can request a deeper version with one click — same content, more depth.
→This is the skill that makes ARIA a credibility tool, not just a dashboard. The brief is what gets cited; the deep-dive is what makes the brief defensible.