ma-agents 3.5.3 → 3.5.5

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-atdd/atdd-checklist-template.md

@@ -3,6 +3,14 @@ stepsCompleted: []
 lastStep: ''
 lastSaved: ''
 workflowType: 'testarch-atdd'
+storyId: '{story_id}'
+storyKey: '{story_key}'
+storyFile: '{story_file}'
+atddChecklistPath: '{test_artifacts}/atdd-checklist-{story_key}.md'
+generatedTestFiles:
+  - '{api_test_file_path}'
+  - '{e2e_test_file_path}'
+  - '{component_test_file_path}'
 inputDocuments: []
 ---
 
@@ -34,7 +42,19 @@ inputDocuments: []
 
 ---
 
-## Failing Tests Created (RED Phase)
+## Story Integration Metadata
+
+- **Story ID:** `{story_id}`
+- **Story Key:** `{story_key}`
+- **Story File:** `{story_file}`
+- **Checklist Path:** `{test_artifacts}/atdd-checklist-{story_key}.md`
+- **Generated Test Files:** `{e2e_test_file_path}`, `{api_test_file_path}`, `{component_test_file_path}`
+
+If this story came from BMM `create-story`, mirror these artifact paths into the story's `Dev Notes` so `dev-story` can discover and activate the red-phase scaffolds.
+
+---
+
+## Red-Phase Test Scaffolds Created
 
 ### E2E Tests ({e2e_test_count} tests)
 
