dw-shapelisted

# dw-shape — one file, then build **This skill synthesises; it does not interview.** If the idea is still fuzzy, run `dw-grill` first and come back — mixing the two produces a document arguing with itself. ## Output location Write to `.ai/work/<slug>/CHANGE.md` — tracked, so it survives a `/clear`, and **working scaffolding rather than a deliverable**: `dw-land` archives it at merge, after promoting anything durable out. 1. **Resolve the branch first — it is the key every other solo skill uses.** `git rev-parse --abbrev-ref HEAD`, resolving the default branch the way `dw-git` does. - On the **default branch**: write `branch: unclaimed` — the literal sentinel. The change is shaped but not yet owned; `dw-start` or `dw-next` claims it later by flipping this field. Shaping several unclaimed changes in one sitting is the plan-session pattern. - On any **other branch**: record the value **verbatim** — shaping on a feature branch is shaping and claiming in one step. `dw-next` and `dw-land` find this file by grepping for it, so a placeholder left in place orphans the change. - **Detached HEAD** — it resolves to the literal `HEAD` (a `git worktree add` without `-b`, a bisect, a tag checkout): **say so and ask which branch to record.** Never write `HEAD`. 2. **Don't start a second change on the same claimed branch.** Look for an existing one first: `grep -l "^branch: $(git rev-parse --abbrev-ref HEAD)\$" .ai/work/*/CHANGE.md 2>/dev/null`. If