Persona Responsibility Matrix
Responsibility matrix for the 7 personas in the BMAD framework.
Responsibility matrix for the 7 personas in the BMAD framework.
Persona x Phase Matrix#
| Persona | Analysis | Planning | Solutioning | Implementation |
|---|---|---|---|---|
| Analyst | ✅ Primary | Support | - | - |
| Product Manager | - | ✅ Primary | - | - |
| Architect | - | - | ✅ Primary | Support |
| UX Designer | - | - | ✅ Primary | Support |
| Flutter Developer | - | - | - | ✅ Primary |
| Backend Developer | - | - | - | ✅ Primary |
| Scrum Master | - | - | - | ✅ Primary |
Detailed Persona Responsibilities#
Linked agent path rules:
agents/xxx→.claude/agents/xxx.mdagents/xxx→.claude/agents/xxx.mdskills/xxx→.claude/skills/xxx/SKILL.md
Analyst#
| Area | Details |
|---|---|
| Primary | Requirements analysis, BDD Gherkin Acceptance Criteria definition , feasibility review |
| Review Items | Requirements clarity, scope appropriateness, Acceptance Criteria Gherkin format , Acceptance Criteria completeness |
| Deliverables | Analyzed requirements, BDD Gherkin Acceptance Criteria list , screen type identification |
| Linked Agents | agents/figma-analyzer-agent, agents/bdd-scenario-agent |
| Approval Criteria | All review items PASS + at least 1 each of Acceptance Criteria @happy-path, @error-handling |
Product Manager (PM)#
| Area | Details |
|---|---|
| Primary | Issue structuring, Story Point estimation, priority setting |
| Review Items | Epic/Story structure, Story Point (1-8), labeling, dependencies |
| Deliverables | Created issues, labels, estimates, dependency relationships |
| Linked Agents | agents/zenhub-integration-agent, ZenHub MCP tools |
| Approval Criteria | Issue created + all review items PASS |
Architect#
| Area | Details |
|---|---|
| Primary | Architecture design, API design, technology selection |
| Review Items | Clean Architecture, DI structure, API design, security |
| Deliverables | Architecture approval, design feedback |
| Linked Agents | skills/quality:review-checklist |
| Approval Criteria | All mandatory review items PASS |
UX Designer#
| Area | Details |
|---|---|
| Primary | UI/UX review, accessibility review |
| Review Items | CoUI compliance, layout, interaction, accessibility (recommended) |
| Deliverables | UX approval, design feedback |
| Linked Agents | agents/flutter-ui, agents/shared/widgetbook-agent |
| Approval Criteria | Mandatory review items PASS (accessibility is recommended) |
Flutter Developer#
| Area | Details |
|---|---|
| Primary | UI implementation, BLoC state management, test creation |
| Review Items | BLoC pattern, CoUI design-system usage (recommended), widget patterns, routing, i18n |
| Deliverables | Completed frontend code, tests |
| Linked Agents | agents/feature-orchestrator-agent, agents/app/presentation-layer-agent |
| Design System |
CoUI — component APIs via the
cc-coui
skill or CoUI source. If a CoUI MCP (
coui-*
) is configured in
.mcp.json
, its tools may be used; discover them at runtime (tool names vary by version) and fall back to
cc-coui
when absent.
|
| Approval Criteria | Lint pass, tests pass |
Backend Developer#
| Area | Details |
|---|---|
| Primary | OpenAPI client integration, data mapping, API communication |
| Review Items | Mapper definition, API error handling, response transformation |
| Deliverables | Mapper classes, Repository Mixin |
| Linked Agents | agents/app/data-layer-agent |
| Approval Criteria | Code generation complete, tests pass |
Scrum Master#
| Area | Details |
|---|---|
| Primary | Workflow management, blocker resolution, status sync |
| Review Items | Step progress, verification gates, Pipeline status, blockers, retry limit (max 3) |
| Deliverables | Workflow completion, merge |
| Linked Agents | agents/sequential-workflow, agents/dev/issue-state-agent |
| Approval Criteria | All steps complete, PR merged |
Review Items x Persona Matrix#
Analysis Phase#
| Review Item | Analyst |
|---|---|
| Requirements clarity | ✅ Required |
| Scope appropriateness | ✅ Required |
| Acceptance Criteria testability | ✅ Required |
| Dependency analysis | ⚠️ Recommended |
Planning Phase#
| Review Item | PM |
|---|---|
| Epic/Story structure | ✅ Required |
| Story Point | ✅ Required |
| Labeling | ✅ Required |
| Dependencies | ✅ Required |
Solutioning Phase#
| Review Item | Architect | UX Designer |
|---|---|---|
| Clean Architecture | ✅ Required | - |
| DI structure | ✅ Required | - |
| API design | ⚠️ Conditional | - |
| Security | ✅ Required | - |
| CoUI compliance | - | ⚠️ Recommended |
| Layout | - | ✅ Required |
| Interaction | - | ✅ Required |
| Accessibility | - | ⚠️ Recommended |
Implementation Phase#
| Review Item | Flutter Dev | Backend Dev | Scrum Master |
|---|---|---|---|
| BLoC pattern | ✅ Required | - | - |
| CoUI usage | ⚠️ Recommended | - | - |
| Widget patterns | ✅ Required | - | - |
| Routing | ✅ Required | - | - |
| i18n | ✅ Required | - | - |
| Mapper definition | - | ✅ Required | - |
| API error handling | - | ✅ Required | - |
| Response transformation | - | ✅ Required | - |
| DioException handling | - | ✅ Required | - |
| Step progress | - | - | ✅ Required |
| Gate verification | - | - | ✅ Required |
| Pipeline status | - | - | ✅ Required |
| Blocker resolution | - | - | ✅ Required |
Parallelizable Combinations#
Solutioning Phase (always parallel)#
Architect ──┬──→ Parallel execution ──→ Proceed when all PASS
UX Designer ─┘Implementation Phase (conditional parallel)#
Condition: When Backend and Frontend are independent
Backend Developer ──┬──→ Parallel execution ──→ Integrate when all complete
Flutter Developer ──┘
Condition: When Backend dependency exists
Backend Developer ──→ Complete ──→ Flutter DeveloperEscalation Path#
| Situation | Primary | Secondary | Escalation |
|---|---|---|---|
| Unclear requirements | Analyst | PM | User confirmation |
| Architecture conflict | Architect | Flutter Dev | Team meeting |
| UI/UX mismatch | UX Designer | Flutter Dev | Design team check |
| Blocker occurs | Scrum Master | PM | Manager escalation |
| Gate fails 3 times | Relevant persona | Scrum Master | Root cause analysis → split/redefine task |
Retry Limit Escalation ⚠️#
When a gate fails 3 consecutive times, it is automatically escalated to Scrum Master:
┌─────────────────────────────────────────────────────────────────┐
│ Procedure when gate fails 3 times │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 1. Scrum Master analyzes failure cause │
│ 2. Identify root cause: │
│ - Requirements issue → Redefine with Analyst │
│ - Technical complexity → Split task │
│ - External dependency → Register blocker │
│ 3. Apply solution and restart (reset retry counter) │
│ │
│ Config: bmad.json → feedback.maxRetries: 3 │
│ │
└─────────────────────────────────────────────────────────────────┘Related Documents#
.claude/personas/- Detailed persona definitions.claude/orchestrators/bmad-orchestrator.md- Orchestrator.claude/orchestrators/phase-gates.md- Gate definitions