docs-activity-summary-reporting

What problem does it solve?

Capture end-of-work context and decisions for stories, bugs, requests, features, and other tracked activities in a concise, durable format so reviewers and future contributors can understand what happened without replaying chat logs or hunting through artifacts.

Core Features & Use Cases

• Generate a structured, nine-section markdown activity summary that records request, outcome, performed work, artifacts, main changes, decisions, open questions, skills used, and next steps.
• Persist the report to execution-plan/reports/activity-summaries/, slugify the filename, timestamp the record, and append a backlink to the source activity frontmatter when present for two-way traceability.
• Support preview mode, idempotent backlink updates, and commit-ready output to make handoffs, reviews, paused work, and completions discoverable and auditable.

Quick Start

Create an activity summary for activity ID US-042 titled Implement user authentication with status completed, list performed work and artifacts, and save the report to execution-plan/reports/activity-summaries/.