bmad-studio 0.1.0 → 0.2.0

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

@@ -1,96 +0,0 @@
----
-name: 'step-01b-resume'
-description: 'Resume interrupted workflow from last completed step'
-outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
----
-
-# Step 1b: Resume Workflow
-
-## STEP GOAL
-
-Resume an interrupted workflow by loading the existing output document, displaying progress, and routing to the next incomplete step.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 Read the entire step file before acting
-- ✅ Speak in `{communication_language}`
-
----
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow the MANDATORY SEQUENCE exactly
-- 📖 Load the next step only when instructed
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Output document with progress frontmatter
-- Focus: Load progress and route to next step
-- Limits: Do not re-execute completed steps
-- Dependencies: Output document must exist from a previous run
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly.
-
-### 1. Load Output Document
-
-Read `{outputFile}` and parse YAML frontmatter for:
-
-- `stepsCompleted` — array of completed step names
-- `lastStep` — last completed step name
-- `lastSaved` — timestamp of last save
-
-**If `{outputFile}` does not exist**, display:
-
-"⚠️ **No previous progress found.** There is no output document to resume from. Please use **[C] Create** to start a fresh workflow run."
-
-**THEN:** Halt. Do not proceed.
-
----
-
-### 2. Display Progress Dashboard
-
-Display progress with ✅/⬜ indicators:
-
-1. ✅/⬜ Preflight & Context (step-01-preflight-and-context)
-2. ✅/⬜ Generation Mode (step-02-generation-mode)
-3. ✅/⬜ Test Strategy (step-03-test-strategy)
-4. ✅/⬜ Generate Tests + Aggregate (step-04c-aggregate)
-5. ✅/⬜ Validate & Complete (step-05-validate-and-complete)
-
----
-
-### 3. Route to Next Step
-
-Based on `lastStep`, load the next incomplete step:
-
-- `'step-01-preflight-and-context'` → load `./step-02-generation-mode.md`
-- `'step-02-generation-mode'` → load `./step-03-test-strategy.md`
-- `'step-03-test-strategy'` → load `./step-04-generate-tests.md`
-- `'step-04c-aggregate'` → load `./step-05-validate-and-complete.md`
-- `'step-05-validate-and-complete'` → **Workflow already complete.** Display: "✅ **All steps completed.** Use **[V] Validate** to review outputs or **[E] Edit** to make revisions." Then halt.
-
-**If `lastStep` does not match any value above**, display: "⚠️ **Unknown progress state** (`lastStep`: {lastStep}). Please use **[C] Create** to start fresh." Then halt.
-
-**Otherwise**, load the identified step file, read completely, and execute.
-
-The existing content in `{outputFile}` provides context from previously completed steps.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Output document loaded and parsed correctly
-- Progress dashboard displayed accurately
-- Routed to correct next step
-
-### ❌ SYSTEM FAILURE:
-
-- Not loading output document
-- Incorrect progress display
-- Routing to wrong step
-
-**Master Rule:** Resume MUST route to the exact next incomplete step. Never re-execute completed steps.

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

