skills.rest
KeyValueSoftwareSystems
KeyValueSoftwareSystemsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

retrospect

Distill completed Maestro workflow runs into structured lessons and documentation updates.

3|Updated Jul 1, 2026
Search Tags:#automation#documentation#retrospective#sdlc#knowledge-management#maestro
One-click install
npx skills add https://github.com/KeyValueSoftwareSystems/maestro --skill retrospect-keyvaluesoftwaresystems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospect
Source: https://github.com/KeyValueSoftwareSystems/maestro/tree/main/skills/core/bootstrap/retrospect
Command: npx skills add https://github.com/KeyValueSoftwareSystems/maestro --skill retrospect-keyvaluesoftwaresystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of knowledge loss between AI-assisted development runs by distilling outcomes into structured, reusable lessons that improve future performance.

Core Features & Use Cases

  • Lesson Extraction: Automatically identifies requested changes and operational hurdles from a completed Maestro run.
  • Knowledge Consolidation: Updates technical, functional, and architectural documentation to reflect the latest feature changes.
  • Use Case: After completing a complex backend feature, use this skill to analyze the run history and generate specific guidance for future developers to avoid the same architectural pitfalls.

Quick Start

Run the retrospect skill to analyze the latest feature run and generate a structured lessons drop for the memory system.

Frequently Asked Questions about retrospect

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

FAQPage Schema
How do I automate retrospective documentation from completed workflow runs?▼

Automated retrospective documentation analyzes completed Maestro workflow runs by reviewing gate history, user feedback, and artifacts to distill structured lessons and update project documentation for future cycles.

What is the best way to prevent knowledge loss between AI-assisted development cycles?▼

Preventing knowledge loss between AI-assisted development cycles requires distilling completed run outcomes into structured, reusable lessons that generate actionable guidance for subsequent development runs.

How do I extract actionable lessons from a completed Maestro run?▼

Extracting actionable lessons from a completed Maestro run involves analyzing operational hurdles and requested changes, then generating specific architectural and functional guidance to prevent repeating past development pitfalls.

Do I need specific access permissions to automate knowledge management for software development?▼

Automating knowledge management for software development requires read access to run state and write access to project documentation to maintain a living knowledge base of structured lessons.

Can I automatically update technical and architectural documentation after a feature run?▼

Automatically updating technical and architectural documentation after a feature run consolidates knowledge by reflecting the latest changes into functional docs, ensuring the project knowledge base remains current.

Related Skills

Explore More Software Engineering Skills→
vsokhvsokh

release

Assess release readiness and generate versioned changelogs from git history.

Community
Advanced
markus41markus41
18

Claude Code Memory & Instructions System

Manage project context with hierarchical CLAUDE.md files and scoped rules.

Community
Advanced
liuminxin45liuminxin45
95

speckit-retrospective

Record completed Spec Kit workflows into feature-local retrospective artifacts before commit.

Community
Advanced
mkalhitti-cloudmkalhitti-cloud
2

trading-knowledge-vault

Enforce mandatory lessons-learned reviews before NinjaTrader code changes.

Community
Advanced