LogoSkills

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#

PersonaAnalysisPlanningSolutioningImplementation
Analystโœ… PrimarySupport--
Product Manager-โœ… Primary--
Architect--โœ… PrimarySupport
UX Designer--โœ… PrimarySupport
Flutter Developer---โœ… Primary
Backend Developer---โœ… Primary
Scrum Master---โœ… Primary

Detailed Persona Responsibilities#

Linked agent path rules:

  • agents/xxx โ†’ .claude/agents/xxx.md
  • commands/agents/xxx โ†’ .claude/commands/agents/xxx.md
  • skills/xxx โ†’ .claude/skills/xxx/SKILL.md

Analyst#

AreaDetails
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 commands/agents/figma-analyzer-agent, commands/agents/bdd-scenario-agent
Approval Criteria All review items PASS + at least 1 each of Acceptance Criteria @happy-path, @error-handling

Product Manager (PM)#

AreaDetails
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 commands/agents/zenhub-integration-agent, ZenHub MCP tools
Approval CriteriaIssue created + all review items PASS

Architect#

AreaDetails
PrimaryArchitecture design, API design, technology selection
Review Items Clean Architecture, DI structure, API design, security
DeliverablesArchitecture approval, design feedback
Linked Agentsskills/code-review-checklist
Approval CriteriaAll mandatory review items PASS

UX Designer#

AreaDetails
PrimaryUI/UX review, accessibility review
Review Items CoUI compliance, layout, interaction, accessibility (recommended)
DeliverablesUX approval, design feedback
Linked Agents agents/flutter-ui, commands/agents/shared/widgetbook-agent
Approval Criteria Mandatory review items PASS (accessibility is recommended)

Flutter Developer#

AreaDetails
PrimaryUI implementation, BLoC state management, test creation
Review Items BLoC pattern, CoUI design-system usage (recommended), widget patterns, routing, i18n
DeliverablesCompleted frontend code, tests
Linked Agents commands/agents/feature-orchestrator-agent , commands/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 CriteriaLint pass, tests pass

Backend Developer#

AreaDetails
Primary OpenAPI client integration, data mapping, API communication
Review Items Mapper definition, API error handling, response transformation
DeliverablesMapper classes, Repository Mixin
Linked Agentscommands/agents/app/data-layer-agent
Approval CriteriaCode generation complete, tests pass

Scrum Master#

AreaDetails
PrimaryWorkflow management, blocker resolution, status sync
Review Items Step progress, verification gates, Pipeline status, blockers, retry limit (max 3)
DeliverablesWorkflow completion, merge
Linked Agents agents/sequential-workflow, commands/agents/dev/issue-state-agent
Approval CriteriaAll steps complete, PR merged

Review Items x Persona Matrix#

Analysis Phase#

Review ItemAnalyst
Requirements clarityโœ… Required
Scope appropriatenessโœ… Required
Acceptance Criteria testabilityโœ… Required
Dependency analysisโš ๏ธ Recommended

Planning Phase#

Review ItemPM
Epic/Story structureโœ… Required
Story Pointโœ… Required
Labelingโœ… Required
Dependenciesโœ… Required

Solutioning Phase#

Review ItemArchitectUX Designer
Clean Architectureโœ… Required-
DI structureโœ… Required-
API designโš ๏ธ Conditional-
Securityโœ… Required-
CoUI compliance-โš ๏ธ Recommended
Layout-โœ… Required
Interaction-โœ… Required
Accessibility-โš ๏ธ Recommended

Implementation Phase#

Review ItemFlutter DevBackend DevScrum 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 Developer

Escalation Path#

SituationPrimarySecondaryEscalation
Unclear requirementsAnalystPMUser confirmation
Architecture conflictArchitectFlutter DevTeam meeting
UI/UX mismatchUX DesignerFlutter DevDesign team check
Blocker occursScrum MasterPMManager 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                      โ”‚
โ”‚                                                                 โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

  • .claude/personas/ - Detailed persona definitions
  • .claude/orchestrators/bmad-orchestrator.md - Orchestrator
  • .claude/orchestrators/phase-gates.md - Gate definitions