retrospective-base

Structured retrospectives across multiple time horizons require a repeatable, markdown-based template covering what worked, what didn't, and how to improve. This framework supports daily, weekly, monthly, quarterly, and yearly intervals for individuals and teams using a one-question-at-a-time approach.

Standardizing team learning and process improvement is best achieved by enforcing a consistent retrospective framework. This approach aggregates inputs from daily logs into higher-level summaries, creating consistent learning loops and enabling meta-improvement across teams.

Yes, markdown-based templates work for both individual and team daily retrospectives. The framework supports daily, weekly, monthly, quarterly, and yearly intervals, allowing users to create a Retro artifact for the current period and fill in sections using guided questions.

Compressing daily logs into higher-level weekly or monthly retrospectives involves aggregating inputs from logs, summaries, and plans. The framework uses input compression to roll up daily reflections into structured sections for what worked, what didn't, and how to improve.

The retrospective framework requires no specific dependencies to operate. It uses an optional scripts, references, and assets workflow to support the process, relying solely on a repeatable markdown structure for documenting reflections and improvements.

You should not use a standardized retrospective template when your process improvement needs require highly customized, non-repeatable reflection structures. The framework enforces a strict markdown-based format with predefined sections, which may limit freeform or unstructured brainstorming sessions.