rai-story-review

To run a structured retrospective after feature completion, trigger the workflow to initiate data gathering, apply a heutagogical checkpoint, persist pattern memory, and generate documentation artifacts for process improvement.

A retrospective framework with telemetry and memory persistence captures development learnings after story completion, emits telemetry data, and updates a knowledge base to close the feedback loop for continuous process improvement.

You capture learnings and actionable improvements from completed stories by executing a structured retrospective flow that gathers data, updates memory patterns, and outputs Markdown documentation artifacts to the knowledge base.

Yes, you can use this retrospective workflow across end-to-end software development cycles, as it applies to planning, implementation, review, and closure phases whenever a story reaches completion.

No external dependencies or components are required to function, as the retrospective workflow operates independently to gather data, emit telemetry, and persist memory updates after story completion.

The best way to update a knowledge base with process improvements is running a retrospective workflow that persists pattern memory and generates Markdown documentation artifacts after completing a software feature.