dxkit-featurelisted

# dxkit-feature This skill drives forward development — building something new — the way `dxkit-action` drives the reverse (fixing what's flagged). Its two jobs: 1. **Orient by graph, not by grep.** Use the code graph to find where the feature plugs in, what patterns already exist, and what a change will touch — at a fraction of the tokens that repeated whole-file reads cost. 2. **Close the loop a plain coding agent skips.** After the edit, run the dxkit analyzers on the change and the guardrail check, so the new feature doesn't quietly ship a vuln, a test gap, or a quality regression. ## The feature loop ``` [1] Clarify → what's the feature + what does "done" mean [2] Orient → query the graph: where it lives, patterns, blast radius [3] Plan → ordered edits, reusing the patterns found in [2] [4] Build → read only the files the graph named, then implement [5] Verify → run the analyzers on the change; confirm nothing regressed [6] Decide baseline→ commit, or re-baseline if the change is deliberately accepted ``` Don't skip [2] or [5]. [2] is where the token saving lives; [5] is the whole reason to use dxkit for forward work instead of a generic agent. ## [2] Orient — query structure before you read files This is the step that differentiates this skill. **Orientation (discovery) is where direct agents burn the most tokens** — grep, read a 2,000-line file, grep again, read another. The graph answers the same questions f