quick

OpenSpec → OMC Quick Bridge

Bridge skill that hands off simple OpenSpec planning artifacts to OMC autopilot. Eliminates the manual copy-paste of tasks.md and context re-explanation.

When to use

• OpenSpec change folder has tasks.md with 3 or fewer tasks
• Single domain change (narrow file modification scope)
• Linear work that does not require parallel agents

Execution flow

Step 1: Identify target change

Scan openspec/changes/ directory for active changes.

ls -d openspec/changes/*/tasks.md 2>/dev/null | grep -v archive

• If exactly 1 change exists, select it automatically
• If multiple exist, ask the user which change to implement
• If none exist, guide user to run /opsx:propose or /opsx:ff first and stop

Step 2: Validate artifacts

Check minimum required files in the selected change folder:

CHANGE_DIR="openspec/changes/<change-name>"
# Required: tasks.md
test -f "$CHANGE_DIR/tasks.md" || echo "MISSING: tasks.md"
# Recommended: proposal.md (for context)
test -f "$CHANGE_DIR/proposal.md" || echo "WARNING: proposal.md missing - context may be insufficient"

If tasks.md is missing, stop. If proposal.md is missing, warn and proceed.

Step 3: Gather context

Read files in order to assemble implementation context:

1. proposal.md — Motivation and scope (Why/What)
2. design.md — Technical approach (How) — read if present, skip if absent
3. tasks.md — Implementation checklist (read in full)

Extract the following:

• Goal summary: 1-2 sentences from the Intent/Why section of proposal.md
• Technical constraints: Key decisions from design.md (engine choice, patterns, etc.)
• Pending tasks: Filter only - [ ] items from tasks.md

Step 4: Delegate to OMC autopilot

Compose gathered context into a single autopilot instruction. Key principles:

• Reference tasks.md verbatim (do not summarize)
• Explicitly pass design.md constraints
• Maintain checklist format so OMC can track progress

Prompt structure to compose: