Vinix24/vnx-orchestration / skills/t0-orchestrator
t0-orchestrator
VerifiedMaster 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.9 KB |
| references/_MAPPING.md | markdown | 241 B |
| references/dispatch-patterns.md | markdown | 2.7 KB |
| references/example-workflows.md | markdown | 2.9 KB |
| references/feature-plan.md | markdown | 1.3 KB |
| references/provider-matrix.md | markdown | 1.7 KB |
| scripts/dispatch_guard.shexecutable | script | 15.1 KB |
| scripts/intelligence.shexecutable | script | 10.1 KB |
| template.md | markdown | 4.8 KB |
references/feature-plan.md
View on GitHub# Feature Plan Reference — Example Shape
> This is a GENERIC EXAMPLE of the feature-plan shape the t0-orchestrator skill
> expects. During deployment, map this reference to your project's real
> `FEATURE_PLAN.md` (see `_MAPPING.md`). It is intentionally content-free:
> project plans are project-specific and never ship with the engine.
## Feature: Example Feature Name
**Status**: In progress
**Priority**: P1
**Source of queue truth**: `PR_QUEUE.md` and `.vnx-data/state/pr_queue_state.json`
## PR-1: First Small Slice
**Track**: A
**Priority**: P1
**Skill**: backend-developer
**Complexity**: Medium
**Estimated Time**: 1 day
Dependencies: []
### Description
One- or two-sentence statement of what this PR delivers.
### Scope
- Bullet the concrete changes (keep the PR 300-450 lines, 300 or less on a security path, independently deployable).
- Name the files or modules touched.
### Success Criteria
- Observable, checkable outcomes (tests pass, contract holds).
### Quality Gate
`gate_pr1_example`:
- [ ] Tests pass
- [ ] Review gate cleared
---
## PR-2: Next Slice
**Track**: B
**Priority**: P2
**Skill**: quality-engineer
**Complexity**: Low
**Estimated Time**: 0.5 day
Dependencies: [PR-1]
### Description
Each subsequent PR follows the same shape: track, skill, complexity,
dependencies, scope, success criteria, and a named quality gate.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |