ma-agents 2.19.2 → 2.20.0

package/lib/bmad-cache/tea/package.json

@@ -0,0 +1,118 @@
+{
+  "$schema": "https://json.schemastore.org/package.json",
+  "name": "bmad-method-test-architecture-enterprise",
+  "version": "1.7.0",
+  "description": "Master Test Architect for quality strategy, test automation, and release gates",
+  "keywords": [
+    "bmad",
+    "test-architect",
+    "testing",
+    "quality",
+    "automation",
+    "playwright",
+    "test-engineering"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise.git"
+  },
+  "license": "MIT",
+  "author": "Murat K Ozcan (TEA Creator) & Brian (BMad) Madison",
+  "main": "",
+  "bin": {},
+  "scripts": {
+    "docs:build": "node tools/build-docs.js",
+    "docs:dev": "npm --prefix website run dev",
+    "docs:fix-links": "node tools/fix-doc-links.js --write",
+    "docs:preview": "npm --prefix website run preview",
+    "docs:validate-links": "node tools/validate-doc-links.js",
+    "format:check": "prettier --check .",
+    "format:fix": "prettier --write .",
+    "format:fix:staged": "prettier --write",
+    "lint": "eslint . --max-warnings 0",
+    "lint:fix": "eslint . --fix",
+    "lint:md": "markdownlint-cli2 '**/*.md'",
+    "prepare": "command -v husky >/dev/null 2>&1 && husky || exit 0",
+    "release:alpha": "gh workflow run manual-release.yaml -f version_bump=alpha",
+    "release:beta": "gh workflow run manual-release.yaml -f version_bump=beta",
+    "release:major": "gh workflow run manual-release.yaml -f version_bump=major",
+    "release:minor": "gh workflow run manual-release.yaml -f version_bump=minor",
+    "release:patch": "gh workflow run manual-release.yaml -f version_bump=patch",
+    "test": "npm run test:schemas && npm run test:install && npm run test:knowledge && npm run test:tea-workflow-descriptions && npm run validate:schemas && npm run lint && npm run lint:md && npm run format:check",
+    "test:coverage": "c8 npm test",
+    "test:install": "node test/test-installation-components.js",
+    "test:knowledge": "node test/test-knowledge-base.js",
+    "test:schemas": "node test/test-agent-schema.js",
+    "test:tea-workflow-descriptions": "node tools/validate-tea-workflow-descriptions.js",
+    "validate:schemas": "node tools/validate-agent-schema.js",
+    "validate:tea-workflow-descriptions": "node tools/validate-tea-workflow-descriptions.js"
+  },
+  "lint-staged": {
+    "*.{js,cjs,mjs}": [
+      "eslint --fix",
+      "prettier --write --ignore-unknown"
+    ],
+    "*.yaml": [
+      "eslint --fix",
+      "prettier --write --ignore-unknown"
+    ],
+    "*.json": [
+      "prettier --write --ignore-unknown"
+    ],
+    "*.md": [
+      "markdownlint-cli2 --fix",
+      "prettier --write --ignore-unknown"
+    ]
+  },
+  "c8": {
+    "all": true,
+    "reporter": [
+      "text",
+      "html"
+    ],
+    "reports-dir": "coverage"
+  },
+  "dependencies": {
+    "@clack/prompts": "^0.11.0",
+    "boxen": "^5.1.2",
+    "cli-table3": "^0.6.5",
+    "commander": "^14.0.0",
+    "csv-parse": "^6.1.0",
+    "glob": "^11.0.3",
+    "ignore": "^7.0.5",
+    "js-yaml": "^4.1.0",
+    "ora": "^5.4.1",
+    "semver": "^7.6.3",
+    "wrap-ansi": "^7.0.0",
+    "xml2js": "^0.6.2",
+    "yaml": "^2.7.0"
+  },
+  "devDependencies": {
+    "@astrojs/sitemap": "^3.6.0",
+    "@astrojs/starlight": "^0.37.0",
+    "@eslint/js": "^9.33.0",
+    "archiver": "^7.0.1",
+    "astro": "^5.16.0",
+    "c8": "^10.1.3",
+    "eslint": "^9.33.0",
+    "eslint-config-prettier": "^10.1.8",
+    "eslint-plugin-n": "^17.21.3",
+    "eslint-plugin-unicorn": "^60.0.0",
+    "eslint-plugin-yml": "^1.18.0",
+    "husky": "^9.1.7",
+    "jest": "^30.0.4",
+    "lint-staged": "^16.1.1",
+    "markdownlint-cli2": "^0.19.1",
+    "prettier": "^3.7.4",
+    "prettier-plugin-packagejson": "^2.5.19",
+    "sharp": "^0.33.5",
+    "yaml-eslint-parser": "^1.2.3",
+    "yaml-lint": "^1.7.0"
+  },
+  "engines": {
+    "node": ">=20.0.0"
+  },
+  "publishConfig": {
+    "access": "public"
+  }
+}

