Claude Code Subagents · page 13

|

|

|

Use proactively before opening a PR that adds or changes BehaviorTree.CPP nodes or BehaviorTree.ROS2 wrappers (RosActionNode/RosServiceNode/RosTopicPub/SubNode, TreeExecutionServer). Reviews a diff against BT.CPP v4 conventions — node base-class choice, non-blocking ticks, ports/blackboard typing, factory/plugin registration, XML v4, and the ROS 2 wrapper contract. Returns a punch list with file:line anchors, not a rewrite.

Use when a design decision touches Clean Architecture boundaries in a ROS 2 project — which layer a new behaviour belongs to, whether a port belongs in domain or application, whether a new node should be lifecycle-managed, whether to compose nodes or split packages. Returns an architectural recommendation with trade-offs, not implementation.

Use when a design decision touches the gz-sim ECS — where new state should live, which system phase should write it, how to avoid coupling, whether to add a component vs. a member variable, whether a new system should be split or merged with an existing one. Returns an architectural recommendation with trade-offs, not implementation.

Use proactively before opening any gz-sim PR. Reviews a diff against the project's C++17 style, ECS conventions, plugin registration patterns, CMake structure, test placement, Migration.md / Changelog.md expectations, and pre-commit configuration. Returns a punch list, not a rewrite.

Use proactively before opening a PR that adds or changes a ros2_control controller, broadcaster, or hardware component (incl. URDF <ros2_control> bringup). Reviews a diff against ros2_controllers / ros2_control_demos conventions — controller & hardware lifecycle, command/state interface configuration, real-time safety of update()/read()/write(), generate_parameter_library usage, pluginlib registration, chainable-controller correctness, URDF wiring, and tests. Returns a punch list with file:line anchors, not a rewrite.

Use proactively before opening any ROS 2 / Nav 2 PR. Reviews a diff against this template's Clean Architecture, ROS 2 communication, lifecycle, testing, and Nav 2 plugin conventions. Returns a punch list with file:line anchors, not a rewrite.

Use proactively before opening a PR that touches a VDA 5050 connector / fleet bridge. Reviews a diff against VDA 5050 v3.0.0 protocol compliance (topics, QoS, header rules, base/horizon, action state machine, schema validation) and the template's Clean Architecture for the MQTT↔Nav 2 bridge. Returns a punch list with file:line anchors, not a rewrite.

Use to watch the whole cc-fleet fleet live from inside this session — it surfaces a running fleet in the agent panel and streams the status board (provider teammates, one-shot subagent jobs, and workflow runs) until interrupted.

Use to watch a running cc-fleet workflow run live from inside this session — it surfaces the run in the agent panel and streams its status until the run finishes. Invoke with the run id (and, on a reattach, the last seq from the previous "still running (seq=N)" line).

Cross-artifact consistency and coverage analysis specialist with Anthropic think protocol. Validates alignment between specifications, plans, tasks, and implementation. Use before implementation to catch conflicts early.

Production deployment specialist with Anthropic safety patterns managing CI/CD pipelines, infrastructure provisioning, and safe rollout strategies. Defaults to canary deployments with auto-rollback. Use for production deployments and release management.

Root cause analysis and debugging specialist with Anthropic think protocol and 3-retry limit. Focuses on systematic problem diagnosis, error tracing, and fix validation. Use for complex bugs and system failures.

Observability and monitoring specialist with Anthropic's three pillars pattern (Metrics, Logs, Traces). Sets up comprehensive monitoring, SLI/SLO tracking, and incident detection. Use for system observability and proactive alerting.

Performance optimization and auto-scaling specialist with Anthropic profiling patterns. Manages horizontal/vertical scaling, load balancing, caching strategies, and continuous performance tuning. Use for scaling challenges and performance work.

Master orchestrator for complex, multi-faceted software projects. Coordinates specialist agents (researchers, planners, implementers) to deliver cohesive solutions. Use for projects requiring 3+ capabilities or cross-domain work (frontend + backend + devops).

Precision execution specialist that implements code following Implementation Plans and ResearchPacks. Makes surgical, minimal edits with self-correction capability (3 retries). Always runs tests and validates against plan. Requires both ResearchPack and Implementation Plan as input.

