SWE Orchestrator

You give it a ticket ID. It gives you a reviewed PR.

Usage

/swe PROJ-123
/swe https://github.com/org/repo/issues/42

---

Phase 1: Parse Arguments

Parse the first positional argument:

• URL → extract ticket ID (Jira key from path, GitHub issue number, Linear ID)
• Bare ID (PROJ-123, #42) → use directly
• No argument → show usage and exit

---

Phase 2: Initialize State

Step 0 — Check plugin dependencies:

Verify /deep_review is available (required for Stage 3). If unavailable, stop and show: /plugin install deep-review@ghcp-dev-plugin.

Step 1 — Detect target branch:

gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'

Fallback: git symbolic-ref refs/remotes/origin/HEAD, then default to main.

Step 2 — Ensure feature branch:

current=$(git branch --show-current)

If on the target branch, ask user to confirm creating feat/{ticket-id}. If on a different branch, use it as the feature branch.

Step 3 — Create directories:

mkdir -p .claude/swe-state/{ticket-id}
mkdir -p .claude/specs

Step 4 — Write full state file to .claude/swe-state/{ticket-id}.json:

Read the template from state-template.json in this skill's directory (find it via **/swe/state-template.json). Replace all {ticket-id} placeholders with the actual ticket ID, {detected} with the target branch, and {current-or-created} with the feature branch. Write the populated JSON to the state file path.

This is the single source of truth for the pipeline. All file paths are pre-populated — downstream skills read paths from state, never construct them. Fields with null, false, 0, or [] are populated by the owning stage.

---

Phase 3: Stage Dispatch Loop

Pipeline runs 4 stages in order: intake → spec → implement_and_review → pr

For each stage in order:

1. Display ## Stage {N}: {Name}
2. Set current_stage and status: "in_progress" in state
3. Invoke the stage skill:

Stage	Skill
intake	/ticket_intake {ticket-id}
spec	/spec_writer {ticket-id}
implement_and_review	/implement_and_review {ticket-id}
pr	/pr_create {ticket-id}

4. Success → proceed
5. Failure → set status: "failed", report which stage failed
6. User abort → set status: "aborted", exit

Each skill handles its own user interaction and state writes.

---

Phase 4: Completion

## Pipeline Complete

**Ticket:** {ticket-id}
**PR:** {pr-url}
**State:** .claude/swe-state/{ticket-id}.json

Set status: "completed".

Tip: Use /swe_status {ticket-id} at any time to check pipeline progress.