full-build

Files (1)

• SKILL.md

SKILL.md (first lines)

# full-build

## If the human said "full-build" / "run the framework"

That is a request to drive the framework, not to write code now. Use `hermes-conductor` (in Hermes) or, in another tool, read `build/STATUS.md`, report the next node, and stop. Never restart a checked phase.

## As the full-build card (goal mode, worktree)

1. Setup: you are on branch `build/<idea>/full-build-c<n>`. Full tier: bring in the winning spike with `git merge --no-edit <winner branch from build/08-spikes.md>`. Quick tier (no `08-spikes.md`): start from main and build what `08-sandbox-plan.md` defines.
2. If this is cycle ≥ 2: read the top block of `build/11-verify.md` first. Those failures are your first task.
   Human decisions (`build/gates/*.approved` notes and `build/decisions.md`, all listed in your card) are features on your list too — they override PARKED assumptions and "out of scope" lines written before the human decided. Put each one on the checklist in step 3.
3. Keep a progress file at `build/runs/full-build-c<n>.md` (main checkout BUILD dir): the feature list from `09-who-what.md` (or the plan's demo definition in quick tier) with `[ ]/[x]`, commands run, decisions made. Models tamper with prose less than with JSON — keep it a checklist.
4. One feature at a time: write the failing test, make it pass, run the `verify:` command from `08-sandbox-plan.md`, commit on the worktree branch.
5. Stay inside BoB: the primary reference's approach, not the anti-pattern. Scope creep → note it in the progress file, don't build it.
6. Never delete, skip, or loosen a test to get green. The verifier checks for exactly that.
7. Only claim what you ran. Your handoff `verification` list must contain commands you actually executed with their real exit codes — a "done" that verify then fails is counted against your lane as a false claim.
8. When every feature is `[x]` and verify passes locally: request review (the card body names a different-vendor reviewer). Put the verify command and exit code in your handoff metadata.

Builders never push, merge to main, deploy, or touch credentials. Blocked on a product question → `kanban_block` with the question.

From Kshintak/new-build-framework, MIT.

More from Kshintak/new-build-framework