# Ultra Vnext Core > Compatibility and preview alias for the main Ultra Orchestrator strict protocol. Use this single skill to start vNext-style orchestrated runs when users still invoke ultra-vnext-core; it should follow the same run-mode decision, strict OpenSpec preference, ledger, JSON artifact, contract validation, slice DAG, review, QA, delivery, and retro behavior as ultra-orchestrator. - **Type:** Skill - **Install:** `agentstack add skill-keithhegit-ultra-orchestration-ultra-vnext-core` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [keithhegit](https://agentstack.voostack.com/s/keithhegit) - **Installs:** 0 - **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills) - **Latest version:** 0.1.0 - **License:** Apache-2.0 - **Upstream author:** [keithhegit](https://github.com/keithhegit) - **Source:** https://github.com/keithhegit/ultra-orchestration/tree/main/skills-vnext/ultra-vnext-core - **Website:** https://keithhegit.github.io/ultra-orchestration/docs.html ## Install ```sh agentstack add skill-keithhegit-ultra-orchestration-ultra-vnext-core ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Ultra VNext Core Use this skill as a compatibility alias for the mainline `$ultra-orchestrator` protocol. The user should not need to list every subskill. Prefer the same behavior as the new main entry point: ```text $ultra-orchestrator ``` `$ultra-vnext-core ` remains valid for existing users and pilot runs. ## Run Mode Decision Classify the run before planning or execution: - `LIGHT` review-only, QA-only, explanation-only, or user-explicit lightweight work - `STANDARD` user-explicit fast orchestration with bounded risk and no full control plane - `STRICT` development work where OpenSpec is unavailable but ledger and JSON contracts are still required - `STRICT_OPENSPEC` default for development work, bug fixes, multi-file implementation, pilots, full orchestration tests, OpenSpec work, slice DAG work, and control-plane validation Development tasks must prefer `STRICT_OPENSPEC`. If that mode is impossible, explain why and downgrade explicitly. Markdown-only artifacts are not enough for `STRICT` or `STRICT_OPENSPEC`. ## Router Duties When invoked: 1. classify the task and choose `run_mode` 2. create or require OpenSpec change scaffolding when `STRICT_OPENSPEC` applies 3. initialize the run ledger for `STRICT` and `STRICT_OPENSPEC` 4. route through the minimal required sibling skills 5. validate machine-checkable artifacts before delivery 6. produce delivery artifacts or a clear blocker Do not ask the user to manually name every subskill. ## Strict Control Plane For `STRICT` and `STRICT_OPENSPEC`, the run must use: - `scripts/new_run.py` to initialize a run directory - `ledger.json` as the execution state record - JSON `TaskManifest` - JSON `WorkPackage` - JSON or structured `AgentResult` - `scripts/validate_contracts.py` for core artifact validation - explicit review and QA gates - final `control_surface_used` If a required script or artifact cannot be used, stop with a blocker instead of silently downgrading to markdown-only orchestration. ## OpenSpec Bootstrap When `STRICT_OPENSPEC` applies and no existing change is available, create or request this scaffold: ```text openspec/changes//proposal.md openspec/changes//design.md openspec/changes//tasks.md openspec/changes//ultra-bridge.md ``` ## Slice-Driven Execution Keep `change` and `slice` separate: - OpenSpec `change` is the specification and progress ledger unit - Ultra `slice` is the implementation, verification, and commit unit Use this slice status vocabulary: - `slice_0_not_opened` - `slice_0_spec_ready` - `slice_1_completed` - `slice_2_in_progress` - `slice_3_qa_pending` - `slice_4_done` ## State Machine Default phases: `Intake -> Plan -> Dispatch -> Execute -> Review -> QA -> Deliver -> Retro` Required loopbacks: - `Review -> Execute` when the plan is valid but the work is wrong - `QA -> Execute` when behavior is wrong but architecture is still valid - `QA -> Plan` when the failure exposes a planning or requirement flaw ## Delivery Requirement Every delivery must include: - `final_deliverable` - `orchestration_log` - `vetter_report` - `control_surface_used` `control_surface_used` must state `run_mode`, OpenSpec use, bridge use, ledger use, contract validation use, slice DAG use, dynamic QA use, and skipped control surfaces with reasons. ## Read Next - Read [routing](references/routing.md) for strict routing examples. - Read [contracts](references/contracts.md) for machine-checkable artifacts. - Read [state-machine](references/state-machine.md) for phase and loopback rules. - Read [design-tenets](references/design-tenets.md) for governing principles. ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [keithhegit](https://github.com/keithhegit) - **Source:** [keithhegit/ultra-orchestration](https://github.com/keithhegit/ultra-orchestration) - **License:** Apache-2.0 - **Homepage:** https://keithhegit.github.io/ultra-orchestration/docs.html Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-keithhegit-ultra-orchestration-ultra-vnext-core - Seller: https://agentstack.voostack.com/s/keithhegit - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.