solo-build

Executes slice-by-slice software builds with anchor validation and independent review gates.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill solo-build-scoots31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solo-build
Source: https://github.com/scoots31/engineering-playbook/tree/main/skills/solo-build
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill solo-build-scoots31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solo builders using AI assistants often jump straight into coding without verifying that a slice is ready, that the design matches available data, or that the output actually meets its done criteria. This Skill enforces a disciplined build execution workflow so every slice is anchored, verified, and independently reviewed before it is considered complete. ## Core Features & Use Cases - Status-gated slice selection: Only Ready slices enter build, selected automatically by plan priority and journey order, with dependency blocking enforced. - Four-anchor validation: Every slice requires a design anchor, data anchor, done anchor, and process anchor, plus a design-to-data correlation gate that hard-stops on missing fields. - Independent review handoff: The builder runs an observation-only QA pass, then hands off to a Review Agent that independently verifies design fidelity, data store contents, and done criteria before clearing the slice. - Use Case: A solo founder building a web app with Claude Code invokes build mode; the Skill reads the backlog, picks the next Ready slice, confirms the design file and mock data fields match, builds the feature, runs a preview server QA pass, and hands off to the Review Agent for an independent CLEARED or GAPS verdict. ## Quick Start Ask the AI to start the next build slice from the backlog and it will select the highest-priority Ready slice, verify its anchors, and begin building.

Frequently Asked Questions about solo-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce build discipline when coding with an AI assistant?

Use a status-gated build workflow where only slices marked Ready can enter build. The Skill reads the backlog, selects the highest-priority Ready slice in journey order, and refuses to start work on slices with open design decisions.

How to verify design matches data before writing code?

Run a design-to-data correlation gate before creating any branch. Extract every data-sourced element from the design file, cross-reference each against the mock data spec, and hard-stop if any field is missing so the solo decides whether to update the data spec or revise the design.

Can the AI builder declare its own work done?

No. The builder only runs an observation-only QA pass producing a manifest of what was seen in the preview, console, network, and data store. An independent Review Agent then verifies done criteria from source files and returns CLEARED or GAPS.

Does this build workflow work in both Cursor and Claude Code?

Yes. In Claude Code the Review Agent and code review run as spawned sub-agents. In Cursor, where no Agent tool exists, the same review skill is read and executed inline with the same independence standard.

What happens when a build reveals a design or process conflict?

The builder stops and surfaces the conflict with explicit options for the solo to decide. If the to-be process map itself is wrong, the slice returns to In Review and a process-change skill is invoked before build resumes.