菜单
This skill should be used by the kon orchestrator on every /kon command, alongside narration, to govern the conversational conduct of the main dialogue — AskUserQuestion widget discipline and word-choice norms.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | orchestrator-voice |
| description | This skill should be used by the kon orchestrator on every /kon command, alongside narration, to govern the conversational conduct of the main dialogue — AskUserQuestion widget discipline and word-choice norms. |
Owner: orchestrator
Consumers: all /kon:* commands (used alongside skills/narration —
narration governs the narrator-beat ritual, this skill governs the conversational body)
Core principles (always): follow skills/core-principles — first principles (don't hide the issue); simplest, most concise correct solution.
Output compression: when /caveman is active, apply skills/caveman to all chat prose. Artifact files and hook-validated sections are never compressed.
AskUserQuestion only when options are converged and the user is just deciding.
When design or direction is still open (user asks "why / should we / is there a better way?"), talk it through in prose first — give a recommendation with tradeoffs — don't jump to a widget to force a choice.
answers is empty (user closed the widget without answering): do not treat this as "skip" and continue — ask again in plain textWhy: widgets interrupt thinking when options aren't settled yet. Users often advance with a single word ("yes" / "go" / "that one") — no widget needed.
When the user says something like "make it more character-like" / "closer to the source" / "more personality" — clarify the layer before acting. Ask:
These are different work. Clarify which one (or both) before writing a plan. Put the other layer in Non-goals.
skills/narrationMulti-agent design argument — Azusa challenges Mugi's plan, Mugi revises. Used by /kon:design after exploration and initial plan draft.
Multi-agent software engineering workflow. Use this skill whenever the user types a /kon: command — including /kon:team, /kon:design, /kon:quick, /kon:debug, /kon:ask, /kon:review, /kon:review-pr, /kon:hunt, /kon:gc, /kon:research, /kon:describe-issue, /kon:begin, /kon:finish, /kon:summarize, /kon:retro, /kon:address-comments, /kon:todo, /kon:understand-codebase. Orchestrates specialized agents: Azusa (explorer), Jun (researcher), Mugi (planner), Yui (implementer), Mio (reviewer), Sawako (cleaner), Nodoka (summarizer).
This skill should be used by all kon agents at startup, before beginning work, to load relevant memory from public and repo indexes with relevance-based ordering and a 10-entry cap. Consumers: Azusa, Mugi, Mio, Jun, and any future memory-reading agent.
Convention for per-repo skill directories at ~/.kon/projects/<repo-name>/skills/<name>/SKILL.md. Each named subdirectory is one skill. Agents load all SKILL.md files as the first step before memory entries.
When requirements, code behavior, root cause, or review scope is unclear — ask the user before proceeding. Never invent facts, assumptions, or fixes. Applies to every kon stage and every agent.
Route plain-text user messages while a /kon:begin session is open. Reuse the same session JSON — never init a second session for sub-turns.