What problem does it solve? Product documentation drifts from reality when reports are written from plans instead of code. This Skill produces a durable, product-level PRD (docs/product/ateam-product-report.md) whose shipped-status verdicts are grounded in the final integrated code, not in intentions or completed tickets. ## Core Features & Use Cases - Code-grounded scope table: Indexes every epic with its MoSCoW class, jobs served, and an implemented/partial/not-implemented verdict backed by concrete code evidence. - Acceptance and milestone reporting: Reports requirement acceptance from the obligations ledger and all six independent feature milestones (implementation, verification, human acceptance, integration, release, product validation) without ever certifying them. - Durable update-only refresh: Runs at the end of an A-Team run's pr phase or standalone, preserving prior content, growing the decision log, and keeping every citation and artifact link resolvable. - Use Case: After a feature run integrates and before the PR opens, invoke this Skill to refresh the product report so reviewers see what the product actually is and how much of it is real. ## Quick Start Ask the agent to refresh the product report for the current run so docs/product/ateam-product-report.md reflects what actually shipped.
