create-mode

# Create Mode A guided journey for adding a new mode to Pneuma Skills. The journey has **three phases** — Discovery (ask the right questions), Brief (write down every key choice with rationale and get the user's confirmation), Implementation (generate files). Each phase has a clear handoff to the next; **never skip Brief**. Pneuma already has twelve modes and a stable contract layer; the cost of a thoughtful 10-minute design brief is much smaller than the cost of building the wrong viewer. The reference material in `references/` is where the **knowledge** lives — go read the relevant one whenever you're about to make a meaningful decision. SKILL.md is the **journey**, not the textbook. --- ## When to use Trigger this skill when the user asks for any of: - "create a new mode for X" - "fork slide / webcraft / … for a different domain" - "scaffold a mode" - "add a [mindmap | spreadsheet | timeline | annotator | …] mode" - "design the viewer for a mode that …" If the user *only* asks about an existing mode's behavior, this skill is **not** the right tool — direct them to `docs/reference/viewer-agent-protocol.md` or the mode's own SKILL.md. --- ## Phase 1 — Discovery interview Goal: extract enough signal that you can fill every field of the design brief without further interrogation. Ask **one question at a time** with `AskUserQuestion`; let each answer shape the next. Don't dump a 20-question survey on the user. ### Discovery questions (ask in this order, branch as not...