@@ -1,125 +0,0 @@
----
-name: 'step-02-generation-mode'
-description: 'Choose AI generation or recording mode'
-outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
-nextStepFile: './step-03-test-strategy.md'
----
-
-# Step 2: Generation Mode Selection
-
-## STEP GOAL
-
-Choose the appropriate generation mode for ATDD tests.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 Read the entire step file before acting
-- ✅ Speak in `{communication_language}`
-
----
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow the MANDATORY SEQUENCE exactly
-- 💾 Record outputs before proceeding
-- 📖 Load the next step only when instructed
-
-## CONTEXT BOUNDARIES:
-
-- Available context: config, loaded artifacts, and knowledge fragments
-- Focus: this step's goal only
-- Limits: do not execute future steps
-- Dependencies: prior steps' outputs (if any)
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-## 1. Default Mode: AI Generation
-
-Use AI generation when:
-
-- Acceptance criteria are clear
-- Scenarios are standard (CRUD, auth, API, navigation)
-- **If {detected_stack} is `backend`:** Always use AI generation (no browser recording needed)
-
-Proceed directly to test strategy if this applies.
-
----
-
-## 2. Optional Mode: Recording (Complex UI)
-
-**Skip this section entirely if {detected_stack} is `backend`.** For backend projects, use AI generation from API documentation, OpenAPI/Swagger specs, or source code analysis instead.
-
-**If {detected_stack} is `frontend` or `fullstack`:**
-
-Use recording when UI interactions need live browser verification.
-
-**Tool selection based on `config.tea_browser_automation`:**
-
-If `auto`:
-
-> **Note:** `${timestamp}` is a placeholder the agent should replace with a unique value (e.g., epoch seconds) for session isolation.
-
-- **Simple recording** (snapshot selectors, capture structure): Use CLI
-  - `playwright-cli -s=tea-atdd-${timestamp} open <url>` → `playwright-cli -s=tea-atdd-${timestamp} snapshot` → extract refs
-- **Complex recording** (drag/drop, wizards, multi-step state): Use MCP
-  - Full browser automation with rich tool semantics
-- **Fallback:** If preferred tool unavailable, use the other; if neither, skip recording
-
-If `cli`:
-
-- Use Playwright CLI for all recording
-- `playwright-cli -s=tea-atdd-${timestamp} open <url>`, `snapshot`, `screenshot`, `click <ref>`, etc.
-
-If `mcp`:
-
-- Use Playwright MCP tools for all recording (current behavior)
-- Confirm MCP availability, record selectors and interactions
-
-If `none`:
-
-- Skip recording mode entirely, use AI generation from documentation
-
----
-
-## 3. Confirm Mode
-
-State the chosen mode and why. Then proceed.
-
----
-
-## 4. Save Progress
-
-**Save this step's accumulated work to `{outputFile}`.**
-
-- **If `{outputFile}` does not exist** (first save), create it with YAML frontmatter:
-
-  ```yaml
-  ---
-  stepsCompleted: ['step-02-generation-mode']
-  lastStep: 'step-02-generation-mode'
-  lastSaved: '{date}'
-  ---
-  ```
-
-  Then write this step's output below the frontmatter.
-
-- **If `{outputFile}` already exists**, update:
-  - Add `'step-02-generation-mode'` to `stepsCompleted` array (only if not already present)
-  - Set `lastStep: 'step-02-generation-mode'`
-  - Set `lastSaved: '{date}'`
-  - Append this step's output to the appropriate section.
-
-Load next step: `{nextStepFile}`
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
-
-### ✅ SUCCESS:
-
-- Step completed in full with required outputs
-
-### ❌ SYSTEM FAILURE:
-
-- Skipped sequence steps or missing outputs
-  **Master Rule:** Skipping steps is FORBIDDEN.

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