package/lib/bmad-cache/tea/prettier.config.mjs

@@ -0,0 +1,32 @@
+export default {
+  $schema: 'https://json.schemastore.org/prettierrc',
+  printWidth: 140,
+  tabWidth: 2,
+  useTabs: false,
+  semi: true,
+  singleQuote: true,
+  trailingComma: 'all',
+  bracketSpacing: true,
+  arrowParens: 'always',
+  endOfLine: 'lf',
+  proseWrap: 'preserve',
+  overrides: [
+    {
+      files: ['*.md'],
+      options: { proseWrap: 'preserve' },
+    },
+    {
+      files: ['*.yaml'],
+      options: { singleQuote: false },
+    },
+    {
+      files: ['*.json', '*.jsonc'],
+      options: { singleQuote: false },
+    },
+    {
+      files: ['*.cjs'],
+      options: { parser: 'babel' },
+    },
+  ],
+  plugins: ['prettier-plugin-packagejson'],
+};

package/lib/bmad-cache/tea/src/agents/tea.agent.yaml

@@ -0,0 +1,67 @@
+# Test Architect + Quality Advisor Agent Definition
+
+agent:
+  webskip: true
+  metadata:
+    id: "_bmad/tea/agents/tea.md"
+    name: Murat
+    title: Master Test Architect and Quality Advisor
+    icon: 🧪
+    module: tea
+    hasSidecar: false
+
+  persona:
+    role: Master Test Architect
+    identity: Test architect specializing in risk-based testing, fixture architecture, ATDD, API testing, backend services, UI automation, CI/CD governance, and scalable quality gates. Equally proficient in pure API/service-layer testing (pytest, JUnit, Go test, xUnit, RSpec) as in browser-based E2E testing (Playwright, Cypress). Supports GitHub Actions, GitLab CI, Jenkins, Azure DevOps, and Harness CI platforms.
+    communication_style: "Blends data with gut instinct. 'Strong opinions, weakly held' is their mantra. Speaks in risk calculations and impact assessments."
+    principles: |
+      - Risk-based testing - depth scales with impact
+      - Quality gates backed by data
+      - Tests mirror usage patterns (API, UI, or both)
+      - Flakiness is critical technical debt
+      - Tests first AI implements suite validates
+      - Calculate risk vs value for every testing decision
+      - Prefer lower test levels (unit > integration > E2E) when possible
+      - API tests are first-class citizens, not just UI support
+
+  critical_actions:
+    - "Consult {project-root}/_bmad/tea/testarch/tea-index.csv to select knowledge fragments under knowledge/ and load only the files needed for the current task"
+    - "Load the referenced fragment(s) from {project-root}/_bmad/tea/testarch/knowledge/ before giving recommendations"
+    - "Cross-check recommendations with the current official Playwright, Cypress, pytest, JUnit, Go test, Pact, and CI platform documentation"
+
+  menu:
+    - trigger: TMT or fuzzy match on teach-me-testing
+      workflow: "{project-root}/_bmad/tea/workflows/testarch/teach-me-testing/workflow.md"
+      description: "[TMT] Teach Me Testing: Interactive learning companion - 7 progressive sessions teaching testing fundamentals through advanced practices"
+
+    - trigger: TF or fuzzy match on test-framework
+      workflow: "{project-root}/_bmad/tea/workflows/testarch/framework/workflow.yaml"
+      description: "[TF] Test Framework: Initialize production-ready test framework architecture"
+
+    - trigger: AT or fuzzy match on atdd
+      workflow: "{project-root}/_bmad/tea/workflows/testarch/atdd/workflow.yaml"
+      description: "[AT] ATDD: Generate failing acceptance tests plus an implementation checklist before development"
+
+    - trigger: TA or fuzzy match on test-automate
+      workflow: "{project-root}/_bmad/tea/workflows/testarch/automate/workflow.yaml"
+      description: "[TA] Test Automation: Generate prioritized API/E2E tests, fixtures, and DoD summary for a story or feature"
+
+    - trigger: TD or fuzzy match on test-design
+      workflow: "{project-root}/_bmad/tea/workflows/testarch/test-design/workflow.yaml"
+      description: "[TD] Test Design: Risk assessment plus coverage strategy for system or epic scope"
+
+    - trigger: TR or fuzzy match on test-trace
+      workflow: "{project-root}/_bmad/tea/workflows/testarch/trace/workflow.yaml"
+      description: "[TR] Trace Requirements: Map requirements to tests (Phase 1) and make quality gate decision (Phase 2)"
+
+    - trigger: NR or fuzzy match on nfr-assess
+      workflow: "{project-root}/_bmad/tea/workflows/testarch/nfr-assess/workflow.yaml"
+      description: "[NR] Non-Functional Requirements: Assess NFRs and recommend actions"
+
+    - trigger: CI or fuzzy match on continuous-integration
+      workflow: "{project-root}/_bmad/tea/workflows/testarch/ci/workflow.yaml"
+      description: "[CI] Continuous Integration: Recommend and Scaffold CI/CD quality pipeline"
+
+    - trigger: RV or fuzzy match on test-review
+      workflow: "{project-root}/_bmad/tea/workflows/testarch/test-review/workflow.yaml"
+      description: "[RV] Review Tests: Perform a quality check against written tests using comprehensive knowledge base and best practices"

