project-retrospective

To synthesize learnings from multiple epics, you can aggregate findings from individual epic-retro files to detect recurring themes, successful strategies, and common pitfalls across the project. This process validates patterns and mines commits to generate a comprehensive project-retro report.

Identifying systemic issues and recurring gotchas involves analyzing project-level artifacts and epic summaries to validate cross-epic patterns. Reviewing methodology effectiveness helps detect common pitfalls and propose concrete process improvements for future development.

You propose methodology updates by synthesizing project retrospective insights to review effectiveness and identify systemic issues. This generates a project-retro report that optionally proposes concrete improvements to development processes, templates, and commands.

You need a project retrospective after completing several epics for a feature to understand if architectural patterns were beneficial or if specific gotchas keep reappearing. It aggregates learnings to inform how your methodology should evolve for future projects.

Yes, you can analyze project commits to extract learning tags for process improvement. Mining project commits for these tags helps validate cross-epic patterns and review methodology effectiveness, which directly informs the generated retrospective report.