Generate a periodic adoption report translating system usage into delivery outcomes — time-to-ship, rework reduction, onboarding speed. Formatted for leadership.
Read context/ds-context-guide.md for environment detection and configuration. Read context/output-patterns.md for leadership-audience output conventions.
Generate a periodic adoption report that translates system usage into delivery outcomes. Adoption numbers are context, not the headline — lead with what the system enabled, not how many components were used. Uses industry benchmarks to project ROI.
$ARGUMENTS = optional time period (e.g., "Q1 2026", "last 30 days") or focus area. Default: last 30 days.
Gather adoption data from available sources:
Translate to delivery outcomes using industry benchmarks where team-specific data isn't available:
Contextualize the numbers. "47 components adopted" means nothing alone. Frame as: "47 components in active use across 12 product teams, covering an estimated 73% of common UI patterns and saving approximately X hours of duplicated implementation effort per sprint."
Identify trends — improving, stable, or declining? New teams onboarding? Teams drifting away?
Include 1-3 recommendations for improving outcomes next period.
Follow the report template from output-patterns.md with leadership-audience conventions. Include executive summary, key metrics with trend, and prioritized recommendations.