Pantheon Epic Retrospective

Automate an epic retrospective by orchestrating an analysis of all build artifacts from completed stories to identify cross-story patterns and generate actionable improvement suggestions for development workflows.

Cross-story pattern identification in epic analysis detects recurring issues or successes across multiple completed stories within a single epic by analyzing build logs, review findings, and progress metrics.

Generate CLAUDE.md patches and playbook updates by running an automated retrospective on completed epic artifacts, which analyzes build logs and review findings to produce specific documentation proposals.

Yes, analyzing build logs, review findings, progress metrics, and reflections from completed stories pinpoints common causes of bugs or delays and suggests specific changes to development workflows and documentation.

Automated artifact analysis for process optimization relies entirely on the quality of build logs and review findings provided; it cannot identify issues or suggest workflow improvements if the input artifacts lack sufficient detail.

Run an automated retrospective on a completed epic immediately upon epic completion to refine development workflows, update documentation, and generate process improvement suggestions based on the final build artifacts.