critic-dialogue

Installation
SKILL.md

Critic Dialogue

This is a reference pattern. Learn from the approach, adapt to your context — don't copy verbatim.


Problem

Documents get written, self-reviewed, and committed. The writer can't see their own blind spots. One-shot reviews don't close the loop — the dev accepts or ignores findings with no record of the reasoning, and no enforcement that the issues were actually resolved.

Solution

A persistent discussion thread where an independent critic scores each document and the dev responds point by point. The loop runs until all documents score 4/5 or higher (max 3 passes). If consensus isn't reached, an arbitrator breaks the deadlock — reading the full thread and making explicit OVERRULE / UPHOLD / THIRD_PATH calls per unresolved point. The thread is the complete history of the dialogue.


Pipeline

Installs
1
First Seen
1 day ago
critic-dialogue — loxosceles-dev/skills