adrlisted

# ADR-Driven Development (front-end for `adr → nightshift`) Turn an intent into one **grounded, cited, build-ready ADR**, then hand it to `nightshift:plan`'s landing step. This collapses `brainstorm → spec → writing-plans → nightshift` into **`adr → nightshift`** for "I know what I want, build it" work. The arc: ``` intent → GROUND → ADR (you approve) → plan PR → Nightshift lands it → you ratify ``` **Stay thin.** This skill is a four-phase orchestrator — prose plus the two embedded blocks below. The determinism lives in Nightshift's `loop/`, not here. One ADR doc, not a multi-file apparatus. For exploratory "not sure what I want yet" work use `brainstorming` first. ## Phase 1 — Ground (scaled) Read the real code and current external practice the change touches. **Default inline; escalate to a `/deep-research` fan-out only when the change is novel, cross-cutting, or the user asks** — a research fan-out on a one-line change is the ceremony to avoid. - **State grounding:** LSP (symbols/types/refs), `git` history, an `Explore` agent for breadth. - **Research grounding:** `context7` for library docs, the cloudflare MCP for CF, a `/deep-research` fan-out for novel/cross-cutting work or on request — current external knowledge, not ~1-year-stale training. - **Record which mode was used** (inline vs research fan-out) in the ADR. **Output:** a grounding brief — every claim already cited — that feeds the ADR. ## Phase 2 — Author the ADR Write `docs/adr/YYYY-MM-DD-<slug>