ask-mohlisted

# Ask moh You don't remember every skill, so ask. This is a router: figure out what the user is trying to do, name the skill or flow that fits, and point at the moh documentation when the question is about moh itself. ## Workflow mode gate (read this first) Every workflow skill below has a slash command (`/implement`, `/tdd`, …), and **those commands only exist while workflow mode is on**. The current state is injected into your prompt (`Workflow mode is currently on|off`). When the user intends to **start a workflow** and workflow mode is **off**: 1. Say so plainly: workflow mode is off, and the workflow commands are unavailable until it's on. 2. Tell them to run **`/workflow on`** — you cannot toggle it yourself (it copies the first-party skills into `~/.moh/skills/`, records the manifest, and persists the toggle in the user config; that is TUI-side machinery, not something an agent turn can do). 3. Stop there. Once they have run `/workflow on` they can re-ask, and the full flow below applies. Never suggest workarounds for a disabled workflow (no "read the SKILL.md from the bundle by hand") — the gate is the gate. With workflow mode **on**, route freely. ## The main flow: idea → ship The route most work travels. You have an idea and want it built. 1. **`/grilling`** — sharpen the idea by interview. Start here. It is the interview primitive: rounds, the frontier, facts are the agent's job and decisions are the user's. When it runs inside a repo it should drive **`/d