メニュー
Orchestrator/agent/Codex delegation matrix. Reference this when scoping a task to determine who owns what. Covers three Codex modes: reviewer-only (default), implementer+reviewer, and no Codex.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/grandamenium/cortextos --skill delegation-matrixコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
You need to write or update memory. This happens at session start, heartbeat, session end, or when you learn something worth keeping. Memory is how you maintain continuity across restarts and context compactions — without it, every session starts blind.
You need to write or update memory. This happens at session start, heartbeat, session end, or when you learn something worth keeping. Memory is how you maintain continuity across restarts and context compactions — without it, every session starts blind.
Migrate ANY cortextOS agent from the claude-code runtime to the live codex-app-server runtime. Use this whenever a user wants to convert, port, move, or switch a Claude-cortextOS agent to Codex / gpt-5-codex / gpt-5.5, "make agent X run on codex", "turn this claude agent into a codex agent", or asks how a Claude agent's CLAUDE.md / .claude/skills / .mcp.json / hooks map onto the codex-app-server adapter. Takes a source agent name and produces a SEPARATE codex-shaped agent (non-destructive, dry-run by default). Trigger even if they only say "migrate <agent> to codex" without naming the artifacts. Do NOT use for creating a brand-new codex agent from scratch (use `cortextos add-agent`) or for hermes/orchestrator/analyst runtimes.
SOC 職業分類に基づく
SKILL.md を表示中
| name | delegation-matrix |
| effort | low |
| description | Orchestrator/agent/Codex delegation matrix. Reference this when scoping a task to determine who owns what. Covers three Codex modes: reviewer-only (default), implementer+reviewer, and no Codex. |
| triggers | ["who owns","delegation","codex or agent","should codex","task scoping","who does this","delegation matrix","codex mode"] |
Reference when scoping any task. Dividing line: execution-heavy → Codex (if configured as implementer). Judgment-heavy → Agent always.
Codex is a configurable option. Pick the mode that matches your setup:
| Mode | Codex role | When to use |
|---|---|---|
| Mode 1 (default) | Reviewer only | Out of the box — Codex reviews Agent output before PR |
| Mode 2 | Implementer + reviewer | Codex is set up and trusted for implementation |
| Mode 3 | Not used | No Codex in your stack — Agent handles everything |
| Work type | Orchestrator | Agent | Codex (Modes 1+2) |
|---|---|---|---|
| Requirement intake from user | owns | — | — |
| Task decomposition + dispatch | owns | consults | — |
| Briefings and status to user | owns | input | — |
| Architecture decisions | — | owns | — |
| Spec writing + acceptance criteria | — | owns | — |
| Security and domain modeling | — | owns | — |
| Ambiguous / judgment calls | routes | owns | — |
| PR decisions (file, scope, merge) | — | owns | — |
| First-pass implementation (clear spec) | — | owns (Modes 1+3) / delegates (Mode 2) | owns (Mode 2) |
| Mechanical refactors and migrations | — | owns (Modes 1+3) / delegates (Mode 2) | owns (Mode 2) |
| Repetitive multi-file edits | — | owns (Modes 1+3) / delegates (Mode 2) | owns (Mode 2) |
| Test drafting and fixture setup | — | owns (Modes 1+3) / delegates (Mode 2) | owns (Mode 2) |
| Code review before PR | — | owns (Mode 3) | owns (Modes 1+2) |
For tasks >~20 lines or touching multiple files:
For one-liners and config changes: Agent writes directly in all modes.
Even in Mode 2, some work stays with the Agent:
Deployment note: replace "Orchestrator" / "Agent" with your actual agent names.
