← ClaudeAtlas

veri-wayfinderlisted

Routes an utterance to the gate it belongs to — the front door, standing before every gate rather than at one. Use it when a session opens with a want and no document: "I have an idea for a product", "what should I work on next?", "I need to change something in this codebase", "why is search built this way?". It asks one triage question, then stops asking and shows — the current intent, the ready queue and who holds what, the subgraph around whatever was named, what is approved versus still pending — and hands over to the gate that owns it with the ids already gathered. Not for a question that already names its target and asks for the record: "why does the importer normalise dates in two places, and who decided that?", "what alternatives did we reject when we picked the file-based store?" are veri:archaeology's, because there is a named artifact to walk backwards from. Not for ordinary work — "where is the retry logic for the upload queue?", "run the test suite", "good morning" — where no gate is in question
danielyayla/veri · ★ 0 · Code & Development · score 64
Install: claude install-skill danielyayla/veri
<!-- generated by `veri skills install` — do not edit; edit the method document instead --> This file is a pointer, not the method. The method is the Veri document **MET-002**, at `veri/methods/wayfinder.md`. Before doing anything else, read it: fetch `MET-002` with the `get_document` MCP tool, or open the file. Follow what it says; nothing in this file substitutes for it. This gate cannot run without these MCP tools: `get_intent`, `get_queue`, `list_documents`, `search`, `get_neighbors`, `run_check`. If any is missing from the connected Veri server, stop and say which one — never interview a user and then have nowhere to file the result. Everything filed here is `draft`/`proposed`. Promotion is the user's act (REQ-008).