Agent Buildprint

Buildprints are executable implementation packets for coding agents.

Skills improve the worker. Buildprints package the work. A skill teaches an agent how to debug, design, review, search, or use a tool well. A Buildprint tells an agent what to install, change, or build in a target codebase and how to prove it worked.

Browse published Buildprints and copy the shortest start command here:

https://agent-buildprint.com/

Shortcuts

AGB is the optional CLI helper for loading exact Buildprint snapshots into a workspace. The v0.1.0 source tag contains the v2 runtime, but npm 0.1.0 is not published and public 0.0.17 lacks v2. For current v2 work, use one fresh source checkout and record its HEAD:

git clone https://github.com/DomEscobar/agent-buildprint agent-buildprint-runtime
git -C agent-buildprint-runtime rev-parse HEAD

Then start from a published Buildprint:

node agent-buildprint-runtime/bin/agb.js start \
  https://agent-buildprint.com/buildprints/buildprint-mapper-os/package.json ./my-build

No global install required:

git clone https://github.com/DomEscobar/agent-buildprint
node agent-buildprint/bin/agb.js start \
  https://agent-buildprint.com/buildprints/buildprint-mapper-os/package.json .

Optionally install the local agent skill harness:

agb harness init .
agb harness check .
agb harness checkup .

Then give the workspace to your coding agent and tell it to read:

.buildprint/next-agent.md

Common Commands

agb start <buildprint-package-json-url-or-file> [target-folder]
agb packet check <packet-folder-or-package-json-url>
agb packet next <packet-folder-or-build-state-folder>
agb harness init [project-folder] [--profile webapp] [--profile backend]
agb harness check [project-folder] [--profiles webapp,backend]
agb harness checkup [project-folder] [--profiles webapp,backend]
agb --help

What You Get

A Buildprint snapshot is a kernel packet: goal, minimal setup, identity when UI-bearing, named loops, independent contract review, blockers, and handover. Default execution is goal → bare agentic loop → optional independent subagent fan-out → contract review. Production harness maturity is an upgrade, not the floor.

The point is not to guess from a repo blindly. The point is to give the agent a precise build path it can follow, while still allowing explicit wishes such as a different door, a bigger garden, or another extension.

Product Buildprints package whole systems. Capability Buildprints package bounded integrations such as Stripe subscriptions, RBAC permissions, API key management, webhooks, auth, analytics, or deployment.

Guided game packet

Guided 2D Game / vertical slice guides scoped intake, graybox/art convergence, coherent sprite animation, validated world placement and evidence-backed game QA. It includes dependency-free contract validators and negative fixtures—not a prebuilt game or paid-generation requirement.

Full standalone isometric game packet

Full Standalone Isometric Game covers the entire agreed original game using a pinned Isometric Framework scaffold and its existing skills: one approved contract, separate world assembly and per-family image-source choices, mobile-first UX, complete world/gameplay production, and user-requested running-build visual/gameplay acceptance. It is separate from Guided 2D Game and does not cap delivery at calibration.

Scaffold the pinned framework host first. Keep one fresh Agent Buildprint source checkout beside it, record that checkout's HEAD, and start the matching local packet with its CLI:

git clone https://github.com/DomEscobar/agent-buildprint.git agb-runtime-v2
git -C agb-runtime-v2 rev-parse HEAD
node agb-runtime-v2/bin/agb.js start agb-runtime-v2/buildprints/standalone-isometric-game/package.json ./my-isometric-game
node agb-runtime-v2/bin/agb.js state status ./my-isometric-game
node agb-runtime-v2/bin/agb.js loop next ./my-isometric-game

git clone https://github.com/DomEscobar/agent-buildprint.git agb-runtime-v2
git -C agb-runtime-v2 rev-parse HEAD
node .\agb-runtime-v2\bin\agb.js start .\agb-runtime-v2\buildprints\standalone-isometric-game\package.json .\my-isometric-game
node .\agb-runtime-v2\bin\agb.js state status .\my-isometric-game
node .\agb-runtime-v2\bin\agb.js loop next .\my-isometric-game

start records packet state; it does not scaffold the framework host. The framework remains separately pinned and locally built as described by the packet. AGB does not bundle framework skills or inject them into an agent session: the host reads the installed framework catalog and the selected skill files. Remote hosted manifests are separate website bytes; npm publishing does not update them or existing snapshots. Remote v2 starts still require an exact manifest SHA-256 from a separately trusted channel. See CLI limitations, release notes, and the historical authoring report.

Opt-in local runtime v2

CLI runtime guide: safe staged start, copy-only pinned bootstrap, resumable hash-linked state, explicit approvals and loop transitions, defects/returns, skill-file routing, and current-build-bound evidence attestations. state status, loop next/begin/accept/advance, evidence bind/record are real commands; none execute tests, manifest scripts, providers or deployment. Legacy manifests keep legacy state and packet operations; there is no automatic migration. Existing state/user files are never overwritten. Byte hashes and recorded review claims are not publisher authentication or verified visual acceptance. Source delivery report.

Local Development

From this repository:

node ./bin/agb.js --help
npm run check:syntax
npm run check:packet:mapper
npm run check:packets
npm run check:guided-2d-game
npm run check:standalone-isometric-game
npm run check:capabilities
npm run check:authors
npm run check:capability:regressions
npm run eval:mapper-overhaul
npm pack --dry-run

Node.js 20 or newer is required.