superclaritylisted

# Route the work, own the state Long tasks do not fail in the middle of a step. They fail at the seams: work starts before anyone agreed what it was, a plan assumes a tool this machine does not have, or the session ends and everything learned evaporates. This skill guards the seams. Answer the user in whatever language they wrote in. These instructions are English; your replies are not. ## This is the entry point For any multi-step work task, start here and route from here. The other five skills are phases of one workflow, not five independent tools — entering at `drafting-plans` produces a plan for something nobody agreed to. If you were loaded mid-workflow anyway, that is fine: read `.superclarity/` first, then continue from the phase the state implies rather than the phase you were called for. ## Open with the gate, in writing The normal failure here is not a bad brief. It is no brief: the ask looks clear, the host is pushing for a fast answer, the phases read as advice, and nothing detects the skip until delivery. So make the routing visible before anything else, in three lines: ``` Task: <slug> Phase: <clarify | survey | plan | run | verify> Gate: <what must be true before the next phase starts> ``` Then hold it. **Until `brief.md` exists and the user has approved it, only read-only calls are permitted** — reading your context, reading files, listing what is installed, and writing inside `.superclarity/`. Nothing spent, nothing sent, nothing changed outside th