← ClaudeAtlas

goal-verified-treenavlisted

The tree-nav arm of goal-verified — same independent-verifier build loop, but the recalled-lessons leg is swapped from preflight's flat embedding/keyword recall to coarse-to-fine topic-tree navigation (memory-tree-nav). The recall leg is gated by a trace-verified span check that makes silently skipping it a wall, not an option. Use to run /goal, build, implement, refactor tasks when you want to pin the bar by *browsing the knowledge tree by subsystem* instead of routing the goal text through the recall ranker — and to A/B the two recall mechanisms head-to-head.
caiuswang/regin · ★ 3 · AI & Automation · score 76
Install: claude install-skill caiuswang/regin
# goal-verified-treenav This is a **sibling of `goal-verified`** that exists for one reason: to swap the *recall mechanism* and compare. Everything about the loop — pin a falsifiable bar before building, build then STOP, verify with a fresh adversarial reviewer + machine gates, fix, commit, feed the outcome back — is **identical** to `goal-verified`. The only change is **how step 1 recalls past lessons into the bar**: | | recalled-lessons leg | how it pulls | |---|---|---| | `goal-verified` | flat recall (`goal preflight --with-lessons`) | routes the **goal text** through the recall ranker → a flat, importance-ordered list (recall-first, may surface vocabulary-only matches) | | `goal-verified-treenav` (this) | `memory-tree-nav` (`index_root`→`index_expand`→`index_fetch`) | **you walk the topic taxonomy by subsystem**, reading node blurbs as gates, and fetch only the leaves the goal touches (precision-first, explainable path) | The rest of the bar — convention **skills**, **reference components**, **hard gates** — is *not* routed by a command in this arm: the hard gates are the universal floor (stated inline in step 1a), the convention skills come from the file-keyed convention mapping your repo defines (e.g. a `CLAUDE.md` / `CLAUDE.local.md` table or its lint config), and the reference components come from the topic leaf's source refs (step 1b). So the *only* variable that differs from `goal-verified` is the way lessons enter the roadmap — same loop, same scaffold, differe