القائمة
When to spawn 📚 Jun for external lookup — WebSearch/docs/APIs — vs 🎸 Azusa for codebase exploration. Used by /kon:research, /kon:team, and /kon:design.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Multi-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.
| name | external-research |
| description | When to spawn 📚 Jun for external lookup — WebSearch/docs/APIs — vs 🎸 Azusa for codebase exploration. Used by /kon:research, /kon:team, and /kon:design. |
Owner: orchestrator
Consumers: /kon:research, /kon:team,
/kon:team, /kon:design
Core principles (always): follow skills/core-principles — cite sources; say "docs silent on X" instead of guessing; concise structured report only.
| Question type | Agent | Artifact |
|---|---|---|
| Where is X in our repo? How does our code work? | 🎸 Azusa | exploration notes (no file, or plan context) |
| What does library Y's API say? What's the migration path? | 📚 Jun | .kon/research.md |
| Compare our hook format to Cursor docs | Both (parallel) | research + exploration |
Rule: repo-first for "our code"; web-first for "their docs".
/kon:team / /kon:designSpawn Jun in parallel with Azusa when the task mentions any of:
Skip Jun when:
.kon/research.md already exists for this topic and is still valid (orchestrator reads + confirms reuse)/kon:research standaloneRead commands/research.md. Jun only — no Azusa/Mugi/Yui.
Use when the user asks a lookup question without intending to implement yet.
When both ran: Mugi reads .kon/research.md (if present) alongside Azusa's exploration
before writing the plan file (.kon/plan-<session-id>.md). Add a ## External context section in the plan summarizing
Jun's recommendations — do not paste raw URLs; link to .kon/research.md.
agents/Jun.md + this skill.kon/research.mdteammate_role: Jun.kon/research.md