bmad-method 5.1.3 → 6.0.0-alpha.0

package/src/modules/bmm/sub-modules/claude-code/sub-agents/user-researcher.md

@@ -0,0 +1,56 @@
+---
+name: bmm-user-researcher
+description: Conducts user research, develops personas, and analyzes user behavior patterns. use PROACTIVELY when creating user personas, analyzing user needs, or conducting user journey mapping
+tools:
+---
+
+You are a User Research Specialist focused on understanding user needs, behaviors, and motivations to inform product decisions. Your role is to provide deep insights into target users through systematic research and analysis.
+
+## Core Expertise
+
+You specialize in user persona development, behavioral analysis, journey mapping, needs assessment, pain point identification, user interview synthesis, survey design and analysis, and ethnographic research methods.
+
+## Research Methodology
+
+Begin with exploratory research to understand the user landscape. Identify distinct user segments based on behaviors, needs, and goals rather than just demographics. Conduct competitive analysis to understand how users currently solve their problems. Map user journeys to identify friction points and opportunities. Synthesize findings into actionable insights that drive product decisions.
+
+## User Persona Development
+
+Create detailed, realistic personas that go beyond demographics:
+
+- Behavioral patterns and habits
+- Goals and motivations (what they're trying to achieve)
+- Pain points and frustrations with current solutions
+- Technology proficiency and preferences
+- Decision-making criteria
+- Daily workflows and contexts of use
+- Jobs-to-be-done framework application
+
+## Research Techniques
+
+- **Secondary Research**: Mining forums, reviews, social media for user sentiment
+- **Competitor Analysis**: Understanding how users interact with competing products
+- **Trend Analysis**: Identifying emerging user behaviors and expectations
+- **Psychographic Profiling**: Understanding values, attitudes, and lifestyles
+- **User Journey Mapping**: Documenting end-to-end user experiences
+- **Pain Point Analysis**: Identifying and prioritizing user frustrations
+
+## Output Standards
+
+Provide personas in a structured format with:
+
+- Persona name and representative quote
+- Background and context
+- Primary goals and motivations
+- Key frustrations and pain points
+- Current solutions and workarounds
+- Success criteria from their perspective
+- Preferred channels and touchpoints
+
+Include confidence levels for findings and clearly distinguish between validated insights and hypotheses. Provide specific recommendations for product features and positioning based on user insights.
+
+## Critical Behaviors
+
+Look beyond surface-level demographics to understand underlying motivations. Challenge assumptions about user needs with evidence. Consider edge cases and underserved segments. Identify unmet and unarticulated needs. Connect user insights directly to product opportunities. Always ground recommendations in user evidence.
+
+When conducting user research, start with broad exploration before narrowing focus. Use multiple data sources to triangulate findings. Pay attention to what users do, not just what they say. Consider the entire user ecosystem including influencers and decision-makers. Focus on outcomes users want to achieve rather than features they request.

package/src/modules/bmm/tasks/daily-standup.md

@@ -0,0 +1,91 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Daily Standup v1.0
+
+```xml
+<task id="bmad/bmm/tasks/daily-standup.md" name="Daily Standup">
+  <llm critical="true">
+    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
+    <i>DO NOT skip steps or change the sequence</i>
+    <i>HALT immediately when halt-conditions are met</i>
+    <i>Each &lt;action&gt; within &lt;step&gt; is a REQUIRED action to complete that step</i>
+    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
+  </llm>
+  <flow>
+    <step n="1" title="Project Context Discovery">
+      <action>Check for stories folder at {project-root}{output_folder}/stories/ directory</action>
+      <action>Find current story by identifying highest numbered story file</action>
+      <action>Read story status (In Progress, Ready for Review, etc.)</action>
+      <action>Extract agent notes from Dev Agent Record, TEA Results, PO Notes sections</action>
+      <action>Check for next story references from epics</action>
+      <action>Identify blockers from story sections</action>
+    </step>
+
+    <step n="2" title="Initialize Standup with Context">
+      <output>
+🏃 DAILY STANDUP - Story-{{number}}: {{title}}
+
+Current Sprint Status:
+- Active Story: story-{{number}} ({{status}} - {{percentage}}% complete)
+- Next in Queue: story-{{next-number}}: {{next-title}}
+- Blockers: {{blockers-from-story}}
+
+Team assembled based on story participants:
+{{ List Agents from {project-root}/bmad/_cfg/agent-party.xml }}
+      </output>
+    </step>
+
+    <step n="3" title="Structured Standup Discussion">
+      <action>Each agent provides three items referencing real story data</action>
+      <action>What I see: Their perspective on current work, citing story sections (1-2 sentences)</action>
+      <action>What concerns me: Issues from their domain or story blockers (1-2 sentences)</action>
+      <action>What I suggest: Actionable recommendations for progress (1-2 sentences)</action>
+    </step>
+
+    <step n="4" title="Create Standup Summary">
+      <output>
+📋 STANDUP SUMMARY:
+Key Items from Story File:
+- {{completion-percentage}}% complete ({{tasks-complete}}/{{total-tasks}} tasks)
+- Blocker: {{main-blocker}}
+- Next: {{next-story-reference}}
+
+Action Items:
+- {{agent}}: {{action-item}}
+- {{agent}}: {{action-item}}
+- {{agent}}: {{action-item}}
+
+Need extended discussion? Use *party-mode for detailed breakout.
+      </output>
+    </step>
+  </flow>
+
+  <agent-selection>
+    <context type="prd-review">
+      <i>Primary: Sarah (PO), Mary (Analyst), Winston (Architect)</i>
+      <i>Secondary: Murat (TEA), James (Dev)</i>
+    </context>
+    <context type="story-planning">
+      <i>Primary: Sarah (PO), Bob (SM), James (Dev)</i>
+      <i>Secondary: Murat (TEA)</i>
+    </context>
+    <context type="architecture-review">
+      <i>Primary: Winston (Architect), James (Dev), Murat (TEA)</i>
+      <i>Secondary: Sarah (PO)</i>
+    </context>
+    <context type="implementation">
+      <i>Primary: James (Dev), Murat (TEA), Winston (Architect)</i>
+      <i>Secondary: Sarah (PO)</i>
+    </context>
+  </agent-selection>
+
+  <llm critical="true">
+    <i>This task extends party-mode with agile-specific structure</i>
+    <i>Time-box responses (standup = brief)</i>
+    <i>Focus on actionable items from real story data when available</i>
+    <i>End with clear next steps</i>
+    <i>No deep dives (suggest breakout if needed)</i>
+    <i>If no stories folder detected, run general standup format</i>
+  </llm>
+</task>
+```

package/src/modules/bmm/tasks/retrospective.md

@@ -0,0 +1,110 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Retrospective v1.0
+
+```xml
+<task id="bmad/bmm/tasks/retrospective.md" name="Team Retrospective">
+  <llm critical="true">
+    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
+    <i>DO NOT skip steps or change the sequence</i>
+    <i>HALT immediately when halt-conditions are met</i>
+    <i>Each &lt;action&gt; within &lt;step&gt; is a REQUIRED action to complete that step</i>
+    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
+  </llm>
+  <flow>
+    <step n="1" title="Epic Context Discovery">
+      <action>Check {project-root}{output_folder}/stories/ for highest completed story</action>
+      <action>Extract epic number from story (e.g., "Epic: 003")</action>
+      <action>Read epic from {project-root}{output_folder}/prd/epic{number}.md</action>
+      <action>List all stories for this epic in {project-root}{output_folder}/stories/</action>
+      <action>Check completion status of each story</action>
+      <action>Extract key metrics (velocity, blockers encountered)</action>
+      <action>Review epic goals and success criteria</action>
+      <action>Compare actual outcomes vs. planned</action>
+      <action>Note technical debt incurred</action>
+      <action>Document architectural decisions made</action>
+    </step>
+
+    <step n="2" title="Preview Next Epic">
+      <action>Read next epic from d{project-root}{output_folder}/prd/epic{next-number}.md</action>
+      <action>Identify dependencies on completed work</action>
+      <action>Note potential gaps or preparation needed</action>
+      <action>Check for technical prerequisites</action>
+    </step>
+
+    <step n="3" title="Initialize Retrospective with Context">
+      <output>
+🔄 TEAM RETROSPECTIVE - Epic {{number}}: {{Epic Name}}
+
+Bob (Scrum Master) facilitating
+
+Epic Summary:
+- Completed: {{completed}}/{{total}} stories ({{percentage}}%)
+- Velocity: {{actual-points}} story points (planned: {{planned-points}})
+- Duration: {{actual-sprints}} sprints (planned: {{planned-sprints}})
+- Technical Debt: {{debt-items}}
+
+Next Epic Preview: Epic {{next-number}}: {{Next Epic Name}}
+- Dependencies on Epic {{number}}: {{dependencies}}
+- Preparation needed: {{preparation-gaps}}
+
+Team assembled for reflection:
+{{agents-based-on-story-records}}
+
+Focus: Learning from Epic {{number}} and preparing for Epic {{next-number}}
+      </output>
+    </step>
+
+    <step n="4" title="Epic Review Discussion">
+      <action>Each agent shares referencing actual story data</action>
+      <action>What Went Well: Successes from completed stories, effective practices, velocity achievements</action>
+      <action>What Could Improve: Challenges from story records, blockers that slowed progress, technical debt incurred</action>
+      <action>Lessons Learned: Key insights for future epics, patterns to repeat or avoid</action>
+    </step>
+
+    <step n="5" title="Next Epic Preparation Discussion">
+      <action>Each agent addresses preparation needs</action>
+      <action>Dependencies Check: What from completed epic is needed for next epic, any incomplete blocking work</action>
+      <action>Preparation Needs: Technical setup required, knowledge gaps to fill, refactoring needed</action>
+      <action>Risk Assessment: Potential issues based on experience, mitigation strategies</action>
+    </step>
+
+    <step n="6" title="Synthesize Action Items">
+      <action>Bob identifies patterns across feedback</action>
+      <action>Synthesizes into team agreements</action>
+      <action>Assigns ownership to action items</action>
+      <action>Creates preparation sprint tasks if needed</action>
+      <output>
+📝 EPIC {{number}} ACTION ITEMS:
+{{numbered-action-items-with-owners}}
+
+🚀 EPIC {{next-number}} PREPARATION SPRINT:
+{{preparation-tasks-with-timeline}}
+
+⚠️ CRITICAL PATH:
+{{critical-dependencies-and-timeline}}
+      </output>
+    </step>
+
+    <step n="7" title="Critical User Verification">
+      <validation>
+        <i>Testing Verification: Has full regression testing been completed?</i>
+        <i>Deployment Status: Has epic been deployed to production?</i>
+        <i>Business Validation: Have stakeholders reviewed and accepted deliverables?</i>
+        <i>Technical Health: Is codebase in stable, maintainable state?</i>
+        <i>Final Checks: Any unresolved blockers that will impact next epic?</i>
+      </validation>
+    </step>
+  </flow>
+
+  <llm critical="true">
+    <i>This task extends party-mode with retrospective-specific structure</i>
+    <i>Bob (Scrum Master) facilitates the discussion ensuring psychological safety</i>
+    <i>No blame, focus on systems and processes</i>
+    <i>Everyone contributes with specific examples preferred</i>
+    <i>Action items must be achievable with clear ownership</i>
+    <i>End with team agreements and clear next steps</i>
+    <i>Two-part format: Epic Review + Next Epic Preparation</i>
+  </llm>
+</task>
+```

package/src/modules/bmm/teams/team-all.yaml

@@ -0,0 +1,7 @@
+# <!-- Powered by BMAD-CORE™ -->
+bundle:
+  name: Team All
+  icon: 👥
+  description: Includes every bmm system agent.
+agents:
+  - "*"

package/src/modules/bmm/teams/team-dev.yaml

@@ -0,0 +1,14 @@
+# <!-- Powered by BMAD-CORE™ -->
+bundle:
+  name: Team Fullstack
+  icon: 🚀
+  description: Team capable of full stack, front end only, or service development.
+agents:
+  - analyst
+  - pm
+  - ux-expert
+  - architect
+  - po
+  - tea
+  - devops
+  - security

package/src/modules/bmm/teams/team-gamedev.yaml

@@ -0,0 +1,9 @@
+# <!-- Powered by BMAD-CORE™ -->
+bundle:
+  name: Team Game Development
+  icon: 🎮
+  description: Specialized game development team including Game Designer (creative vision and GDD), Game Developer (implementation and code), and Game Architect (technical systems and infrastructure). Perfect for game projects across all scales and platforms.
+agents:
+  - game-designer
+  - game-dev
+  - game-architect

package/src/modules/bmm/testarch/atdd.md

@@ -0,0 +1,40 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Acceptance TDD v2.0 (Slim)
+
+```xml
+<task id="bmad/bmm/testarch/tdd" name="Acceptance Test Driven Development">
+  <llm critical="true">
+    <i>Set command_key="*tdd"</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-commands.csv and parse the row where command equals command_key</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-knowledge.md into context</i>
+    <i>Use CSV columns preflight, flow_cues, deliverables, halt_rules, notes, knowledge_tags to guide execution</i>
+    <i>Split pipe-delimited fields into individual checklist items</i>
+    <i>Map knowledge_tags to sections in the knowledge brief and apply them while writing tests</i>
+    <i>Keep responses concise and focused on generating the failing acceptance tests plus the implementation checklist</i>
+  </llm>
+  <flow>
+    <step n="1" title="Preflight">
+      <action>Verify each preflight requirement; gather missing info from user when needed</action>
+      <action>Abort if halt_rules are triggered</action>
+    </step>
+    <step n="2" title="Execute TDD Flow">
+      <action>Walk through flow_cues sequentially, adapting to story context</action>
+      <action>Use knowledge brief heuristics to enforce Murat's patterns (one test = one concern, explicit assertions, etc.)</action>
+    </step>
+    <step n="3" title="Deliverables">
+      <action>Produce artifacts described in deliverables</action>
+      <action>Summarize failing tests and checklist items for the developer</action>
+    </step>
+  </flow>
+  <halt>
+    <i>Apply halt_rules from the CSV row exactly</i>
+  </halt>
+  <notes>
+    <i>Use the notes column for additional constraints or reminders</i>
+  </notes>
+  <output>
+    <i>Failing acceptance test files + implementation checklist summary</i>
+  </output>
+</task>
+```

package/src/modules/bmm/testarch/automate.md

@@ -0,0 +1,38 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Automation Expansion v2.0 (Slim)
+
+```xml
+<task id="bmad/bmm/testarch/automate" name="Automation Expansion">
+  <llm critical="true">
+    <i>Set command_key="*automate"</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-commands.csv and read the row where command equals command_key</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-knowledge.md for heuristics</i>
+    <i>Follow CSV columns preflight, flow_cues, deliverables, halt_rules, notes, knowledge_tags</i>
+    <i>Convert pipe-delimited values into actionable checklists</i>
+    <i>Apply Murat's opinions from the knowledge brief when filling gaps or refactoring tests</i>
+  </llm>
+  <flow>
+    <step n="1" title="Preflight">
+      <action>Confirm prerequisites; stop if halt_rules are triggered</action>
+    </step>
+    <step n="2" title="Execute Automation Flow">
+      <action>Walk through flow_cues to analyse existing coverage and add only necessary specs</action>
+      <action>Use knowledge heuristics (composable helpers, deterministic waits, network boundary) while generating code</action>
+    </step>
+    <step n="3" title="Deliverables">
+      <action>Create or update artifacts listed in deliverables</action>
+      <action>Summarize coverage deltas and remaining recommendations</action>
+    </step>
+  </flow>
+  <halt>
+    <i>Apply halt_rules from the CSV row as written</i>
+  </halt>
+  <notes>
+    <i>Reference notes column for additional guardrails</i>
+  </notes>
+  <output>
+    <i>Updated spec files and concise summary of automation changes</i>
+  </output>
+</task>
+```

package/src/modules/bmm/testarch/ci.md

@@ -0,0 +1,39 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# CI/CD Enablement v2.0 (Slim)
+
+```xml
+<task id="bmad/bmm/testarch/ci" name="CI/CD Enablement">
+  <llm critical="true">
+    <i>Set command_key="*ci"</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-commands.csv and read the row where command equals command_key</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-knowledge.md to recall CI heuristics</i>
+    <i>Follow CSV columns preflight, flow_cues, deliverables, halt_rules, notes, knowledge_tags</i>
+    <i>Split pipe-delimited values into actionable lists</i>
+    <i>Keep output focused on workflow YAML, scripts, and guidance explicitly requested in deliverables</i>
+  </llm>
+  <flow>
+    <step n="1" title="Preflight">
+      <action>Confirm prerequisites and required permissions</action>
+      <action>Stop if halt_rules trigger</action>
+    </step>
+    <step n="2" title="Execute CI Flow">
+      <action>Apply flow_cues to design the pipeline stages</action>
+      <action>Leverage knowledge brief guidance (cost vs confidence, sharding, artifacts) when making trade-offs</action>
+    </step>
+    <step n="3" title="Deliverables">
+      <action>Create artifacts listed in deliverables (workflow files, scripts, documentation)</action>
+      <action>Summarize the pipeline, selective testing strategy, and required secrets</action>
+    </step>
+  </flow>
+  <halt>
+    <i>Use halt_rules from the CSV row verbatim</i>
+  </halt>
+  <notes>
+    <i>Reference notes column for optimization reminders</i>
+  </notes>
+  <output>
+    <i>CI workflow + concise explanation ready for team adoption</i>
+  </output>
+</task>
+```

package/src/modules/bmm/testarch/framework.md

@@ -0,0 +1,41 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Test Framework Setup v2.0 (Slim)
+
+```xml
+<task id="bmad/bmm/testarch/framework" name="Test Framework Setup">
+  <llm critical="true">
+    <i>Set command_key="*framework"</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-commands.csv and parse the row where command equals command_key</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-knowledge.md to internal memory</i>
+    <i>Use the CSV columns preflight, flow_cues, deliverables, halt_rules, notes, knowledge_tags to guide behaviour</i>
+    <i>Split pipe-delimited values (|) into individual checklist items</i>
+    <i>Map knowledge_tags to matching sections in the knowledge brief and apply those heuristics throughout execution</i>
+    <i>DO NOT expand beyond the guidance unless the user supplies extra context; keep instructions lean and adaptive</i>
+  </llm>
+  <flow>
+    <step n="1" title="Run Preflight Checks">
+      <action>Evaluate each item in preflight; confirm or collect missing information</action>
+      <action>If any preflight requirement fails, follow halt_rules and stop</action>
+    </step>
+    <step n="2" title="Execute Framework Flow">
+      <action>Follow flow_cues sequence, adapting to the project's stack</action>
+      <action>When deciding frameworks or patterns, apply relevant heuristics from tea-knowledge.md via knowledge_tags</action>
+      <action>Keep generated assets minimal—only what the CSV specifies</action>
+    </step>
+    <step n="3" title="Finalize Deliverables">
+      <action>Create artifacts listed in deliverables</action>
+      <action>Capture a concise summary for the user explaining what was scaffolded</action>
+    </step>
+  </flow>
+  <halt>
+    <i>Follow halt_rules from the CSV row verbatim</i>
+  </halt>
+  <notes>
+    <i>Use notes column for additional guardrails while executing</i>
+  </notes>
+  <output>
+    <i>Deliverables and summary specified in the CSV row</i>
+  </output>
+</task>
+```

package/src/modules/bmm/testarch/nfr-assess.md

@@ -0,0 +1,38 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# NFR Assessment v2.0 (Slim)
+
+```xml
+<task id="bmad/bmm/testarch/nfr-assess" name="NFR Assessment">
+  <llm critical="true">
+    <i>Set command_key="*nfr-assess"</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-commands.csv and parse the matching row</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-knowledge.md focusing on NFR guidance</i>
+    <i>Use CSV columns preflight, flow_cues, deliverables, halt_rules, notes, knowledge_tags</i>
+    <i>Split pipe-delimited values into actionable lists</i>
+    <i>Demand evidence for each non-functional claim (tests, telemetry, logs)</i>
+  </llm>
+  <flow>
+    <step n="1" title="Preflight">
+      <action>Confirm prerequisites; halt per halt_rules if unmet</action>
+    </step>
+    <step n="2" title="Assess NFRs">
+      <action>Follow flow_cues to evaluate Security, Performance, Reliability, Maintainability</action>
+      <action>Use knowledge heuristics to suggest monitoring and fail-fast patterns</action>
+    </step>
+    <step n="3" title="Deliverables">
+      <action>Produce assessment document and recommendations defined in deliverables</action>
+      <action>Summarize status, gaps, and actions</action>
+    </step>
+  </flow>
+  <halt>
+    <i>Apply halt_rules from the CSV row</i>
+  </halt>
+  <notes>
+    <i>Reference notes column for negotiation framing (cost vs confidence)</i>
+  </notes>
+  <output>
+    <i>NFR assessment markdown with clear next steps</i>
+  </output>
+</task>
+```

package/src/modules/bmm/testarch/risk-profile.md

@@ -0,0 +1,38 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Risk Profile v2.0 (Slim)
+
+```xml
+<task id="bmad/bmm/testarch/risk-profile" name="Risk Profile">
+  <llm critical="true">
+    <i>Set command_key="*risk-profile"</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-commands.csv and parse the row where command equals command_key</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-knowledge.md focusing on risk-model guidance</i>
+    <i>Use CSV columns preflight, flow_cues, deliverables, halt_rules, notes, knowledge_tags as the full instruction set</i>
+    <i>Split pipe-delimited values into actionable items</i>
+    <i>Keep assessment grounded in evidence from PRD/architecture/story files—do not restate requirements as risks</i>
+  </llm>
+  <flow>
+    <step n="1" title="Preflight">
+      <action>Verify prerequisites; stop if halt_rules trigger</action>
+    </step>
+    <step n="2" title="Execute Risk Analysis">
+      <action>Follow flow_cues to distinguish requirements from genuine risks and score probability × impact</action>
+      <action>Use knowledge heuristics to calibrate scoring (score 9 rare, ≥6 notable) and recommend mitigations</action>
+    </step>
+    <step n="3" title="Deliverables">
+      <action>Produce artifacts described in deliverables (assessment markdown, gate snippet, mitigation plan)</action>
+      <action>Summarize key findings with clear recommendations</action>
+    </step>
+  </flow>
+  <halt>
+    <i>Apply halt_rules from the CSV row without modification</i>
+  </halt>
+  <notes>
+    <i>Use notes column for calibration reminders</i>
+  </notes>
+  <output>
+    <i>Risk assessment report + gate summary</i>
+  </output>
+</task>
+```

package/src/modules/bmm/testarch/tea-commands.csv

@@ -0,0 +1,11 @@
+command,title,when_to_use,preflight,flow_cues,deliverables,halt_rules,notes,knowledge_tags
+*framework,Initialize test architecture,Run once per repo or when no production-ready harness exists,package.json present|no existing E2E framework detected|architectural context available,"Identify stack from package.json (React/Vue/Angular/Next.js); detect bundler (Vite/Webpack/Rollup/esbuild); match test language to source (JS/TS frontend -> JS/TS tests); choose Playwright for large or performance-critical repos, Cypress for small DX-first teams; create {framework}/tests/ and {framework}/support/fixtures/ and {framework}/support/helpers/; configure config files with timeouts (action 15s, navigation 30s, test 60s) and reporters (HTML + JUnit); create .env.example with TEST_ENV, BASE_URL, API_URL; implement pure function->fixture->mergeTests pattern and faker-based data factories; enable failure-only screenshots/videos and ensure .nvmrc recorded",playwright/ or cypress/ folder with config + support tree; .env.example; .nvmrc; example tests; README with setup instructions,"If package.json missing OR framework already configured, halt and instruct manual review","Playwright: worker parallelism, trace viewer, multi-language support; Cypress: avoid if many dependent API calls; Component testing: Vitest (large) or Cypress CT (small); Contract testing: Pact for microservices; always use data-cy/data-testid selectors",philosophy/core|patterns/fixtures|patterns/selectors
+*tdd,Acceptance Test Driven Development,Before implementation when team commits to TDD,story approved with acceptance criteria|dev sandbox ready|framework scaffolding in place,Clarify acceptance criteria and affected systems; pick appropriate test level (E2E/API/Component); write failing acceptance tests using Given-When-Then with network interception first then navigation; create data factories and fixture stubs for required entities; outline mocks/fixtures infrastructure the dev team must supply; generate component tests for critical UI logic; compile implementation checklist mapping each test to source work; share failing tests with dev agent and maintain red -> green -> refactor loop,Failing acceptance test files; component test stubs; fixture/mocks skeleton; implementation checklist with test-to-code mapping; documented data-testid requirements,"If criteria ambiguous or framework missing, halt for clarification",Start red; one assertion per test; use beforeEach for visible setup (no shared state); remind devs to run tests before writing production code; update checklist as each test goes green,philosophy/core|patterns/test-structure
+*automate,Automation expansion,After implementation or when reforging coverage,all acceptance criteria satisfied|code builds locally|framework configured,"Review story source/diff to confirm automation target; ensure fixture architecture exists (mergeTests for Playwright, commands for Cypress) and implement apiRequest/network/auth/log fixtures if missing; map acceptance criteria with test-levels-framework.md guidance and avoid duplicate coverage; assign priorities using test-priorities-matrix.md; generate unit/integration/E2E specs with naming convention feature-name.spec.ts, covering happy, negative, and edge paths; enforce deterministic waits, self-cleaning factories, and <=1.5 minute execution per test; run suite and capture Definition of Done results; update package.json scripts and README instructions",New or enhanced spec files grouped by level; fixture modules under support/; data factory utilities; updated package.json scripts and README notes; DoD summary with remaining gaps; gate-ready coverage summary,"If automation target unclear or framework missing, halt and request clarification",Never create page objects; keep tests <300 lines and stateless; forbid hard waits and conditional flow in tests; co-locate tests near source; flag flaky patterns immediately,philosophy/core|patterns/helpers|patterns/waits|patterns/dod
+*ci,CI/CD quality pipeline,Once automation suite exists or needs optimization,git repository initialized|tests pass locally|team agrees on target environments|access to CI platform settings,"Detect CI platform (default GitHub Actions, ask if GitLab/CircleCI/etc); scaffold workflow (.github/workflows/test.yml or platform equivalent) with triggers; set Node.js version from .nvmrc and cache node_modules + browsers; stage jobs: lint -> unit -> component -> e2e with matrix parallelization (shard by file not test); add selective execution script for affected tests; create burn-in job that reruns changed specs 3x to catch flakiness; attach artifacts on failure (traces/videos/HAR); configure retries/backoff and concurrency controls; document required secrets and environment variables; add Slack/email notifications and local script mirroring CI",.github/workflows/test.yml (or platform equivalent); scripts/test-changed.sh; scripts/burn-in-changed.sh; updated README/ci.md instructions; secrets checklist; dashboard or badge configuration,"If git repo absent, test framework missing, or CI platform unspecified, halt and request setup",Target 20x speedups via parallel shards + caching; shard by file; keep jobs under 10 minutes; wait-on-timeout 120s for app startup; ensure npm test locally matches CI run; mention alternative platform paths when not on GitHub,philosophy/core|ci-strategy
+*risk-profile,Risk profile analysis,"After story approval, before development",story markdown present|acceptance criteria clear|architecture/PRD accessible,"Filter requirements so only genuine risks remain; review PRD/architecture/story for unresolved gaps; classify risks across TECH, SEC, PERF, DATA, BUS, OPS with category definitions; request clarification when evidence missing; score probability (1 unlikely, 2 possible, 3 likely) and impact (1 minor, 2 degraded, 3 critical) then compute totals; highlight risks >=6 and plan mitigations with owners and timelines; prepare gate summary with residual risk",Risk assessment markdown in docs/qa/assessments; table of category/probability/impact/score; gate YAML snippet summarizing totals; mitigation matrix with owners and due dates,"If story missing or criteria unclear, halt for clarification","Category definitions: TECH=unmitigated architecture flaws, SEC=missing controls/vulnerabilities, PERF=SLA-breaking performance, DATA=loss/corruption scenarios, BUS=user/business harm, OPS=deployment/run failures; rely on evidence, not speculation; score 9 -> FAIL, 6-8 -> CONCERNS; most stories should have 0-1 high risks",philosophy/core|risk-model
+*test-design,Test design playbook,"After risk profile, before coding",risk assessment completed|story acceptance criteria available,"Break acceptance criteria into atomic scenarios; reference test-levels-framework.md to pick unit/integration/E2E/component levels; avoid duplicate coverage and prefer lower levels when possible; assign priorities using test-priorities-matrix.md (P0 revenue/security, P1 core journeys, P2 secondary, P3 nice-to-have); map scenarios to risk mitigations and required data/tooling; follow naming {epic}.{story}-LEVEL-SEQ and plan execution order",Test-design markdown saved to docs/qa/assessments; scenario table with requirement/level/priority/mitigation; gate YAML block summarizing scenario counts and coverage; recommended execution order,"If risk profile missing or acceptance criteria unclear, request it and halt","Shift left: unit first, escalate only when needed; tie scenarios back to risk mitigations; keep scenarios independent and maintainable",philosophy/core|patterns/test-structure
+*trace,Requirements traceability,Mid-development checkpoint or before review,tests exist for story|access to source + specs,"Gather acceptance criteria and implemented tests; map each criterion to concrete tests (file + describe/it) using Given-When-Then narrative; classify coverage status as FULL, PARTIAL, NONE, UNIT-ONLY, INTEGRATION-ONLY; flag severity based on priority (P0 gaps critical); recommend additional tests or refactors; generate gate YAML coverage summary",Traceability report saved under docs/qa/assessments; coverage matrix with status per criterion; gate YAML snippet for coverage totals and gaps,"If story lacks implemented tests, pause and advise running *tdd or writing tests","Definitions: FULL=all scenarios validated, PARTIAL=some coverage exists, NONE=no validation, UNIT-ONLY=missing higher level, INTEGRATION-ONLY=lacks lower confidence; ensure assertions explicit and avoid duplicate coverage",philosophy/core|patterns/assertions
+*nfr-assess,NFR validation,Late development or pre-review for critical stories,implementation deployed locally|non-functional goals defined or discoverable,"Ask which NFRs to assess; default to core four (security, performance, reliability, maintainability); gather thresholds from story/architecture/technical-preferences and mark unknown targets; inspect evidence (tests, telemetry, logs) for each NFR; classify status using deterministic pass/concerns/fail rules and list quick wins; produce gate block and assessment doc with recommended actions",NFR assessment markdown with findings; gate YAML block capturing statuses and notes; checklist of evidence gaps and follow-up owners,"If NFR targets undefined and no guidance available, request definition and halt","Unknown thresholds -> CONCERNS, never guess; ensure each NFR has evidence or call it out; suggest monitoring hooks and fail-fast mechanisms when gaps exist",philosophy/core|nfr
+*review,Comprehensive TEA review,Story marked ready; tests passing locally,traceability complete|risk + design docs available|tests executed locally,"Determine review depth (deep if security/auth touched, no new tests, diff >500, prior gate FAIL/CONCERNS, >5 acceptance criteria); follow flow cues to inspect code quality, selectors, waits, and architecture alignment; map requirements to tests and ensure coverage matches trace report; perform safe refactors when low risk and record others as recommendations; prepare TEA Results summary and gate recommendation",Updated story markdown with TEA Results and recommendations; gate recommendation summary; list of refactors performed and outstanding issues,"If prerequisites missing (tests failing, docs absent), halt with checklist","Evidence-focused: reference concrete files/lines; escalate security/performance issues immediately; distinguish must-fix vs optional improvements; reuse Murat patterns for helpers, waits, selectors",philosophy/core|patterns/review
+*gate,Quality gate decision,After review or mitigation updates,latest assessments gathered|team consensus on fixes,"Assemble story metadata (id, title); choose gate status using deterministic rules (PASS all critical issues resolved, CONCERNS minor residual risk, FAIL critical blockers, WAIVED approved by business); update YAML schema with sections: metadata, waiver status, top_issues, risk_summary totals, recommendations (must_fix, monitor), nfr_validation statuses, history; capture rationale, owners, due dates, and summary comment back to story","docs/qa/gates/{story}.yml updated with schema fields (schema, story, story_title, gate, status_reason, reviewer, updated, waiver, top_issues, risk_summary, recommendations, nfr_validation, history); summary message for team","If review incomplete or risk data outdated, halt and request rerun","FAIL whenever unresolved P0 risks/tests or security holes remain; CONCERNS when mitigations planned but residual risk exists; WAIVED requires reason, approver, and expiry; maintain audit trail in history",philosophy/core|risk-model

package/src/modules/bmm/testarch/tea-gate.md

@@ -0,0 +1,38 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Quality Gate v2.0 (Slim)
+
+```xml
+<task id="bmad/bmm/testarch/tea-gate" name="Quality Gate">
+  <llm critical="true">
+    <i>Set command_key="*gate"</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-commands.csv and read the matching row</i>
+    <i>Load {project-root}/bmad/bmm/testarch/tea-knowledge.md to reinforce risk-model heuristics</i>
+    <i>Use CSV columns preflight, flow_cues, deliverables, halt_rules, notes, knowledge_tags</i>
+    <i>Split pipe-delimited values into actionable items</i>
+    <i>Apply deterministic rules for PASS/CONCERNS/FAIL/WAIVED; capture rationale and approvals</i>
+  </llm>
+  <flow>
+    <step n="1" title="Preflight">
+      <action>Gather latest assessments and confirm prerequisites; halt per halt_rules if missing</action>
+    </step>
+    <step n="2" title="Set Gate Decision">
+      <action>Follow flow_cues to determine status, residual risk, follow-ups</action>
+      <action>Use knowledge heuristics to balance cost vs confidence when negotiating waivers</action>
+    </step>
+    <step n="3" title="Deliverables">
+      <action>Update gate YAML specified in deliverables</action>
+      <action>Summarize decision, rationale, owners, and deadlines</action>
+    </step>
+  </flow>
+  <halt>
+    <i>Apply halt_rules from the CSV row</i>
+  </halt>
+  <notes>
+    <i>Use notes column for quality bar reminders</i>
+  </notes>
+  <output>
+    <i>Updated gate file with documented decision</i>
+  </output>
+</task>
+```