When you have a client or a product and need to understand it before you design or build,Documentation Index
Fetch the complete documentation index at: https://mintlify.com/jsagir/mindrian-os-plugin/llms.txt
Use this file to discover all available pages before exploring further.
/mos:discover runs a guided one-question-at-a-time conversation across six movements and lands a Discovery Brief plus a scaffolded Data Room. It does not design the site; it makes every later decision strategic instead of arbitrary. Larry uses WebFetch to pull external references when needed, alongside standard file and shell tools.
How It Works
Discovery opens with a reframe question — a reward before any interview movement begins. Then Larry leads you through six movements, spending more time where the energy and ambiguity are highest. Between movements, Larry offers a choice gate: go deeper, move on, or branch somewhere unexpected. Larry never dumps a questionnaire. The question bank is the back pocket, not the script. Each question follows from your last answer.The Six Movements
Warm-up and the Real Why
Why does this project exist at all? What happens if it works — and what happens if nothing changes? Larry surfaces the stakes, the urgency, and the internal reality behind the brief.
The Brand's Soul
History, mission, values, personality archetype, and voice. Larry pushes past adjectives like “modern and clean” into stories and the things the brand would never say.
The Product's Essence
What it actually is, the one job it does best, what it replaces, the business case, the non-negotiable constraints, and what “done well” looks like in measurable terms.
The Users and Their Jobs (JTBD)
For each persona: who they are in context, why they “hire” this product, what they “fire” today, and the trigger that sends them looking. Larry completes the job statement: “When I ___ (situation), I want to ___ (motivation), so I can ___ (outcome).”
The Competition and the Whitespace
Who the client admires and why, who they refuse to resemble, and where the whole category looks and sounds the same. The one true sentence no competitor can honestly say.
The Output
After the conversation, Larry synthesizes everything into:- A Discovery Brief filed to the room — brand soul, product essence, personas with JTBD cards, positioning, habit loop, plain-language message, design implications, and open questions
- A scaffolded Data Room with sections per movement, each ready for the next phase
- Persona files at
room/team/ai-personas/with embedded JTBD cards
proposed — it will not harden into a fact until you confirm it.
After Discovery
Once the Discovery Brief is complete, Larry bridges it to a plain-language message (“explain it to a smart twelve-year-old”) and routes to/mos:ignite for room birth. The brief content pre-fills the B2 blueprint gate.
Usage
All discovery content — brand soul, product essence, persona names, JTBD content — stays local. None of it enters a Brain query. The only Brain-bound value is the generic framework handle used to fetch methodology guidance.