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 | 0 | Task router, complexity classification, model tier assignment | Every task |
| planner | 1 | Scope-adaptive planning, Gate 1, bead decomposition | Standard/complex tasks |
| architect | 1 | ADRs, system design | Complex tasks |
| tester | 2 | Test writing (TDD red/green/refactor) | After planning |
| security | 2, 4 | Security audit, BLOCK verdicts | Auth/payment changes |
| developer | 3 | Implementation, bead processing | After tester |
| evaluator | 3, 4 | Behavioral verification, rubric grading | Harness pipeline, mk:evaluate |
| reviewer | 4 | 5-dimension structural audit, Gate 2 | After developer |
| shipper | 5 | Deploy pipeline, PR creation | After Gate 2 |
| documenter | 6 | Living docs, changelogs | After ship |
| analyst | 0, 6 | Cost tracking, pattern analysis | Session start/end |
| 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 | 1 | Trade-off analysis, solution exploration | advisory |
| researcher | 0, 1, 4 | Technology research, library evaluation | advisory |
| ui-ux-designer | 3 | UI design, accessibility, design systems | advisory |
| git-manager | 5, any | Git operations, conventional commits | utility |
| 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 | Single-issue CRUD (create, read, update, delete) | 4-tier graduated confirmation |
| jira-search | JQL queries, filter management, result export | Mandatory JQL sanitization |
| jira-lifecycle | Transitions, assignments, versions, components | Workflow discovery before transitions |
| jira-collaborate | Comments, attachments, watchers, notifications | Internal-vs-public comment gate |
| jira-relationships | Issue links, blockers, dependencies, clones | Semantic link type enforcement |
| jira-time | Work logging, estimates, time reports | Confirm before worklog edits/deletes |
| jira-agile | Sprints, epics, backlog, story points, velocity | Board ID ≠ Project Key validation |
| jira-fields | Custom field discovery and caching | Read-only by default; admin for config |
| jira-bulk | Bulk transition, assign, priority, clone, delete | Mandatory dry-run for all operations |
| jira-jsm | Service desks, requests, SLAs, approvals | JSM license + agent role required |
| jira-admin | Projects, users, groups, schemes, automation | 2-step token confirmation for deletes |
| jira-dev | Branch names, PR descriptions, commit links | Read-only, output generation only |
| jira-ops | Cache management, connectivity, project context | Diagnostic-only, no Jira state changes |
| jira-evaluator | Ticket complexity scoring (8 dimensions) | Read-only analysis |
| jira-estimator | Story point estimation with reasoning | Read-only, never sets points |
| 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 | Single-page CRUD + hierarchy + version + copy/move | 4-tier graduated confirmation; ADF-round-trip warning on macro-heavy bodies |
| confluence-search | CQL queries, validation, space listing, saved filters, export | Mandatory CQL sanitization for any user-derived term |
| 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 | Bulk-label / bulk-move / bulk-delete on 10+ pages | Mandatory 3-step dry-run + typed-token confirmation |
| 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 |