self-reflect

To generate a structured reflection document after a stakeholder correction, trigger a guided reflection that captures what happened, what should have happened, the root cause, and proposed fixes. The output is saved as a file under docs/clasi/reflections.

Root cause analysis on missed instructions in AI agent workflows is performed by analyzing the triggering event and stakeholder feedback to identify why steps were ignored or prompts were ambiguous. This analysis populates the Root Cause section of the reflection document.

Capture stakeholder feedback for process improvement in AI ops by logging the correction event and proposed fixes into an auditable reflection document. This document includes YAML frontmatter with a name and description, followed by structured improvement sections.

Yes, the reflection document format supports an optional TODO section for post-review improvements. This section is appended after the required What Happened, What Should Have Happened, Root Cause, and Proposed Fix sections to track future actions.

Yes, you can use this reflection approach for post-review improvements across typical task scenarios such as missed instructions, ambiguity, or ignored steps. It applies broadly to AI agent workflows involving error corrections to guide future behavior.