self-improvement

Post-sprint retrospectives are generated by evaluating sprint outcomes through a first-principles framework, producing structured improvement reports stored under the docs/superomni/improvements/ directory for continuous learning.

First-principles reflection analyzes process quality and delivery history by breaking down sprint outcomes into fundamental truths, generating actionable improvement evidence rather than relying on assumptions or surface-level observations.

Continuous improvement actions are tracked by auto-generating documented improvement plans and retrospective artifacts, ensuring post-task and post-sprint learnings are auditable and stored for future reference.

The retrospective process enforces a strict completion protocol per session using statuses like DONE, DONE_WITH_CONCERNS, or BLOCKED, ensuring clear visibility into execution outcomes and unresolved blockers.

To evaluate what you shipped, trigger a performance evaluation on the latest sprint to analyze delivery history, assess process quality, and output an evidence-based improvement report.

Weekly retrospectives can be run without manual documentation overhead by auto-generating structured improvement reports and retrospective evidence directly to your repository's docs directory.