build-loop

Solid

Drive a build to actually-works, near-finish-line craft by looping build → see → exercise → check → critique → rebuild over the agent's existing tools (bash build/test, headless screenshot + vision, Playwright, axe/Lighthouse) until acceptance criteria pass or an explicit stop-condition fires — no infinite thrash. ALWAYS invoke when the user says any of "tighten this build", "iterate until it passes", "self-verify the UI", "make it actually work, not just compile", "loop until the core flows pass", or "drive this to near-finish-line". Also invoke proactively after a scaffold or feature lands and before handing a draft to a human. Composition-first over existing tools, not a new program; it states its own honest bounds — objective craft only, taste self-graded, ~80% ceiling, market validation out of scope. Do NOT use to decide WHAT to build (that's ideate) or whether a design/strategy is sound (deep-dive).

AI & Automation 83 stars 8 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
64
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Build-Loop — see-and-exercise iteration until a build actually works `build-loop` takes a build that compiles-but-isn't-done and drives it toward **near-finish-line craft** by repeating one disciplined cycle — **build → see → exercise → check → critique → rebuild** — until its acceptance criteria pass or a stop-condition fires. It doesn't just re-read its own plan; it *runs, sees, and exercises what it built*, then feeds those observations back into the next rebuild. It is **composition-first**: it orchestrates tools the agent already has — `bash` (build/test), a headless screenshot + vision to *see*, Playwright/headless to *exercise* the flows, `axe`/Lighthouse to *check* — via prose. It is **not** a new program, and not a reinvention of the see-and-exercise agents vendors already ship; it's the discipline that wraps them: a target, a loop, a stop-condition, and an honest ledger of what was actually checked. This skill is the downstream partner to `prompt-pack` (which sequences *what* to build) and `ideate` (which decides *whether* to build it). It carries `prompt-pack`'s execute-discipline (**never fake a signal you didn't run**) and `ideate`'s conditional-design (**a design bar only when feel is load-bearing**). ## When to use this **Strong triggers — invoke without asking:** - "Tighten this build" / "drive it to near-finish-line" / "make it actually work, not just compile" - "Iterate until it passes" / "loop until the core flows pass" - "Self-verify the UI" / "see ...

Details

Author
nelsonwerd
Repository
nelsonwerd/idea-to-ship-skills
Created
2 months ago
Last Updated
2 weeks ago
Language
Shell
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

loop-builder

Build a file-based agent loop (harness) for a long, powerful task BEFORE running it — so you design the loop and only verify the output, instead of supervising every step. Runs a short interview (goal, done-condition, non-goals, verify commands), scaffolds loops/<slug>/ with VISION.md + specs + IMPLEMENTATION_PLAN.md + AGENTS.md + PROMPT files + loop.sh, runs PLANNING, gets ONE plan approval, then loops BUILDING autonomously and hands back the diff + eval results. Trigger when the user says "loop-builder", "/loop-builder", "build a loop", "create a loop for X", "set up an autonomous loop", or asks to run a long autonomous task (a feature, a refactor, a tool, a content batch).

2 Updated 4 weeks ago
criscatalyst
AI & Automation Listed

loop

The build loop - locate yourself, investigate the real code, build one slice completely, verify it for real, fix and re-verify, then close and hand off. Use for any session that is implementing something from the plan.

8 Updated 1 months ago
cbdreamer11
AI & Automation Listed

build-loop

Autonomous generator-evaluator cycle that builds a feature against contract.json, with the evaluator launching the live app via Playwright MCP for grading. Generator and evaluator have separate context windows. Loops until pass, restart, or max iterations. Use after /contract is written, for new features (not bugfixes — those use /diagnose + /tdd). User triggers — /build-loop, "autonomous build", "let it cycle", "generator-evaluator", "GAN loop". Requires Playwright MCP installed and contract.json present.

0 Updated 1 months ago
createusernam