How to use daedalus
Daedalus is for an idea that is not yet work. You think it through together, over as many sittings as it takes, and when the idea is ready it goes to metis as a plan document.
In the chain, it comes first: idea → daedalus → metis → coordinator → your agents → you.
How it works
- You start it in the repository the idea is for. It says who it is and lists the ideas already there. The first time it runs in a workspace, it also asks up to five questions on how you like to work.
- Each sitting is a round. It brainstorms with you into one running
document — one page, with a poster drawn beside it — and offers options
with the one it leans to. Zeus shows the idea in the app as an
exploration,
E-n. - Research is asked for. When a question needs research, it names the topic and what it would settle, and asks first. On your yes, one helper researches it.
- Every round ends the same way: one pull request for the page, and one question — go on, shelve it, or hand it to metis.
Four things to say
zeus run daedalus
Run it in a terminal, in the repository. It starts the conversation.
New idea: <the idea in one sentence>. What matters most to me is <…>.
Its first question asks for exactly this. The second half matters: it is what the document is built around.
Yes, run it.
Say it when it proposes a research run and you want the answer. Say no, and the round goes on without it.
Hand it to metis.
Say it to the round’s question when the idea is ready. Daedalus writes the
plan document, plan.md, and ends with the next step:
next: run metis — zeus run metis — and give it <path>.
What it never does
- It never shelves an idea or hands it on by itself. Both are your words.
- It never starts metis, or any other agent.
- It writes no code, takes no task, and files no task on its own.
Next: How to use metis →