← ClaudeAtlas

brain-buildlisted

The autonomous build contract, out of the box — "/brain-build <what you want>" activates the disciplined hands-off build power users used to hand-write a standing prompt for. Use when the user says "/brain-build", "brain build", "build this autonomously", "build this hands-off", "loop until it's done", "don't ask me, just build it", or asks for an unattended/self-grading build. Phase-gated per rUv's SPARC, self-verified and self-graded /100 against a per-phase rubric (below 95 → fix and regrade, max 5 iterations), cost-tier routed with printed receipts, crash-resumable via checkpoints, questions batched into one list — the user writes the goal, not the contract.
stuinfla/ruvnet-brain · ★ 24 · AI & Automation · score 68
Install: claude install-skill stuinfla/ruvnet-brain
<!-- Credit: this contract productizes a community field pattern — the 7-rule standing prompt hand-written by the PR #8 contributor (Eva Draganova, 2026-07-10) to force the brain into disciplined autonomous building. Her forcing insight: "grade 1-100, no pass under 95 → forced it to loop and improve." All the machinery existed; this skill removes the 40 hand-written lines needed to activate it. --> # Brain-Build — the standing contract, activated by one line `/brain-build <what you want>` means: no human is watching until it's done. Run the whole build under the contract below. The AUTONOMOUS MODE rules injected by the grounding hook (`plugin/scripts/ground-ruvnet.sh`) apply in full — this skill carries them even on turns where that hook doesn't fire. ## 1. Phases — rUv's SPARC, with a rubric per phase Structure the build as the five SPARC phases with a quality gate between each — rUv's own convention (phases + gates: `concepts/sparc/CARD/sparc-card`; per-phase docs: `sparc/specification/README.md`). Gate criteria follow rUv's ruflo-sparc gate checks (`ruflo/plugins/ruflo-sparc/commands/ruflo-sparc.md`): | Phase | Rubric (the /100 grade is against THIS) | |---|---| | **S** Specification | Requirements complete; ≥3 acceptance criteria; constraints explicit; edge cases identified. | | **P** Pseudocode | Design covers every acceptance criterion; error paths explicit; complexity annotated. | | **A** Architecture | Every constraint addressed; API contracts