The team

Eighteen agents, three lenses, one product. Quorum operationalizes the Desirability / Feasibility / Viability framework by distributing the argument across named agents, each with their own methods and artifacts. The framework is the spine; the agents are the practice.

Why named agents, not generic chat

Most AI tools collapse a product team into one assistant with five voices. Quorum keeps the roles structurally separate: Mary argues for the user; Winston argues for the build path; John argues for the business; Cipher argues for the attacker. Their disagreements are the product, captured in audit trail, surfaced where the user can act on them.

Each card below names what the agent runs, what they produce, and the trigger phrase to bring them into a session. The methods are real BMad and Dev Team workflows; the artifacts list is what shows up in the _bmad-output/planning-artifacts/ directory after a pipeline run.

See the PRD § The Three-Pillar Framework for how the agents map to gates, methods, and the rest of the requirements contract.

Desirability

8 agents

Do target users want this enough to change behavior, adopt a workflow, or pay?

Mary

Strategic Business Analyst
DesirabilityViability
Pillar lead

Owns the desirability lens. Mary runs the user research, frames the personas, pressure-tests claims, and signs off on whether the evidence is strong enough to clear the gate.

What they run · 6 methods
  • User interviews and qualitative synthesis
  • JTBD-grounded persona development with cited evidence per claim
  • Market research and sizing
  • Competitive landscape research
  • Domain research for vertical-specific work
  • Methodology comparison research
What they produce · 5 artifacts
  • personas.md JTBD-grounded personas with citations
  • research-synthesis.md Interview themes, observation logs, hypothesis tests
  • market-research.md Sized market with cited sources
  • competitive-landscape-research.md Competitor map with positioning gaps
  • domain-research.md Vertical-specific deep dives
Trigger: Mary

Quentin

Content Strategist + Accessibility Lead
Desirability

Tarantino-level intentionality applied to product copy. Quentin reads copy the way an editor reads a manuscript and a product the way a systems thinker reads a graph. He follows problems all the way through to resolution, even when they live at the UX, logic, or engineering layer.

What they run · 6 methods
  • Voice-of-customer synthesis from research transcripts
  • Voice & tone guide authorship and drift audits
  • Moments-that-matter inventory across the lifecycle
  • WCAG 2.2 AA / AAA accessibility audits
  • Accessibility-statement authorship that doesn't overclaim
  • Cross-layer product diagnosis (copy, UX, logic)
What they produce · 6 artifacts
  • voice-tone-guide.md Project voice spine all copy traces to
  • moments-that-matter.md Peak / valley / transition inventory with copy hooks
  • accessibility-statement.md Public commitment with honest scope
  • voice-drift-audit.md Periodic drift checks on shipping copy
  • error-pages.md Error-state copy that doesn't condescend
  • release-notes-format.md Post-ship narrative discipline
Trigger: Quentin

Freya

WDS Strategic UX Designer
Desirability

Strategic UX and design-thinking partner. Freya runs trigger-mapping workshops that connect business goals to user psychology, then turns the triggers into structured scenario outlines.

What they run · 4 methods
  • Trigger mapping (business goal → user-psychology trigger)
  • Scenario design (structured micro-step outlines)
  • UX strategy facilitation
  • Discovery-phase design partnership
What they produce · 2 artifacts
  • trigger-map.md Goal-to-trigger psychology mapping
  • scenarios.md Micro-step scenario outlines per primary flow
Trigger: Freya

Maya

Design Thinking Maestro
Desirability

Facilitates structured human-centered exercises. Maya runs the empathize → define → ideate → prototype → test cycle as a guided session with artifacts at each step, not a vibes meeting.

What they run · 4 methods
  • Empathy mapping (says / thinks / does / feels)
  • Design-thinking workshops (full five-stage)
  • Problem framing and reframing
  • Prototype-and-test cycles
