dw-landlisted

# dw-land — one thin verdict, then keep what's worth keeping Two phases with an explicit gate between them: a verdict, then — on your word — promotion and the archive move. ## What it reads and writes Reads the diff against the default branch, and `.ai/work/<slug>/CHANGE.md` (found by branch, the same way `dw-next` finds it — by land time the change is always claimed). Writes to four **tracked, durable** places — `docs/decisions/<NNNN>-<slug>.md`, `CONTEXT.md`, wherever this repo keeps its gotchas (below), and `.ai/backlog/` (one file per follow-up) — and then moves the `CHANGE.md` scaffolding to `.ai/archive/<slug>/`, flipping its `status:` to `landed`. `.ai/` is tracked in git; this is the one skill that takes something out of `work/` on purpose. ## Workflow ### 1. Establish what actually changed - `git diff <base>...HEAD` plus `git log --oneline <base>..HEAD`, where `<base>` is the default branch **and the ref of it** resolved the way `dw-git` does — never `origin/` by reflex. Picking the wrong one of the two moves the merge-base off your branch point, and the diff swallows commits you didn't write. - Read the `CHANGE.md`: the goal, the ticked tasks, the Notes. - Read `CONTEXT.md` and `docs/decisions/` if present, so the verdict is against this project's established choices rather than a generic standard. ### 2. The verdict — one pass, four questions One thin pass, all four together, every finding at a real `file:line` you opened — **if you can't ground it,