box-it-up

Files (1)

• SKILL.md

SKILL.md (first lines)

# box-it-up

Three steps; your card's `Args.step` says which one you are.

## step: plan

Read BoB + assumptions + human decisions (`build/gates/*.approved` notes and `build/decisions.md` — binding, they override PARKED items). **Quick tier** (`Args.tier: quick`): there is no BoB or spike — plan straight from `00-intake.md` + `01-assumptions.md`, and make the demo definition the whole deliverable. Write `build/08-sandbox-plan.md` (`~/.build-framework/templates/build/08-sandbox-plan.md`):

- Demo definition — the smallest thing that would falsify the idea
- `verify: <one shell command>` — exit 0 means the demo works (this line is required)
- Out of scope (explicit)
- Budget per spike (default `router.yaml budgets.spike_max_usd_each`)

## step: spike (one card per spike, parallel, each in its own worktree)

1. You are in an isolated worktree on branch `build/<idea>/spike-<name>-c<n>` (card body). Never touch main.
2. Build only the demo. No extra features, no refactors outside the demo.
3. Run the `verify:` command. If red, patch up to 3 times, then stop.
4. Commit on the worktree branch (local only; never push).
5. Write `build/spikes/<name>.md` in the **main checkout's** BUILD dir: result (PASS/FAIL), verify command + exit code, `git diff --stat` vs base, branch, worktree path, cost, what you would do next.
6. Request review as the card body says (a different vendor reviews). This is a goal-mode card: the judge keeps you going until the report and verify evidence exist.

## step: compare

1. Read `build/spikes/*.md` and each branch's diff (`git diff <base>...<branch> --stat`).
2. Pick a winner against the plan's demo definition — not the prettier code. A spike whose verify failed cannot win unless every spike failed (then say so).
3. Write `build/08-spikes.md`: winner, **branch**, why, and the loser's one idea worth keeping. (Hermes removes spike worktrees after this card; the branches stay.)
4. End with the human instruction for the gate:
   > `git -C <repo> worktree add .worktrees/review-<winner> <winner branch>`, open that folder in Cursor, and review the diff against `build/08-sandbox-plan.md` (the `review-diffs` rule helps). Then `hbs approve gate-cursor --note "..."`.

From Kshintak/new-build-framework, MIT.

More from Kshintak/new-build-framework