loopbench-retrospective

Inspect Loopbench task histories and propose reversible workflow improvements from evidence.

1|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/hideh1231/loopbench --skill loopbench-retrospective-hideh1231
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loopbench-retrospective
Source: https://github.com/hideh1231/loopbench/tree/main/skills/loopbench-retrospective
Command: npx skills add https://github.com/hideh1231/loopbench --skill loopbench-retrospective-hideh1231

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Recurring failures, gate rejections, and blockers in Loopbench task histories often go unexamined, so teams repeat the same mistakes or add premature process machinery. This Skill turns that accumulated evidence into a small number of well-justified, reversible workflow improvement proposals. ## Core Features & Use Cases - Evidence-led analysis: Inspects accepted revision diffs, gate events, blockers, finish rejections, adversarial reviews, and source-backed notes via the loopbench CLI, separating recurring patterns from one-off incidents. - Graduated codification threshold: Uses an N=3 default threshold for codifying interaction-shaped mechanisms, while allowing immediate safeguards for high-impact incidents with cheap, testable fixes. - Deterministic harness diagnostic: Runs a three-agent, read-only diagnostic across conversation, repository, and agent-customization evidence lanes when diagnosing Loopbench itself. - Use Case: After several tasks fail the same human gate, run a retrospective to identify the recurring cause, consider a competing explanation, and propose at most two minimal reversible changes with validation tasks and rollback conditions. ## Quick Start Ask the assistant to run a Loopbench retrospective over recent task histories and propose evidence-backed workflow improvements for your approval.

Frequently Asked Questions about loopbench-retrospective

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

FAQPage Schema
How do I run a retrospective on Loopbench task histories?

Run loopbench status and loopbench history for representative tasks, then use loopbench show and loopbench diff to inspect meaningful contract revisions. Gather cited logs, artifacts, and task_note events, separate recurring patterns from one-off incidents, and present at most two proposals for user approval.

When should I codify a recurring workflow pattern into a rule?

Use N=3 distinct comparable cases as the default threshold before proposing codification of interaction-shaped mechanisms. At N=1 keep observing with a source-backed note, at N=2 test competing explanations, and skip the wait only for deterministic defects or high-impact incidents with cheap, reversible safeguards.

What are the requirements for using the Loopbench retrospective workflow?

It requires Python 3.11 or later, the loopbench CLI, and one or more existing Loopbench task histories containing events, revisions, and gate records. It is not intended for use during routine task execution.

Can the retrospective apply workflow changes automatically?

No. Every proposal must be explicitly accepted, rejected, or revised by the user before any change is made. A proposed repair becomes an unaccepted successor contract bound to one finding, one owner, and one verification check until approved.

How are invalidated comprehension records handled in a retrospective?

Treat comprehension_invalidated events as corrections rather than failed quiz attempts. If evidence shows a record lacks a real human answer, propose loopbench comprehension invalidate with the event ID and reason, never deleting or rewriting the original ledger line.