bmad-method-test-architecture-enterprise 1.5.0 → 1.5.2

package/README.md

@@ -54,7 +54,7 @@ flowchart LR
 
 ### How It Works at Runtime
 
-1. **Trigger** — User types `/bmad:tea:automate` (or shorthand `TA`). The agent menu in `tea.agent.yaml` maps the trigger to `automate/workflow.yaml`.
+1. **Trigger** — Direct commands are `/bmad:tea:automate` (Claude/Cursor/Windsurf) and `$bmad-tea-testarch-automate` (Codex). `TA` is an agent-menu trigger available only after TEA is activated; the menu in `tea.agent.yaml` maps `TA` to `automate/workflow.yaml`.
 2. **Agent loads** — `tea.agent.yaml` injects the persona (identity, principles, critical actions) into the context window.
 3. **Workflow loads** — `workflow.yaml` resolves config variables and `workflow.md` presents the mode menu (Create / Edit / Validate), then routes to the first step file.
 4. **Step-by-step execution** — Only the current step file is in context (just-in-time loading). Each step explicitly names the next one (`nextStepFile: './step-02-...'`). The LLM reads, executes, saves output, then loads the next step. No future steps are ever preloaded.
@@ -81,9 +81,9 @@ BMad workflows and Claude Code Skills solve different problems at different scal
 
 The key insight is that there is **no external runtime engine** — the LLM _is_ the engine. BMad workflows are structured markdown that the LLM follows as instructions: "read this file, execute it completely, save your output, load the next file." Skills are a single tool in a toolbox; BMad workflows are a workshop with a process manual.
 
-**How workflows become commands.** When you run `npx bmad-method install`, the installer converts every workflow and agent into a Claude Code command in `.claude/commands/`. For example, `bmad-tea-testarch-automate.md` tells the LLM: "load the core workflow engine (`workflow.xml`), pass it this workflow config (`automate/workflow.yaml`), follow the instructions exactly." That single command file is the bridge — it triggers the workflow entry point; the multi-step engine takes over from there.
+**How workflows become commands.** When you run `npx bmad-method install`, the installer generates tool-specific artifacts for your runtime (for example, Claude Code uses `.claude/commands/`, while Codex uses `.agents/skills/`). In Claude Code, `bmad-tea-testarch-automate.md` tells the LLM: "load the core workflow engine (`workflow.xml`), pass it this workflow config (`automate/workflow.yaml`), follow the instructions exactly." That launcher artifact is the bridge — it triggers the workflow entry point; the multi-step engine takes over from there.
 
-```
+```text
 .claude/commands/                         # Generated by installer
 ├── bmad-agent-tea-tea.md                 # /tea → loads agent persona + menu
 ├── bmad-tea-testarch-automate.md         # /automate → loads workflow.xml + workflow.yaml
@@ -103,13 +103,20 @@ npx bmad-method install
 
 **Note:** TEA is automatically added to party mode after installation. Use `/party` to collaborate with TEA alongside other BMad agents.
 
+### Tool-specific invocation
+
+| Tool                            | Invocation style                | Example                       |
+| ------------------------------- | ------------------------------- | ----------------------------- |
+| Claude Code / Cursor / Windsurf | Slash command                   | `/bmad:tea:automate`          |
+| Codex                           | `$` skill from `.agents/skills` | `$bmad-tea-testarch-automate` |
+
 ## Quickstart
 
 1. Install TEA (above)
 2. Run one of the core workflows:
-   - `TD` / `/bmad:tea:test-design` — test design and risk assessment
-   - `AT` / `/bmad:tea:atdd` — failing acceptance tests first (TDD red phase)
-   - `TA` / `/bmad:tea:automate` — expand automation coverage
+   - `TD` / `/bmad:tea:test-design` / `$bmad-tea-testarch-test-design` — test design and risk assessment
+   - `AT` / `/bmad:tea:atdd` / `$bmad-tea-testarch-atdd` — failing acceptance tests first (TDD red phase)
+   - `TA` / `/bmad:tea:automate` / `$bmad-tea-testarch-automate` — expand automation coverage
 3. Or use in party mode: `/party` to include TEA with other agents
 
 ## Engagement Models
@@ -121,17 +128,17 @@ npx bmad-method install
 
 ## Workflows
 
