skills.rest
DojoGenesis
DojoGenesisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retrospective

Generate a structured retrospective markdown document with themes and action items.

2|Updated Apr 8, 2026
Search Tags:#documentation#learning#retrospective#action items#sprint#memory garden
One-click install
npx skills add https://github.com/DojoGenesis/gateway --skill retrospective-dojogenesis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/DojoGenesis/gateway/tree/main/plugins/continuous-learning/skills/retrospective
Command: npx skills add https://github.com/DojoGenesis/gateway --skill retrospective-dojogenesis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lose valuable insights after a sprint or release, making it hard to turn experiences into future improvements.

Core Features & Use Cases

  • Guided Workflow: Step‑by‑step instructions to create a retrospective markdown document.
  • Structured Output: Three core questions, theme analysis table, actionable items, and memory‑garden seeds.
  • Use Cases: End‑of‑sprint reviews, post‑release reflections, or mid‑project check‑ins to capture learnings and seed future work.

Quick Start

Ask the retrospective skill to generate a structured retrospective document for the last sprint, providing a brief description of its context.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I generate a structured sprint retrospective document?▼

To generate a sprint retrospective document, provide a brief description of your sprint context and the tool produces a markdown file containing three core questions, theme analysis, action items, and memory-garden seeds.

What should a post-release retrospective include to capture lessons learned?▼

A post-release retrospective should include answers to what went well, what was hard, and what to change, plus a theme analysis table, actionable items, and memory-garden seeds to retain insights.

When should I run a project retrospective to capture learnings?▼

You should run a project retrospective after a sprint, following a release, or during a project slowdown to capture learnings and seed future work before insights are lost.

What is the best way to turn sprint experiences into actionable insights?▼

The best way to turn sprint experiences into actionable insights is using a guided workflow that structures lessons learned into a markdown file with theme analysis and concrete action items.

Can I use this retrospective format for mid-project check-ins?▼

Yes, you can use this retrospective format for mid-project check-ins to capture learnings and seed future work by generating a structured markdown document with action items.

What are memory-garden seeds in a retrospective document?▼

Memory-garden seeds in a retrospective document are structured entries that preserve sprint learnings and insights to seed future work and prevent valuable experiences from being lost.

Related Skills

Explore More Product & Management Skills→
semicolon-devteamsemicolon-devteam

close-sprint

Automates sprint closure, velocity calculation, retrospective generation, task migration, and label removal for Iterations.

Official
Intermediate
ilove323ilove323

update

Synchronizes project tracker tasks and updates related metadata.

Community
Intermediate
webn77webn77

retro

Analyze sprint completion data to generate retrospective documents with metrics and action items.

Community
Intermediate
Ethical-AI-SyndicateEthical-AI-Syndicate
1

retrospective-action-tracker

Track retrospective action items and detect recurring systemic patterns.

Official
Intermediate