build-pipeline

Orchestrates accepted work from admission through verification and close in the live-spec pack.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/happysasha18/live-spec --skill build-pipeline-happysasha18
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-pipeline
Source: https://github.com/happysasha18/live-spec/tree/main/skills/build-pipeline
Command: npx skills add https://github.com/happysasha18/live-spec --skill build-pipeline-happysasha18

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When an AI coding agent builds from a spec, nothing checks that the shipped code, the tests, and the spec actually agree, and unreviewed behavior slips through green test suites. This Skill closes that gap by admitting work only with a frozen definition of done and a recorded acceptance command, then verifying and closing each task against that contract instead of the producer's self-report. ## Core Features & Use Cases - Task admission and board management: Derives the observable outcome, definition of done, and acceptance command for each request, then writes exactly one row to the plan via scripts/task-admission.py, refusing duplicates and unverifiable work. - Tamper-evident closure kernel: Freezes the definition of done as a hash anchored on a checkpoint, runs the recorded acceptance at verify time, and refuses closes where evidence was voided or the contract moved. - Specialist orchestration: Assembles the smallest graph of specialists (spec-author, test-author, and others) named by the director, with spawn tokens gating every delegated worker. - Project setup walks: Attaches live-spec to an existing project, founds a new one, or catches an install up to the current pack version, plus the MINOR-bump release gate procedure. - Use Case: You say "the report page needs a date filter"; the pipeline admits the work with a testable done condition, calls the right specialists, verifies the result against the recorded acceptance, and closes the row only when the evidence holds. ## Quick Start Say "attach live-spec to this project" to set up your repository, then state any change you want in plain words and the pipeline will admit, build, verify, and close it.

Frequently Asked Questions about build-pipeline

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

FAQPage Schema
How do I set up live-spec on an existing project?▼

Say "attach live-spec to this project" and the skill resolves the pack tree, reads your project tree, and runs the matching setup walk. It handles attaching existing projects, founding new ones, and catching older installs up to the current pack version.

How does the pipeline decide when a task is done?▼

Each task is admitted with a frozen definition of done and a recorded acceptance command. The verify step runs that recorded command, writes a receipt, and close reads the receipt, refusing any row whose contract or tree changed after verification.

What is the difference between director and build-pipeline?▼

Director reads and classifies the human's message and returns a route contract, stopping there. Build-pipeline begins after that contract exists and owns everything from admission and specialist orchestration through verification and close.

Can a task close without running its acceptance test?▼

No. A row with no recorded acceptance cannot be verified at all, and close refuses rows lacking a passing receipt. The acceptance is also re-run in CI at the pushed commit, so a hand-written receipt cannot publish a done nobody earned.

When should I not use this pipeline for a change?▼

Questions, ideas, observations routed as evidence, and halts create no work and get no decision sheet. Authoring the spec, architecture, tests, or code itself belongs to the specialist skills this pipeline calls, not to the pipeline.