Explorations

An exploration builds something to answer one question. Use it for what only building can tell you: how it looks, if it works, or how much work it is. It does not change the repositories. Its artifacts stay in its folder, because they are progress.

intake writes explorations/E-001-<slug>/exploration.md, with its status at ready.

#Two ways to run one

#Wireframes and design

The explore skill works in a fixed order: references, wireframes, a lock, design rounds, a choice. It waits for you at each step. 6. Explore walks through it.

#From an exploration to tasks

After you accept an exploration, its status is done. Then run intake with its id, and it writes the change tasks. Each task gives the id in exploration, and it can use the artifacts as a reference.

The status becomes consumed when each of those tasks is done.

The changes under ## Context changes of an exploration do not go to context/ when you accept it. intake copies them to the change tasks. They reach context/ when you accept those tasks.