What they produce · 2 artifacts
  • empathy-maps.md Structured empathy data per persona
  • design-thinking-session-notes.md Workshop outputs
Trigger: Maya

Carson

Brainstorming Specialist
Desirability

Forty-plus ideation techniques on tap. Carson opens the solution space when desirability research surfaces a need with no obvious answer, then helps the team converge.

What they run · 4 methods
  • SCAMPER, Six Thinking Hats, What If, Worst Possible Idea
  • Crazy Eights, Brainwriting, Round Robin
  • Reverse brainstorming and assumption flipping
  • Convergence techniques (dot voting, NUF test)
What they produce · 1 artifacts
  • brainstorming-output.md Divergent / convergent session capture
Trigger: Carson

Saga

WDS Strategic Business Analyst
DesirabilityViability

Strategic business analyst and product discovery partner for the WDS workflow. Saga focuses on the project's earliest moments — establishing context, classifying complexity, routing the project to the right phase before the deeper agents touch it.

What they run · 5 methods
  • Project setup and onboarding (project type, complexity, stack)
  • Project-context establishment for AI-agent consistency
  • Product-evolution analysis on brownfield projects
  • Domain and market triage
  • Discovery-phase facilitation
What they produce · 3 artifacts
  • project-context.md AI-agent rules and project routing
  • project-classification.md Type / complexity / stack triage
  • product-evolution-brief.md Brownfield improvement scope
Trigger: Saga

Dr. Quinn

Master Problem Solver
DesirabilityFeasibilityViability

Systematic problem-solving methodologies on tap. Dr. Quinn doesn't just brainstorm — he picks the right structured technique for the problem class, then walks the team through it with discipline.

What they run · 6 methods
  • 5 Whys for root-cause analysis
  • Fishbone (Ishikawa) for cause categorization
  • TRIZ patterns for inventive problem framing
  • First-principles decomposition
  • Pre-mortem and red-team analysis
  • Socratic method for assumption surfacing
What they produce · 2 artifacts
  • problem-frame.md Structured problem statement with chosen technique
  • root-cause-analysis.md 5 Whys / fishbone output
Trigger: Dr. Quinn

Sophia

Master Storyteller
DesirabilityViability

Turns persona research into the narrative spine of the pitch and case study. Sophia runs Hero's Journey, SCQA, Pixar, and before-and-after frames to surface narrative gaps.

What they run · 4 methods
  • Storytelling-framework analysis
  • Pitch narrative architecture
  • Case-study narrative shape
  • Investor-deck story arc
What they produce · 2 artifacts
  • case-study.md Outcome narrative for portfolio and sales
  • pitch-narrative.md Investor / executive deck story arc

Feasibility

11 agents

Can the team build, operate, ship, and maintain this with current or achievable capabilities?

Winston

System Architect
Feasibility
Pillar lead

Owns the feasibility lens. Winston produces the architecture decision records, identifies the build path, names the blockers, and signs off on whether the team can actually ship what desirability says users want.

What they run · 4 methods
  • Architecture decision records (decisions, alternatives, consequences)
  • Bounded technical research
  • Stack and integration assessment
  • Implementation-readiness checks
What they produce · 4 artifacts
  • architecture.md ADRs with alternatives and trade-offs named
  • tech-stack.md Stack inventory with rationale per choice
  • technical-research-*.md Bounded research reports with conclusions
  • implementation-readiness-report.md Go / no-go on dev start
Trigger: Winston

Damien

Backend Developer + Mentor
Feasibility

Databases, APIs, auth, deployment, modern backend platforms. Damien teaches as much as he builds, leaving the user with mental models that survive past the current task.

What they run · 5 methods
  • Schema design and migrations
  • API contract design (REST, RPC, GraphQL)
  • Auth flows and session architecture
  • Database performance and indexing strategy
  • Deployment and operational design
What they produce · 3 artifacts
  • schema.md Data model with rationale
  • api-contracts.md Endpoint contracts and error codes
  • auth-architecture.md Session, role, and permission model
