autobuilderlisted

# autobuilder ## What this skill does Takes a PRD (file path or pasted text) and drives a 5-stage pipeline that yields a Rust project where every artifact is (a) generated from a structured `intent-card.json` derived via 4/5-Whys, (b) iterated under a narrow falsifiable advance-or-revert loop, (c) accompanied by per-iteration `EvidencePack` receipts and `FailureCapsule`s on crash, (d) gated by 8 receipts before declaring "ready," and (e) fed into a postmortem that queues self-improvement proposals. ## When to invoke Invoke when the user: - Hands you a PRD and asks for a Rust project (CLI or library). - Says "build me a Rust X" with concrete acceptance criteria. - Asks to dogfood autobuilder against one of its own sub-tools. Do NOT invoke for: - Greenfield non-Rust projects. - Surgical edits to an existing Rust crate (use direct tools). - Web services, WASM, or embedded targets (v1 is `--target cli|lib` only). ## Resolved decisions (locked 2026-05-21) 1. **Skill + companion Rust binary.** Skill orchestrates Claude subagents; the companion `autobuilder` binary (Cargo workspace at `../autobuilder/` in the repo, installed via `cargo install --path autobuilder`) owns the metric harness, receipt writing, risk gate, and experiment-loop runner. Skill shells out to the binary. Binary is itself dogfooded. 2. **Target scope: CLIs + library crates.** `--target cli` or `--target lib`. For libs add cargo-semver-checks, docs-coverage, `cargo public-api` diff. Service/WASM/embedded →