retrospective

You can generate a retrospective report by reading recent session archives to produce a concise summary. The skill analyzes multiple PLAN, ACT, and EVAL sessions to surface patterns and export actionable improvement recommendations to your docs folder.

Session analysis for TDD trend detection is the process of examining archived development cycles to identify test-driven development patterns. This skill analyzes session history to surface TDD cycle indicators across PLAN, ACT, and EVAL phases for team retrospectives.

You identify coding patterns by analyzing archived session data to reveal mode usage and agent utilization. This skill processes context archives from multiple sessions to discover recurring issues, decisions, and improvement opportunities for structured team retrospectives.

Yes, you can use session archives for sprint planning by generating a structured retrospective report. This skill converts long-lived session archives into concise, data-driven insights that guide process improvements and inform coding practices for upcoming sprints.

Yes, you need multiple PLAN, ACT, and EVAL sessions before running a retrospective. This skill is applicable after several archived sessions have been completed, as it requires sufficient historical data to perform pattern discovery and TDD trend analysis effectively.

The best way to turn session data into actionable improvements is by analyzing archived sessions to identify recurring issues and decisions. This skill surfaces mode usage patterns and TDD cycle indicators, generating a structured report with recommendations for process improvements.