← ClaudeAtlas

veri-evidence-intakelisted

Staffs the evidence door: takes material arriving from outside — user feedback, metrics, a support ticket, a competitor move, an incident, research findings — and files it as a source linked to what it bears on, so it lands on the graph instead of in a drawer. Use it when something external is pointed at the record: "here is a support thread where three customers hit the same import failure, get it on the record against whatever it bears on", "last month's activation numbers came back for the onboarding release, file them", "a competitor just shipped the thing REQ-021 bets against, where does that go?". It files the material faithfully, with tests, supports or refutes links to the requirements and outcome-of links to the shipping work orders, and leaves what it means to you. Not for judging a bet whose evidence is already in: "did the caching work actually move p95 latency to the target REQ-028 declared?", "all of REQ-035's work orders are done, was the bet right or do we retire it?" are veri:did-it-work's, w
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-004**, at `veri/methods/evidence-intake.md`. Before doing anything else, read it: fetch `MET-004` 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: `file_source`, `search`, `get_neighbors`, `get_import_instructions`, `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).