-| Trigger | Command                      | Purpose                                                   |
-| ------- | ---------------------------- | --------------------------------------------------------- |
-| TMT     | `/bmad:tea:teach-me-testing` | Teach Me Testing (TEA Academy)                            |
-| TF      | `/bmad:tea:framework`        | Scaffold test framework (frontend, backend, or fullstack) |
-| CI      | `/bmad:tea:ci`               | Set up CI/CD quality pipeline (multi-platform)            |
-| TD      | `/bmad:tea:test-design`      | System-level or epic-level test design                    |
-| AT      | `/bmad:tea:atdd`             | Generate failing acceptance tests + checklist             |
-| TA      | `/bmad:tea:automate`         | Expand test automation coverage                           |
-| RV      | `/bmad:tea:test-review`      | Review test quality and score                             |
-| TR      | `/bmad:tea:trace`            | Trace requirements to tests + gate decision               |
-| NR      | `/bmad:tea:nfr-assess`       | Assess non-functional requirements                        |
+| Trigger | Slash Command                | Codex Skill                      | Purpose                                                   |
+| ------- | ---------------------------- | -------------------------------- | --------------------------------------------------------- |
+| TMT     | `/bmad:tea:teach-me-testing` | `$bmad-tea-teach-me-testing`     | Teach Me Testing (TEA Academy)                            |
+| TF      | `/bmad:tea:framework`        | `$bmad-tea-testarch-framework`   | Scaffold test framework (frontend, backend, or fullstack) |
+| CI      | `/bmad:tea:ci`               | `$bmad-tea-testarch-ci`          | Set up CI/CD quality pipeline (multi-platform)            |
+| TD      | `/bmad:tea:test-design`      | `$bmad-tea-testarch-test-design` | System-level or epic-level test design                    |
+| AT      | `/bmad:tea:atdd`             | `$bmad-tea-testarch-atdd`        | Generate failing acceptance tests + checklist             |
+| TA      | `/bmad:tea:automate`         | `$bmad-tea-testarch-automate`    | Expand test automation coverage                           |
+| RV      | `/bmad:tea:test-review`      | `$bmad-tea-testarch-test-review` | Review test quality and score                             |
+| TR      | `/bmad:tea:trace`            | `$bmad-tea-testarch-trace`       | Trace requirements to tests + gate decision               |
+| NR      | `/bmad:tea:nfr-assess`       | `$bmad-tea-testarch-nfr`         | Assess non-functional requirements                        |
 
 ## Configuration
 

package/docs/MIGRATION.md

@@ -36,6 +36,10 @@ All TEA commands have changed namespace from `/bmad:bmm:tea:*` to `/bmad:tea:*`.
 | `TF`, `CI`, `TD`, `AT`, `TA`   | Same                     |
 | `RV`, `TR`, `NR`               | Same                     |
 
+Codex skill-mode workflow equivalents: `framework` → `$bmad-tea-testarch-framework`, `ci` → `$bmad-tea-testarch-ci`, `test-design` → `$bmad-tea-testarch-test-design`, `atdd` → `$bmad-tea-testarch-atdd`, `automate` → `$bmad-tea-testarch-automate`, `test-review` → `$bmad-tea-testarch-test-review`, `trace` → `$bmad-tea-testarch-trace`, `nfr-assess` → `$bmad-tea-testarch-nfr`, `teach-me-testing` → `$bmad-tea-teach-me-testing`.
+
+Clarification: short triggers like `TD` and `TA` are agent menu triggers after TEA activation; invocation differs by tool (slash commands vs Codex skill calls).
+
 **Action Required**: Update any saved prompts, scripts, or documentation that reference the old commands.
 
 ### 2. Module Installation
@@ -172,6 +176,8 @@ claude "/bmad:bmm:tea:test-design"
 claude "/bmad:tea:test-design"
 ```
 
+Codex skill mode (in Codex chat): `$bmad-tea-testarch-test-design`
+
 **Example: Updating Documentation**
 
 ```markdown
@@ -184,6 +190,8 @@ Run `/bmad:bmm:tea:automate` to expand test coverage.
 Run `/bmad:tea:automate` to expand test coverage.
 ```
 
+Codex skill-mode equivalent: use `$bmad-tea-testarch-automate`.
+
 ### Step 4: Verify Installation
 
 Load the TEA agent and run a test command:
@@ -353,12 +361,15 @@ See [Configure Browser Automation](/docs/how-to/customization/configure-browser-
 
 **Solution**: Update to new namespace:
 
-```bash
+```text
 # Old (won't work)
 /bmad:bmm:tea:test-design
 
 # New (correct)
 /bmad:tea:test-design
+
+# Codex skill mode
+$bmad-tea-testarch-test-design
 ```
 
 ### Issue: Configuration Variables Not Set
