2-build

Implements an approved plan file step by step, recording deviations and test results.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/AiFirstDevelopment/quorum --skill 2-build-aifirstdevelopment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 2-build
Source: https://github.com/AiFirstDevelopment/quorum/tree/main/plugins/quorum/skills/2-build
Command: npx skills add https://github.com/AiFirstDevelopment/quorum --skill 2-build-aifirstdevelopment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding sessions often drift from what was agreed, improvise scope, or silently work around a flawed plan, leaving no record of what actually happened. This Skill enforces disciplined implementation: it builds only what an approved plan specifies, ticks off steps as it goes, and records every deviation so later review has an honest baseline. ## Core Features & Use Cases - Plan-gated execution: Reads docs/work/<slug>/plan.md in full and refuses to build unless the plan status is approved, preventing unauthorized work. - Resumable step tracking: Ticks each step's checkbox in plan.md as it completes, so an interrupted session can resume exactly where it stopped. - Deviation and PLAN DEFECT logging: Appends deviations to Build notes and flags genuinely wrong plans under a PLAN DEFECT heading, which downstream review escalates. - Honest test reporting: Runs the repo's test suite and records the result as green, red, or none in the state file, never reporting success over failing tests. - Use Case: After approving a plan for a new API endpoint, run this step to have the change implemented exactly as specified, with each step checked off, two minor deviations documented, and the test suite result recorded for the review stage. ## Quick Start Run /quorum:2-build with the slug of an approved plan in docs/work to implement it step by step.

Frequently Asked Questions about 2-build

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

FAQPage Schema
How do I implement an approved plan with the quorum pipeline?▼

Run /quorum:2-build with the plan's slug. The Skill reads docs/work/<slug>/plan.md, verifies its status is approved, then implements each step in order, ticking checkboxes as it goes and updating the plan status to built when finished.

What happens if the plan has not been approved yet?▼

The build stops and asks for confirmation. It shows the plan's Intent, Acceptance criteria, and Non-goals, and states plainly that the plan has not been approved, so a human explicitly authorizes the work before any code is written.

How are deviations from the plan recorded during a build?▼

Deviations are appended to the Build notes section of plan.md as they happen. If the plan itself is wrong, the issue is recorded under a separate PLAN DEFECT heading, which the later adjudication step escalates and counts separately.

Can the build step change scope or fix unrelated issues it notices?▼

No. The plan bounds the work, and scope changes are escalated rather than absorbed. Unrelated issues are noted for the user instead of being fixed, and Intent, Acceptance criteria, and Non-goals sections are never edited.

What happens when tests fail after implementing the plan?▼

The suite result is recorded honestly as red in the state file, and the build is not reported as complete with failing tests. Existing tests are never weakened or deleted to make a change pass.