worca git:20260922.e9b561fA

Immutable. This exact content never changes and is served at /api/v1/blob/8a0414c8cb096767.

---
name: worca
description: Run the node-graph multi-agent orchestrator over a software task in the current project. Triggers on "/worca", "/worca <prompt>", "/worca --ui", and on requests to orchestrate, run the orchestration pipeline, or drive plan/refine/implement/review for a task.
---

# Orchestrate

Drive the current project through the selected pipeline template (default `wf_default`: Plan → Refine ↺ → Implement → Review ↺ → End). Orchestration is performed by a deterministic Node.js script; this skill just launches it. Artifacts (plans, reviews, pipeline audit logs) are written under `ai-artifacts/` in the project.

The orchestrator repo lives wherever it was installed. `<WORCA_REPO>` below is the absolute path of that repo (the directory containing `src/cli/worca-cc.mjs`). If you installed via `tools/install.mjs`, the installer rewrites `<WORCA_REPO>` in this file to the real path automatically; otherwise substitute it yourself (or set an `WORCA_REPO` environment variable and use `"$WORCA_REPO"`).

## /worca <prompt> — run the pipeline (default action)

When invoked as `/worca <prompt>`, run the CLI with the user's text as the prompt and the user's current project as the working directory:

```bash
node <WORCA_REPO>/src/cli/worca-cc.mjs --project "$PWD" --prompt "<args>"
```

- `--project "$PWD"` — operate inside the user's current project (the orchestrator does all file writes here).
- `--prompt "<args>"` — everything the user typed after `/worca`. Quote it.
- The CLI streams every agent execution (start/done, cycle, cost) and live agent logs to the terminal. When the clarify step needs a decision it shows each question's 2–4 options plus a free-text field; when a refine/review loop hits its cap it shows the open critical/major issues and asks whether to continue or approve another cycle. Answer interactively.
- On completion it prints the pipeline directory under `ai-artifacts/pipelines/`.

Useful flags (pass through when the user asks):
- `--file <path.md>` — use a markdown file as the prompt instead of `--prompt`.
- `--title "<name>"` — label the pipeline.
- `--workflow <id>` — run a saved pipeline template instead of the built-in default (`wf_default`).
- `--model <m>` / `--permission-mode <m>` — Claude model / permission mode (default `acceptEdits`).
- `--mock` — run the full pipeline offline with canned agents (no Claude spawn, no tokens); great for a dry run. Equivalent to setting `WORCA_MOCK=1`.
- `--yes` / `--non-interactive` — auto-answer (clarify picks the first option; gates choose "continue"). Use for unattended runs.
- `--at "<when>"` — schedule the run instead of starting it now (`02:00`, `tomorrow 02:00`, `+90m`, `2026-09-19 02:00`). Add `--wait` to hold the terminal and start it there; otherwise the Worca UI server starts it. `--every "weekdays 02:00"` / `--cron "0 2 * * 1-5"` repeat it. Manage with `worca schedule list | cancel <id>`. `--after <id>` starts it when that run ends (`--after-any` also on failure, `--source-from-previous` on its branch).

Example:

```bash
node <WORCA_REPO>/src/cli/worca-cc.mjs \
  --project "$PWD" --prompt "Add rate limiting to the public API"
```

## /worca --ui — launch the web UI

To start the web app (new-pipeline form, live pipeline graph, live log window, question + loop-gate panels, Stop button, run history):

```bash
node <WORCA_REPO>/src/cli/worca-cc.mjs --ui
```

This starts `ui/server.mjs` (Express + WebSocket, default port `4317`; set `PORT` to change). Open the printed URL in a browser. In the UI you pick the project folder to operate in, supply a prompt OR a markdown document (plus optional extra files), optionally toggle mock mode, and Start. The UI also has an "Install agents into this folder" button.

## Installing the agents + skill into another project

So a teammate can open Claude Code in their own repo and type `/worca <prompt>`, copy the agents and this skill into that project's `.claude/`:

```bash
node <WORCA_REPO>/tools/install.mjs "<targetDir>"
```

- Copies `agents/*.md` into `<targetDir>/.claude/agents/` and `skills/worca/` into `<targetDir>/.claude/skills/worca/`.
- Add `--force` to overwrite existing copies.
- Prints a next-step hint. After installing, open Claude Code in `<targetDir>` and run `/worca <prompt>`.
- You can also trigger this from the CLI (`--install <targetDir>`) or the UI ("Install agents into this folder").

## Notes
- The orchestrator auto-initializes a git repo in the target project (initial commit) if none exists, so the reviewer can diff the implementation.
- Preflight auto-detects `graphify` and `code-review-graph`; if both are present it always uses graphify and tells the agents to ground their work in it.
- Prefer `--mock` first if you just want to see the pipeline run end-to-end without spending tokens.