Skip to content

Vinix24/vnx-orchestration / skills/t0-orchestrator

t0-orchestrator

Verified

Master orchestration for the VNX multi-terminal system. Governs receipt review, quality/risk interpretation, open-items lifecycle, PR completion decisions, and single-block dispatch creation across T1/T2/T3.

FileKindSize
SKILL.mdskill md7.9 KB
references/_MAPPING.mdmarkdown241 B
references/dispatch-patterns.mdmarkdown2.7 KB
references/example-workflows.mdmarkdown2.9 KB
references/feature-plan.mdmarkdown1.3 KB
references/provider-matrix.mdmarkdown1.7 KB
scripts/dispatch_guard.shexecutablescript15.1 KB
scripts/intelligence.shexecutablescript10.1 KB
template.mdmarkdown4.8 KB

references/provider-matrix.md

View on GitHub
# Provider Capability Matrix (Runtime-Realistic)

## Policy First

- T0 runtime policy is currently **Claude Opus only**.
- Provider comparison below is for worker-terminal dispatch planning (mainly T1).

## How to Check Active Provider

```bash
jq -r '.T1.provider' .vnx-data/state/panes.json
```

## Capability Matrix

| Capability | claude_code | codex_cli | gemini_cli |
|---|---|---|---|
| Native skill invocation command | Yes | No guaranteed native slash-skill command | No guaranteed native slash-skill command |
| Fallback via inline role/context preamble | Supported (optional) | Supported (primary pattern) | Supported (primary pattern) |
| Context reset command | `/clear` | `/new` | `/clear` |
| Planning mode support | Yes | Limited (`/plan`, verify per version) | No |
| Thinking mode support | Yes | No | No |
| MCP support in worker runtime | Yes (provider/config dependent) | No | No |

## Dispatch Guidance by Provider

### Claude Code

- Use standard skill-first dispatch with `Workflow: [[@.claude/skills/<skill>/SKILL.md]]`.
- `Mode: planning` and `Mode: thinking` are available when appropriate.

### Codex CLI

- Do not assume native slash-skill invocation.
- Use explicit `Role`, `Workflow`, and `Context` fields in Manager Block.
- Avoid `Mode: thinking`; planning support must be validated in-session.
- Omit Claude-specific `Requires-Model` values unless confirmed compatible.

### Gemini CLI

- Do not assume native slash-skill invocation.
- Use explicit `Role`, `Workflow`, and `Context` fields in Manager Block.
- Avoid `Mode: thinking` and `Mode: planning`.
- Omit `Requires-Model` fields (single-model runtime behavior).

## MCP Routing Rule

If a task requires MCP-dependent capabilities, set `Requires-MCP: true` and route to T3.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall