orc

Timpl — Multi-Agent Orchestration Plugin for Claude Code

What Is This?

A Claude Code plugin that transforms Claude Code from a single-session assistant into a team of specialized AI agents that collaborate on software engineering tasks. It's a port of an internal system called "pi orchestration" to the Claude Code environment.

Invocation: /orc:run <task description>

The plugin is never auto-triggered — you invoke it explicitly when you want structured multi-agent workflows.

---

Plugin Structure

orc/
├── .claude-plugin/
│   └── plugin.json              # Plugin metadata
├── commands/
│   └── run.md                   # /orc:run entry point
└── agents/
    ├── researcher.md            # Read-only codebase explorer
    ├── planner.md               # Creates implementation plans
    ├── worker.md                # Implements code changes
    ├── reviewer.md              # Audits code for bugs/regressions
    ├── sceptic.md               # Adversarial reviewer
    └── session-analyzer.md      # Extracts knowledge from sessions

All agents are scoped to the plugin — they are not directly accessible from Claude Code, only through /orc:run.

---

The Agents

The system defines a pipeline of specialists, each with strictly scoped capabilities:

1. Researcher (researcher.md)

• Role: Read-only codebase explorer. First agent in any workflow.
• Model: Opus
• Tools: Read, Write, Bash, Glob, Grep (write access limited to research documents)
• Key behavior: Only writes research outcome documents (plans/<branch>/RESEARCH.md) — never modifies existing project files. Reads .agent/knowledge/ docs before exploring code. Verifies claims against actual code, not just filenames.
• Output: RESEARCH.md document in plans folder, plus: Summary, Findings (with file paths + evidence), Recommendations, Open Questions

2. Planner (planner.md)

• Role: Converts research into structured implementation plans. Produces PLAN.md and ARCHITECTURE.md.
• Model: Opus
• Tools: Read, Write, Edit, MultiEdit, Bash, Glob, Grep (has write access)
• Key behavior: Plans go in plans/<branch-name>/PLAN.md. Plans must be precise enough that the worker agent can execute verbatim.
• Output: PLAN.md (milestones, dependencies, file changes) and ARCHITECTURE.md (system overview, data flow, interfaces)

3. Worker (worker.md)

• Role: Implementation specialist. Writes code, runs tests, self-reviews.
• Model: Opus
• Tools: Read, Write, Edit, MultiEdit, Bash, Glob, Grep (full write access)
• Key behavior: Reads PLAN.md FIRST — the plan is law. Implements ONLY what the plan specifies. Self-reflects after making changes.
• Output: Changes Made (per-file), Specs (test results), Self-Review Findings, Plan Gaps

4. Reviewer (reviewer.md)

• Role: Post-implementation code auditor. Reads changed code AND interacting code.
• Model: Opus
• Tools: Read, Bash, Glob, Grep (no write access)
• Key behavior: Reviews changed files AND their callers/dependencies. Checks for race conditions, N+1 queries, missing validations, TOCTOU issues, dead code.
• Output: Verdict (PASS/FAIL), CRITICAL / MODERATE / MINOR issues, plus a "Positive" section

5. Sceptic (sceptic.md)

• Role: Adversarial challenger. Finds problems, not confirms solutions.
• Model: Opus
• Tools: Read, Bash, Glob, Grep (no write access)
• Key behavior: Does its OWN independent research — reads actual code to verify/disprove claims. Provides counter-proposals when it finds issues.
• Output: Verdict (SOLID / HAS ISSUES / NEEDS REWORK), Critical Issues, Concerns, Counter-proposals

6. Session Analyzer (session-analyzer.md)

• Role: Meta-learning agent. Mines conversation transcripts for reusable knowledge.
• Model: Opus
• Tools: Read, Glob, Grep (most restricted — no Bash, no write)
• Key behavior: Distinguishes between SKILLS (techniques, workflows) and MEMORIES (preferences, decisions, conventions).
• Output: Categorized findings (SKILL or MEMORY) with title, description, examples, and source context

Access Control Summary

Agent	Can Read	Can Write	Can Run Shell
Researcher	Yes	Research docs only	Yes
Planner	Yes	Yes	Yes
Worker	Yes	Yes	Yes
Reviewer	Yes	No	Yes
Sceptic	Yes	No	Yes
Session Analyzer	Yes	No	No

---

Workflow Patterns

The /orc:run command analyzes your task and selects the appropriate workflow:

Workflow 1: Adversarial Research

When: Architecture decisions, technology evaluations Pipeline: Researcher (explore) -> Sceptic (challenge findings) -> optional Researcher rebuttal Purpose: Structured debate to stress-test technical decisions