# LazyClaude Agents

LazyClaude agents map the LazyClaude team workflow into Claude Code subagents
with bounded responsibilities.

| Agent | Responsibility | Boundary |
| --- | --- | --- |
| `prometheus-planner` | Build implementation plans and identify risks. | Read-only tools, no write/edit/bash tools. |
| `boulder-executor` | Execute checked plan tasks. | Must follow task acceptance criteria and collect evidence. |
| `oracle-verifier` | Verify tests, artifacts, and task completion. | Reviews evidence before approval. |
| `quality-reviewer` | Perform code-review style risk checks. | Findings first, no unrelated rewrites. |
| `librarian-researcher` | Fetch and summarize external references. | Use primary sources and cite them. |
| `qa-runner` | Run tmux/manual QA scenarios. | Must clean up sessions and capture receipts. |

The planner is deliberately constrained because the safest Claude Code retrofit
keeps planning separate from mutation. Executor and QA agents can act only
inside the plan and evidence contract.

## Review Work Routing

The v0.2.0 workflow parity review route uses five evidence lanes:

| Review lane | Agent routing | Required evidence |
| --- | --- | --- |
| goal/constraint verification | `oracle-verifier` with `review-work` and `rules` | Goal, non-goals, acceptance criteria, publish boundary, and constraints checked against current docs/test reads. |
| hands-on QA execution | `qa-runner` with `start-work` and `review-work` | Automated test output, Manual-QA channels, artifacts, and cleanup receipt. |
| code quality | `quality-reviewer` with `review-work` and `programming` | Findings-first code review focused on regressions and maintainability. |
| security | `quality-reviewer` with `review-work` and `programming` | Prompt injection, malformed input, local state, and unsafe command handling risks. |
| local-first context mining | `librarian-researcher` with `rules` | Local checkout, docs, tests, and ledgers checked before external references. |

The aggregate verdict is PASS, FAIL, or NEEDS-CONTEXT. Broad review work may
use Dynamic workflow when Claude Code exposes it; isolated edits can use
`claude --worktree <short-name> --tmux` when a separate checkout is required.

## Dynamic Workflow Delegation

The v0.2.1 `/dynamic-workflow` route makes the delegation map explicit for
Claude Code Dynamic workflow lanes and subagent spawning:

| Delegation lane | Agent | Evidence boundary |
| --- | --- | --- |
| plan and dependency order | `prometheus-planner` | Read-only plan with files, tests, Manual-QA channel, and cleanup. |
| implementation | `boulder-executor` | Smallest checked code change with RED -> GREEN evidence. |
| acceptance verification | `oracle-verifier` | Goal, criteria, and artifact checks before completion. |
| manual QA | `qa-runner` | tmux/browser/HTTP/computer-use artifact plus cleanup receipt. |
| code/security review | `quality-reviewer` | Findings-first review with concrete file references. |
| local-first context mining | `librarian-researcher` | Repo/docs/history search before external sources. |

`lazyclaude-ai workflow-check --json` verifies that this route, goal guidance,
Dynamic workflow guidance, and subagent delegation surface are present.

## Local Use

Load the plugin from this checkout:

```bash
claude --plugin-dir ./plugins/lazyclaude
```

Then reload after edits:

```text
/reload-plugins
```
