build-it Plugin
Single-command autonomous delivery orchestrator — the build stage of the *-it lifecycle (plan-it plans it, build-it builds it); formerly fable-it. Model-adaptive for Sonnet 5 and Opus 4.8. Hand it a goal and a numbered Definition of Done and it runs the whole job to completion, conducting launch/iterate/full-qa/chrome-cdp with a 5-gate catalog, disk-backed run state, an evidence ledger (VERIFIED = lookup), a fresh-context verifier, and an honest per-criterion report.
So installierst du das build-it Plugin
Führe beide Befehle in Claude Code aus. Der erste fügt den Marketplace einmalig hinzu; der zweite installiert das Plugin.
/plugin marketplace add DevOtts/build-it
/plugin install build-it@build-itWas ist in build-it enthalten
5 Teile wurden aus den eigenen Dateien des Plugins gelesen.
Skills 5
Claude lädt es, wenn die Aufgabe passt- 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 subagent
- chrome-cdp-control
Drive the user's real, logged-in Chrome browser via Chrome DevTools Protocol using Playwright (endpoint from CDP_URL, defaulting to localhost). Trigger this skill when the user explicitly asks to "use my Chrome", "use my browser", "log into", "post on" (X, Reddit, LinkedIn, etc.), or any task that requires an authenticated session, persistent cookies, or bot-detection evasion that headless scraping cannot provide. Also trigger when the user references their CDP setup, their `~/.chrome-automation` profile, or asks Claude to manually walk through actions on a real site one step at a time. Do NOT use this skill for simple unauthenticated content fetches (use `web_fetch`), bulk headless scraping (use a standalone Playwright script), or anything where a fresh Chromium instance would suffice. Do NOT use for tasks that can be solved by an API call to the same service.
- full-qa
Generic autonomous QA suite for any project — reads a test plan (markdown file or inline spec), runs all tests using Chrome CDP + iterate cycles, fixes bugs found, and produces a final QA report. Works with any web stack. Trigger with /full-qa [path-to-test-plan.md]. Use before releases, after significant changes, or whenever you want a full system health check.
- iterate
Autonomous multi-cycle problem solver for complex tasks that require diagnosis → fix → test → verify loops. Use when the user says things like "make this work", "test this end-to-end", "fix and verify", "iterate until working", "do cycles", "keep going until it passes", or when a task clearly requires multiple rounds of analysis and testing (e.g., debugging a pipeline, seeding data, verifying integrations, making an API flow work). Also activates when the user wants autonomous QA, test runs, or system-level verification. Splits heavy work across subagents to preserve context and speed up iteration.
- launch
Mission control for autonomous projects — analyzes tasks, recommends approaches (sub-agents/teams), sets up environment (features, evals, hooks, init.sh), suggests and configures tooling (MCPs), and launches the work.
Verwendung von build-it in Claude Code
Skills benötigen keinen Command. Claude liest sie, wenn deine Anfrage dem entspricht, was sie beschreiben.
Aktualisieren, deaktivieren oder entfernen
- Plugin aktualisieren (shell)
- claude plugin update build-it@build-it
- marketplace aktualisieren
- /plugin marketplace update build-it
- Vorerst deaktivieren
- /plugin disable build-it@build-it
- Entfernen
- /plugin uninstall build-it@build-it
Skills in build-it
- build-itDevOtts/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 subagent
16Stars - chrome-cdp-controlDevOtts/build-it
Drive the user's real, logged-in Chrome browser via Chrome DevTools Protocol using Playwright (endpoint from CDP_URL, defaulting to localhost). Trigger this skill when the user explicitly asks to "use my Chrome", "use my browser", "log into", "post on" (X, Reddit, LinkedIn, etc.), or any task that requires an authenticated session, persistent cookies, or bot-detection evasion that headless scraping cannot provide. Also trigger when the user references their CDP setup, their `~/.chrome-automation` profile, or asks Claude to manually walk through actions on a real site one step at a time. Do NOT use this skill for simple unauthenticated content fetches (use `web_fetch`), bulk headless scraping (use a standalone Playwright script), or anything where a fresh Chromium instance would suffice. Do NOT use for tasks that can be solved by an API call to the same service.
16Stars - full-qaDevOtts/build-it
Generic autonomous QA suite for any project — reads a test plan (markdown file or inline spec), runs all tests using Chrome CDP + iterate cycles, fixes bugs found, and produces a final QA report. Works with any web stack. Trigger with /full-qa [path-to-test-plan.md]. Use before releases, after significant changes, or whenever you want a full system health check.
16Stars - iterateDevOtts/build-it
Autonomous multi-cycle problem solver for complex tasks that require diagnosis → fix → test → verify loops. Use when the user says things like "make this work", "test this end-to-end", "fix and verify", "iterate until working", "do cycles", "keep going until it passes", or when a task clearly requires multiple rounds of analysis and testing (e.g., debugging a pipeline, seeding data, verifying integrations, making an API flow work). Also activates when the user wants autonomous QA, test runs, or system-level verification. Splits heavy work across subagents to preserve context and speed up iteration.
16Stars - launchDevOtts/build-it
Mission control for autonomous projects — analyzes tasks, recommends approaches (sub-agents/teams), sets up environment (features, evals, hooks, init.sh), suggests and configures tooling (MCPs), and launches the work.
16Stars
Fragen zum build-it Plugin
Wie installiere ich das build-it Plugin?
Führe in Claude Code /plugin marketplace add DevOtts/build-it aus, dann /plugin install build-it@build-it.
Was enthält das build-it Plugin?
build-it bündelt 5 Skills.
Wie aktualisiere oder entferne ich das build-it Plugin?
Aktualisiere es mit claude plugin update build-it@build-it in deiner shell oder über den Installed-Tab von /plugin. Entferne es mit /plugin uninstall build-it@build-it.
Unter welcher Lizenz steht das build-it Plugin?
MIT, wie im Manifest des Plugins angegeben.