Writing Final Reports

Overview

Consolidate a feature's spec history into a single human-readable final report. The report presents the final implemented state as its primary content — what WAS BUILT, not what was tried. A brief Journey Log at the end captures notable failures and pivots for future designers.

Core principle: Final state first. The reader should understand the feature from this report alone, without reading any spec.

Announce at start: "I'm using the report skill to write the final report for this feature."

Save reports to: the reports/ directory given in the <compose_docs_dir> block of your prompt, as <feature-name>.md

• No date in filename — the report is overwritten in place when the feature evolves
• Git history tracks revisions
• User preferences for report location override this default

Update Semantics