| name | openspec-ultra-bridge-v2 |
| description | Bridge OpenSpec change artifacts into Codex Ultra vNext execution contracts. Use when a repo stores long-lived specs in `openspec/changes` or `openspec/specs`, but execution should still flow through Ultra manifests, work packages, review, QA, ledger tracking, and final delivery rather than replacing Ultra with a separate control plane. |
OpenSpec Ultra Bridge V2
OpenSpec is the specification layer. Ultra remains the control plane.
This skill is a compatibility bridge for vNext users. The default public entry
point is now $ultra-orchestrator, which invokes this bridge as needed.
What This Skill Does
Translate:
proposal.mddesign.mdtasks.md- optional
ultra-bridge.md
into:
TaskManifestWorkPackage set- bridge notes for review and QA
Bridge Rules
- Do not let OpenSpec replace Ultra's execution ledger or review gates.
- Prefer one bounded
change as the default execution unit.
- Use OpenSpec for durable spec memory and archive history.
- Use Ultra for dispatch, retries, review, QA, and delivery.
- In
STRICT_OPENSPEC, do not continue without change scaffold, slice status,
JSON-ready planning artifacts, and ledger handoff.
How To Use
- Point the bridge at an OpenSpec change directory.
- Read the proposal, design, and task assets.
- If
ultra-bridge.md exists, treat it as the preferred mapping hint.
- Normalize the change into a reviewable
TaskManifest and WorkPackage
set.
- Hand off those outputs to
ultra-planning or ultra-execution-control.
Required Change Scaffold
For newly opened strict changes, initialize at minimum:
proposal.mddesign.mdtasks.mdultra-bridge.md
Default status:
slice_0_spec_ready when the change is ready for implementationslice_0_not_opened only for unopened planned changes
Slice Contract
Keep change and slice separate:
- OpenSpec
change is the durable spec and progress node
- Ultra
slice is the implementation and verification unit
Every bridge output should name:
change_id- current slice status
- next slice
- owned paths
- review targets
- QA targets
- blockers for status sync or archive
Script
Use scripts/bridge_change.py to extract and materialize bridge artifacts from
a real OpenSpec change directory.
Read Next
