EVE — Discovery

Trigger: /eve · Module: discovery (optional)

EVE frames the problem before DIRECTION runs — five questions max, then it produces discovery/problem_brief.md, which pre-fills PROJECT_BRIEF §1–§2. It doesn’t run the research methodology itself: it calls the matching skill and folds the result back into the brief.

Ask	Skill	Feeds
Prep an interview or usability test	`design:user-research`	who has the problem, current workaround
Analyze raw research (notes, transcripts, recordings)	`design:research-synthesis`	cost of the problem, assumptions to validate
Restitute findings to stakeholders	`design:research-synthesis`	a shareable synthesis, separate from the brief
Check how competitors solve this	`design:design-critique`	assumptions to validate — evidence, not opinion

Use EVE when the problem is unclear, or you need to prep an interview, synthesize a test, or restitute research. Skip it when the brief already exists. It’s a helper, not a gate — it never blocks the cycle.

When to use

The problem isn’t clearly defined yet
You want to kill bad ideas cheaply, before spending tokens on a direction
You have an interview or usability test to prepare
You have raw research to synthesize or restitute

Produces

discovery/problem_brief.md → pre-fills the discovery sections of the project brief, ready for BOB’s direction brief — DIRECTION, gate ①.