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/example-workflows.md
View on GitHub# T0 Example Orchestration Workflows
## Example 1: Successful PR Completion
```
π₯ Receipt: PR-3 completion report received
β
π¬ Read QUALITY line: [approve|risk:0.12] β Standard review
β
π Check: `open_items_manager.py digest`
β 7 open items for PR-3 (3 blockers, 3 warns, 1 info)
β Evidence attached by receipt processor
β
π Read report: tests pass, E2E passes, stress test 93%, memory stable
β
β
Close: OI-PR3-001 --reason "405 tests pass per report"
β
Close: OI-PR3-002 --reason "E2E suite passes"
β
Close: OI-PR3-003 --reason "3-concurrent 100% per stress test section"
β
Close: OI-PR3-004 --reason "5-concurrent 93.3% (>=60% threshold met)"
β
Close: OI-PR3-005 --reason "memory stable at 140MB, no regression"
β
Close: OI-PR3-006 --reason "zero zombies confirmed in cleanup section"
β
Close: OI-PR3-007 --reason "dashboard data validated in report"
β
π― All blockers/warns closed β `pr_queue_manager.py complete PR-3`
β
π Result: PR-4 dependencies now met, ready to dispatch
```
## Example 2: Partial Completion with Follow-Up
```
π₯ Receipt: PR-5 completion report received
β
π¬ Read QUALITY line: [hold|risk:0.55] β Critical review
β
π Check: `open_items_manager.py digest`
β 5 open items for PR-5 (2 blockers, 2 warns, 1 info)
β 2 new OIs auto-created by quality advisory
β
π Read report: tests pass but dead_code(3) flagged
β
β
Close: OI-PR5-001 --reason "unit tests 95% coverage per report"
β
Close: OI-PR5-002 --reason "API contract validated"
β Open: OI-PR5-003 (blocker) β dead code not cleaned up
βΈοΈ Defer: OI-PR5-004 --reason "cosmetic, not blocking"
β
β οΈ Blocker OI-PR5-003 still open β Dispatch follow-up
[[TARGET:A]]
Manager Block
Role: backend-developer
Terminal: T1
PR-ID: PR-5
Priority: P1
Cognition: normal
Dispatch-ID: 20260210-143000-pr5-dead-code
Parent-Dispatch: none
Reason: Remove dead code flagged by quality advisory (OI-PR5-003)
Context: [[@quality-advisory-report]]
Instruction:
- Remove dead code identified in quality advisory
- Run vulture to verify no more dead code
- Success: OI-PR5-003 blocker resolved
[[DONE]]
```
## Example 3: WAIT Decision
```
=== ORCHESTRATION DECISION ===
Status: WAIT
Reason: T2 currently working on storage optimization (12m elapsed)
Terminal States: T1=idle T2=working(12m) T3=idle
Queue: pending=1 active=1 conflicts=0
Open Items: PR-4 has 2 open blockers
Next Action: Monitor T2, review when receipt arrives
================================
```
## Example 4: ESCALATE Decision
```
=== ORCHESTRATION DECISION ===
Status: ESCALATE
Reason: T3 blocked for >30min on MCP connection failure, manual intervention needed
Terminal States: T1=idle T2=idle T3=blocked(35m)
Queue: pending=5 active=0 conflicts=2
Recommendation: Check T3 MCP server connectivity, restart if needed
================================
```
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: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |