Individual skill
build-it
Single-command autonomous delivery orchestrator. Invoke it with a goal and a numbered Definition of Done (DoD) and it runs the whole job to completion — typically unattended, overnight — by conducting the bundled /launch, /iterate, /full-qa and /chrome-cdp-control skills. v2 encodes the Fable 5 behavioral contract as checkable gates (not postures) with disk-backed run state, an evidence ledger that makes VERIFIED a lookup, and a model-adaptive posture for Sonnet 5 and Opus 4.8. Use this whenever the user says "/build-it", "build it", "build-it", "/fable-it", "fable it", "fable-it" (the pre-v3.1.0 name — still routes here), "ship this", "run to DoD", "work autonomously until done", "I'm going to bed, finish this", "green light, take decisions", or pastes a goal + numbered acceptance criteria and expects an autonomous overnight run with a report waiting in the morning. Also use when the request describes an agile, cycle-based build (epics → tests → code → test → fix → loop) split across Claude teams or subagents. Prefer this over invoking /launch or /iterate directly when the request is a full goal-to-DoD delivery rather than a single phase.
plugins/build-it/skills/build-it/SKILL.md
Source commit bea0e4a062a3ac7f73bd6467341c4062be8e7f68
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 16
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agents Repository topic
- anthropic Repository topic
- autonomous Repository topic
- claude-code Repository topic
- definition-of-done Repository topic
- orchestrator Repository topic
- plugin Repository topic
- workflow Repository topic
- agent-skill Repository topic
- agent-skills Repository topic
- legal Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytesSKILL.mdcore · 30,621 bytes
Read excerpt
# /build-it — Autonomous Delivery Orchestrator (v2)
You are running a goal-to-DoD delivery, usually unattended. The user hands you a goal and a numbered Definition of Done and goes to sleep. Your job is to reach every DoD item, or stop honestly at the ones you could not, and leave a report and a credentials file they can act on in the morning.
Three principles govern everything below (evidence: `docs/research/01-fable5-vs-opus.md` §4):
1. **Gates, not vibes** — every load-bearing behavior has a trigger, a test, and an action, checked at a decision point. Standing exhortations decay over a long run; gates don't.
2. **Externalize state** — everything the run must not forget lives on disk in `.taskstate/` and is re-read at phase boundaries. State that survives compaction beats retention you don't have.
3. **Verify with fresh eyes** — the honesty mechanism is structural (evidence ledger + fresh-context audit), not motivational.
This skill is a **conductor, not a replacement**. Environment setup, approach selection, fix-test cycles and UI verification live in `/launch`, `/iterate`, `/full-qa` and `/chrome-cdp-control`; invoke them by name. If a behavior exists in one of those skills, call it — do not paste a worse copy here. If a delegated skill is missing in this environment, perform that phase's work inline following the same principle it would have applied, and note in the report that it ran inline. Degrade, never break.
---
## The gates catalog