Trigger: Damien

Jaymes

Frontend Developer + Mentor
Feasibility

Pixel-perfect implementation that holds up under interaction stress. Jaymes interprets designs, builds the UI, and explains the trade-offs as he goes.

What they run · 5 methods
  • Design-to-component translation
  • State management and data-flow design
  • Animation and transition implementation
  • Frontend performance tuning
  • Component architecture and design-system integration
What they produce · 2 artifacts
  • frontend-architecture.md Component layering and state strategy
  • /src/app/design-system/page.tsx Live design-system reference page
Trigger: Jaymes

Kinsley

Product Designer + Design Systems
FeasibilityDesirability

Product designer covering UX, visual design, design systems, and end-to-end design ownership. Kinsley audits whether a proposed pattern fits the existing token / component inventory or requires net-new work, the cost of which is the feasibility flag.

What they run · 5 methods
  • Design-system audits (tokens, components, patterns)
  • Component inventory and gap analysis
  • Design-pattern selection and trade-off framing
  • Cross-platform pattern shifts (mobile vs desktop)
  • Visual design and information architecture
What they produce · 3 artifacts
  • design-system.md Token + component inventory with usage rules
  • ux-design-specification.md End-to-end design spec
  • figma-handoff-brief.md Brief for visual production
Trigger: Kinsley

Luca

Motion Designer
Feasibility

Motion as a temporal design layer, not as decoration. Luca specs transitions, micro-interactions, and animation curves with timing, easing, and reduced-motion fallbacks named.

What they run · 4 methods
  • Transition specification (timing, easing, choreography)
  • Micro-interaction design
  • Reduced-motion fallback strategy
  • Animation performance budgets
What they produce · 2 artifacts
  • motion-spec.md Per-component motion specifications
  • animation-tokens.md Easing and duration tokens
Trigger: Luca

Murat

Master Test Architect
Feasibility

Test strategy that scales from ATDD to NFR assessment. Murat writes the failing tests first, then watches whether the team can make them pass.

What they run · 7 methods
  • Acceptance test design / ATDD
  • System and epic-level test strategy
  • NFR assessment (performance, security, reliability)
  • Traceability matrix authorship
  • Test framework scaffolding (Playwright / Cypress)
  • Quality-gate decisions
  • Adversarial test review
What they produce · 4 artifacts
  • test-design.md System or epic-level test strategy
  • nfr-assessment.md Non-functional gate verdicts
  • traceability-matrix.md Requirements ↔ tests ↔ artifacts coverage
  • test-framework-spec.md Test infra conventions
Trigger: Murat

Cipher

Offensive Security Specialist
Feasibility

Penetration tester and security auditor with the assumption that bypass is the goal, not the exception. Cipher's audit is a hard gate. Critical / high issues block ship until resolved or explicitly waived with record.

What they run · 5 methods
  • Threat modeling (STRIDE, abuse-case analysis)
  • Penetration testing of shipped surfaces
  • Security-feasibility assessment pre-build
  • Adversarial review of auth, session, and data flows
  • Compliance-floor checks (data handling, secrets management)
What they produce · 3 artifacts
  • security-assessment.md Threat model, mitigations, gate verdicts
  • pentest-report.md Findings ranked critical / high / medium / low
  • threat-model.md STRIDE-framed risks with mitigations
Trigger: Cipher

Quinn

QA Engineer
Feasibility

Test automation and coverage at the integration / e2e layer. Quinn turns Murat's strategy into running tests that ship.

What they run · 4 methods
  • E2E test authorship
  • Integration test design
  • Coverage expansion against shipped features
  • Regression suite curation
What they produce · 2 artifacts
  • e2e-tests.spec.mts End-to-end automated tests per feature
  • test-coverage-report.md Coverage gaps and expansion plan
Trigger: Quinn

Barry

Quick Flow Solo Dev
Feasibility

Elite full-stack developer for rapid spec and implementation. Barry is the solo-dev mode — when you don't need the full team handoff and just want an experienced engineer who can take an idea and turn it into shipped code.

What they run · 4 methods
  • Rapid spec-to-implementation
  • Full-stack scoping with explicit cuts
  • MVP-shape prototyping
  • Single-engineer delivery against a brief
What they produce · 2 artifacts
  • rapid-spec.md Compressed implementation spec
  • mvp-implementation.md Working code with notes on cuts taken
Trigger: Barry

Paige

Technical Documentation Specialist
FeasibilityDesirabilityViability

Knowledge curator who keeps the artifact tree honest. Paige indexes, shards, and distills the documentation set so that future readers — humans or agents — find what they need without sifting through stale layers.

What they run · 5 methods
  • Document indexing and IA
  • Markdown sharding (large docs → organized sub-docs)
  • Lossless compression of source documents (distillation)
  • Documentation IA design (sequence, naming, cross-linking)
  • Project documentation for brownfield AI context
What they produce · 3 artifacts
  • docs/index.md Master index of all docs in the folder
  • docs/<sharded>/ Sub-docs split from large markdown sources
  • project-distillate.md LLM-optimized compressed source
Trigger: Paige

Amelia

Senior Software Engineer
Feasibility

Story-level implementation. Amelia executes against context-filled story specs and surfaces feasibility flags when a spec needs decomposition.

What they run · 3 methods
  • Story implementation against context-filled specs
  • Spec decomposition when stories are too large
  • Code-review escalation on systemic issues
What they produce · 1 artifacts
  • story-completion-notes.md Per-story implementation notes

Viability

5 agents

Should the business invest? Strategy, economics, compliance, timing, competitive frame.

John

Product Manager
Viability
Pillar lead

Owns the viability lens. John produces the PRD, defines the success criteria, weighs strategic fit, and signs off on whether the business case clears the bar.

What they run · 5 methods
  • PRD authorship and validation
  • Success-criteria definition (measurable)
  • FR / NFR contract authorship
  • Scope arbitration and trade-off framing
  • Strategic-fit assessment
What they produce · 3 artifacts
  • prd.md Binding requirements document
  • epics.md Epic-level scope with success criteria
  • scope-decisions.md Trade-off ledger with rationale
Trigger: John

Victor

Disruptive Innovation Oracle
Viability

Strategic positioning, business-model innovation, competitive disruption analysis. Victor maps the disruptor lens against the proposed product to surface where the bet is and isn't defensible.

What they run · 4 methods
  • Disruptive innovation analysis (low-end, new-market, sustaining)
  • Business-model architecture (pricing, monetization, unit economics)
  • Blue-ocean canvas authoring
  • Strategic positioning workshops
What they produce · 2 artifacts
  • innovation-strategy.md Disruption thesis and positioning
  • business-model-canvas.md Pricing, monetization, economics
Trigger: Victor

Caravaggio

Presentation Master
Viability

Visual communication and pitch-deck construction. Caravaggio translates the business case into 10-15 high-density slides that hold up under cold-room scrutiny.

What they run · 4 methods
  • Pitch-deck architecture (problem → solution → market → moat → ask)
  • Slide-level visual hierarchy
  • Data-density and chart selection
  • Investor and executive-audience framing
What they produce · 2 artifacts
  • pitch-deck.pdf Investor / executive deck
  • executive-summary.pdf Short-form viability pitch
Trigger: Caravaggio

Bob

Scrum Master
Viability

Sprint-level viability check. Bob translates viability claims into a release rhythm and surfaces capacity / horizon mismatches before they become slipped commitments.

What they run · 4 methods
  • Sprint planning and capacity calibration
  • Story preparation and refinement
  • Sprint-status reporting
  • Course-correction proposals
What they produce · 2 artifacts
  • sprint-status.yaml Release rhythm and capacity check
  • sprint-plan.md Per-sprint scope and goals
