---
title: Agents Reference
description: Complete agent roster — 38 specialist agents (12 core, 5 support, 16 Jira, 5 Confluence) with type, role, phase, and activation conditions.
---

# Agents Reference

MeowKit ships 38 specialist agents across four categories: 12 core pipeline agents, 5 support agents, 16 Jira integration agents, and 5 Confluence Cloud integration agents. Each owns a specific phase or concern. No two agents modify the same file type.

## Core Agents

Pipeline agents that execute sequentially through phases 0-6.

| Agent | Phase | Role | Auto-activates |
|-------|-------|------|---------------|
| [orchestrator](/reference/agents/orchestrator) | 0 | Task router, complexity classification, model tier assignment | Every task |
| [planner](/reference/agents/planner) | 1 | Scope-adaptive planning, Gate 1, bead decomposition | Standard/complex tasks |
| [architect](/reference/agents/architect) | 1 | ADRs, system design | Complex tasks |
| [tester](/reference/agents/tester) | 2 | Test writing (TDD red/green/refactor) | After planning |
| [security](/reference/agents/security) | 2, 4 | Security audit, BLOCK verdicts | Auth/payment changes |
| [developer](/reference/agents/developer) | 3 | Implementation, bead processing | After tester |
| [evaluator](/reference/agents/evaluator) | 3, 4 | Behavioral verification, rubric grading | Harness pipeline, `mk:evaluate` |
| [reviewer](/reference/agents/reviewer) | 4 | 5-dimension structural audit, Gate 2 | After developer |
| [shipper](/reference/agents/shipper) | 5 | Deploy pipeline, PR creation | After Gate 2 |
| [documenter](/reference/agents/documenter) | 6 | Living docs, changelogs | After ship |
| [analyst](/reference/agents/analyst) | 0, 6 | Cost tracking, pattern analysis | Session start/end |
| [project-manager](/reference/agents/project-manager) | on-demand | Cross-workflow delivery tracking, status reports | On request via `/mk:status` |

## Support Agents

Invoked on-demand by core agents or explicitly by the user.

| Agent | Phase | Role | Subagent type |
|-------|-------|------|--------------|
| [brainstormer](/reference/agents/brainstormer) | 1 | Trade-off analysis, solution exploration | advisory |
| [researcher](/reference/agents/researcher) | 0, 1, 4 | Technology research, library evaluation | advisory |
| [ui-ux-designer](/reference/agents/ui-ux-designer) | 3 | UI design, accessibility, design systems | advisory |
| [git-manager](/reference/agents/git-manager) | 5, any | Git operations, conventional commits | utility |
| [journal-writer](/reference/agents/journal-writer) | 6 | Failure documentation, root cause analysis | escalation |

## Jira Agents

Domain agents for Jira integration via the `jira-as` CLI wrapper. All share a 4-tier safety model and follow the Rule of Two.

| Agent | Role | Safety highlight |
|-------|------|-----------------|
| [jira-issue](/reference/agents/jira-issue) | Single-issue CRUD (create, read, update, delete) | 4-tier graduated confirmation |
| [jira-search](/reference/agents/jira-search) | JQL queries, filter management, result export | Mandatory JQL sanitization |
| [jira-lifecycle](/reference/agents/jira-lifecycle) | Transitions, assignments, versions, components | Workflow discovery before transitions |
| [jira-collaborate](/reference/agents/jira-collaborate) | Comments, attachments, watchers, notifications | Internal-vs-public comment gate |
| [jira-relationships](/reference/agents/jira-relationships) | Issue links, blockers, dependencies, clones | Semantic link type enforcement |
| [jira-time](/reference/agents/jira-time) | Work logging, estimates, time reports | Confirm before worklog edits/deletes |
| [jira-agile](/reference/agents/jira-agile) | Sprints, epics, backlog, story points, velocity | Board ID ≠ Project Key validation |
| [jira-fields](/reference/agents/jira-fields) | Custom field discovery and caching | Read-only by default; admin for config |
| [jira-bulk](/reference/agents/jira-bulk) | Bulk transition, assign, priority, clone, delete | Mandatory dry-run for all operations |
| [jira-jsm](/reference/agents/jira-jsm) | Service desks, requests, SLAs, approvals | JSM license + agent role required |
| [jira-admin](/reference/agents/jira-admin) | Projects, users, groups, schemes, automation | 2-step token confirmation for deletes |
| [jira-dev](/reference/agents/jira-dev) | Branch names, PR descriptions, commit links | Read-only, output generation only |
| [jira-ops](/reference/agents/jira-ops) | Cache management, connectivity, project context | Diagnostic-only, no Jira state changes |
| [jira-evaluator](/reference/agents/jira-evaluator) | Ticket complexity scoring (8 dimensions) | Read-only analysis |
| [jira-estimator](/reference/agents/jira-estimator) | Story point estimation with reasoning | Read-only, never sets points |
| [jira-analyst](/reference/agents/jira-analyst) | Full context analysis with media and linked issues | Read-only, processes attachments |

## Confluence Agents

Domain agents for Confluence Cloud integration via the `confluence-as` CLI wrapper. Cloud-only (the wrapper exits 3 on non-`*.atlassian.net` URLs); follow the Rule of Two.

| Agent | Role | Safety highlight |
|-------|------|-----------------|
| [confluence-page](/reference/agents/confluence-page) | Single-page CRUD + hierarchy + version + copy/move | 4-tier graduated confirmation; ADF-round-trip warning on macro-heavy bodies |
| [confluence-search](/reference/agents/confluence-search) | CQL queries, validation, space listing, saved filters, export | Mandatory CQL sanitization for any user-derived term |
| [confluence-spec-analyst](/reference/agents/confluence-spec-analyst) | Read-only deep spec analysis with macro-aware ADF fetch + persisted Spec Research Report | Read-only at Confluence side; `[UNHANDLED_NODE]` keys-only metadata blocks injection |
| [confluence-bulk](/reference/agents/confluence-bulk) | Bulk-label / bulk-move / bulk-delete on 10+ pages | Mandatory 3-step dry-run + typed-token confirmation |
| [confluence-collaborate](/reference/agents/confluence-collaborate) | Comments, attachments, labels, watchers per page | Footer-default for comments; path-traversal guard on uploads |

## Agent communication

All subagents report structured status on completion:

```
**Status:** DONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT
**Summary:** [1-2 sentences]
**Concerns/Blockers:** [if applicable]
```

## File ownership

No two agents modify the same file type. Conflicts escalate to human.

| File type | Owned by |
|-----------|----------|
| `src/`, `lib/`, `app/` | developer |
| `tasks/plans/` | planner |
| `tasks/reviews/` | reviewer |
| `docs/` | documenter |
| `.claude/memory/` | analyst, documenter |

## See also

- [How agents and skills work together](/core-concepts/how-it-works)
- [Workflow phases](/core-concepts/workflow)
- [Skills reference](/reference/skills)
- [Agent definitions on disk](https://github.com/ngocsangyem/MeowKit/tree/main/.claude/agents) — canonical source
