retro

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.

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.

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.

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.

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.

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.