From wannabuild
WannaBuild implementation phase entrypoint for implementing a concrete plan or task with focused verification and adaptive delegation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wannabuild:wb-buildThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This prompt follows `docs/contract-standard.md` and inherits the four mandates in
This prompt follows docs/contract-standard.md and inherits the four mandates in
skills/internal/build/references/doctrine.md; where this file is silent, the doctrine governs.
Shared contract: purpose, inputs, process, hard gates, evidence, output, handoff, forbidden actions.
Runtime gates fail closed and cannot be rationalized past. The runtime gate result is authoritative: a FAIL or runtime-unavailable result is a hard stop, never permission to proceed. Specialist judgment is advisory only; it never lowers a gate or substitutes for execution evidence.
Use this phase skill when the user invokes implementation or the active WannaBuild workflow is ready to build. A wb-build or wannabuild:wb-build invocation starts or resumes the full WannaBuild loop. A "build only" request suppresses only delivery in the Summary phase — every gate below, full self-verification evidence, and the integration hard gate still apply.
Before any implementation phase work:
wb-discover and complete the mandatory collaborative grill (one question at a time, each with a recommended answer) and the proportionate research bundle before any planning or implementation. Discovery fires on every task, including one-line changes; it is never skipped on a "trivial" classification.scripts/wannabuild-session.sh assert-discovery-ready <project_root>scripts/wannabuild-session.sh assert-plan-ready <project_root>assert-discovery-ready is not satisfied — discovery missing, incomplete, or based only on a vague goal, or requirements.md has no Acceptance Criteria section with at least one concrete checkable criterion — STOP and invoke wb-discover. You may not plan or build against an unmeasurable goal. If assert-plan-ready is not satisfied, STOP and invoke/complete the WannaBuild planning phase.bash, and install missing dependencies. Log each attempt and its result. Only if it still cannot run after these attempts may you stop, and you must report every attempt and its outcome.scripts/wannabuild-workspace.sh --json and continue inside the reported workspace_path. If that script cannot run, attempt to repair it (path, permissions, bash invocation) and log the attempt before stopping.Implement the requested change in micro-steps with evidence that the work satisfies the goal.
.wannabuild/outputs/acquisition-log.json: provision and seed a database via the available connector or CLI (Supabase/Neon branch), run the app locally, stand up a preview environment, drive a real browser, generate fixtures, or read live docs via Context7. "Missing env", "no access", and "can't test" are grounds to obtain the resource or — only for billable, outward-facing, or destructive acquisition — to ask the user, never to stop. assert-acquisition-attempted rejects any blocked status with no logged attempt.total > 0, failed == 0, errored == 0) and every acceptance criterion is covered.Prefer concise summaries. Write implementation artifacts to files and keep final responses focused on what changed and how it was verified, including the exact commands run, their exit codes, and output — not assertions that checks "should" pass.
In full-loop mode, continue automatically through implementation, validation, and QA without stopping for mechanical steps. Pause for the user ONLY when: an assumption with scope, product, security, or cost impact is unconfirmed; a discovery or plan gate failed; acceptance criteria conflict; or you have reached a public phase boundary. Within a phase, run to completion exhaustively — do not pause mid-execution for checkpoints and do not stop early on review or QA burden.
At each public phase boundary (Discover → Plan → Implement → Review → QA → Summary), present what the phase produced, name the next phase, and hard-stop for an explicit approval word ("go", "proceed", "approved", "continue", "next", "lgtm", "do it"). A vague acknowledgment ("ok", "sure") continues the current phase; it never crosses a boundary.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
npx claudepluginhub gl11tchy/wannabuild --plugin wannabuild