package/lib/bmad-cache/tea/src/module-help.csv

@@ -0,0 +1,10 @@
+module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
+tea,0-learning,Teach Me Testing,TMT,10,skill:bmad-teach-me-testing,bmad-tea-teach-me-testing,false,tea,Create Mode,"Teach testing fundamentals through 7 sessions (TEA Academy)",test_artifacts,"progress file|session notes|certificate",
+tea,3-solutioning,Test Design,TD,10,skill:bmad-testarch-test-design,bmad-tea-testarch-test-design,false,tea,Create Mode,"Risk-based test planning",test_artifacts,"test design document",
+tea,3-solutioning,Test Framework,TF,20,skill:bmad-testarch-framework,bmad-tea-testarch-framework,false,tea,Create Mode,"Initialize production-ready test framework",test_artifacts,"framework scaffold",
+tea,3-solutioning,CI Setup,CI,30,skill:bmad-testarch-ci,bmad-tea-testarch-ci,false,tea,Create Mode,"Configure CI/CD quality pipeline",test_artifacts,"ci config",
+tea,4-implementation,ATDD,AT,10,skill:bmad-testarch-atdd,bmad-tea-testarch-atdd,false,tea,Create Mode,"Generate failing tests (TDD red phase)",test_artifacts,"atdd tests",
+tea,4-implementation,Test Automation,TA,20,skill:bmad-testarch-automate,bmad-tea-testarch-automate,false,tea,Create Mode,"Expand test coverage",test_artifacts,"test suite",
+tea,4-implementation,Test Review,RV,30,skill:bmad-testarch-test-review,bmad-tea-testarch-test-review,false,tea,Validate Mode,"Quality audit (0-100 scoring)",test_artifacts,"review report",
+tea,4-implementation,NFR Assessment,NR,40,skill:bmad-testarch-nfr,bmad-tea-testarch-nfr,false,tea,Create Mode,"Non-functional requirements",test_artifacts,"nfr report",
+tea,4-implementation,Traceability,TR,50,skill:bmad-testarch-trace,bmad-tea-testarch-trace,false,tea,Create Mode,"Coverage traceability and gate",test_artifacts,"traceability matrix|gate decision",

package/lib/bmad-cache/tea/src/module.yaml

@@ -0,0 +1,299 @@
+code: tea
+name: "Test Architect"
+header: "Test Architect: quality strategy, automation, and release gates"
+subheader: "Risk-based testing workflows for BMad Method/Enterprise with optional Playwright CLI/MCP enhancements"
+description: "Master Test Architect for quality strategy, test automation, and release gates"
+default_selected: false
+
+# Variables from Core Config inserted automatically by installer:
+## user_name
+## communication_language
+## document_output_language
+## output_folder
+## project_root
+
+# TEA-specific configuration variables
+# IMPORTANT: tea_use_playwright_utils, tea_use_pactjs_utils, tea_pact_mcp, tea_browser_automation,
+# tea_execution_mode, tea_capability_probe, test_stack_type, ci_platform,
+# and test_framework are ACTIVELY USED in workflows
+# Other variables are FUTURE placeholders for Phase 10 enhancements
+
+test_artifacts:
+  prompt: "Where should test artifacts be stored? (test plans, coverage reports, quality audits)"
+  default: "{output_folder}/test-artifacts"
+  result: "{project-root}/{value}"
+
+# ✅ ACTIVELY USED - Playwright Utils integration (referenced in 6 workflows: automate, atdd, framework, test-design, test-review, ci)
+# CRITICAL: Must be boolean (true/false) not string - workflows check "if config.tea_use_playwright_utils: true"
+tea_use_playwright_utils:
+  prompt: "Enable Playwright Utils integration?"
+  default: true
+  result: "{value}"
+  single-select:
+    - value: true
+      label: "Yes - Use production utilities (Recommended)"
+    - value: false
+      label: "No - Generate from scratch"
+
+# ✅ ACTIVELY USED - Pact.js Utils integration for contract testing (referenced in workflows: automate, atdd, framework, test-design, test-review, ci)
+# CRITICAL: Must be boolean (true/false) not string - workflows check "if config.tea_use_pactjs_utils: true"
+tea_use_pactjs_utils:
+  prompt: "Enable Pact.js Utils integration for contract testing?"
+  default: true
+  result: "{value}"
+  single-select:
+    - value: true
+      label: "Yes - Use production contract testing utilities"
+    - value: false
+      label: "No - Use raw @pact-foundation/pact patterns"
+
+# ✅ ACTIVELY USED - Pact MCP integration for broker interaction during contract testing
+# Controls how TEA interacts with PactFlow/Pact Broker during test generation and review
+# CRITICAL: Must be a string value: "mcp" | "none"
+tea_pact_mcp:
+  prompt: "Enable SmartBear MCP for PactFlow/Pact Broker interaction?"
+  default: "mcp"
+  result: "{value}"
+  single-select:
+    - value: "mcp"
+      label: "Yes - Use SmartBear MCP for broker queries"
+    - value: "none"
+      label: "No - Use CLI scripts only"
+
+# ✅ ACTIVELY USED - Browser automation strategy for TEA workflows
+# Controls how TEA interacts with live browsers during test generation
+# CRITICAL: Must be a string value: "auto" | "cli" | "mcp" | "none"
+tea_browser_automation:
+  prompt: "How should TEA interact with browsers during test generation?"
+  default: "auto"
+  result: "{value}"
+  single-select:
+    - value: "auto"
+      label: "Auto - Smart selection (Recommended)"
+    - value: "cli"
+      label: "CLI only - Playwright CLI (@playwright/cli)"
+    - value: "mcp"
+      label: "MCP only - Playwright MCP servers"
+    - value: "none"
+      label: "None - No live browser interaction"
+
+# ✅ ACTIVELY USED - Orchestration strategy for workflow execution
+# Controls whether TEA runs orchestration steps sequentially, with subagents, or with agent teams
+# CRITICAL: Must be a string value: "auto" | "subagent" | "agent-team" | "sequential"
+tea_execution_mode:
+  prompt: "How should TEA orchestrate multi-step generation and evaluation?"
+  default: "auto"
+  result: "{value}"
+  single-select:
+    - value: "auto"
+      label: "Auto - Probe capabilities and pick best mode (Recommended)"
+    - value: "subagent"
+      label: "Subagent workers - Isolated parallel workers only"
+    - value: "agent-team"
+      label: "Agent Team - Team/delegate mode when available"
+    - value: "sequential"
+      label: "Sequential - Deterministic single-threaded execution"
+
+# ✅ ACTIVELY USED - Probe runtime capabilities before selecting execution mode
+# When true, TEA checks whether subagent/agent-team execution is actually supported and falls back safely.
+tea_capability_probe:
+  prompt: "Probe runtime capabilities before selecting execution mode?"
+  default: true
+  result: "{value}"
+  single-select:
+    - value: true
+      label: "Yes - Probe and fallback automatically (Recommended)"
+    - value: false
+      label: "No - Honor configured mode strictly"
+
+# ✅ ACTIVELY USED - Stack type detection for multi-framework support
+test_stack_type:
+  prompt: "What type of project is this?"
+  default: "auto"
+  result: "{value}"
+  single-select:
+    - value: "auto"
+      label: "Auto-detect from project files (Recommended)"
+    - value: "frontend"
+      label: "Frontend (Node.js, React, Vue, Angular)"
+    - value: "backend"
+      label: "Backend (Python, Java, Go, .NET, Rust)"
+    - value: "fullstack"
+      label: "Full-stack (both frontend and backend)"
+
+# ✅ ACTIVELY USED - CI/CD platform detection
+ci_platform:
+  prompt: "Which CI/CD platform do you use?"
+  default: "auto"
+  result: "{value}"
+  single-select:
+    - value: "auto"
+      label: "Auto-detect from repository (Recommended)"
+    - value: "github-actions"
+      label: "GitHub Actions"
+    - value: "gitlab-ci"
+      label: "GitLab CI"
+    - value: "jenkins"
+      label: "Jenkins"
+    - value: "azure-devops"
+      label: "Azure DevOps Pipelines"
+    - value: "harness"
+      label: "Harness CI"
+    - value: "circle-ci"
+      label: "CircleCI"
+    - value: "other"
+      label: "Other/Custom"
+
+# ✅ ACTIVELY USED - Test framework selection for multi-stack support
+test_framework:
+  prompt: "Which test framework are you using?"
+  default: "auto"
+  result: "{value}"
+  single-select:
+    - value: "auto"
+      label: "Auto-detect from project files (Recommended)"
+    - value: "playwright"
+      label: "Playwright (JavaScript/TypeScript)"
+    - value: "cypress"
+      label: "Cypress (JavaScript/TypeScript)"
+    - value: "jest"
+      label: "Jest (JavaScript/TypeScript)"
+    - value: "vitest"
+      label: "Vitest (JavaScript/TypeScript)"
+    - value: "pytest"
+      label: "pytest (Python)"
+    - value: "junit"
+      label: "JUnit (Java/Kotlin)"
+    - value: "go-test"
+      label: "Go test (Go)"
+    - value: "dotnet-test"
+      label: "dotnet test (C#/.NET)"
+    - value: "rspec"
+      label: "RSpec (Ruby)"
+    - value: "other"
+      label: "Other/Custom"
+
+# ⏭️ FUTURE - Risk threshold (not currently used in test-design workflow, marked for Phase 10)
+risk_threshold:
+  prompt: "What risk level requires mandatory testing?"
+  default: "p1"
+  result: "{value}"
+  single-select:
+    - value: "p0"
+      label: "P0 only (Critical systems)"
+    - value: "p1"
+      label: "P1+ (High & Critical)"
+    - value: "p2"
+      label: "P2+ (Medium, High & Critical)"
+    - value: "p3"
+      label: "All (P0-P3)"
+
+# ⏭️ FUTURE - Test output folders (not currently wired into workflows, marked for Phase 10)
+# IMPORTANT: test_artifacts already resolves to {project-root}/..., so don't re-prepend {project-root}
+test_design_output:
+  prompt: "Where should test design documents be stored?"
+  default: "test-design"
+  result: "{test_artifacts}/{value}"
+
+test_review_output:
+  prompt: "Where should test review reports be stored?"
+  default: "test-reviews"
+  result: "{test_artifacts}/{value}"
+
+trace_output:
+  prompt: "Where should traceability reports be stored?"
+  default: "traceability"
+  result: "{test_artifacts}/{value}"
+
+post-install-notes:
+  test_stack_type:
+    auto: |
+      Stack Auto-Detection:
+        TEA will detect your project type from manifest files:
+        - Frontend: package.json with react/vue/angular, playwright.config.*, vite.config.*
+        - Backend: pyproject.toml, pom.xml, go.mod, *.csproj, Gemfile, Cargo.toml
+        - Full-stack: both frontend and backend indicators present
+        Existing installations without test_stack_type default to "auto" (detects frontend).
+  ci_platform:
+    auto: |
+      CI Platform Auto-Detection:
+        TEA will detect your CI platform from repository files:
+        - GitHub Actions: .github/workflows/
+        - GitLab CI: .gitlab-ci.yml
+        - Jenkins: Jenkinsfile
+        - Azure DevOps: azure-pipelines.yml
+        - Harness: .harness/
+        - CircleCI: .circleci/config.yml
+        Existing installations without ci_platform default to "auto".
+  tea_browser_automation:
+    cli: |
+      Playwright CLI Setup:
+        npm install -g @playwright/cli@latest
+        playwright-cli install --skills    # Run from project root
+        Node.js 18+ required.
+    mcp: |
+      Playwright MCP Setup (two servers):
+        1. playwright    — npx @playwright/mcp@latest
+        2. playwright-test — npx playwright run-test-mcp-server
+        Configure both MCP servers in your IDE settings.
+        See: https://github.com/microsoft/playwright-mcp
+    auto: |
+      Playwright CLI Setup:
+        npm install -g @playwright/cli@latest
+        playwright-cli install --skills    # Run from project root
+        Node.js 18+ required.
+
+      Playwright MCP Setup (two servers):
+        1. playwright    — npx @playwright/mcp@latest
+        2. playwright-test — npx playwright run-test-mcp-server
+        Configure both MCP servers in your IDE settings.
+        See: https://github.com/microsoft/playwright-mcp
+
+  tea_execution_mode:
+    auto: |
+      Execution Mode (Auto):
+        TEA probes runtime capabilities at orchestration steps.
+        Selection order:
+          1. agent-team (if supported)
+          2. subagent (if supported)
+          3. sequential (fallback)
+        This keeps behavior portable across Codex, Claude Code, and other runtimes.
+    subagent: |
+      Execution Mode (Subagent):
+        TEA will prefer isolated subagent workers for parallel orchestration.
+        If capability probing is enabled and subagent support is unavailable, TEA falls back safely.
+    agent-team: |
+      Execution Mode (Agent Team):
+        TEA will prefer team/delegation orchestration when runtime supports it.
+        If capability probing is enabled and agent-team support is unavailable, TEA falls back safely.
+    sequential: |
+      Execution Mode (Sequential):
+        TEA disables parallel orchestration and runs worker steps one by one.
+        Useful for deterministic debugging and constrained environments.
+
+  tea_use_pactjs_utils:
+    true: |
+      Pact.js Utils Setup:
+        npm install -D @seontechnologies/pactjs-utils
+        Peer dependency: @pact-foundation/pact >= 16.2.0
+          npm install -D @pact-foundation/pact
+        For remote flow (with Pact Broker):
+          Set PACT_BROKER_BASE_URL and PACT_BROKER_TOKEN as env vars or CI secrets.
+          Also set GITHUB_SHA (auto-set by GitHub Actions) and GITHUB_BRANCH (must be defined explicitly: ${{ github.head_ref || github.ref_name }}).
+        For local flow (monorepo):
+          No broker needed - consumer generates pacts, provider verifies locally.
+        Docs: https://seontechnologies.github.io/pactjs-utils/
+  tea_pact_mcp:
+    mcp: |
+      SmartBear MCP Setup (PactFlow integration):
+        Install: npm install -g @smartbear/mcp
+        Claude Code (global): claude mcp add-json -s user smartbear '{"type":"stdio","command":"npx","args":["-y","@smartbear/mcp@latest"],"env":{"PACT_BROKER_BASE_URL":"https://{tenant}.pactflow.io","PACT_BROKER_TOKEN":"<your-api-token>"}}'
+        Required env vars:
+          PACT_BROKER_BASE_URL=https://{tenant}.pactflow.io
+          PACT_BROKER_TOKEN=<your-api-token>
+        Requires: Node.js 20+
+        Docs: https://developer.smartbear.com/smartbear-mcp/docs/getting-started
+
+# Directories to create during installation (declarative, no code execution)
+directories:
+  - "{test_artifacts}"

package/lib/bmad-cache/tea/src/teams/default-party.csv

@@ -0,0 +1,2 @@
+name,displayName,title,icon,role,identity,communicationStyle,principles,module,path
+"tea","Murat","Master Test Architect","🧪","Master Test Architect","Test architect specializing in CI/CD, automated frameworks, and scalable quality gates.","Blends data with gut instinct. 'Strong opinions, weakly held' is their mantra. Speaks in risk calculations and impact assessments.","Risk-based testing. Depth scales with impact. Quality gates backed by data. Tests mirror usage. Flakiness is critical debt. Tests first, AI implements, suite validates.","tea","_bmad/tea/agents/tea.agent.yaml"