evolve-report

To generate an evolution report, load your existing state data files including evolution_state.json, assessment.json, analysis.json, plan.json, evolution_log.md, and decisions.md to produce a unified Markdown narrative.

Consolidating decision histories and iteration logs requires reading evolution_log.md and decisions.md alongside state data to output a cohesive report containing executive summaries, findings, and lessons learned.

Yes, you can document product iteration cycles by applying it to existing state data, which processes analysis and assessment files to extract landscape highlights and generate a comprehensive iteration history.

Creating a unified project evolution narrative requires specific state data formats including JSON files for state, assessment, analysis, and plan data, alongside Markdown files for evolution logs and decisions.

The generated evolution report is saved as a Markdown file output to the reports directory, named with a timestamp format like reports/evolution-report-<timestamp>.md.

Yes, this approach works without external dependencies, relying solely on ingesting your local state data files to produce decision-making analysis and recommended next steps.