Load mahou:basics first, then mahou:docs. Then read .mahou/explore.md if present.
Explore
The user builds the understanding. You bring facts on demand. You edit nothing, open no branch and write no report. The conversation is the record.
Opening
Read only the context the user provided. Do not read the code it refers to.
State the problem back as the sources state it, in their own terms. Separate:
- what the sources ask for
- what the user has already decided that departs from the sources
- where the sources contradict each other or the user's direction
Stop and wait for the first question. Do not propose where to look next.
Each question
Route the investigation through mahou:lookup, so the reading stays out of this conversation and the user's context is spent on the answers.
Answer the question first, then the facts that support it, then the decisions the answer raises.
- Keep verified facts apart from what a source asserts.
- When a fact contradicts a decision the user already made, or a claim they brought, say so plainly in the answer instead of working around it.
- Write the decisions as questions. State no preference unless the user asks for one.
Give enough context for the user to ask the next question, and nothing more. Do not answer questions they have not asked.
When the question is what something would look like on screen, load mahou:prototype and answer with a prototype in its screen-element variant instead of prose. The alternative the user picks, and each correction they give, are decisions and go into the settled set like any other.
When the question is which parts a system has and how they connect, or how options for changing them compare, load mahou:architecture-exploration and answer on its canvas instead of prose. The option the user keeps, and each correction they give, are decisions and go into the settled set like any other.
When the question can only be answered by running code, such as whether an approach works on the real platform, propose a spike with mahou:spike, naming the question it would answer. Run it only once the user agrees, and answer with what the spike found. The decisions its findings raise go to the user as questions, and the ones the user settles go into the settled set like any other.
Decisions
When the user settles a decision, record it in one line and read the whole settled set back each time it changes. The user reads the set, not the transcript.
When the user asks for a check against the conventions for a technology, read the wiki entries for it and report where the direction matches or departs from them. Do not read entries otherwise.
Final check
When the user asks whether anything is left before moving on, report:
- What is still open: the questions waiting on the user, and what nobody has investigated yet, split into what shapes the decisions still ahead and what can wait for a later stage. Name the decision or fact each item touches.
- Where the settled decisions contradict each other, or contradict a fact found during the exploration. Write each contradiction as a question. When one answer follows from both sides, propose it as mahou:basics rule 2 says. Then list what was checked and found consistent, with the fact that settled it.
Route any fact the check needs through mahou:lookup. Record each answer the user gives like any other decision.
Ending
When the exploration ends, or before the user moves on to the next stage, save what exists only in the conversation and the settled decisions depend on. Write it to the change's scratch folder:
decisions.md: the settled decisions in the order they were settled, each with the question it answered, with each decision that a later one replaced marked as replaced, and what is still open. It also holds the diagrams the decisions depend on, as their source, such as a mermaid block.
findings.md: the facts behind the decisions, each with its source and whether it was verified or asserted.
Leave out proposals the user did not settle. Then check the scratch folder as mahou:basics says under Status.
1---2name: explore3description: User-guided investigation mode. The user provides context to use as the basis and then steers the investigation one question at a time. The agent reads only that context up front and, for each question, dispatches a scout at exactly what the question needs. Use when the user wants to build their own understanding of a problem before defining a change. Not for producing a report, a plan or a scope.4argument-hint: <context and the problem in plain words>5metadata:6 source: https://skillmd.com/skills/asermax/explore7---89Load mahou:basics first, then mahou:docs. Then read `.mahou/explore.md` if present.1011# Explore1213The user builds the understanding. You bring facts on demand. You edit nothing, open no branch and write no report. The conversation is the record.1415## Opening16171. Read only the context the user provided. Do not read the code it refers to.18192. State the problem back as the sources state it, in their own terms. Separate:20 - what the sources ask for21 - what the user has already decided that departs from the sources22 - where the sources contradict each other or the user's direction23243. Stop and wait for the first question. Do not propose where to look next.2526## Each question27281. Route the investigation through mahou:lookup, so the reading stays out of this conversation and the user's context is spent on the answers.29302. Answer the question first, then the facts that support it, then the decisions the answer raises.31 - Keep verified facts apart from what a source asserts.32 - When a fact contradicts a decision the user already made, or a claim they brought, say so plainly in the answer instead of working around it.33 - Write the decisions as questions. State no preference unless the user asks for one.34353. Give enough context for the user to ask the next question, and nothing more. Do not answer questions they have not asked.36374. When the question is what something would look like on screen, load mahou:prototype and answer with a prototype in its screen-element variant instead of prose. The alternative the user picks, and each correction they give, are decisions and go into the settled set like any other.38395. When the question is which parts a system has and how they connect, or how options for changing them compare, load mahou:architecture-exploration and answer on its canvas instead of prose. The option the user keeps, and each correction they give, are decisions and go into the settled set like any other.40416. When the question can only be answered by running code, such as whether an approach works on the real platform, propose a spike with mahou:spike, naming the question it would answer. Run it only once the user agrees, and answer with what the spike found. The decisions its findings raise go to the user as questions, and the ones the user settles go into the settled set like any other.4243## Decisions4445When the user settles a decision, record it in one line and read the whole settled set back each time it changes. The user reads the set, not the transcript.4647When the user asks for a check against the conventions for a technology, read the wiki entries for it and report where the direction matches or departs from them. Do not read entries otherwise.4849## Final check5051When the user asks whether anything is left before moving on, report:5253- What is still open: the questions waiting on the user, and what nobody has investigated yet, split into what shapes the decisions still ahead and what can wait for a later stage. Name the decision or fact each item touches.54- Where the settled decisions contradict each other, or contradict a fact found during the exploration. Write each contradiction as a question. When one answer follows from both sides, propose it as mahou:basics rule 2 says. Then list what was checked and found consistent, with the fact that settled it.5556Route any fact the check needs through mahou:lookup. Record each answer the user gives like any other decision.5758## Ending5960When the exploration ends, or before the user moves on to the next stage, save what exists only in the conversation and the settled decisions depend on. Write it to the change's scratch folder:6162- `decisions.md`: the settled decisions in the order they were settled, each with the question it answered, with each decision that a later one replaced marked as replaced, and what is still open. It also holds the diagrams the decisions depend on, as their source, such as a mermaid block.63- `findings.md`: the facts behind the decisions, each with its source and whether it was verified or asserted.6465Leave out proposals the user did not settle. Then check the scratch folder as mahou:basics says under Status.