skills.rest
JeremyKalmus
JeremyKalmusCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze completed epic telemetry to generate improvement recommendations for prompts and workflows.

27|3|Updated Jan 4, 2026
Search Tags:#automation#reports#beads#telemetry#retro#epic-analysis#workflow-improvement
One-click install
npx skills add https://github.com/JeremyKalmus/parade --skill retro-jeremykalmus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/JeremyKalmus/parade/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/JeremyKalmus/parade --skill retro-jeremykalmus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes completed epic executions to identify performance gaps and transformation opportunities, turning raw telemetry into actionable improvements.

Core Features & Use Cases

  • Reads telemetry data to compute efficiency scores and surface actionable recommendations for prompts, debug knowledge, and workflow configuration.
  • Archives retrospectives and updates the internal Insights report to track patterns over time.
  • Supports an optional approval flow before applying any changes to the project configuration or epics.

Quick Start

Use the retro skill after completing an epic to review performance, approve recommended changes, and trigger archival and insights updates.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate actionable improvement recommendations from epic telemetry data?▼

Yes, you can automate retrospective reports by reading beads summaries and existing post-completion reviews to identify performance gaps, tracking transformation patterns over time through archived insights.

Do I need existing beads summaries to perform an epic analysis?▼

Yes, retro supports an optional approval flow that requires user review before applying any recommended changes to project configuration, epics, or workflow settings.

What is the best way to track workflow improvement patterns after epic completion?▼

Yes, retro reads telemetry data and beads summaries from completed epics, computing efficiency scores and surfacing actionable recommendations for prompts, debug knowledge, and workflow configuration.

Can I review performance recommendations before they modify my workflow configuration?▼

Yes, the retrospective analysis includes an optional approval flow that requires user review before applying any recommended changes to project configuration, epics, or workflow settings.

What is the best way to track workflow improvement patterns after epic completion?▼

The best way to track workflow improvement patterns after epic completion is to archive retrospectives and update an internal Insights report, capturing performance data to monitor trends over time.

Related Skills

Explore More Software Engineering Skills→
JeremyKalmusJeremyKalmus
27

approve-spec

Convert approved specifications into Beads epics with tasks and dependencies.

Community
Intermediate
Obsidian-OwlObsidian-Owl
9

sw-learn

Capture and curate reusable knowledge from software development work units.

Official
Advanced
justcoonjustcoon
1

golem-enable-otlp-ts

Configure Golem TypeScript agents to export traces, logs, and metrics to an OTLP collector.

Community
Basic
insightwavesmithinsightwavesmith

code-analyzer

Analyze code changes to identify those meeting evidence-shape-check criteria.

Community
Intermediate