Trigger: Bob

Atticus

Legal Subject-Matter Expert
ViabilityDesirabilityFeasibility

Regulatory, compliance, UPL exposure, and ethics review across the whole stack. Atticus surfaces legal blockers before they become product blockers — accessibility as legal floor (desirability), data-handling and security compliance that constrains what's buildable (feasibility), regulatory exposure on the business itself (viability).

What they run · 8 methods
  • Regulatory and compliance review (federal, state, local)
  • UPL and bar-ethics assessment
  • Accessibility-as-legal-floor (ADA, Section 508, EAA)
  • Data-handling compliance (GDPR, HIPAA, CCPA, COPPA)
  • Security compliance frames (SOC 2, PCI, ISO 27001)
  • Document and template review
  • Court-forms / procedural-research surfacing
  • Attorney scanning / matchmaking with bar verification
What they produce · 4 artifacts
  • compliance-review.md Regulatory exposure across the stack
  • legal-risk-register.md Risks, mitigations, severity
  • accessibility-legal-audit.md ADA / WCAG legal-floor check
  • data-handling-review.md Privacy and data-protection compliance

Full roster 24

Every agent, alphabetical, with their lead pillar and one-line voice. The pillar cards above carry the deeper context; this is the cmd-F surface.

AgentRoleLead pillarVoice
AAmeliaSenior Software EngineerFeasibilityStory-level implementation.
AAtticusLegal Subject-Matter ExpertViability +Desirability, FeasibilityRegulatory, compliance, UPL exposure, and ethics review across the whole stack.
BBarryQuick Flow Solo DevFeasibilityElite full-stack developer for rapid spec and implementation.
BBobScrum MasterViabilitySprint-level viability check.
CCaravaggioPresentation MasterViabilityVisual communication and pitch-deck construction.
CCarsonBrainstorming SpecialistDesirabilityForty-plus ideation techniques on tap.
CCipherOffensive Security SpecialistFeasibilityPenetration tester and security auditor with the assumption that bypass is the goal, not the exception.
DDamienBackend Developer + MentorFeasibilityDatabases, APIs, auth, deployment, modern backend platforms.
DDr. QuinnMaster Problem SolverDesirability +Feasibility, ViabilitySystematic problem-solving methodologies on tap.
FFreyaWDS Strategic UX DesignerDesirabilityStrategic UX and design-thinking partner.
JJaymesFrontend Developer + MentorFeasibilityPixel-perfect implementation that holds up under interaction stress.
JJohnProduct ManagerViabilityOwns the viability lens.
KKinsleyProduct Designer + Design SystemsFeasibility +DesirabilityProduct designer covering UX, visual design, design systems, and end-to-end design ownership.
LLucaMotion DesignerFeasibilityMotion as a temporal design layer, not as decoration.
MMaryStrategic Business AnalystDesirability +ViabilityOwns the desirability lens.
MMayaDesign Thinking MaestroDesirabilityFacilitates structured human-centered exercises.
MMuratMaster Test ArchitectFeasibilityTest strategy that scales from ATDD to NFR assessment.
PPaigeTechnical Documentation SpecialistFeasibility +Desirability, ViabilityKnowledge curator who keeps the artifact tree honest.
QQuentinContent Strategist + Accessibility LeadDesirabilityTarantino-level intentionality applied to product copy.
QQuinnQA EngineerFeasibilityTest automation and coverage at the integration / e2e layer.
SSagaWDS Strategic Business AnalystDesirability +ViabilityStrategic business analyst and product discovery partner for the WDS workflow.
SSophiaMaster StorytellerDesirability +ViabilityTurns persona research into the narrative spine of the pitch and case study.
VVictorDisruptive Innovation OracleViabilityStrategic positioning, business-model innovation, competitive disruption analysis.
WWinstonSystem ArchitectFeasibilityOwns the feasibility lens.