agile-retrospective

Name: agile-retrospective
Availability: InStock
Author: reiser

Extract and route task lessons to project or global memory files.

Updated Aug 23, 2026

Search Tags:#documentation #retrospective #agile #memory #process-improvement #lessons-learned

Ready to run

npx skills add https://github.com/reiserwang/Coding_Agent --skill agile-retrospective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agile-retrospective
Source: https://github.com/reiserwang/Coding_Agent/tree/main/.gemini/skills/agile-retrospective
Command: npx skills add https://github.com/reiserwang/Coding_Agent --skill agile-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conducts a structured retrospective to identify and document actionable lessons from a completed task, ensuring knowledge is captured in the correct memory layer (project-specific lessons to agent/memory/LESSONS.md, global lessons to GEMINI.md/CLAUDE.md).

Core Features & Use Cases

Automatic extraction of successes, failures, and process improvements from task context.
Distinguishes between project-level lessons and globally applicable practices, routing them to the appropriate memory store.
Provides a repeatable format for recording lessons, including date, outcome, lesson, and action.

Quick Start

Run a retrospective after a task completes to capture lessons and update the appropriate memory layer.

Frequently Asked Questions about agile-retrospective

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

FAQPage Schema

How do I document agile retrospective lessons learned from a completed task?▼

To conduct an agile retrospective, the skill analyzes completed task context to automatically extract successes, failures, and process improvements, recording them in a structured format with date, outcome, lesson, and action.

Where should project-level lessons and global lessons be stored in an agile memory file?▼

Project-level lessons should be stored in agent/memory/LESSONS.md, while globally applicable practices and lessons should be routed to GEMINI.md or CLAUDE.md to ensure proper memory layer separation.

When should I run a retrospective to capture process improvement insights?▼

You should run a retrospective immediately after a task completes to capture process improvement insights, ensuring knowledge is consolidated and written to the appropriate memory layer while context is fresh.

Does this retrospective tool require access to workspace state and memory files?▼

Yes, the retrospective tool requires access to workspace state and memory files to identify recent task context and carefully handle writing updates to the correct project or global memory stores.

What is the best way to separate project-specific lessons from globally applicable practices?▼

The best way to separate lessons is to route project-specific updates to agent/memory/LESSONS.md and global practices to GEMINI.md/CLAUDE.md, distinguishing between local memory and global configurations.