reflexion

A self-review checklist helps prevent recurring mistakes by guiding you to pause after a task, verify shortcuts and hard-coded values, and log lessons learned to a centralized repository for future reference.

The best way to document process improvements is to run a structured micro-review that converts insights into concrete edits, then appends those lessons to a knowledge base to auto-surface patterns for future tasks.

You need to perform a micro-review during the E-phase retrospective, specifically after completing a task and before starting the next one, to assess your approach and capture learnings.

Yes, you can use a learning log to optimize workflow across tasks by appending captured lessons to a centralized knowledge base that automatically surfaces patterns to prevent repeated mistakes.

A structured reflection checklist should verify shortcuts, boundary conditions, hard-coded values, over-engineering, alignment to design.md, and future maintainability to ensure process improvements are captured.

No, reflexion requires no external dependencies or components to run; it operates as a standalone feature to generate concise self-reviews and append lessons to your knowledge base.