mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
Daniel Avila
7f890b1b3b
* feat: add Loops component type with referenced components Introduce "loops" as a new first-class component type — autonomous agentic workflows (goal + interval + stop condition) inspired by Loop Engineering and the Forward Future Loop Library. A loop references other components (agents, skills, hooks, commands) and the dashboard renders those references as clickable cards on the loop detail page. - Add 10 starter loops under cli-tool/components/loops/ (engineering, evaluation, operations) - Catalog generator: scan loops + write per-component content files - Dashboard: new type in icons/types/data, /loops page, and a "Referenced Components" section on the loop detail page - CLI: --loop flag installs the loop to .claude/loops/ and auto-installs its referenced components - Docs: CLAUDE.md and cli-tool rule updated Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T9ynMiCHt8JwdMd8KjCkES * feat: add 8 more loops (goal/loop/schedule patterns) Expand the loops catalog to 18, drawing ideas from community "Loop Engineering" patterns. Adds loops across the three trigger verbs (/goal, /loop, /schedule) and emphasizes the verifier-in-the-loop and budget / anti-spin guardrails: - engineering/five-minute-maintainer-loop - engineering/build-test-fix-loop - engineering/anti-spin-build-loop - engineering/completion-contract-loop (goal) - engineering/goal-refiner-loop (goal) - engineering/adversarial-review-loop (cross-model) - operations/overnight-pr-routine-loop (schedule) - evaluation/human-approval-loop (human-in-the-loop) All referenced components verified to exist; catalog regenerated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T9ynMiCHt8JwdMd8KjCkES --------- Co-authored-by: Claude <noreply@anthropic.com>
43 lines
2.3 KiB
Markdown
43 lines
2.3 KiB
Markdown
---
|
|
name: devils-advocate-loop
|
|
description: Adversarially challenges a design or decision until every serious objection is resolved or explicitly accepted.
|
|
category: evaluation
|
|
interval: 15m
|
|
stop-condition: No unresolved serious objections remain — each is fixed or consciously accepted with rationale.
|
|
components: [agent:expert-advisors/architect-review, agent:expert-advisors/critical-thinking, command:git-workflow/pr-review]
|
|
tags: [evaluation, design-review, decision-making, loop]
|
|
---
|
|
|
|
# Devil's-Advocate Loop
|
|
|
|
> **Loop Engineering** — put a dedicated critic in the loop. It keeps attacking the design until the proposal survives scrutiny or is knowingly accepted with its trade-offs.
|
|
|
|
## 🎯 Goal
|
|
Stress-test a design, RFC, or architectural decision by generating the strongest possible objections, then resolving or explicitly accepting each one — no objection silently ignored.
|
|
|
|
## ⏱️ Schedule
|
|
Suggested interval: `15m` (or run until the design is settled).
|
|
|
|
## ▶️ Run it
|
|
```
|
|
/loop 15m "Act as a devil's advocate against the current design. Raise the strongest objections (scaling, security, cost, edge cases, maintainability). For each, either fix the design or record an explicit accepted trade-off with rationale. Continue until no serious objection is unresolved."
|
|
```
|
|
|
|
## 🔁 Iteration steps
|
|
1. **Perceive** — read the current design/decision.
|
|
2. **Reason** — the `critical-thinking` agent generates the strongest counter-arguments.
|
|
3. **Plan** — for each objection, choose fix vs accept-with-rationale.
|
|
4. **Act** — update the design or the decision log; `architect-review` validates the revision.
|
|
5. **Observe** — re-run with `/pr-review`; stop only when nothing serious is unresolved.
|
|
|
|
## 🛑 Stopping condition
|
|
Every serious objection is either resolved or recorded as an explicit, justified trade-off.
|
|
|
|
## 🧩 Referenced components
|
|
- `agent:expert-advisors/architect-review` — validates each revision.
|
|
- `agent:expert-advisors/critical-thinking` — generates adversarial objections.
|
|
- `command:git-workflow/pr-review` — structured review of the design changes.
|
|
|
|
## 💡 Example
|
|
A proposed single-region database is challenged on availability; the loop either adds a replication plan or records "single-region accepted for MVP, revisit at scale" with reasoning.
|