← ClaudeAtlas

veri-product-discoverylisted

Turns a vague idea into a defined problem, a direction, non-goals and the first named bets — the gate an empty or reopened record passes through before anything can be required of it. Use it when the utterance carries enough to argue with: "I have an idea for a tool that helps freelance designers chase unpaid invoices, nothing is written down yet", "we are pivoting, the team-collaboration angle is not landing and I want to restart from the solo user's problem", "nobody is using the free tier and we never defined the problem it solves". It interviews Socratically, one question at a time, then files a product-brief source and one draft requirement per foundational bet. Not for a record whose problem is settled and whose user is the thing in doubt: "we keep writing 'small teams' into every requirement and I could not tell you who that actually is" is veri:user-discovery's, because what is undefined is who rather than what. Not for a bare "I have an idea" carrying nothing — that is veri:wayfinder's triage — nor f
danielyayla/veri · ★ 0 · AI & Automation · 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-003**, at `veri/methods/product-discovery.md`. Before doing anything else, read it: fetch `MET-003` 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`, `file_requirement`, `get_intent`. 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).