rjv-gated-buildlisted

Use automatically for financial/money, production-safety, security, destructive, high-blast-radius, zero-debt, multi-agent, or phase-reviewed builds where an INDEPENDENT reviewer must approve each slice—even when the user never says 'gated build'. Compose with `rjv-work-plan` and `rjv-spec-driven`: durable acceptance criteria live in `spec.md`; the plan holds cast, active criterion IDs, evidence, grill trail, and RESUME HERE. Enforce spec grill before code, ID-bound WORK/REVIEW, explicit APPROVED/REJECTED loops, crash/compaction durability, and model-economy routing. Triggers also include: gated build, grill each step, adversarial review, overnight run, high-stakes build, human QA gate, or repeated review rejections.
rjvim/ai-skills · ★ 0 · AI & Automation · score 61

Install: claude install-skill rjvim/ai-skills

# Gated build — adversarial multi-agent construction For work where being *plausibly wrong* is expensive. One agent can't reliably catch its own errors — the blind spot that produced the bug reviews the bug. Quality comes from **independence**: a second agent whose job is NO-AGREE, grilling every step to an explicit APPROVED. Economics: compress everything agents read (specs, notes, grill prompts) so you can afford a second agent to disagree. Efficiency funds redundancy. ## 1. Casting the roles → `CASTING.md` Three roles: **Orchestrator** (holds anchor doc, casts, integrates), **Author** (drafts), **Reviewer** (grills to APPROVED). Cast by task, not habit. - **The human casts the orchestrator at launch — ASK, don't assume.** - **Reviewer ≥ author strength, and independent** — self-review is not review above mechanical work; prefer cross-vendor for the grill. - **Record the cast once** in the anchor plan's `## Cast` (`rjv-work-plan`), models named. Every resume obeys it; recasting is a logged Decision with a why. - **The human is also a reviewer** — surface designs at phase boundaries. Read [`CASTING.md`](./CASTING.md) at build start or when recasting: the orchestrator-choice table (Opus / Sonnet / Codex and the reviewer each requires), the author×reviewer pairings, execution bindings for each cast, and the evidence behind the two hard rules. ## 2. Grill the durable SPEC before any code Highest-leverage grill is pre-implementation. Source build: the reviewer's roun