The devil's-advocate loop
A critic-and-builder workflow that attacks a design, tracks every objection, and requires evidence before an objection can be closed.
High Quality
New
Join 0+ developers using this skill
This loop is republished with attribution. Full credit and the original content belong to the source linked above.
command
Loops & Automation
intermediate
AI Skill Market Insights
Real data. Real impact.
Popularity
Rising
Emerging
Active Users
0+
Developers
Kickoff Prompt
Copy this prompt and run it with your agent to start the loop.
Before committing to an architecture, interface, or rollout plan, have a critic argue that it is wrong. Record each objection, impact, and status in a repository-local log at .agent-reviews/redteam.md. The builder must fix and verify each high-impact weakness or document why it is accepted; the critic may reopen unsupported answers. Stop when no high-impact objection remains or the same issues repeat for two rounds without new evidence. Finish with the decision, resolved and accepted objections, evidence, and any stalemate.TEAR & SHARE
2-3hrs/WK
RISING
0.0K+ USING
Tags
agent:claude-code
tag:evaluation
anonymous-contributor
devils-advocate-loop
adversarial-design-review
critic-builder-workflow
architecture-objection-log
red-team-design-process
forward-future
loop