@@ -427,7 +438,7 @@ Use this checklist to ensure a smooth migration:
 - [ ] Verify BMAD Method version is v7.0.0 or later
 - [ ] Install standalone TEA module via `npx bmad-method install`
 - [ ] Configure TEA variables (test_artifacts, Playwright Utils, MCP)
-- [ ] Update saved prompts to use new namespace (`/bmad:tea:*`)
+- [ ] Update saved invocations for your tool (`/bmad:tea:*` for slash-command tools, or `$bmad-tea-*` skills for Codex)
 - [ ] Update documentation references to new commands
 - [ ] Update CI/CD scripts if they invoke TEA commands
 - [ ] Test each workflow you use (e.g., `test-design`, `automate`, `atdd`)

package/docs/explanation/tea-overview.md

@@ -345,7 +345,7 @@ Production-ready contract testing utilities that reduce raw Pact.js boilerplate
 - Install: `npm install -D @seontechnologies/pactjs-utils @pact-foundation/pact`
 - Config: `tea_use_pactjs_utils: true` (default is `true`)
 - Impacts: `framework`, `atdd`, `automate`, `test-design`, `test-review`, `ci`
-- Utilities include: createProviderState, toJsonMap, buildVerifierOptions, buildMessageVerifierOptions, createRequestFilter, noOpRequestFilter, handlePactBrokerUrlAndSelectors, getProviderVersionTags
+- Utilities include: createProviderState, toJsonMap, setJsonBody, setJsonContent, buildVerifierOptions, buildMessageVerifierOptions, createRequestFilter, noOpRequestFilter, handlePactBrokerUrlAndSelectors, getProviderVersionTags
 - Supports local monorepo flow (`pactUrls`) and remote broker flow (`PACT_BROKER_BASE_URL`, `PACT_BROKER_TOKEN`)
 
 ### Browser Automation (Playwright CLI + MCP)
@@ -455,7 +455,7 @@ Optional MCP integration for design-time broker interaction in contract testing
 - [Test Quality Standards](/docs/explanation/test-quality-standards.md) - Definition of Done, determinism, isolation, explicit assertions
 - [Fixture Architecture](/docs/explanation/fixture-architecture.md) - Pure function → fixture → composition pattern
 - [Network-First Patterns](/docs/explanation/network-first-patterns.md) - Intercept-before-navigate, eliminating flakiness
-- [Knowledge Base System](/docs/explanation/knowledge-base-system.md) - Context engineering with tea-index.csv, 40 fragments
+- [Knowledge Base System](/docs/explanation/knowledge-base-system.md) - Context engineering with tea-index.csv, 42 fragments
 - [Engagement Models](/docs/explanation/engagement-models.md) - TEA Lite, TEA Solo, TEA Integrated (5 models explained)
 
 ### Philosophy & Design
@@ -470,5 +470,5 @@ Optional MCP integration for design-time broker interaction in contract testing
 
 - [TEA Command Reference](/docs/reference/commands.md) - All 9 workflows: inputs, outputs, phases, frequency
 - [TEA Configuration Reference](/docs/reference/configuration.md) - Config options, file locations, setup examples