@@ -166,7 +186,7 @@ test('should do something', async ({ {fixtureName} }) => {
 
 ## Implementation Checklist
 
-{Map each failing test to concrete implementation tasks that will make it pass}
+{Map each scaffolded test to concrete implementation tasks that will make it pass}
 
 ### Test: {test_name_1}
 
@@ -205,7 +225,7 @@ test('should do something', async ({ {fixtureName} }) => {
 ## Running Tests
 
 ```bash
-# Run all failing tests for this story
+# Run all activated tests for this story
 {test_command_all}
 
 # Run specific test file
@@ -229,7 +249,7 @@ test('should do something', async ({ {fixtureName} }) => {
 
 **TEA Agent Responsibilities:**
 
-- ✅ All tests written and failing
+- ✅ All tests written as red-phase scaffolds with `test.skip()`
 - ✅ Fixtures and factories created with auto-cleanup
 - ✅ Mock requirements documented
 - ✅ data-testid requirements listed
@@ -237,9 +257,9 @@ test('should do something', async ({ {fixtureName} }) => {
 
 **Verification:**
 
-- All tests run and fail as expected
-- Failure messages are clear and actionable
-- Tests fail due to missing implementation, not test bugs
+- All generated tests are present and marked with `test.skip()`
+- Activation guidance is clear and actionable
+- Any activated test fails due to missing implementation, not test bugs
 
 ---
 
@@ -247,12 +267,13 @@ test('should do something', async ({ {fixtureName} }) => {
 
 **DEV Agent Responsibilities:**
 
-1. **Pick one failing test** from implementation checklist (start with highest priority)
-2. **Read the test** to understand expected behavior
-3. **Implement minimal code** to make that specific test pass
-4. **Run the test** to verify it now passes (green)
-5. **Check off the task** in implementation checklist
-6. **Move to next test** and repeat
+1. **Pick one scaffolded test** from implementation checklist (start with highest priority)
+2. **Remove `test.skip()`** for that test and confirm it fails first
+3. **Read the test** to understand expected behavior
+4. **Implement minimal code** to make that specific test pass
+5. **Run the test** to verify it now passes (green)
+6. **Check off the task** in implementation checklist
+7. **Move to next test** and repeat
 
 **Key Principles:**
 
@@ -297,14 +318,15 @@ test('should do something', async ({ {fixtureName} }) => {
 
 ## Next Steps
 
-1. **Share this checklist and failing tests** with the dev workflow (manual handoff)
-2. **Review this checklist** with team in standup or planning
-3. **Run failing tests** to confirm RED phase: `{test_command_all}`
+1. **Link this checklist and generated tests** into the story file `Dev Notes` / `ATDD Artifacts` section when a writable story file is available
+2. **If the story file cannot be updated automatically**, share this checklist and generated tests with the dev workflow as a manual handoff
+3. **Review this checklist** with team in standup or planning
 4. **Begin implementation** using implementation checklist as guide
-5. **Work one test at a time** (red → green for each)
-6. **Share progress** in daily standup
-7. **When all tests pass**, refactor code for quality
-8. **When refactoring complete**, manually update story status to 'done' in sprint-status.yaml
+5. **Activate one scaffold at a time** by removing `test.skip()` for the current task, then confirm it fails before implementing
+6. **Work one activated test at a time** (red → green for each)
+7. **Share progress** in daily standup
+8. **When all activated tests pass**, refactor code for quality
+9. **When refactoring complete**, manually update story status to 'done' in sprint-status.yaml
 
 ---
 
@@ -325,25 +347,26 @@ See `tea-index.csv` for complete knowledge fragment mapping.
 
 ## Test Execution Evidence
 
-### Initial Test Run (RED Phase Verification)
+### Initial Scaffold Review / RED Verification
 
-**Command:** `{test_command_all}`
+**Command:** `{test_command_all}` (or a narrower command after removing `test.skip()` for the current task)
 
 **Results:**
 
 ```
-{paste_test_run_output_showing_all_tests_failing}
+{paste_test_run_output_showing_scaffolds_skipped_or_activated_tests_failing}
 ```
 
 **Summary:**
 
 - Total tests: {total_test_count}
-- Passing: 0 (expected)
-- Failing: {total_test_count} (expected)
-- Status: ✅ RED phase verified
+- Skipped: {total_test_count} (expected before activation)
+- Activated RED tests: {activated_test_count} (expected after activation, before implementation)
+- Passing: 0 before implementation (expected for activated tests)
+- Status: ✅ Red-phase scaffolds verified
 
 **Expected Failure Messages:**
-{list_expected_failure_messages_for_each_test}
+{list_expected_skip_or_failure_states_for_each_test}
 
 ---
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-atdd/checklist.md

@@ -50,7 +50,7 @@ Before starting this workflow, verify:
 
 ---
 
-## Step 3: Failing Tests Generated
+## Step 3: Red-Phase Test Scaffolds Generated
 
 ### Test File Structure Created
 
@@ -68,8 +68,8 @@ Before starting this workflow, verify:
 - [ ] One assertion per test (atomic test design)
 - [ ] No hard waits or sleeps (explicit waits only)
 - [ ] Network-first pattern applied (route interception BEFORE navigation)
-- [ ] Tests fail initially (RED phase verified by local test run)
-- [ ] Failure messages are clear and actionable
+- [ ] Tests are generated as `test.skip()` scaffolds
+- [ ] Activation guidance is documented for the current task
 
 ### API Tests (If Applicable)
 
@@ -79,7 +79,7 @@ Before starting this workflow, verify:
 - [ ] HTTP status codes verified
 - [ ] Response body validation includes all required fields
 - [ ] Error cases tested (400, 401, 403, 404, 500)
-- [ ] Tests fail initially (RED phase verified)
+- [ ] Tests are generated as `test.skip()` scaffolds
 
 ### Component Tests (If Applicable)
 
@@ -89,7 +89,7 @@ Before starting this workflow, verify:
 - [ ] Interaction testing covers user actions (click, hover, keyboard)
 - [ ] State management within component validated
 - [ ] Props and events tested
-- [ ] Tests fail initially (RED phase verified)
+- [ ] Tests are generated as `test.skip()` scaffolds
 
 ### Test Quality Validation
 
@@ -144,7 +144,7 @@ Before starting this workflow, verify:
 ## Step 5: Implementation Checklist Created
 
 - [ ] Implementation checklist created with clear structure
-- [ ] Each failing test mapped to concrete implementation tasks
+- [ ] Each scaffolded test mapped to concrete implementation tasks
 - [ ] Tasks include:
   - [ ] Route/component creation
   - [ ] Business logic implementation
@@ -170,12 +170,12 @@ Before starting this workflow, verify:
 
 ### ATDD Checklist Document Created
 
-- [ ] Output file created at `{test_artifacts}/atdd-checklist-{story_id}.md`
+- [ ] Output file created at `{test_artifacts}/atdd-checklist-{story_key}.md`
 - [ ] Document follows template structure from `atdd-checklist-template.md`
 - [ ] Document includes all required sections:
   - [ ] Story summary
   - [ ] Acceptance criteria breakdown
-  - [ ] Failing tests created (paths and line counts)
+  - [ ] Red-phase test scaffolds created (paths and line counts)
   - [ ] Data factories created
   - [ ] Fixtures created
   - [ ] Mock requirements
@@ -184,15 +184,16 @@ Before starting this workflow, verify:
   - [ ] Red-green-refactor workflow
   - [ ] Execution commands
   - [ ] Next steps for DEV team
-- [ ] Output shared with DEV workflow (manual handoff; not auto-consumed)
+- [ ] Checklist frontmatter includes `storyId`, `storyKey`, `storyFile`, `atddChecklistPath`, and generated test file paths
+- [ ] If a writable story file was provided, ATDD artifacts were linked back into story context
+- [ ] If a story file could not be updated, manual handoff instructions are present
 
-### All Tests Verified to Fail (RED Phase)
+### Red-Phase Scaffolds Verified
 
-- [ ] Full test suite run locally before finalizing
-- [ ] All tests fail as expected (RED phase confirmed)
-- [ ] No tests passing before implementation (if passing, test is invalid)
-- [ ] Failure messages documented in ATDD checklist
-- [ ] Failures are due to missing implementation, not test bugs
+- [ ] All generated acceptance test scaffolds are marked with `test.skip()`
+- [ ] No scaffold was emitted as an active passing test before implementation
+- [ ] Activation guidance is documented: remove `test.skip()` for the current task, then confirm RED before implementing
+- [ ] Any assumptions or expected failure reasons are documented in ATDD checklist
 - [ ] Test run output captured for reference
 
 ### Summary Provided
@@ -279,9 +280,9 @@ Before starting this workflow, verify:
 All of the following must be true before marking this workflow as complete:
 
 - [ ] **Story acceptance criteria analyzed** and mapped to appropriate test levels
-- [ ] **Failing tests created** at all appropriate levels (E2E, API, Component)
+- [ ] **Red-phase test scaffolds created** at all appropriate levels (E2E, API, Component)
 - [ ] **Given-When-Then format** used consistently across all tests
-- [ ] **RED phase verified** by local test run (all tests failing as expected)
+- [ ] **RED phase verified** by scaffold generation plus task-by-task activation guidance
 - [ ] **Network-first pattern** applied to E2E tests with network requests
 - [ ] **Data factories created** using faker (no hardcoded test data)
 - [ ] **Fixtures created** with auto-cleanup in teardown

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-atdd/instructions.md

@@ -8,7 +8,7 @@
 
 ## Overview
 
-Generates **failing acceptance tests** before implementation (TDD red phase), plus an implementation checklist. Produces tests at appropriate levels (E2E/API/Component) with supporting fixtures and helpers.
+Generates **red-phase acceptance test scaffolds** before implementation (TDD red phase), plus an implementation checklist. Produces tests at appropriate levels (E2E/API/Component) with supporting fixtures and helpers.
 
 ---
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-atdd/steps-c/step-01-preflight-and-context.md

@@ -1,7 +1,7 @@
 ---
 name: 'step-01-preflight-and-context'
 description: 'Verify prerequisites and load story, framework, and knowledge base'
-outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
+outputFile: '{test_artifacts}/atdd-checklist-{story_key}.md'
 nextStepFile: './step-02-generation-mode.md'
 knowledgeIndex: './resources/tea-index.csv'
 ---
@@ -10,7 +10,7 @@ knowledgeIndex: './resources/tea-index.csv'
 
 ## STEP GOAL
 
-Verify prerequisites and load all required inputs before generating failing tests.
+Verify prerequisites and load all required inputs before generating red-phase acceptance test scaffolds.
 
 ## MANDATORY EXECUTION RULES
 
@@ -71,6 +71,17 @@ If any are missing: **HALT** and notify the user.
 - Read story markdown from `{story_file}` (or ask user if not provided)
 - Extract acceptance criteria and constraints
 - Identify affected components and integrations
+- Derive and store `story_key` from the story filename when available (for BMM stories, this is the filename without `.md`, e.g. `1-2-user-authentication`)
+- Derive and store `story_id` from story metadata, the H1 heading, or the filename when available (for BMM stories, this is typically `{epic_num}.{story_num}`)
+- If a filename-based `story_key` is not available, create and persist a stable slug from the story title:
+  - lowercase the title
+  - collapse runs of whitespace to single `-`
+  - strip all non-alphanumeric and non-hyphen characters
+  - trim leading/trailing hyphens
+  - truncate to a safe max length (64 chars)
+- Use that slug as `story_key` and for `{outputFile}` basename so all checklist and handoff paths stay consistent
+- If `story_id` is still unavailable after metadata/H1/filename parsing, set it to the final `story_key` so `story_id` is never empty
+- Preserve `{story_file}` as a tracked artifact path for later handoff into BMM `dev-story`
 
 ---
 
@@ -210,7 +221,14 @@ Summarize loaded inputs and confirm with the user. Then proceed.
   - Set `lastSaved: '{date}'`
   - Append this step's output to the appropriate section.
 
-**Update `inputDocuments`**: Set `inputDocuments` in the output template frontmatter to the list of artifact paths loaded in this step (e.g., knowledge fragments, test design documents, configuration files).
+**Update frontmatter fields**:
+
+- Set `storyId` to `{story_id}`
+- Set `storyKey` to `{story_key}`
+- Set `storyFile` to `{story_file}`
+- Set `atddChecklistPath` to `{outputFile}`
+- Initialize `generatedTestFiles` to `[]`
+- Set `inputDocuments` to the list of artifact paths loaded in this step (e.g., knowledge fragments, test design documents, configuration files)
 
 Load next step: `{nextStepFile}`
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-atdd/steps-c/step-01b-resume.md

@@ -1,7 +1,7 @@
 ---
 name: 'step-01b-resume'
 description: 'Resume interrupted workflow from last completed step'
-outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
+outputFile: '{test_artifacts}/atdd-checklist-{story_key}.md'
 ---
 
 # Step 1b: Resume Workflow

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-atdd/steps-c/step-02-generation-mode.md

@@ -1,7 +1,7 @@
 ---
 name: 'step-02-generation-mode'
 description: 'Choose AI generation or recording mode'
-outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
+outputFile: '{test_artifacts}/atdd-checklist-{story_key}.md'
 nextStepFile: './step-03-test-strategy.md'
 ---
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-atdd/steps-c/step-03-test-strategy.md

@@ -1,7 +1,7 @@
 ---
 name: 'step-03-test-strategy'
 description: 'Map acceptance criteria to test levels and priorities'
-outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
+outputFile: '{test_artifacts}/atdd-checklist-{story_key}.md'
 nextStepFile: './step-04-generate-tests.md'
 ---
 

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-atdd/steps-c/step-04-generate-tests.md

@@ -1,14 +1,14 @@
 ---
 name: 'step-04-generate-tests'
-description: 'Orchestrate adaptive FAILING test generation (TDD red phase)'
+description: 'Orchestrate adaptive red-phase test scaffold generation (TDD red phase)'
 nextStepFile: './step-04c-aggregate.md'
 ---
 
-# Step 4: Orchestrate Adaptive FAILING Test Generation
+# Step 4: Orchestrate Adaptive Red-Phase Test Scaffold Generation
 
 ## STEP GOAL
 
-Select execution mode deterministically, then generate FAILING API and E2E tests (TDD RED PHASE) with consistent output contracts across agent-team, subagent, or sequential execution.
+Select execution mode deterministically, then generate red-phase API and E2E test scaffolds (TDD RED PHASE) with consistent output contracts across agent-team, subagent, or sequential execution.
 
 ## MANDATORY EXECUTION RULES
 
@@ -16,10 +16,10 @@ Select execution mode deterministically, then generate FAILING API and E2E tests
 - ✅ Speak in `{communication_language}`
 - ✅ Resolve execution mode from config (`tea_execution_mode`, `tea_capability_probe`)
 - ✅ Apply fallback rules deterministically when requested mode is unsupported
-- ✅ Generate FAILING tests only (TDD red phase)
+- ✅ Generate red-phase test scaffolds only (TDD red phase)
 - ✅ Wait for required worker steps to complete
 - ❌ Do NOT skip capability checks when probing is enabled
-- ❌ Do NOT generate passing tests (this is red phase)
+- ❌ Do NOT generate active passing tests (this is red phase)
 - ❌ Do NOT proceed until required worker steps finish
 
 ---
@@ -162,7 +162,7 @@ If probing is disabled, honor the requested mode strictly. If that mode cannot b
 
 ---
 
-### 3. Dispatch Worker A: Failing API Test Generation
+### 3. Dispatch Worker A: Red-Phase API Test Generation
 
 **Dispatch worker:**
 
@@ -172,21 +172,21 @@ If probing is disabled, honor the requested mode strictly. If that mode cannot b
 - **Execution:**
   - `agent-team` or `subagent`: launch non-blocking
   - `sequential`: run blocking and wait before next dispatch
-- **TDD Phase:** RED (failing tests)
+- **TDD Phase:** RED (scaffold tests with `test.skip()`)
 
 **System Action:**
 
 ```
-🚀 Launching Subagent A: FAILING API Test Generation (RED PHASE)
+🚀 Launching Subagent A: RED-PHASE API Test Generation
 📝 Output: /tmp/tea-atdd-api-tests-${timestamp}.json
 ⚙️ Mode: ${resolvedMode}
-🔴 TDD Phase: RED (tests will fail until feature implemented)
+🔴 TDD Phase: RED (tests emitted as `test.skip()` scaffolds)
 ⏳ Status: Running...
 ```
 
 ---
 
-### 4. Dispatch Worker B: Failing E2E Test Generation
+### 4. Dispatch Worker B: Red-Phase E2E Test Generation
 
 **Dispatch worker:**
 
@@ -196,15 +196,15 @@ If probing is disabled, honor the requested mode strictly. If that mode cannot b
 - **Execution:**
   - `agent-team` or `subagent`: launch non-blocking
   - `sequential`: run blocking and wait before next dispatch
-- **TDD Phase:** RED (failing tests)
+- **TDD Phase:** RED (scaffold tests with `test.skip()`)
 
 **System Action:**
 
 ```
-🚀 Launching Subagent B: FAILING E2E Test Generation (RED PHASE)
+🚀 Launching Subagent B: RED-PHASE E2E Test Generation
 📝 Output: /tmp/tea-atdd-e2e-tests-${timestamp}.json
 ⚙️ Mode: ${resolvedMode}
-🔴 TDD Phase: RED (tests will fail until feature implemented)
+🔴 TDD Phase: RED (tests emitted as `test.skip()` scaffolds)
 ⏳ Status: Running...
 ```
 
@@ -251,14 +251,15 @@ if (!apiOutputExists || !e2eOutputExists) {
 **Display TDD status:**
 
 ```
-🔴 TDD RED PHASE: Failing Tests Generated
+🔴 TDD RED PHASE: Test Scaffolds Generated
 
 ✅ Both subagents completed:
 - API Tests: Generated with test.skip()
 - E2E Tests: Generated with test.skip()
 
 📋 All tests assert EXPECTED behavior
-📋 All tests will FAIL until feature implemented
+📋 Activated tests will FAIL until feature is implemented
+📋 Scaffolds stay skipped until a developer activates the current task
 📋 This is INTENTIONAL (TDD red phase)
 
 Next: Aggregation will verify TDD compliance
@@ -300,8 +301,8 @@ The aggregation step (4C) will:
 
 Proceed to Step 4C (Aggregation) when:
 
-- ✅ Subagent A (API failing tests) completed successfully
-- ✅ Subagent B (E2E failing tests) completed successfully
+- ✅ Subagent A (API red-phase tests) completed successfully
+- ✅ Subagent B (E2E red-phase tests) completed successfully
 - ✅ Both output files exist and are valid JSON
 - ✅ TDD red phase status reported
 
@@ -309,7 +310,7 @@ Proceed to Step 4C (Aggregation) when:
 
 - ❌ One or both subagents failed
 - ❌ Output files missing or corrupted
-- ❌ Subagent generated passing tests (wrong - must be failing)
+- ❌ Subagent generated active passing tests (wrong - must be red-phase scaffolds)
 
 ---
 
@@ -331,4 +332,4 @@ Proceed to Step 4C (Aggregation) when:
 - Tests generated without test.skip() (wrong phase)
 - Unsupported requested mode with probing disabled
 
-**Master Rule:** TDD RED PHASE requires FAILING tests (with test.skip()). Mode selection changes orchestration, never red-phase requirements.
+**Master Rule:** TDD RED PHASE requires acceptance test scaffolds marked with `test.skip()`. Mode selection changes orchestration, never red-phase requirements.

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-atdd/steps-c/step-04a-subagent-api-failing.md

@@ -1,15 +1,15 @@
 ---
 name: 'step-04a-subagent-api-failing'
-description: 'Subagent: Generate FAILING API tests (TDD red phase)'
+description: 'Subagent: Generate red-phase API test scaffolds (TDD red phase)'
 subagent: true
 outputFile: '/tmp/tea-atdd-api-tests-{{timestamp}}.json'
 ---
 
-# Subagent 4A: Generate Failing API Tests (TDD Red Phase)
+# Subagent 4A: Generate Red-Phase API Test Scaffolds (TDD Red Phase)
 
 ## SUBAGENT CONTEXT
 
-This is an **isolated subagent** running in parallel with E2E failing test generation.
+This is an **isolated subagent** running in parallel with E2E red-phase test generation.
 
 **What you have from parent workflow:**
 
@@ -21,19 +21,19 @@ This is an **isolated subagent** running in parallel with E2E failing test gener
 
 **If `use_pactjs_utils` is enabled:** Also generate consumer contract tests alongside API tests. Use the loaded pactjs-utils fragments (`pactjs-utils-overview`, `pactjs-utils-consumer-helpers`, `pactjs-utils-provider-verifier`, `pactjs-utils-request-filter`, `pact-consumer-di`) for patterns. If `pact_mcp` is `"mcp"`, use SmartBear MCP tools (Fetch Provider States, Generate Pact Tests) to inform test generation.
 
-**Your task:** Generate API tests that will FAIL because the feature is not implemented yet (TDD RED PHASE).
+**Your task:** Generate API test scaffolds for the feature's expected behavior. They stay in `test.skip()` until the developer activates them for the current task (TDD RED PHASE).
 
 ---
 
 ## MANDATORY EXECUTION RULES
 
 - 📖 Read this entire subagent file before acting
-- ✅ Generate FAILING API tests ONLY
-- ✅ Tests MUST fail when run (feature not implemented yet)
+- ✅ Generate red-phase API test scaffolds ONLY
+- ✅ Tests MUST be emitted with `test.skip()` until the developer activates them
 - ✅ Output structured JSON to temp file
 - ✅ Follow knowledge fragment patterns
 - ❌ Do NOT generate E2E tests (that's subagent 4B)
-- ❌ Do NOT generate passing tests (this is TDD red phase)
+- ❌ Do NOT generate active passing tests (this is TDD red phase)
 - ❌ Do NOT run tests (that's step 5)
 
 ---
@@ -59,7 +59,7 @@ Story: User Registration
 - System returns 422 Unprocessable Entity if validation fails
 ```
 
-### 2. Generate FAILING API Test Files
+### 2. Generate Red-Phase API Test Files
 
 For each API endpoint, create test file in `tests/api/[feature].spec.ts`:
 
@@ -108,7 +108,7 @@ test.describe('[Story Name] API Tests (ATDD)', () => {
 
 **CRITICAL ATDD Requirements:**
 
-- ✅ Use `test.skip()` to mark tests as intentionally failing (red phase)
+- ✅ Use `test.skip()` to mark tests as red-phase scaffolds
 - ✅ Write assertions for EXPECTED behavior (even though not implemented)
 - ✅ Use realistic test data (not placeholder data)
 - ✅ Test both happy path and error scenarios from acceptance criteria
@@ -213,7 +213,7 @@ Write JSON to temp file: `/tmp/tea-atdd-api-tests-{{timestamp}}.json`
     {
       "file": "tests/api/user-registration.spec.ts",
       "content": "[full TypeScript test file content with test.skip()]",
-      "description": "ATDD API tests for user registration (RED PHASE)",
+      "description": "ATDD API test scaffolds for user registration (RED PHASE)",
       "expected_to_fail": true,
       "acceptance_criteria_covered": [
         "User can register with email/password",
@@ -239,7 +239,7 @@ Write JSON to temp file: `/tmp/tea-atdd-api-tests-{{timestamp}}.json`
   "test_count": 3,
   "tdd_phase": "RED",
   "provider_scrutiny": "completed",
-  "summary": "Generated 3 FAILING API tests for user registration story"
+  "summary": "Generated 3 red-phase API test scaffolds for user registration story"
 }
 ```
 
@@ -263,7 +263,7 @@ Write JSON to temp file: `/tmp/tea-atdd-api-tests-{{timestamp}}.json`
 Subagent completes when:
 
 - ✅ All API endpoints from acceptance criteria have test files
-- ✅ All tests use `test.skip()` (documented failing tests)
+- ✅ All tests use `test.skip()` (documented red-phase scaffolds)
 - ✅ All tests assert EXPECTED behavior (not placeholder assertions)
 - ✅ JSON output written to temp file
 - ✅ Fixture needs to be tracked
@@ -286,7 +286,7 @@ Subagent completes when:
 
 ### ❌ FAILURE:
 
-- Generated passing tests (wrong - this is RED phase)
+- Generated active passing tests (wrong - this is RED phase)
 - Tests without test.skip() (will break CI)
 - Placeholder assertions (expect(true).toBe(true))
 - Did not follow knowledge fragment patterns

package/lib/bmad-cache/tea/src/workflows/testarch/bmad-testarch-atdd/steps-c/step-04b-subagent-e2e-failing.md

@@ -1,15 +1,15 @@
 ---
 name: 'step-04b-subagent-e2e-failing'
-description: 'Subagent: Generate FAILING E2E tests (TDD red phase)'
+description: 'Subagent: Generate red-phase E2E test scaffolds (TDD red phase)'
 subagent: true
 outputFile: '/tmp/tea-atdd-e2e-tests-{{timestamp}}.json'
 ---
 
-# Subagent 4B: Generate Failing E2E Tests (TDD Red Phase)
+# Subagent 4B: Generate Red-Phase E2E Test Scaffolds (TDD Red Phase)
 
 ## SUBAGENT CONTEXT
 
-This is an **isolated subagent** running in parallel with API failing test generation.
+This is an **isolated subagent** running in parallel with API red-phase test generation.
 
 **What you have from parent workflow:**
 
@@ -18,19 +18,19 @@ This is an **isolated subagent** running in parallel with API failing test gener
 - Knowledge fragments loaded: fixture-architecture, network-first, selector-resilience
 - Config: test framework, Playwright Utils enabled/disabled
 
-**Your task:** Generate E2E tests that will FAIL because the feature UI is not implemented yet (TDD RED PHASE).
+**Your task:** Generate E2E test scaffolds for the feature's expected UI behavior. They stay in `test.skip()` until the developer activates them for the current task (TDD RED PHASE).
 
 ---
 
 ## MANDATORY EXECUTION RULES
 
 - 📖 Read this entire subagent file before acting
-- ✅ Generate FAILING E2E tests ONLY
-- ✅ Tests MUST fail when run (UI not implemented yet)
+- ✅ Generate red-phase E2E test scaffolds ONLY
+- ✅ Tests MUST be emitted with `test.skip()` until the developer activates them
 - ✅ Output structured JSON to temp file
 - ✅ Follow knowledge fragment patterns
 - ❌ Do NOT generate API tests (that's subagent 4A)
-- ❌ Do NOT generate passing tests (this is TDD red phase)
+- ❌ Do NOT generate active passing tests (this is TDD red phase)
 - ❌ Do NOT run tests (that's step 5)
 
 ---
@@ -89,7 +89,7 @@ If `none`:
 
 - Generate selectors from best practices without browser verification
 
-### 3. Generate FAILING E2E Test Files
+### 3. Generate Red-Phase E2E Test Files
 
 For each user journey, create test file in `tests/e2e/[feature].spec.ts`:
 
@@ -129,7 +129,7 @@ test.describe('[Story Name] E2E User Journey (ATDD)', () => {
 
 **CRITICAL ATDD Requirements:**
 
-- ✅ Use `test.skip()` to mark tests as intentionally failing (red phase)
+- ✅ Use `test.skip()` to mark tests as red-phase scaffolds
 - ✅ Write assertions for EXPECTED UI behavior (even though not implemented)
 - ✅ Use resilient selectors: getByRole, getByText, getByLabel (from selector-resilience)
 - ✅ Follow network-first patterns if API calls involved (from network-first)
@@ -169,7 +169,7 @@ Write JSON to temp file: `/tmp/tea-atdd-e2e-tests-{{timestamp}}.json`
     {
       "file": "tests/e2e/user-registration.spec.ts",
       "content": "[full TypeScript test file content with test.skip()]",
-      "description": "ATDD E2E tests for user registration journey (RED PHASE)",
+      "description": "ATDD E2E test scaffolds for user registration journey (RED PHASE)",
       "expected_to_fail": true,
       "acceptance_criteria_covered": [
         "User can navigate to /register",
@@ -189,7 +189,7 @@ Write JSON to temp file: `/tmp/tea-atdd-e2e-tests-{{timestamp}}.json`
   "knowledge_fragments_used": ["fixture-architecture", "network-first", "selector-resilience"],
   "test_count": 2,
   "tdd_phase": "RED",
-  "summary": "Generated 2 FAILING E2E tests for user registration story"
+  "summary": "Generated 2 red-phase E2E test scaffolds for user registration story"
 }
 ```
 
@@ -213,7 +213,7 @@ Write JSON to temp file: `/tmp/tea-atdd-e2e-tests-{{timestamp}}.json`
 Subagent completes when:
 
 - ✅ All user journeys from acceptance criteria have test files
-- ✅ All tests use `test.skip()` (documented failing tests)
+- ✅ All tests use `test.skip()` (documented red-phase scaffolds)
 - ✅ All tests assert EXPECTED UI behavior (not placeholder assertions)
 - ✅ Resilient selectors used (getByRole, getByText)
 - ✅ JSON output written to temp file
@@ -236,7 +236,7 @@ Subagent completes when:
 
 ### ❌ FAILURE:
 
-- Generated passing tests (wrong - this is RED phase)
+- Generated active passing tests (wrong - this is RED phase)
 - Tests without test.skip() (will break CI)
 - Placeholder assertions (expect(true).toBe(true))
 - Brittle selectors used (CSS classes, XPath)