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/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.
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