What problem does it solve? Writing weekly status reports by hand means digging through task folders, PRs, meeting notes, and project state files, then translating engineering detail into audience-appropriate prose without fabricating or overstating progress. This Skill automates that evidence gathering and enforces a strict no-fabrication, no-engineering-jargon writing process. ## Core Features & Use Cases - Evidence-first reporting: Builds a Phase A evidence table from TasksSummary files, per-task folders, meeting summaries, ProjectState, and live gh pr queries before writing any prose. - Audience-configurable voice: Reads config_hints.json to match tone and detail level for executives, engineering leads, or product teams, stripping branch names, ticket numbers, and PR chatter from management copy. - Defensible classification: Applies a fixed decision matrix (Shipped, Development Done, In progress, Concerns, Next) based on merge target, deploy confirmation, and mock/stub state, with a multi-step self-review before saving. - Use Case: On a Friday, ask for the weekly report and receive a saved Markdown report where every claim traces to a this-week source, carried-forward items are accounted for, and mocked dependencies are explicitly disclosed. ## Quick Start Say "ar-weekly-report" or "weekly report" to generate this week's evidence-grounded status report for the configured audience.
