retrospective

Automating a post-sprint code review requires spawning parallel agents to verify process compliance and analyze code quality. This skill generates a comprehensive report, applies fixes, and updates project learnings based on the sprint's output.

Verifying development principles like DDD and TDD after a sprint is done through automated auditing. The skill checks code robustness, dependency injection design, and test coverage to ensure adherence to these specified development workflows.

An automated retrospective integrates process lessons by recording insights directly into project memory. After analyzing code quality and process compliance, it updates project learnings to provide actionable insights for the next sprint.

Yes, you can run a retrospective on a specific git branch. The skill handles optional branch name arguments to target the retrospective analysis directly against the code changes made in that specific branch.

No, you do not need to manually select models for the auditor and researcher agents. The skill ensures explicit model selection internally for all spawned agent tasks, handling the configuration automatically.

Limitations when checking process compliance involve relying on the explicit model selection for agent tasks. The automated auditing verifies adherence to defined principles like DRY, but complex contextual workflow deviations may require manual review.