orca-crew

{
  "name": "orca-crew",
  "version": "0.8.2",
  "description": "The orchestrator/worker session model over Orca orchestration. An orchestrator session keeps its context for decisions and dispatches everything else to worker sessions launched by seat name: the operator's own files name each seat (~/.claude/orca-crew/agents.md on the machine, .orca-crew/roles.md in the project), implementers route by complexity class, one reviewer session runs /code-review once per PR, the retained implementer works GitHub threads to zero, merge only on the operator's word. A session budget caps each work item at one implementer and one verifier. Since 0.3.0 a spine planned in that same session runs in three layers: the top agrees one implementer and one verifier seat per item with the operator and starts one spine session, that session creates a child Run and owns both item terminals per item, nested worker depth 2 is required with no fallback, no inherited-runtime subagent runs there, and the reviewer is chosen only at the PR. Since 0.4.0 the first verifier failure blocks and asks, the close and every PR loop run in fresh sessions the top dispatches, and the record pass is single and conditional. Since 0.5.0 each item closes through the lane before the barrier, a fix-now close review halts to a dispatched writer, a clean delegated review carries its reviewed head, a left-open PR resumes on its prior review state, the merge executor is the top's explicit assignment, and seat-launched terminals are closed and verified at teardown. Since 0.6.0 one fail-open hook tells a coordinator seat its own context figure past a configurable ceiling (default 500000 tokens), and the top, spine session and work-PR session rotate to a fresh seat at their next boundary — the hook itself runs on Claude Code only. Since 0.7.0 seats, agent commands, roles and conditions live in the operator's two files — the spine sidecar is deleted and the approved seats travel inside the spine session's brief. Defers every other Orca command to the Orca binary's own guide. Since 0.8.0, a spine's spine and close seats can be a DeepSeek Harness session (kind dsh-spine-driver, with dsh-crew), its items routed by .dsh-crew/roles.md. No lib, no state.",
  "author": {
    "name": "Pras"
  },
  "repository": "https://github.com/pulseai-labs/claude-agent-scaffolding",
  "license": "MIT",
  "keywords": [
    "orchestration",
    "orca",
    "multi-agent",
    "code-review",
    "skills"
  ],
  "skills": "./skills/",
  "interface": {
    "displayName": "Orca Crew",
    "shortDescription": "Orchestrator/worker session model over Orca.",
    "longDescription": "Orca Crew states who does what when one orchestrator session drives worker sessions through Orca orchestration: which named seat fills each role, what a brief must carry, where the orchestrator stops and dispatches instead, one code review per PR with findings returned through worker_done, GitHub threads worked to zero, and a merge only on the operator's explicit word. It defers every other Orca command to the Orca binary's own version-matched guide.",
    "developerName": "Pras",
    "category": "Coding",
    "capabilities": [
      "Interactive",
      "Read",
      "Write"
    ],
    "defaultPrompt": [
      "Start an orchestrator run for this objective.",
      "Spawn a worker session for this task.",
      "Review PR 123 in a fresh session."
    ],
    "websiteURL": "https://github.com/pulseai-labs/claude-agent-scaffolding/tree/main/orca-crew",
    "brandColor": "#1D4ED8"
  }
}

{
  "name": "orca-crew",
  "version": "0.8.2",
  "description": "The orchestrator/worker session model over Orca orchestration. An orchestrator session keeps its context for decisions and dispatches everything else to worker sessions launched by seat name: the operator's own files name each seat (~/.claude/orca-crew/agents.md on the machine, .orca-crew/roles.md in the project), implementers route by complexity class, one reviewer session runs /code-review once per PR, the retained implementer works GitHub threads to zero, merge only on the operator's word. A session budget caps each work item at one implementer and one verifier. Since 0.3.0 a spine planned in that same session runs in three layers: the top agrees one implementer and one verifier seat per item with the operator and starts one spine session, that session creates a child Run and owns both item terminals per item, nested worker depth 2 is required with no fallback, no inherited-runtime subagent runs there, and the reviewer is chosen only at the PR. Since 0.4.0 the first verifier failure blocks and asks, the close and every PR loop run in fresh sessions the top dispatches, and the record pass is single and conditional. Since 0.5.0 each item closes through the lane before the barrier, a fix-now close review halts to a dispatched writer, a clean delegated review carries its reviewed head, a left-open PR resumes on its prior review state, the merge executor is the top's explicit assignment, and seat-launched terminals are closed and verified at teardown. Since 0.6.0 one fail-open hook tells a coordinator seat its own context figure past a configurable ceiling (default 500000 tokens), and the top, spine session and work-PR session rotate to a fresh seat at their next boundary — the hook itself runs on Claude Code only. Since 0.7.0 seats, agent commands, roles and conditions live in the operator's two files — the spine sidecar is deleted and the approved seats travel inside the spine session's brief. Defers every other Orca command to the Orca binary's own guide. Since 0.8.0, a spine's spine and close seats can be a DeepSeek Harness session (kind dsh-spine-driver, with dsh-crew), its items routed by .dsh-crew/roles.md. No lib, no state.",
  "author": {
    "name": "Pras"
  },
  "userConfig": {
    "context_ceiling": {
      "type": "number",
      "title": "Context ceiling (tokens)",
      "description": "Past this many tokens of context, an Orca coordinator seat (the top, a spine session, a work-PR session) is told to finish the unit in hand, start no new one and rotate at its next boundary. 500000 is half a 1M window.",
      "default": 500000,
      "min": 1
    }
  }
}