القائمة
This skill should be used by the maigo orchestrator whenever a Soyo or Anon output contains a
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
This skill should be used when assembling git commits — deciding what to stage, how to scope a bash/agent command's working directory, whether to amend an unreleased commit or stack a new one, and how to size a diff against the correct baseline. Applies to the commit-assembly step of /maigo:go, /maigo:quick, /maigo:team, and /maigo:address-comments, and to the orchestrator generally.
This skill should be used when the maigo orchestrator, running in the Claude Code harness, decides whether to delegate work to a subagent instead of doing it on the main thread, needs to keep a long task's acceptance criteria from drifting after context compaction, or needs to keep verification independent from whoever produced the work. Scope note: 只在 Claude Code harness 下才適用——這裡的 orchestrator context 會被計費、可能被壓縮、且可 spawn subagent 分攤負載；沒有 subagent 能力的 harness 不適用此 skill。
This skill should be used by all maigo agents at startup, before beginning work, to load relevant cross-project memory entries with relevance-based ordering and a 10-entry cap. Consumers: Raana, Tomori, Soyo, the orchestrator itself, and any future agent that reads ~/.config/maigo/memory/.
This skill should be used by the maigo orchestrator on every /maigo command, alongside narration, to govern the conversational conduct of the main dialogue — AskUserQuestion widget discipline and Taiwanese Mandarin word-choice norms.
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 9-item checklist, demanding evidence, and giving specific改法 instead of vague critique.
This skill should be used when orchestrating the full MyGO!!!!! teammate flow — Raana explores, Tomori plans, Anon implements, Soyo reviews, Taki validates. Applies to /maigo:go and /maigo:team (both sequential and parallel variants).
| name | memory-propose-confirm |
| description | This skill should be used by the maigo orchestrator whenever a Soyo or Anon output contains a |
Owner: orchestrator
Consumers: /maigo:go、/maigo:quick、/maigo:team、/maigo:review
當 🟡 Soyo 或 🎀 Anon 的輸出末尾含 ## Memory propose 段時，orchestrator 在該 agent 完成後、繼續下一步前，立刻執行 confirm flow。
name / slug / description / body / type / rationale）是否齊全。
缺任一欄位 → 不 confirm，印一行提示「偵測到 propose 段但格式不完整，已跳過」，繼續正常流程。~/.config/maigo/memory/MEMORY.md（cross-project）~/.claude/projects/<current-project>/memory/MEMORY.md（per-project，若存在）存 / 修改 / 跳過。/maigo:remember 步驟 5+6
（以 propose 的欄位為預填值；「修改」時步驟 5 讓使用者改各欄位）。Confirm flow 完成後繼續主線流程——不改變命令的步驟結構。
confirm flow 的結果有三種，不是兩種。orchestrator 不可把後兩者混為一談：
| 結果 | 觸發 | 處置 |
|---|---|---|
| 存 | 使用者選「存」/「修改」 | 寫檔（step 5） |
| 跳過 | 使用者明確選「跳過」 | 不寫檔，丟棄 propose，繼續 |
| 未決 | 使用者沒選任何項（關掉問題 / dismiss / AskUserQuestion 回 "did not answer"） | 不寫檔，但不丟棄 propose |
「沒回答」≠「跳過」。 dismiss 一個問題不是 decline——它只代表「現在不決定」。把 no-answer 當成跳過會把使用者還想留著的 memory 默默吃掉。
未決時 orchestrator 必須：
## Memory propose（fenced，可複製），讓使用者之後說一聲就能存使用者之後任何時點說「存那個 memory」/「剛剛那條記起來」→ 直接 reuse step 5 寫檔，不必重跑整個 confirm flow。
偵測 ## Memory propose 標頭時，只掃描 code fence 外的行；code block 內（triple-backtick fence 之間）的同名標頭不觸發 confirm flow。
追蹤法：從輸出文字開頭往下追蹤 triple-backtick 計數（奇數 → in-fence），遇到 ^## Memory propose 且 in-fence 為 true 時跳過。
在 /maigo:team 的並行場景（🟡 Soyo 和 🟣 Taki 並行）下：若 Soyo 輸出含 ## Memory propose，等兩邊都回來後再跑 confirm flow，不要插在 Taki 還在執行中間。