retrospective-base

Create markdown-based retrospectives across daily to yearly time horizons.

5|2|Updated Nov 25, 2025

Search Tags:#planning #scalability #retrospective #process-improvement #team-learning

Ready to run

npx skills add https://github.com/ZachBeta/claude-as-coach --skill retrospective-base

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective-base
Source: https://github.com/ZachBeta/claude-as-coach/tree/main/skills/retrospective-base
Command: npx skills add https://github.com/ZachBeta/claude-as-coach --skill retrospective-base

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The retrospective-base framework standardizes the reflection process across multiple time horizons, enabling consistent learning loops and meta-improvement.

Core Features & Use Cases

Multi-scale retrospectives: supports daily, weekly, monthly, quarterly, and yearly intervals for individuals and teams.
Input compression: aggregates inputs from daily logs to higher-level retrospectives.
Structured template: guides what worked, what didn't, and how to improve, with a repeatable workflow.

Quick Start

To begin, create a [Scale]-Retro artifact for your current period and start filling sections using the one-question-at-a-time approach described in this guide. No code fences in Quick Start; just commands or steps in plain text.

Frequently Asked Questions about retrospective-base

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run structured retrospectives across multiple time horizons?▼

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.

What is the best way to standardize team learning and process improvement?▼

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.

Can I use a markdown-based template for both individual and team daily retrospectives?▼

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.

How do I compress daily logs into higher-level weekly or monthly retrospectives?▼

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.

Does the retrospective framework require any specific dependencies or scripts to operate?▼

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.

When should I not use a standardized retrospective template for process improvement?▼

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.