@@ -1,110 +0,0 @@
----
-name: 'step-03-test-strategy'
-description: 'Map acceptance criteria to test levels and priorities'
-outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
-nextStepFile: './step-04-generate-tests.md'
----
-
-# Step 3: Test Strategy
-
-## STEP GOAL
-
-Translate acceptance criteria into a prioritized, level-appropriate test plan.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 Read the entire step file before acting
-- ✅ Speak in `{communication_language}`
-- 🚫 Avoid duplicate coverage across levels
-
----
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow the MANDATORY SEQUENCE exactly
-- 💾 Record outputs before proceeding
-- 📖 Load the next step only when instructed
-
-## CONTEXT BOUNDARIES:
-
-- Available context: config, loaded artifacts, and knowledge fragments
-- Focus: this step's goal only
-- Limits: do not execute future steps
-- Dependencies: prior steps' outputs (if any)
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-## 1. Map Acceptance Criteria
-
-- Convert each acceptance criterion into test scenarios
-- Include negative and edge cases where risk is high
-
----
-
-## 2. Select Test Levels
-
-Choose the best level per scenario based on `{detected_stack}`:
-
-**If {detected_stack} is `frontend` or `fullstack`:**
-
-- **E2E** for critical user journeys
-- **API** for business logic and service contracts
-- **Component** for UI behavior
-
-**If {detected_stack} is `backend` or `fullstack`:**
-
-- **Unit** for pure functions, business logic, and edge cases
-- **Integration** for service interactions, database queries, and middleware
-- **API/Contract** for endpoint validation, request/response schemas, and Pact contracts
-- **No E2E** for pure backend projects (no browser-based testing needed)
-
----
-
-## 3. Prioritize Tests
-
-Assign P0–P3 priorities using risk and business impact.
-
----
-
-## 4. Confirm Red Phase Requirements
-
-Ensure all tests are designed to **fail before implementation** (TDD red phase).
-
----
-
-## 5. Save Progress
-
-**Save this step's accumulated work to `{outputFile}`.**
-
-- **If `{outputFile}` does not exist** (first save), create it with YAML frontmatter:
-
-  ```yaml
-  ---
-  stepsCompleted: ['step-03-test-strategy']
-  lastStep: 'step-03-test-strategy'
-  lastSaved: '{date}'
-  ---
-  ```
-
-  Then write this step's output below the frontmatter.
-
-- **If `{outputFile}` already exists**, update:
-  - Add `'step-03-test-strategy'` to `stepsCompleted` array (only if not already present)
-  - Set `lastStep: 'step-03-test-strategy'`
-  - Set `lastSaved: '{date}'`
-  - Append this step's output to the appropriate section.
-
-Load next step: `{nextStepFile}`
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
-
-### ✅ SUCCESS:
-
-- Step completed in full with required outputs
-
-### ❌ SYSTEM FAILURE:
-
-- Skipped sequence steps or missing outputs
-  **Master Rule:** Skipping steps is FORBIDDEN.

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

