kaizen

Run a post-development retrospective by reviewing the completed development cycle to identify successes, recurring errors, and patterns. Document lessons in .ai_state/lessons.md, update .ai_state/conventions.md with identified patterns, and generate a concise summary for stakeholders.

Continuous improvement in software development is a structured post-development reflection that captures successes and identifies recurring errors. It documents team patterns by recording lessons in .ai_state/lessons.md and updating .ai_state/conventions.md to enable better future practices.

No specific dependencies or frameworks are required to facilitate a development retrospective. The process applies after each development cycle and requires only the designated .ai_state files to record lessons and update conventions documentation.

The best way to document recurring errors and successes after a development cycle is through a structured Kaizen review. It automatically guides teams to record lessons in .ai_state/lessons.md and update .ai_state/conventions.md with identified patterns for future reference.

You need to run a continuous improvement session after completing each development cycle. This structured post-development reflection addresses the lack of formal review by helping teams capture successes, identify recurring errors, and produce a concise summary for stakeholders.

Software teams often lack structured post-development reflection because there is no formal process to capture successes and identify recurring errors. A Kaizen retrospective solves this by documenting lessons in .ai_state/lessons.md and updating .ai_state/conventions.md with identified patterns.