菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dentiny/kon --skill orchestrator-voice命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Map a codebase for learning — glossary, architecture, flashcards, and quiz. Produces interactive HTML (clickable terms/diagrams + side panel) and an optional PDF.
Multi-agent software engineering workflow. Use when the user mentions /kon: commands in plain text — 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. Prefer the explicit /kon:<command> slash commands when available.
This skill should be used when performing code review on a diff (whether implemented by another agent or an external PR), enforcing a strict reviewer stance, applying a mandatory 7-item golden checklist, demanding evidence, and giving specific改法 instead of vague critique.
基于 SOC 职业分类
正在显示 SKILL.md
| 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/narration