@@ -1,334 +0,0 @@
----
-name: 'step-04-generate-tests'
-description: 'Orchestrate adaptive FAILING test generation (TDD red phase)'
-nextStepFile: './step-04c-aggregate.md'
----
-
-# Step 4: Orchestrate Adaptive FAILING Test 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.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 Read the entire step file before acting
-- ✅ 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)
-- ✅ 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 proceed until required worker steps finish
-
----
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow the MANDATORY SEQUENCE exactly
-- 💾 Wait for subagent outputs
-- 📖 Load the next step only when instructed
-
-## CONTEXT BOUNDARIES:
-
-- Available context: config, acceptance criteria from Step 1, test strategy from Step 3
-- Focus: orchestration only (mode selection + worker dispatch)
-- Limits: do not generate tests directly (delegate to worker steps)
-- Dependencies: Steps 1-3 outputs
-
----
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-### 1. Prepare Execution Context
-
-**Generate unique timestamp** for temp file naming:
-
-```javascript
-const timestamp = new Date().toISOString().replace(/[:.]/g, '-');
-```
-
-**Prepare input context for both subagents:**
-
-```javascript
-const parseBooleanFlag = (value, defaultValue = true) => {
-  if (typeof value === 'string') {
-    const normalized = value.trim().toLowerCase();
-    if (['false', '0', 'off', 'no'].includes(normalized)) return false;
-    if (['true', '1', 'on', 'yes'].includes(normalized)) return true;
-  }
-  if (value === undefined || value === null) return defaultValue;
-  return Boolean(value);
-};
-
-const subagentContext = {
-  story_acceptance_criteria: /* from Step 1 */,
-  test_strategy: /* from Step 3 */,
-  knowledge_fragments_loaded: /* list of fragments */,
-  config: {
-    test_framework: config.test_framework,
-    use_playwright_utils: config.tea_use_playwright_utils,
-    use_pactjs_utils: config.tea_use_pactjs_utils,
-    pact_mcp: config.tea_pact_mcp,  // "mcp" | "none"
-    browser_automation: config.tea_browser_automation,
-    execution_mode: config.tea_execution_mode || 'auto',  // "auto" | "subagent" | "agent-team" | "sequential"
-    capability_probe: parseBooleanFlag(config.tea_capability_probe, true),  // supports booleans and "false"/"true" strings
-    provider_endpoint_map: /* from Step 1/3 context, if use_pactjs_utils enabled */,
-  },
-  timestamp: timestamp
-};
-```
-
----
-
-### 2. Resolve Execution Mode with Capability Probe
-
-```javascript
-const normalizeUserExecutionMode = (mode) => {
-  if (typeof mode !== 'string') return null;
-  const normalized = mode.trim().toLowerCase().replace(/[-_]/g, ' ').replace(/\s+/g, ' ');
-
-  if (normalized === 'auto') return 'auto';
-  if (normalized === 'sequential') return 'sequential';
-  if (normalized === 'subagent' || normalized === 'sub agent' || normalized === 'subagents' || normalized === 'sub agents') {
-    return 'subagent';
-  }
-  if (normalized === 'agent team' || normalized === 'agent teams' || normalized === 'agentteam') {
-    return 'agent-team';
-  }
-
-  return null;
-};
-
-const normalizeConfigExecutionMode = (mode) => {
-  if (mode === 'subagent') return 'subagent';
-  if (mode === 'auto' || mode === 'sequential' || mode === 'subagent' || mode === 'agent-team') {
-    return mode;
-  }
-  return null;
-};
-
-// Explicit user instruction in the active run takes priority over config.
-const explicitModeFromUser = normalizeUserExecutionMode(runtime.getExplicitExecutionModeHint?.() || null);
-
-const requestedMode = explicitModeFromUser || normalizeConfigExecutionMode(subagentContext.config.execution_mode) || 'auto';
-const probeEnabled = subagentContext.config.capability_probe;
-
-const supports = {
-  subagent: runtime.canLaunchSubagents?.() === true,
-  agentTeam: runtime.canLaunchAgentTeams?.() === true,
-};
-
-let resolvedMode = requestedMode;
-
-if (requestedMode === 'auto') {
-  if (supports.agentTeam) resolvedMode = 'agent-team';
-  else if (supports.subagent) resolvedMode = 'subagent';
-  else resolvedMode = 'sequential';
-} else if (probeEnabled && requestedMode === 'agent-team' && !supports.agentTeam) {
-  resolvedMode = supports.subagent ? 'subagent' : 'sequential';
-} else if (probeEnabled && requestedMode === 'subagent' && !supports.subagent) {
-  resolvedMode = 'sequential';
-}
-
-subagentContext.execution = {
-  requestedMode,
-  resolvedMode,
-  probeEnabled,
-  supports,
-};
-
-if (!probeEnabled && (requestedMode === 'agent-team' || requestedMode === 'subagent')) {
-  const unsupportedRequestedMode =
-    (requestedMode === 'agent-team' && !supports.agentTeam) || (requestedMode === 'subagent' && !supports.subagent);
-
-  if (unsupportedRequestedMode) {
-    subagentContext.execution.error = `Requested execution mode "${requestedMode}" is unavailable because capability probing is disabled.`;
-    throw new Error(subagentContext.execution.error);
-  }
-}
-```
-
-Resolution precedence:
-
-1. Explicit user request in this run (`agent team` => `agent-team`; `subagent` => `subagent`; `sequential`; `auto`)
-2. `tea_execution_mode` from config
-3. Runtime capability fallback (when probing enabled)
-
-If probing is disabled, honor the requested mode strictly. If that mode cannot be executed at runtime, fail with explicit error instead of silent fallback.
-
----
-
-### 3. Dispatch Worker A: Failing API Test Generation
-
-**Dispatch worker:**
-
-- **Subagent File:** `./step-04a-subagent-api-failing.md`
-- **Output File:** `/tmp/tea-atdd-api-tests-${timestamp}.json`
-- **Context:** Pass `subagentContext`
-- **Execution:**
-  - `agent-team` or `subagent`: launch non-blocking
-  - `sequential`: run blocking and wait before next dispatch
-- **TDD Phase:** RED (failing tests)
-
-**System Action:**
-
-```
-🚀 Launching Subagent A: FAILING API Test Generation (RED PHASE)
-📝 Output: /tmp/tea-atdd-api-tests-${timestamp}.json
-⚙️ Mode: ${resolvedMode}
-🔴 TDD Phase: RED (tests will fail until feature implemented)
-⏳ Status: Running...
-```
-
----
-
-### 4. Dispatch Worker B: Failing E2E Test Generation
-
-**Dispatch worker:**
-
-- **Subagent File:** `./step-04b-subagent-e2e-failing.md`
-- **Output File:** `/tmp/tea-atdd-e2e-tests-${timestamp}.json`
-- **Context:** Pass `subagentContext`
-- **Execution:**
-  - `agent-team` or `subagent`: launch non-blocking
-  - `sequential`: run blocking and wait before next dispatch
-- **TDD Phase:** RED (failing tests)
-
-**System Action:**
-
-```
-🚀 Launching Subagent B: FAILING E2E Test Generation (RED PHASE)
-📝 Output: /tmp/tea-atdd-e2e-tests-${timestamp}.json
-⚙️ Mode: ${resolvedMode}
-🔴 TDD Phase: RED (tests will fail until feature implemented)
-⏳ Status: Running...
-```
-
----
-
-### 5. Wait for Required Worker Completion
-
-**If `resolvedMode` is `agent-team` or `subagent`:**
-
-```
-⏳ Waiting for subagents to complete...
-  ├── Subagent A (API RED): Running... ⟳
-  └── Subagent B (E2E RED): Running... ⟳
-
-[... time passes ...]
-
-  ├── Subagent A (API RED): Complete ✅
-  └── Subagent B (E2E RED): Complete ✅
-
-✅ All subagents completed successfully!
-```
-
-**If `resolvedMode` is `sequential`:**
-
-```
-✅ Sequential mode: each worker already completed during dispatch.
-```
-
-**Verify both outputs exist:**
-
-```javascript
-const apiOutputExists = fs.existsSync(`/tmp/tea-atdd-api-tests-${timestamp}.json`);
-const e2eOutputExists = fs.existsSync(`/tmp/tea-atdd-e2e-tests-${timestamp}.json`);
-
-if (!apiOutputExists || !e2eOutputExists) {
-  throw new Error('One or both subagent outputs missing!');
-}
-```
-
----
-
-### 6. TDD Red Phase Report
-
-**Display TDD status:**
-
-```
-🔴 TDD RED PHASE: Failing Tests 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
-📋 This is INTENTIONAL (TDD red phase)
-
-Next: Aggregation will verify TDD compliance
-```
-
----
-
-### 7. Execution Report
-
-**Display performance metrics:**
-
-```
-🚀 Performance Report:
-- Execution Mode: {resolvedMode}
-- API Test Generation: ~X minutes
-- E2E Test Generation: ~Y minutes
-- Total Elapsed: ~mode-dependent
-- Parallel Gain: ~50% faster when mode is subagent/agent-team
-```
-
----
-
-### 8. Proceed to Aggregation
-
-**Load aggregation step:**
-Load next step: `{nextStepFile}`
-
-The aggregation step (4C) will:
-
-- Read both subagent outputs
-- Verify TDD red phase compliance (all tests have test.skip())
-- Write all test files to disk
-- Generate ATDD checklist
-- Calculate summary statistics
-
----
-
-## EXIT CONDITION
-
-Proceed to Step 4C (Aggregation) when:
-
-- ✅ Subagent A (API failing tests) completed successfully
-- ✅ Subagent B (E2E failing tests) completed successfully
-- ✅ Both output files exist and are valid JSON
-- ✅ TDD red phase status reported
-
-**Do NOT proceed if:**
-
-- ❌ One or both subagents failed
-- ❌ Output files missing or corrupted
-- ❌ Subagent generated passing tests (wrong - must be failing)
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
-
-### ✅ SUCCESS:
-
-- Both subagents launched successfully
-- Both worker steps completed without errors
-- Output files generated and valid
-- Tests generated with test.skip() (TDD red phase)
-- Fallback behavior respected configuration and capability probe rules
-
-### ❌ SYSTEM FAILURE:
-
-- Failed to launch subagents
-- One or both subagents failed
-- Output files missing or invalid
-- 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.