double-loop-execution-reviewer

Reconstruct completed task episodes into evidence-based retrospectives with double-loop learning.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/limerickgds/dashi-skills --skill double-loop-execution-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: double-loop-execution-reviewer
Source: https://github.com/limerickgds/dashi-skills/tree/main/skills/double-loop-execution-reviewer
Command: npx skills add https://github.com/limerickgds/dashi-skills --skill double-loop-execution-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill turns completed work into a concise, evidence-based retrospective, handoff, or improvement memo using a double-loop learning framework. It helps answer what was supposed to happen, what actually happened, what evidence supports that, and what changes should be made for the next pass. It is useful after coding, writing, research, planning, debugging, or operational tasks where several artifacts were produced and a clear continuation is needed.

Core Features & Use Cases

  • After Action Review (AAR) framework: clarify intended outcomes, actual results, gaps, and next actions.
  • Double-loop learning: assess whether goals, assumptions, and working rules should change for the next iteration.
  • Handoff-ready outputs: produce structured summaries for teammates or future agents, while preserving ownership and decision context.

Quick Start

Execute the review workflow on a completed task and generate a structured retrospective with concrete next steps.

Frequently Asked Questions about double-loop-execution-reviewer

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

FAQPage Schema
How do I write an after-action review for a completed coding or research task?

Generate an after-action review by reconstructing the completed task episode using a double-loop learning framework, which evaluates execution findings and framing recommendations to produce an evidence-based retrospective.

What is double-loop learning and how does it apply to task retrospectives?

Double-loop learning assesses whether goals, assumptions, and working rules should change for the next iteration, moving beyond simple execution adjustments to fundamentally reframe how future tasks are approached and executed.

How do I create a handoff memo that preserves decision context for teammates?

Create a handoff-ready output by evaluating the completed task's execution history and evidence, structuring the findings into a concise summary that explicitly defines ownership and a concrete next action for the receiving team.

Can I use this retrospective framework for operational and debugging tasks?

Yes, the retrospective framework applies to tasks with execution history across operations, debugging, planning, and writing, evaluating the produced artifacts to generate an improvement memo with a clear continuation path.

What is the best way to evaluate completed work and generate an improvement memo?

The best way to evaluate completed work is applying a double-loop learning framework to compare intended outcomes against actual results, yielding structured execution findings and framing recommendations with explicit ownership.

When do I need a double-loop retrospective instead of a standard review?

You need a double-loop retrospective when a completed task requires evaluating not just execution gaps, but also whether the underlying goals, assumptions, and working rules should change before starting the next iteration.