What problem does it solve? After a feature is implemented across multiple spec and plan iterations, documentation becomes fragmented and outdated. This Skill consolidates the entire spec history into a single self-contained final report describing what was actually built, so readers no longer need to dig through superseded design documents. ## Core Features & Use Cases - Final-State Report Generation: Produces a structured Markdown report (What Was Built, Architecture, Usage, Verification, Journey Log) derived from the implemented code rather than the specs. - Spec and Plan Marking: Prepends an idempotent NOTE admonition to each related spec and plan file pointing readers to the final report, without moving or deleting anything. - Workflow Integration: Runs after verification and hands off to the merge step, with frontmatter listing specs, plans, branch, and commit range for tooling. - Use Case: After shipping a multi-iteration feature, invoke this Skill to write reports/<feature-name>.md, mark all related specs as superseded, and commit everything before merging the branch. ## Quick Start Ask the assistant to use the report skill to write the final report for the feature just implemented and verified.