High-speed documentation specialist. Fetches version-accurate docs from official sources to prevent coding from stale memory. Use before implementing any feature with external libraries or APIs. Delivers ResearchPack in < 2 minutes.

Strategic architect that transforms ResearchPacks into surgical, reversible implementation plans. Analyzes codebase structure, identifies minimal changes, and creates step-by-step blueprints with rollback procedures. Requires ResearchPack as input.

WOZCODE free-plan fallback agent — active when the monthly free-plan cap is exhausted. Claude Code's built-in Read, Edit, Write, Grep, Glob, and NotebookEdit are available; WOZCODE MCP tools are disallowed until the cap resets or the user upgrades.

WozCode enhanced coding agent with smart search, batch editing, and SQL introspection. Use as the default main thread agent.

Fast read-only agent for file searches, symbol lookups, and codebase questions like "where is X defined?", "where is X called?", or "how does X flow through the system?". Prefer over shell-based exploration when answering would take 3+ Search/Sql calls. Cheaper model (haiku) so delegation pays for itself on any real scan.

Runs the recall CLI over the user's past Claude Code sessions and returns the one actionable item — a command, decision, or fix — distilled from a prior conversation, not raw transcripts.

Minimal-context exercise agent for the weak-agent-test benchmark. No Skill tool (and therefore no skills catalog in context) — the benchmark's "capable-but-fresh agent" must discover docx-cli from the tool's own --help, and the catalog is pure token overhead on every turn. Tools are the small set the exercise actually uses.

Idun coding-guideline review against the active rule set.

Read-only investigation engine: codebase exploration, auditing, research, and runtime evidence gathering for a failure. Cannot modify files. Use before planning, to answer a question that requires grounding findings in evidence (file:line, config value, schema fact), or to reproduce a failure and capture its runtime evidence before anyone reads the source.

Implements all files listed in an approved plan. Writes production code, configuration, and updates test implementations. Use after test skeleton approval.

Designs implementation plans for coding tasks. Writes plan.md and capabilities.md to the project root. Use after exploration, before test writing.

Reviews an implementation diff in two passes (spec-compliance first, then code quality). Read-only. Returns structured findings. Replaces the separate spec/code-quality reviewers.

Writes test skeleton files with method signatures and assertions based on an approved plan. Use after plan approval, before implementation.

Runs a project's configured verification stages (build/unit/integration/etc.) from `.lattice/verification.yaml` via the deterministic runner script, then returns the run's summary.json verbatim. Invoke before declaring work done, to confirm a change actually works, or whenever a faithful execution report is needed without pulling raw logs into the session. Only executes what is configured — never writes or chooses checks, never opens a log file. Example: "Run verification and tell me if it's safe to proceed.

|

Agora member. Use standalone for task separation & community-feeling analysis, or via /hearth for relationship deliberation.

Agora member. Use standalone for meaning-finding & attitudinal freedom analysis, or via /clinic or /oracle for deliberation.

Agora member. Use standalone for love-as-practice & productive orientation analysis, or via /hearth for relationship deliberation.

Agora member. Use standalone for shadow integration & individuation analysis, or via /oracle or /clinic for deliberation.

Agora member. Use standalone for categorical imperative & universalizability analysis, or via /hearth or /forge for deliberation.

Agora member. Use standalone for creative destruction & value revaluation, or via /forge, /oracle, or /atelier for deliberation.

Agora member. Use standalone for simplicity audit & complexity reduction, or via /forge or /atelier for deliberation.

Agora member. Use standalone for falsification & red-team analysis, or via /forge for engineering deliberation.

Agora member. Use standalone for radical freedom & responsibility analysis, or via /oracle for life crossroads deliberation.

Agora member. Use standalone for creative destruction & entrepreneurship analysis, or via /bazaar for business & strategy deliberation.

Agora member. Use standalone for behavioral design & environmental analysis, or via /clinic for psychological resilience deliberation.

Agora member. Use standalone for language decomposition & F/D/Q analysis, or via /forge or /atelier for deliberation.

Agora member. Use standalone for effortless action & perspective liberation analysis, or via /hearth or /clinic for deliberation.

