mcpbeat

Retro Learn

hoangnguyen0403/retro-learn

Convert delivery findings into skill, eval, workflow, and documentation improvements.

629 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
536
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill retro-learn

The instruction itself

8 sections, as written by the author

Retro Learn Skill

> [!IMPORTANT]

> Convert delivery findings into skill, eval, workflow, and documentation improvements.

Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

Retro Learn Workflow

Goal: Turn defects, missed expectations, and delivery friction into durable standards improvements.

Steps

  • Gather evidence:
  • Review findings
  • Bugs found during verification
  • Security findings
  • User corrections
  • Failed or slow checks
  • Token or context pain
  • session-report artifacts
  • Classify:
  • Skill rule gap
  • Eval coverage gap
  • Workflow gap
  • Documentation gap
  • Tooling gap
  • Specialist gap
  • Environment-only issue
  • Decide action:
  • Existing skill should prevent it: update SKILL.md and evals/evals.json.
  • No skill covers it: propose a new skill.
  • Workflow caused drift: update .agents/workflows.
  • Specialist caused drift: add budget, fallback, or output-format rule.
  • Tooling can catch it: add or update an audit script.
  • Verify learning:
  • Run changed skill validation.
  • Run eval alignment.
  • Record remaining follow-ups.

Runtime Contract

  • Use after delivery findings, corrections, or friction need converting into durable standards improvements.
  • Required inputs: review findings, verification results, or session-report artifacts to classify.
  • Return BLOCKED only when no evidence exists to classify.

Handoff Payload

  • slug, root causes, skill/eval updates, follow-ups, next workflow.

Blocking Questions

  • Ask max 3 at a time with a recommended default and 2-3 options.

Output Template

# Retro: [Name]

## Evidence

## Root Causes

| Finding | Category | Action |
| --- | --- | --- |
| [finding] | [category] | [action] |

## Skill Or Eval Updates

## Outcome Report
feature_status: implemented
requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: none

## Next Workflow

## Follow-Ups

## Cost Report
Call `get_session_cost(workflow="retro-learn")` before final handoff.

How to use it

Copy the folder

Take hoangnguyen0403/retro-learn from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.