setup-cliban

# Setup Cliban Scaffold the per-repo binding that every cliban workflow skill — and any third-party craft stack — reads: - **The adapter** — `docs/agents/issue-tracker.md`, declaring cliban as this repo's issue tracker and recording the four bindings (project key, craft stack, key policy, branch convention) - **The pointer** — an `## Agent skills` block in `CLAUDE.md` / `AGENTS.md` so agents find the adapter - **The board** — the cliban project itself, created if missing This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write. ## The division of artifacts (doctrine, not a question) Cliban is for work-lifecycle artifacts; the repo is for knowledge that outlives the work. Write this into the adapter as-is — it is the contract's foundation, not a preference to collect: | Artifact | Home | Why | |---|---|---| | Spec / PRD | issue `## Spec` | scoped to the work | | Implementation plan | issue `## Plan` | nobody needs ticked checkboxes in git history | | Progress, findings, dead ends | issue `## Activity Log` via `issue log` | timeline, not documentation | | Durable reusable lessons | project `## Notes` via search-first round-trip | queryable across sessions | | ADRs, `CONTEXT.md`, domain docs | **the repo**, plaintext, git-tracked | survives contributors, travels with clones | ## Process ### 1. Explore Read whatever exists; don't assume: - **Cliban availability** — probe `cliban --help`. If missing, st...