Council member. Use standalone for formal systems & computational analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for categorization & structural analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for resilience & moral clarity analysis, or via /council for multi-perspective deliberation, or via /oracle, /hearth, /clinic for life & relationship deliberation.

Council member. Use standalone for first-principles debugging & explanation testing, or via /council for multi-perspective deliberation.

Council member. Use standalone for cognitive bias detection & decision science analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for neural network intuition & empirical ML analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for emergence & non-intervention analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for power dynamics & incentive analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for systems thinking & feedback loop analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for multi-model reasoning & economic analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for strategic timing & situational awareness analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for user-centered design & simplicity analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for assumption destruction & dialectical analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for adversarial strategy & competitive analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for scaling frontier & AI safety analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for antifragility & tail risk analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for pragmatic engineering & shipping analysis, or via /council for multi-perspective deliberation.

Council member. Use standalone for perspective dissolution & reframing analysis, or via /council for multi-perspective deliberation.

Orchestrates CLAUDE.md updates for changed files

API endpoint testing. Discovery, validation, auth flows, error handling.

Supervisor agent. Coordinates auditors, validates fixes, iterates until production-ready.

Navigates running web applications via Chrome integration to find UI bugs, console errors, and UX issues. Uses /chrome tools to interact with localhost or deployed apps.

Runtime bug scanner. Finds error handling gaps, race conditions, memory leaks, null refs.

Code quality auditor. Reviews patterns, maintainability, complexity, consistency.

Implements fixes from FIXES.md. Production-quality code following project patterns.

Real-time console monitoring during browser sessions. Watches for errors, warnings, and logs as you test.

Database auditor. Schema design, N+1 queries, indexes, connection pooling.

Dependency auditor. Outdated packages, vulnerabilities, licenses, unused deps.

Pre-deployment validation. Build, env vars, dependencies, migrations, health checks.

Documentation coverage analyzer. Finds missing docs, outdated comments, API gaps.

Environment configuration validator. Compares .env.example vs .env, checks for secrets.

Creates prioritized fix plans from audit findings. Generates FIXES.md with deduplication.

Coordinates browser-qa-agent with code-fixer for complete test-fix-verify cycles. The Replit-style workflow.

Infrastructure and deployment checker. Env vars, headers, database config.

Performance auditor. Bundle size, Core Web Vitals, slow queries, memory leaks.

Pull request description generator. Summarizes changes, creates checklist.

Comprehensive security analysis. OWASP Top 10, injection, auth, secrets, headers.

Test data generator. Creates realistic seed data based on schema.

SEO and discoverability auditor. Meta tags, OpenGraph, sitemap, structured data.

Runs tests and validates fixes. TypeScript, lint, unit tests.

Auto-generates tests for existing code. Unit tests, integration tests, coverage gaps.

UI/UX consistency and accessibility checker. Design patterns, a11y issues.

Screenshot comparison for visual regression testing. Captures before/after states and reports differences.

Use this agent when reviewing local code changes or in the pull request to identify bugs and critical issues through systematic root cause analysis. This agent should be invoked proactively after completing a logical chunk of work.

Expert business analyst. MUST BE USED to analyze requirements, create user stories, define acceptance criteria, and translate business needs into technical specifications.

Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, or for reviwing pull request changes.

Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.

Expert full-stack developer specializing in modern web technologies. MUST BE USED for all implementation tasks including backend APIs, frontend applications, database operations, and full-stack features. Works with the project's configured tech stack.

Use this agent when reviewing local code changes or pull requests to understand the historical context of modified code, including past issues, patterns, and lessons learned. This agent should be invoked to prevent repeating past mistakes and to ensure consistency with previous decisions.

Senior principal software engineer. MUST BE USED to review code quality, architecture, design patterns, best practices, and investigate technical issues. Proactively reviews after any code changes and investigates bugs or performance problems.

Expert QA/QC engineer. MUST BE USED for all testing tasks, test plan creation, test execution, and quality assurance. Use for unit tests, integration tests, and test coverage analysis.

Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.

Expert solution architect. MUST BE USED to design system architecture, create technical specifications, define data models, and make technology stack decisions based on analyzed requirements.