-- [Knowledge Base Index](/docs/reference/knowledge-base.md) - 40 fragments categorized and explained
+- [Knowledge Base Index](/docs/reference/knowledge-base.md) - 42 fragments categorized and explained
 - [Glossary - TEA Section](/docs/glossary/index.md#test-architect-tea-concepts) - 20 TEA-specific terms defined

package/docs/explanation/testing-as-engineering.md

@@ -41,7 +41,7 @@ The solution combines three components that work together to enforce quality:
 
 **Playwright-Utils examples:** `api-request`, `auth-session`, `intercept-network-call`, `recurse`, `log`, `network-recorder`, `burn-in`, `network-error-monitor`, `file-utils`.
 
-**pactjs-utils examples:** `createProviderState`, `toJsonMap`, `createRequestFilter`, `noOpRequestFilter`, `buildVerifierOptions`, `buildMessageVerifierOptions`.
+**pactjs-utils examples:** `createProviderState`, `toJsonMap`, `setJsonBody`, `setJsonContent`, `createRequestFilter`, `noOpRequestFilter`, `buildVerifierOptions`, `buildMessageVerifierOptions`.
 
 Together, these utility libraries eliminate the need to reinvent core testing primitives across UI, API, web, non-web, and contract testing.
 

package/docs/how-to/customization/configure-browser-automation.md

@@ -33,7 +33,7 @@ npm install -g @playwright/cli@latest    # Install globally (Node.js 18+)
 playwright-cli install --skills          # Register as an agent skill
 ```
 
-The global npm install is one-time. The skills install (`playwright-cli install --skills`) should be run from your project root — it registers skills in your project's `.claude/skills/` directory (Claude Code, GitHub Copilot, and other coding agents that support the skills convention). Agents without skills support can still use the CLI directly via `playwright-cli --help`.
+The global npm install is one-time. The skills install (`playwright-cli install --skills`) should be run from your project root — it registers skills in your active tool's project skills directory (for example, Claude Code uses `.claude/skills/` and Codex uses `.agents/skills/`). Agents without skills support can still use the CLI directly via `playwright-cli --help`.
 
 ### For MCP (`mcp` or `auto` mode)
 

package/docs/reference/commands.md

@@ -7,6 +7,11 @@ description: Quick reference for all 9 TEA workflows - inputs, outputs, and link
 
 Quick reference for all 9 TEA (Test Engineering Architect) workflows. For detailed step-by-step guides, see the how-to documentation.
 
+**Invocation by tool:**
+
+- Claude Code / Cursor / Windsurf: use slash commands (for example, `/bmad:tea:automate`)
+- Codex: use `$` skills from `.agents/skills` (for example, `$bmad-tea-testarch-automate`)
+
 ## Quick Index
 
 - [`teach-me-testing`](#teach-me-testing) - Learn testing (TEA Academy)

package/docs/reference/knowledge-base.md

@@ -175,14 +175,16 @@ Feature flag testing and pure API testing patterns.
 
 Contract testing fundamentals plus Pact.js Utils and Pact MCP integrations.
 
-| Fragment                                                                                                                                                                       | Description                                                                      | Key Topics                                     |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------- | ---------------------------------------------- |
-| [contract-testing](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/contract-testing.md)                             | Raw Pact patterns, publishing, verification, resilience                          | Contract testing, Pact fundamentals            |
-| [pactjs-utils-overview](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pactjs-utils-overview.md)                   | Installation, flow decision tree, utility map                                    | pactjs-utils, CDCT/BDCT, integration strategy  |
-| [pactjs-utils-consumer-helpers](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pactjs-utils-consumer-helpers.md)   | `createProviderState`, `toJsonMap` for consumer-side provider states             | pactjs-utils, consumer testing, provider state |
-| [pactjs-utils-provider-verifier](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pactjs-utils-provider-verifier.md) | `buildVerifierOptions`, `buildMessageVerifierOptions`, broker selectors, tagging | pactjs-utils, provider verification, CI        |
-| [pactjs-utils-request-filter](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pactjs-utils-request-filter.md)       | `createRequestFilter`, `noOpRequestFilter` auth/header patterns                  | pactjs-utils, request filter, auth injection   |
-| [pact-mcp](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pact-mcp.md)                                             | SmartBear MCP tools for provider states, review, can-i-deploy, matrix            | pact-mcp, broker interaction, pactflow         |
+| Fragment                                                                                                                                                                       | Description                                                                                                                    | Key Topics                                     |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------- |
+| [contract-testing](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/contract-testing.md)                             | Raw Pact patterns, publishing, verification, resilience                                                                        | Contract testing, Pact fundamentals            |
+| [pactjs-utils-overview](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pactjs-utils-overview.md)                   | Installation, flow decision tree, utility map                                                                                  | pactjs-utils, CDCT/BDCT, integration strategy  |
+| [pactjs-utils-consumer-helpers](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pactjs-utils-consumer-helpers.md)   | Provider-state helpers: `createProviderState`, `toJsonMap`; request/response callback helpers: `setJsonBody`, `setJsonContent` | pactjs-utils, consumer testing, provider state |
+| [pactjs-utils-provider-verifier](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pactjs-utils-provider-verifier.md) | `buildVerifierOptions`, `buildMessageVerifierOptions`, broker selectors, tagging                                               | pactjs-utils, provider verification, CI        |
+| [pactjs-utils-request-filter](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pactjs-utils-request-filter.md)       | `createRequestFilter`, `noOpRequestFilter` auth/header patterns                                                                | pactjs-utils, request filter, auth injection   |
+| [pact-mcp](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pact-mcp.md)                                             | SmartBear MCP tools for provider states, review, can-i-deploy, matrix                                                          | pact-mcp, broker interaction, pactflow         |
+| [pact-consumer-framework-setup](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pact-consumer-framework-setup.md)   | Consumer CDC framework scaffolding: directory layout, scripts, CI workflow, and PactV4 test patterns                           | pactjs-utils, consumer CDC, framework setup    |
+| [pact-consumer-di](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/blob/main/src/testarch/knowledge/pact-consumer-di.md)                             | Dependency-injection pattern for Pact consumer tests using real client code                                                    | pact, consumer, DI, contract accuracy          |
 
 **Used in:** `framework`, `test-design`, `atdd`, `automate`, `test-review`, `ci` (conditioned by `tea_use_pactjs_utils` and `tea_pact_mcp`)
 
@@ -255,7 +257,7 @@ Fragments are loaded based on workflow needs and tier priority:
 - **Extended tier**: Loaded when the workflow context requires them (e.g., `auth-session.md` when tests involve authentication)
 - **Specialized tier**: Only loaded when the specific use case matches (e.g., contract-testing for microservices, email-auth for email flows)
 
-**Fragment Location:** `src/testarch/knowledge/` (all 40 fragments in a single directory)
+**Fragment Location:** `src/testarch/knowledge/` (all 42 fragments in a single directory)
 
 **Manifest:** `src/testarch/tea-index.csv`
 

package/docs/reference/troubleshooting.md

@@ -195,9 +195,13 @@ If the BMAD installer can run but cannot fetch the Test Architect module from Gi
    ```
 
 3. Test workflow trigger directly:
-   ```bash
-   # Try full command
+
+   ```text
+   # Try full slash command
    /bmad:tea:test-design
+
+   # Codex skill-mode alternative
+   $bmad-tea-testarch-test-design
    ```
 
 ---
@@ -304,7 +308,7 @@ If the BMAD installer can run but cannot fetch the Test Architect module from Gi
 
    ```bash
    cat _bmad/tea/testarch/tea-index.csv | wc -l
-   # Should show 41 lines (header + 40 fragments)
+   # Should show 43 lines (header + 42 fragments)
    ```
 
 2. Check knowledge fragment files:
@@ -609,7 +613,7 @@ If the BMAD installer can run but cannot fetch the Test Architect module from Gi
 
 **Causes**:
 
-- Up to 40 fragments loading at once (depends on workflow and enabled integrations)
+- Up to 42 fragments loading at once (depends on workflow and enabled integrations)
 - Large fragment file sizes
 - Disk I/O bottleneck
 
@@ -685,9 +689,9 @@ When reporting issues, include:
 Check these first:
 
 - [ ] TEA is installed: `ls -la _bmad/tea/`
-- [ ] Using correct command namespace: `/bmad:tea:*` not `/bmad:bmm:tea:*`
+- [ ] Using the correct invocation for your tool: slash namespace `/bmad:tea:*` (not `/bmad:bmm:tea:*`) or Codex skill equivalents (`$bmad-tea-*`)
 - [ ] Module.yaml exists and is valid
-- [ ] Knowledge base files present (40 fragments)
+- [ ] Knowledge base files present (42 fragments)
 - [ ] Output directory exists and is writable
 - [ ] No disk space issues: `df -h`
 - [ ] Node version >=20.0.0: `node --version`
@@ -751,7 +755,7 @@ done
 
 # Check knowledge base
 fragment_count=$(ls _bmad/tea/testarch/knowledge/*.md 2>/dev/null | wc -l)
-echo "Knowledge fragments: $fragment_count (expected: 40)"
+echo "Knowledge fragments: $fragment_count (expected: 42)"
 
 # Check tea-index.csv
 csv_lines=$(wc -l < _bmad/tea/testarch/tea-index.csv 2>/dev/null || echo "0")

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method-test-architecture-enterprise",
-  "version": "1.5.0",
+  "version": "1.5.2",
   "description": "Master Test Architect for quality strategy, test automation, and release gates",
   "keywords": [
     "bmad",

package/release_notes.md

@@ -1,11 +1,13 @@
-## 🚀 What's New in v1.5.0
+## 🚀 What's New in v1.5.2
 
 ### ✨ New Features
-- feat: harden generated ci related yml
+- feat: harden pact framework and knowledge
+
+### 🐛 Bug Fixes
+- fix: pr comments
 
 ### 📦 Other Changes
-- addressed PR comments
-- Merge pull request #49 from bmad-code-org/feat/harden-generated-ci-related-yml
+- Merge pull request #51 from bmad-code-org/feat/harden-pact-framework-flow
 
 
 ## 📦 Installation
@@ -15,4 +17,4 @@ npx bmad-method install
 # Select "Test Architect" from module menu
 ```
 
-**Full Changelog**: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/compare/v1.4.1...v1.5.0
+**Full Changelog**: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/compare/v1.5.1...v1.5.2