sw-do

sw-do — work an increment to done

One loop: pick a task, claim it, implement inside its Files:, prove it with a test, record the evidence. Repeat until nothing is claimable, then verify and close. State is the ledger (sw-task); the spec is the contract.

Run specweave --version: exit 0 → CLI path. Not found → manual path (same files, appended by hand — see sw-task).

Pick the increment

No id given → the single increment whose metadata.json has status: active. Several active → list them and ask which. None → run sw-increment first.

The loop

1. Next — specweave task next <inc>: the first open task whose deps are done and whose Files: no live claim holds. Manual: lowest open T-id in tasks.md with no live claim in ledger.jsonl.
2. Claim — specweave task claim T-01 <inc> (exit 3 = someone owns it, pick another · 4 = Files overlap · 6 = deps unmet). Manual: append {"t":"T-01","e":"claim","by":"<agent>","at":"<ISO>"}. Never edit before claiming.
3. Read — the task's AC: ids in spec.md and its Files:. Read the Approach section for that scope only; do not re-read the whole repo.
4. Implement — inside that task's Files: and nothing else. Need another file → claim the task that owns it, or add a task: ### T-07 Title + - AC: AC-03 | Files: src/b.ts | Test: npm test -- b.
5. Prove — run the task's Test: command. Red → fix; never continue past a failing test.
6. Commit — subject starts with the increment id: git commit -m "0042: fold the ledger".
7. Done with evidence — specweave task done T-01 <inc> --run "npm test -- a" (exit 5 = the command failed, task stays open). No Test: → --evidence "<sha> + what you ran". Manual: append {"t":"T-01","e":"done","by":"<agent>","at":"<ISO>","evidence":"npm test -- a → exit 0 / <sha>"}.
8. Stuck / not needed — task block T-01 --note "<what is missing>" or task skip T-01 --note "<why>" (skip is terminal and needs a reason).
9. Back to 1.