retro

Name: retro
Availability: InStock
Author: enduser123

Chains /recap, /gto, /friction, /pre-mortem, and /rns to produce a formal RNS output.

Updated Apr 26, 2026

Search Tags:#gap-analysis #recap #friction #retro #pre-mortem #rns #self-contrast

Ready to run

npx skills add https://github.com/EndUser123/cc-marketplace --skill retro-enduser123

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/EndUser123/cc-marketplace/tree/main/plugins/cc-skills-meta/skills/retro
Command: npx skills add https://github.com/EndUser123/cc-marketplace --skill retro-enduser123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies what went wrong, what went right, and what to do differently next time by chaining a defined self-review protocol across recap, gap analysis, friction, pre-mortem, and action extraction.

Core Features & Use Cases

End-to-end SELF-CONTRAST orchestration: executes the full post-session review to surface actionable improvements.
Structured outputs: produces a formal RNS-formatted action list with domain grouping and explicit next steps.
Red-team validation: triggers adversarial checks when scores fall below thresholds to improve robustness.
Use Case: end-of-sprint retrospectives, post-incident reviews, or planning sessions seeking continuous improvement.

Quick Start

Run /retro at the end of a session to execute the full SELF-CONTRAST retrospective.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I automate an end-of-sprint retrospective to surface friction points?▼

To automate a retrospective, you run a chained protocol that analyzes session recaps, identifies gaps, and extracts friction points. This Skill coordinates that full self-contrast workflow to surface actionable improvements and formalize next steps for continuous improvement.

What is a self-contrast retrospective and how does it improve project outcomes?▼

A self-contrast retrospective is a structured review process that chains recap, gap analysis, friction identification, and pre-mortem checks. It improves outcomes by surfacing what went wrong, what went right, and carrying over unresolved actions to enforce continuous improvement across sessions.

Can I use this for post-incident reviews and planning sessions?▼

Yes, you can use this retrospective protocol for post-incident reviews and planning sessions. It applies domain grouping to surface gaps and friction points, triggering adversarial red-team validation when scores fall below thresholds to ensure robust action extraction.

How do I extract a formal action list with domain grouping from a project review?▼

You extract a formal action list by running the chained retrospective workflow that processes recaps and pre-mortems. This Skill generates an RNS-formatted output with domain grouping, explicitly defining next steps and carrying over any unresolved actions from previous sessions.

Does the retrospective workflow carry over unresolved actions from previous sessions?▼

Yes, the retrospective workflow enforces strict rules to carry over unresolved retro actions from previous sessions. This ensures that outstanding gaps and friction points are continuously tracked until they are formally resolved in the formal RNS action output.

When should I trigger a pre-mortem analysis during a retrospective?▼

A pre-mortem analysis is triggered as part of the chained self-contrast retrospective workflow. It specifically executes during the review phase to anticipate potential failures, with red-team validation automatically triggering when review scores fall below defined thresholds.