ripwire-before-you-build

# Before you build — with ripwire > Routing: > • Writing ONE symbol (fn/class/helper) and want to reuse rather than reinvent → **ripwire-reuse-first**. > • You've already written the change and want the pre-submit check → **ripwire-change-check**. > • You want to judge whether the code you wrote got better/worse → **ripwire-quality-bar**. > • Restructuring EXISTING code (not new work) → **ripwire-fresh-eyes**. > • Not sure which skill? → **ripwire-router**. `<dir>` = repo root. `FEATURE`/`APPROACH` = your task in 2–4 plain words; `SYM` = a representative symbol. Run only the sections your question needs — they share the same building blocks. ## Common first move — recall + reusable blocks Almost every section starts here; do it once. **One-call shortcut:** `ripwire <dir> --pack-task="FEATURE"` assembles the recall + `--for` ranking + top bodies + caller signatures + notes + `tests_to_run` into ONE bundle under one token budget — reach for it first instead of firing the calls below one at a time; drop to the individual calls only when you need a specific section's full output. - **Recall prior decisions** — `ripwire <dir> --recall="FEATURE"` → full bodies of the most relevant markdown docs (planning/design notes, READMEs) ranked by relevance. **If a doc already covers this, read it fully — the decision may be made.** Look for explicit "rejected" / "future work" language. - **Reusable building blocks — the one-call write-mode bundle** — `ripwire <dir> --for="FEATURE"` ...