command-router
/command-router
Codex pseudo-command router for Maigo. Use when the user sends or discusses any `/maigo:*` or `maigo:*` command, including go, team, quick, review, board, remember, memory, retro, crystallize, describe-pr, address-comments, triage-issue, take-issue, doctor, or repo-audit; also use when the user asks why Maigo commands do not behave like native Codex slash commands.
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 1
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Codex pseudo-command router for Maigo. Use when the user sends or discusses any `/maigo:*` or `maigo:*` command, including go, team, quick, review, board, remember, memory, retro, crystallize, describe-pr, address-comments, triage-issue, take-issue, doctor, or repo-audit; also use when the user asks why Maigo commands do not behave like native Codex slash commands.
Original author description
Codex pseudo-command router for Maigo. Use when the user sends or discusses any `/maigo:*` or `maigo:*` command, including go, team, quick, review, board, remember, memory, retro, crystallize, describe-pr, address-comments, triage-issue, take-issue, doctor, or repo-audit; also use when the user asks why Maigo commands do not behave like native Codex slash commands.
How it works
- Boundary
- Dispatch
- Codex compatibility
- Poor command UX
SKILL.md preview
---
name: command-router
description: Codex pseudo-command router for Maigo. Use when the user sends or discusses any `/maigo:*` or `maigo:*` command, including go, team, quick, review, board, remember, memory, retro, crystallize, describe-pr, address-comments, triage-issue, take-issue, doctor, or repo-audit; also use when the user asks why Maigo commands do not behave like native Codex slash commands.
---
<!-- mkdocs-include-start -->
# Command Router
**Owner**: orchestrator
**Consumers**: Codex sessions only. Claude Code uses `commands/` as native slash commands.
## Boundary
Codex plugin manifests do not expose Claude Code-style `commands/` as native slash commands. Treat this skill as a compatibility shim:
- Improve model-side dispatch for Maigo-shaped input.
- Keep `commands/*.md` as the single source of truth; do not copy command behavior here.
- Do not promise slash-command autocomplete, command palette entries, or platform-level interception.
- Prefer `maigo:<name> ...` in Codex. A leading `/maigo:*` may be intercepted before it reaches the model.
## Dispatch
Accept all of these forms:
- `maigo:<name> [arguments...]`
- `/maigo:<name> [arguments...]` when it reaches the model
- Natural language clearly asking to run a Maigo command
For every recognized command:
1. Read `../orchestrator-voice/SKILL.md` completely.
2. Read `../narration/SKILL.md` completely.
3. Read `../../commands/<name>.md` completely.
4. For commands that execute roles, read [`model-dispatch`](https://github.com/Lee-W/maigo/blob/main/skills/model-dispatch/SKILL.md) before starting. Consume `--model-profile <path>` if supplied and resolve it against the entry project cwd; forward the absolute path to any inner route.
5. Execute the command workflow with the remaining text as its argument string. Read every additional skill or agent file required by that command before applying it.
Resolve Maigo-local references from the plugin root:
- `skills/<skill>/SKILL.md` -> `../<skill>/SKILL.md` from this skill directory.
- `agents/<agent>.md` -> `../../agents/<agent>.md`.
- `commands/<command>.md` -> `../../commands/<command>.md`.
- `${CLAUDE_PLUGIN_ROOT}` -> the plugin root two directories above this skill.
Known commands:
| Input | Command source |
|-------|----------------|
| `maigo:address-comments` | `commands/address-comments.md` |
| `maigo:board` | `commands/board.md` |
| `maigo:crystallize` | `commands/crystallize.md` |
| `maigo:describe-pr` | `commands/describe-pr.md` |
| `maigo:doctor` | `commands/doctor.md` |
| `maigo:go` | `commands/go.md` |
| `maigo:memory` | `commands/memory.md` |
| `maigo:quick` | `commands/quick.md` |
| `maigo:remember` | `commands/remember.md` |
| `maigo:repo-audit` | `commands/repo-audit.md` |
| `maigo:retro` | `commands/retro.md` |
| `maigo:review` | `commands/review.md` |
| `maigo:take-issue` | `commands/take-issue.md` |
| `maigo:team` | `commands/team.md` |
| `maigo:triage-issue` | `commands/triage-issue.md` |
If `../../commands/<name>.md` does not exist, state that the command is not implemented and stop. Do not invent behavior.
## Codex compatibility
Translate Claude Code concepts without changing the workflow's intent:
- Ignore `allowed-tools` frontmatter as a permission declaration; use the tools actually exposed by the current Codex session.
- Map `AskUserQuestion` to structured user input when available. Otherwise ask one concise plain-text question and wait.
- Map explicit agent or `Task` delegation using model-dispatch's resolved capabilities. Check the current tool schema for per-call model selection and context inheritance; do not infer support from the Codex name. If subagents are unavailable, execute the named roles sequentially in the main agent and disclose the fallback.
- Use Codex planning tools for command-level plans when available, while preserving `.maigo/*.md` artifacts required by the command.
- Use patch-based file editing and the current shell/tooling policies rather than Claude-specific Read, Write, Edit, or Bash tool names.
- Claude Code lifecycle hooks are not installed by the Codex manifest. Run the command's required review and verification steps explicitly; never claim that SubagentStop or Stop hooks enforced completion. For `quick`, run `<plugin-root>/scripts/verify_task.py --cwd <project-cwd>` and follow its status contract in `commands/quick.md`; hook exit 0 is not a test result.
- If a command needs to write outside the active workspace, request the required approval instead of silently skipping the write.
## Poor command UX
When the user reports that a Maigo entry is not behaving like a native slash command:
- Acknowledge the limitation directly.
- Recommend `maigo:<name>` or a natural-language request instead of starting with `/maigo:*`.
- Explain that this router improves model-side dispatch only; native slash-command UX requires Codex platform support.
Files in this package (2)
- SKILL.md 5 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named command-router.
Database snapshot: 13.11.2026 · package version 5693798b9ed0 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90memory-propose-confirm
This skill should be used by the maigo orchestrator whenever a Soyo or Anon output contains a ## Memory propose section. Handles the confirm flow, fence-tracking rules for detecting the section, no-answer handling, and parallel-mode timing adjustments. Applies to /maigo:go,… - 100failure-handling
This skill should be used when handling failures in go-class command flows — Soyo blocking with NEEDS_CHANGES / BLOCKED, Taki test failures, subagent infrastructure overload / unavailability (e.g. 529), mid-task usage/session-limit interruption of a running subagent, and… - 100writing-commands
Use when creating new commands, editing existing commands, or reviewing command quality. Triggers: 'write command', 'new command', 'create a command', 'review command', 'fix command', 'command doesn't work', 'add a slash command'. NOT for: skill creation (use writing-skills). - 95create-slash-commands
Expert guidance for creating Claude Code slash commands. Use when working with slash commands, creating custom commands, understanding command structure, or learning YAML configuration. - 95create-slash-commands
Expert guidance for creating Claude Code slash commands. Use when working with slash commands, creating custom commands, understanding command structure, or learning YAML configuration. - 95meta-command-development
Use when the user asks to ”create a slash command”, ”add a command”, or ”write a custom command” for Claude Code.