keel-devlisted

# Keel Dev — development conductor **User-invoked conductor, not an auto-firing router.** You reach for it by name when you're doing dev work; it orchestrates the pipeline and pulls in the right specialist per phase. It carries **zero context cost** until invoked. It writes no product code itself — the phase skills do that. **Backbone = Pocock (`mattpocock/skills`). gstack + superpowers = opt-in power-tools. keel-v2 governs everything.** ## Deference — keel-v2 is the arbiter Scan the nine danger surfaces first, record the lane line (`Rigor: FAST/HEAVY — …`). keel-v2's /review tripwires, a11y, design conformance, and human gates outrank every phase and every power-tool. A power-tool's own ethos (e.g. gstack "boil the ocean") is subordinate to keel-v2. ## Comprehension — graphify-first To understand the code (how X works, what depends on Y, data flow, blast radius, architecture) **query graphify** (`query`/`path`/`explain`) instead of grep+read — it returns a targeted subgraph, not a dozen file reads. **Grep only** for an exact known string/symbol, a tiny throwaway scope with no `graphify-out/` yet, or an area just edited (graph may be stale). Default graphify; grep is the deliberate exception. ## The pipeline (spine default · power-tools opt-in) | Phase | Default (Pocock spine) | Opt-in power-tools | Rigor | |---|---|---|---| | 0 · Align | `grill` — one Q at a time, look up facts, recommend answers | gstack `/office-hours` for product/scope reframes | HEAVY/ambiguous only