Onex Execute Plan

---
name: "onex-execute-plan"
description: >-
  Autonomous implementation pipeline. Reads a plan file, reviews it adversarially,
disable-model-invocation: true
---

# onex-execute-plan

Autonomous implementation pipeline. Reads a plan file, reviews it adversarially,
creates Linear tickets, then runs the full ticket pipeline (implement → PR → CI → merge)
for each ticket via the Omnimarket bridge.

**Announce at start:** "I'm using the onex-execute-plan skill."

## Usage

```
/execute-plan docs/plans/my-plan.md
```

Or **single ticket mode** — skip Steps 1–2 and drive the Omnimarket pipeline for one Linear issue key you already have:

```
/execute-plan OMN-47
```

(Pass whatever identifier Linear shows for your workspace, not a generic placeholder.)

## Pipeline

### Step 1: Plan Review

In **single ticket mode**, skip Steps 1–2 and continue at Step 3 with that identifier.

Otherwise follow `skills/plan-review.md` on the plan file:

- If verdict is **FAIL** (any CRITICAL or MAJOR findings): stop. Report the findings. Do not create any tickets.
- If verdict is **PASS**: continue to Step 2.

### Step 2: Create Linear Tickets

In **single ticket mode**, skip this step entirely.

Otherwise follow `skills/plan-to-tickets.md` on the plan file:

- Creates one Linear epic + one ticket per `## Task N:` section.
- Records the mapping: Task N → ticket ID.
- If Linear MCP is unavailable: stop and report "Linear MCP not configured. See QUICKSTART.md."

### Step 3: Run Ticket Pipeline for Each Ticket

For each ticket in task order (respecting `blockedBy` dependencies), **or once** when you invoked single-ticket mode:

**Bridge contract**

- MCP tool **`run_ticket_pipeline`** (FastMCP server **`omnicursor-omnimarket`** in this repo; Cursor UI may label the project MCP differently) expects the Linear identifier as **`ticket_id`** — same name as the JSON/MCP argument, e.g. `run_ticket_pipeline(ticket_id="OMN-47")`.
- The bridge subprocess runs `python -m omnimarket.nodes.node_ticket_pipeline` with optional `--skip-test-iterate` / `--dry-run` **first**, then the issue key **as the final positional argument**. Omnimarket’s CLI does **not** take `--ticket-id`; if you see `unrecognized arguments: --ticket-id`, reinstall OmniCursor in the venv the MCP server uses (`pip install -e ".[dev]"` from this repo) so the bridge matches omnimarket.
- Use the **real** prefix for your Linear team (examples below use `OMN-` only as illustration).

**3a. Via Omnimarket bridge (preferred)**

If the Omnimarket MCP server is available, call:

```
run_ticket_pipeline(ticket_id="OMN-47")
```

This drives the full pipeline unattended:
- IMPLEMENT → LOCAL_REVIEW → CREATE_PR → TEST_ITERATE → CI_WATCH → PR_REVIEW → AUTO_MERGE → DONE

Parse the MCP tool’s JSON envelope; when `ok` is true and `state` is present, read `final_phase` (and `pr_number` when present):

On return, check `final_phase`:
- `done` → record pr_number, continue to next ticket
- `blocked` → note failure reason, continue to next ticket
- `failed` → note failure reason, continue to next ticket

**3b. Fallback — inline implementation (if bridge unavailable)**

If `run_ticket_pipeline` is not available:

1. Read the task description from the plan
2. Write failing tests first (TDD where applicable)
3. Implement minimal code to pass
4. Run tests — on failure, follow `skills/systematic-debugging.md` (max 2 attempts)
5. On success: push branch, open PR via `gh pr create`, mark ticket done in Linear
6. On failure after 2 attempts: mark ticket blocked, continue

**3c. On dependency not met**

If a ticket's `blockedBy` dependency is blocked or failed:
- Mark ticket **skipped**
- Continue to next ticket

### Step 4: Report Summary

After all tickets are processed:

```
execute-plan summary: docs/plans/my-plan.md
  Done:    N tickets (OMN-101 → PR #12, OMN-102 → PR #13)
  Blocked: N tickets (OMN-103 — pipeline failed: test_auth.py timeout)
  Skipped: N tickets (OMN-104 — blocked by OMN-103)

Next steps:
  - Review blocked tickets and fix root cause manually
  - Re-run /execute-plan after resolving blockers
```

## Failure Modes

| Condition | Action |
|-----------|--------|
| plan-review returns FAIL | Stop before creating any tickets (skipped in single ticket mode) |
| Linear MCP unavailable | Stop before creating any tickets (skipped in single ticket mode) |
| Ticket creation fails | Report, continue with remaining tasks |
| Bridge returns blocked/failed | Record reason, continue to next ticket |
| Inline fallback fails after 2 attempts | Mark blocked, continue to next ticket |
| Dependency ticket is blocked | Mark dependent as skipped, continue |