@cregis-dev/cckit 0.3.0 → 0.4.1

package/templates/bmad/tea/workflows/testarch/automate/steps-c/step-03-generate-tests.md

@@ -1,37 +1,38 @@
 ---
 name: 'step-03-generate-tests'
-description: 'Orchestrate parallel test generation via subprocesses'
+description: 'Orchestrate adaptive test generation (agent-team, subagent, or sequential)'
 nextStepFile: './step-03c-aggregate.md'
 ---
 
-# Step 3: Orchestrate Parallel Test Generation
+# Step 3: Orchestrate Adaptive Test Generation
 
 ## STEP GOAL
 
-Launch parallel subprocesses to generate tests simultaneously for maximum performance. Subprocess selection depends on `{detected_stack}`.
+Select execution mode deterministically, then generate tests using agent-team, subagent, or sequential execution while preserving the same output contract. Worker selection depends on `{detected_stack}`.
 
 ## MANDATORY EXECUTION RULES
 
 - 📖 Read the entire step file before acting
 - ✅ Speak in `{communication_language}`
-- ✅ Launch subprocesses in PARALLEL based on `{detected_stack}`
-- ✅ Wait for ALL launched subprocesses to complete
-- ❌ Do NOT generate tests sequentially (use subprocesses)
-- ❌ Do NOT proceed until all subprocesses finish
+- ✅ Resolve execution mode from config (`tea_execution_mode`, `tea_capability_probe`)
+- ✅ Apply fallback rules deterministically when requested mode is unsupported
+- ✅ Preserve output schema and temp file naming across all modes
+- ❌ Do NOT skip capability checks when probing is enabled
+- ❌ Do NOT change output paths or JSON schema by mode
 
 ---
 
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Follow the MANDATORY SEQUENCE exactly
-- 💾 Wait for subprocess outputs
+- 💾 Wait for subagent outputs
 - 📖 Load the next step only when instructed
 
 ## CONTEXT BOUNDARIES:
 
 - Available context: config, coverage plan from Step 2, knowledge fragments
-- Focus: subprocess orchestration only
-- Limits: do not generate tests directly (delegate to subprocesses)
+- Focus: orchestration only (mode selection + worker dispatch)
+- Limits: do not generate tests directly (delegate to worker steps)
 - Dependencies: Step 2 outputs (coverage plan, target features)
 
 ---
@@ -40,7 +41,7 @@ Launch parallel subprocesses to generate tests simultaneously for maximum perfor
 
 **CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
 
-### 1. Prepare Subprocess Inputs
+### 1. Prepare Execution Context
 
 **Generate unique timestamp** for temp file naming:
 
@@ -48,17 +49,31 @@ Launch parallel subprocesses to generate tests simultaneously for maximum perfor
 const timestamp = new Date().toISOString().replace(/[:.]/g, '-');
 ```
 
-**Prepare input context for subprocesses:**
+**Prepare input context for subagents:**
 
 ```javascript
-const subprocessContext = {
+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 = {
   features: /* from Step 2 coverage plan */,
   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,  // "auto" | "cli" | "mcp" | "none"
-    detected_stack: '{detected_stack}'  // "frontend" | "backend" | "fullstack"
+    detected_stack: '{detected_stack}',  // "frontend" | "backend" | "fullstack"
+    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
   },
   timestamp: timestamp
 };
@@ -66,100 +81,217 @@ const subprocessContext = {
 
 ---
 
-### 2. Subprocess Dispatch Matrix
+### 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: false,
+  agentTeam: false,
+};
+
+if (probeEnabled) {
+  // Probe using runtime-native capability checks or a no-op launch test.
+  supports.subagent = runtime.canLaunchSubagents?.() === true;
+  supports.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,
+};
+```
+
+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.
+
+Report selected mode before dispatch:
+
+```
+⚙️ Execution Mode Resolution:
+- Requested: {requestedMode}
+- Probe Enabled: {probeEnabled}
+- Supports agent-team: {supports.agentTeam}
+- Supports subagent: {supports.subagent}
+- Resolved: {resolvedMode}
+```
+
+---
+
+### 3. Subagent Dispatch Matrix
 
-**Select subprocesses based on `{detected_stack}`:**
+**Select subagents based on `{detected_stack}`:**
 
-| `{detected_stack}` | Subprocess A (API) | Subprocess B (E2E) | Subprocess B-backend |
-| ------------------ | ------------------ | ------------------ | -------------------- |
-| `frontend`         | Launch             | Launch             | Skip                 |
-| `backend`          | Launch             | Skip               | Launch               |
-| `fullstack`        | Launch             | Launch             | Launch               |
+| `{detected_stack}` | Subagent A (API) | Subagent B (E2E) | Subagent B-backend |
+| ------------------ | ---------------- | ---------------- | ------------------ |
+| `frontend`         | Launch           | Launch           | Skip               |
+| `backend`          | Launch           | Skip             | Launch             |
+| `fullstack`        | Launch           | Launch           | Launch             |
+
+### 3A. Runtime-Managed Parallelism
+
+When `resolvedMode` is `agent-team` or `subagent`, let the runtime decide concurrency and scheduling. TEA does not impose an additional worker ceiling.
 
 ---
 
-### 3. Launch Subprocess A: API Test Generation (always)
+### Contract Test Generation Note
+
+When `use_pactjs_utils` is enabled, the API test generation subagent (step-03a) also generates:
 
-**Launch subprocess in parallel:**
+- **Consumer contract tests**: Using `createProviderState` for type-safe provider states
+- **Provider verification tests**: Using `buildVerifierOptions` for one-call verifier setup
+- **Message contract tests**: Using `buildMessageVerifierOptions` if async/Kafka patterns detected
+- **Helper files**: Request filter setup with `createRequestFilter`, shared state constants
+
+When `pact_mcp` is `"mcp"`, the subagent can use SmartBear MCP tools to fetch existing provider states and generate tests informed by broker data.
+
+---
 
-- **Subprocess File:** `./step-03a-subprocess-api.md`
+### 4. Dispatch Worker A: API Test Generation (always)
+
+**Dispatch worker:**
+
+- **Subagent File:** `./step-03a-subagent-api.md`
 - **Output File:** `/tmp/tea-automate-api-tests-${timestamp}.json`
-- **Context:** Pass `subprocessContext`
-- **Execution:** PARALLEL (non-blocking)
+- **Context:** Pass `subagentContext`
+- **Execution:**
+  - `agent-team` or `subagent`: launch non-blocking
+  - `sequential`: run blocking and wait before next dispatch
 
 **System Action:**
 
 ```
-🚀 Launching Subprocess A: API Test Generation
+🚀 Launching Subagent A: API Test Generation
 📝 Output: /tmp/tea-automate-api-tests-${timestamp}.json
-⏳ Status: Running in parallel...
+⚙️ Mode: ${resolvedMode}
+⏳ Status: Running...
 ```
 
 ---
 
-### 4. Launch Subprocess B: E2E Test Generation (frontend/fullstack only)
+### 5. Dispatch Worker B: E2E Test Generation (frontend/fullstack only)
 
 **If {detected_stack} is `frontend` or `fullstack`:**
 
-**Launch subprocess in parallel:**
+**Dispatch worker:**
 
-- **Subprocess File:** `./step-03b-subprocess-e2e.md`
+- **Subagent File:** `./step-03b-subagent-e2e.md`
 - **Output File:** `/tmp/tea-automate-e2e-tests-${timestamp}.json`
-- **Context:** Pass `subprocessContext`
-- **Execution:** PARALLEL (non-blocking)
+- **Context:** Pass `subagentContext`
+- **Execution:**
+  - `agent-team` or `subagent`: launch non-blocking
+  - `sequential`: run blocking and wait before next dispatch
 
 **System Action:**
 
 ```
-🚀 Launching Subprocess B: E2E Test Generation
+🚀 Launching Subagent B: E2E Test Generation
 📝 Output: /tmp/tea-automate-e2e-tests-${timestamp}.json
-⏳ Status: Running in parallel...
+⚙️ Mode: ${resolvedMode}
+⏳ Status: Running...
 ```
 
-**If {detected_stack} is `backend`:** Skip this subprocess.
+**If {detected_stack} is `backend`:** Skip this subagent.
 
 ---
 
-### 5. Launch Subprocess B-backend: Backend Test Generation (backend/fullstack only)
+### 6. Dispatch Worker B-backend: Backend Test Generation (backend/fullstack only)
 
 **If {detected_stack} is `backend` or `fullstack`:**
 
-**Launch subprocess in parallel:**
+**Dispatch worker:**
 
-- **Subprocess File:** `./step-03b-subprocess-backend.md`
+- **Subagent File:** `./step-03b-subagent-backend.md`
 - **Output File:** `/tmp/tea-automate-backend-tests-${timestamp}.json`
-- **Context:** Pass `subprocessContext`
-- **Execution:** PARALLEL (non-blocking)
+- **Context:** Pass `subagentContext`
+- **Execution:**
+  - `agent-team` or `subagent`: launch non-blocking
+  - `sequential`: run blocking and wait before next dispatch
 
 **System Action:**
 
 ```
-🚀 Launching Subprocess B-backend: Backend Test Generation
+🚀 Launching Subagent B-backend: Backend Test Generation
 📝 Output: /tmp/tea-automate-backend-tests-${timestamp}.json
-⏳ Status: Running in parallel...
+⚙️ Mode: ${resolvedMode}
+⏳ Status: Running...
 ```
 
-**If {detected_stack} is `frontend`:** Skip this subprocess.
+**If {detected_stack} is `frontend`:** Skip this subagent.
 
 ---
 
-### 6. Wait for All Subprocesses to Complete
+### 7. Wait for Expected Worker Completion
 
-**Monitor subprocess execution based on `{detected_stack}`:**
+**If `resolvedMode` is `agent-team` or `subagent`:**
 
 ```
-⏳ Waiting for subprocesses to complete...
-  ├── Subprocess A (API): Running... ⟳
-  ├── Subprocess B (E2E): Running... ⟳       [if frontend/fullstack]
-  └── Subprocess B-backend: Running... ⟳     [if backend/fullstack]
+⏳ Waiting for subagents to complete...
+  ├── Subagent A (API): Running... ⟳
+  ├── Subagent B (E2E): Running... ⟳       [if frontend/fullstack]
+  └── Subagent B-backend: Running... ⟳     [if backend/fullstack]
 
 [... time passes ...]
 
-  ├── Subprocess A (API): Complete ✅
-  ├── Subprocess B (E2E): Complete ✅         [if frontend/fullstack]
-  └── Subprocess B-backend: Complete ✅       [if backend/fullstack]
+  ├── Subagent A (API): Complete ✅
+  ├── Subagent B (E2E): Complete ✅         [if frontend/fullstack]
+  └── Subagent B-backend: Complete ✅       [if backend/fullstack]
+
+✅ All subagents completed successfully!
+```
+
+**If `resolvedMode` is `sequential`:**
 
-✅ All subprocesses completed successfully!
+```
+✅ Sequential mode: each worker already completed during dispatch.
 ```
 
 **Verify outputs exist (based on `{detected_stack}`):**
@@ -170,71 +302,53 @@ const apiOutputExists = fs.existsSync(`/tmp/tea-automate-api-tests-${timestamp}.
 // Check based on detected_stack
 if (detected_stack === 'frontend' || detected_stack === 'fullstack') {
   const e2eOutputExists = fs.existsSync(`/tmp/tea-automate-e2e-tests-${timestamp}.json`);
-  if (!e2eOutputExists) throw new Error('E2E subprocess output missing!');
+  if (!e2eOutputExists) throw new Error('E2E subagent output missing!');
 }
 if (detected_stack === 'backend' || detected_stack === 'fullstack') {
   const backendOutputExists = fs.existsSync(`/tmp/tea-automate-backend-tests-${timestamp}.json`);
-  if (!backendOutputExists) throw new Error('Backend subprocess output missing!');
+  if (!backendOutputExists) throw new Error('Backend subagent output missing!');
 }
-if (!apiOutputExists) throw new Error('API subprocess output missing!');
+if (!apiOutputExists) throw new Error('API subagent output missing!');
 ```
 
 ---
 
-### Subprocess Output Schema Contract
-
-Both `step-03b-subprocess-e2e.md` and `step-03b-subprocess-backend.md` MUST write JSON to their output file with identical schema:
-
-```json
-{
-  "subprocessType": "e2e | backend",
-  "testsGenerated": [
-    {
-      "file": "path/to/test-file",
-      "content": "[full test file content]",
-      "description": "Test description",
-      "priority_coverage": { "P0": 0, "P1": 0, "P2": 0, "P3": 0 }
-    }
-  ],
-  "coverageSummary": {
-    "totalTests": 0,
-    "testLevels": ["unit", "integration", "api", "e2e"],
-    "fixtureNeeds": []
-  },
-  "status": "complete | partial"
-}
-```
+### Subagent Output Schema Contract
+
+The aggregate step expects both outputs to include `success`, but the payload shapes are intentionally different:
+
+- `step-03b-subagent-e2e.md` output includes `success`, `subagent`, `tests`, `fixture_needs`, `knowledge_fragments_used`, `test_count`, and `summary`.
+- `step-03b-subagent-backend.md` output includes `success`, `subagent`, `subagentType`, `testsGenerated`, `coverageSummary` (with `fixtureNeeds`), `status`, `knowledge_fragments_used`, and `summary`.
 
-The aggregate step reads whichever output file(s) exist based on `{detected_stack}`.
+The aggregate step reads whichever output file(s) exist based on `{detected_stack}` and must use the matching schema per subagent type.
 
 ---
 
-### 7. Performance Report
+### 8. Execution Report
 
 **Display performance metrics:**
 
 ```
 🚀 Performance Report:
-- Execution Mode: PARALLEL (subprocesses based on {detected_stack})
+- Execution Mode: {resolvedMode}
 - Stack Type: {detected_stack}
 - API Test Generation: ~X minutes
 - E2E Test Generation: ~Y minutes       [if frontend/fullstack]
 - Backend Test Generation: ~Z minutes    [if backend/fullstack]
-- Total Elapsed: ~max(X, Y, Z) minutes
-- Sequential Would Take: ~(X + Y + Z) minutes
-- Performance Gain: ~40-70% faster!
+- Total Elapsed: ~mode-dependent
+- Parallel Gain: ~40-70% faster when mode is subagent/agent-team
 ```
 
 ---
 
-### 8. Proceed to Aggregation
+### 9. Proceed to Aggregation
 
 **Load aggregation step:**
 Load next step: `{nextStepFile}`
 
 The aggregation step (3C) will:
 
-- Read all subprocess outputs (based on `{detected_stack}`)
+- Read all subagent outputs (based on `{detected_stack}`)
 - Write all test files to disk
 - Generate shared fixtures and helpers
 - Calculate summary statistics
@@ -245,17 +359,17 @@ The aggregation step (3C) will:
 
 Proceed to Step 3C (Aggregation) when:
 
-- ✅ Subprocess A (API tests) completed successfully
-- ✅ Subprocess B (E2E tests) completed successfully [if frontend/fullstack]
-- ✅ Subprocess B-backend (Backend tests) completed successfully [if backend/fullstack]
+- ✅ Subagent A (API tests) completed successfully
+- ✅ Subagent B (E2E tests) completed successfully [if frontend/fullstack]
+- ✅ Subagent B-backend (Backend tests) completed successfully [if backend/fullstack]
 - ✅ All expected output files exist and are valid JSON
-- ✅ Performance metrics displayed
+- ✅ Execution metrics displayed
 
 **Do NOT proceed if:**
 
-- ❌ Any launched subprocess failed
+- ❌ Any launched subagent failed
 - ❌ Output files missing or corrupted
-- ❌ Timeout occurred (subprocesses took too long)
+- ❌ Timeout occurred (parallel mode only)
 
 ---
 
@@ -263,16 +377,16 @@ Proceed to Step 3C (Aggregation) when:
 
 ### ✅ SUCCESS:
 
-- All required subprocesses launched successfully (based on `{detected_stack}`)
-- All subprocesses completed without errors
+- All required subagents launched successfully (based on `{detected_stack}`)
+- All required worker steps completed without errors
 - Output files generated and valid
-- Parallel execution achieved ~40-70% performance gain
+- Fallback behavior respected configuration and capability probe rules
 
 ### ❌ SYSTEM FAILURE:
 
-- Failed to launch subprocesses
-- One or more subprocesses failed
+- Failed to launch subagents
+- One or more subagents failed
 - Output files missing or invalid
-- Attempted sequential generation instead of parallel
+- Unsupported requested mode with probing disabled
 
-**Master Rule:** Parallel subprocess execution is MANDATORY for performance.
+**Master Rule:** Deterministic mode selection + stable output contract. Use the best supported mode, then aggregate normally.

package/templates/bmad/tea/workflows/testarch/automate/steps-c/step-03a-subagent-api.md

@@ -0,0 +1,193 @@
+---
+name: 'step-03a-subagent-api'
+description: 'Subagent: Generate API tests only'
+subagent: true
+outputFile: '/tmp/tea-automate-api-tests-{{timestamp}}.json'
+---
+
+# Subagent 3A: Generate API Tests
+
+## SUBAGENT CONTEXT
+
+This is an **isolated subagent** running in parallel with E2E test generation.
+
+**What you have from parent workflow:**
+
+- Target features/components identified in Step 2
+- Knowledge fragments loaded: api-request, data-factories, api-testing-patterns
+- Config: test framework, Playwright Utils enabled/disabled, Pact.js Utils enabled/disabled, Pact MCP mode
+- Coverage plan: which API endpoints need testing
+
+**Your task:** Generate API tests ONLY (not E2E, not fixtures, not other test types).
+
+**If `use_pactjs_utils` is enabled:** Also generate consumer contract tests and provider verification 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`) for patterns. If `pact_mcp` is `"mcp"`, use SmartBear MCP tools (Fetch Provider States, Generate Pact Tests) to inform test generation.
+
+---
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read this entire subagent file before acting
+- ✅ Generate API tests ONLY
+- ✅ Output structured JSON to temp file
+- ✅ Follow knowledge fragment patterns
+- ❌ Do NOT generate E2E tests (that's subagent 3B)
+- ❌ Do NOT run tests (that's step 4)
+- ❌ Do NOT generate fixtures yet (that's step 3C aggregation)
+
+---
+
+## SUBAGENT TASK
+
+### 1. Identify API Endpoints
+
+From the coverage plan (Step 2 output), identify:
+
+- Which API endpoints need test coverage
+- Expected request/response formats
+- Authentication requirements
+- Error scenarios to test
+
+### 2. Generate API Test Files
+
+For each API endpoint, create test file in `tests/api/[feature].spec.ts`:
+
+**Test Structure:**
+
+```typescript
+import { test, expect } from '@playwright/test';
+// If Playwright Utils enabled:
+// import { apiRequest } from '@playwright-utils/api';
+
+test.describe('[Feature] API Tests', () => {
+  test('[P0] should handle successful [operation]', async ({ request }) => {
+    // Use apiRequest helper if Playwright Utils enabled
+    // Otherwise use standard request fixture
+    const response = await request.post('/api/endpoint', {
+      data: {
+        /* test data */
+      },
+    });
+
+    expect(response.status()).toBe(200);
+    expect(await response.json()).toMatchObject({
+      /* expected */
+    });
+  });
+
+  test('[P1] should handle [error scenario]', async ({ request }) => {
+    // Test error handling
+  });
+});
+```
+
+**Requirements:**
+
+- ✅ Use `apiRequest()` helper if Playwright Utils enabled (from api-request fragment)
+- ✅ Use data factories for test data (from data-factories fragment)
+- ✅ Follow API testing patterns (from api-testing-patterns fragment)
+- ✅ Include priority tags [P0], [P1], [P2], [P3]
+- ✅ Test both happy path and error scenarios
+- ✅ Use proper TypeScript types
+- ✅ Deterministic assertions (no timing dependencies)
+
+**If Pact.js Utils enabled (from `subagentContext.config.use_pactjs_utils`):**
+
+- ✅ Generate consumer contract tests in `pact/http/consumer/` using `createProviderState({ name, params })` pattern
+- ✅ Generate provider verification tests in `pact/http/provider/` using `buildVerifierOptions({ provider, port, includeMainAndDeployed, stateHandlers })` pattern
+- ✅ Generate request filter helpers in `pact/http/helpers/` using `createRequestFilter({ tokenGenerator: () => string })`
+- ✅ Generate shared state constants in `pact/http/helpers/states.ts`
+- ✅ If async/message patterns detected, generate message consumer tests in `pact/message/` using `buildMessageVerifierOptions`
+
+### 3. Track Fixture Needs
+
+Identify fixtures needed for API tests:
+
+- Authentication fixtures (auth tokens, API keys)
+- Data factories (user data, product data, etc.)
+- API client configurations
+
+**Do NOT create fixtures yet** - just track what's needed for aggregation step.
+
+---
+
+## OUTPUT FORMAT
+
+Write JSON to temp file: `/tmp/tea-automate-api-tests-{{timestamp}}.json`
+
+```json
+{
+  "success": true,
+  "subagent": "api-tests",
+  "tests": [
+    {
+      "file": "tests/api/auth.spec.ts",
+      "content": "[full TypeScript test file content]",
+      "description": "API tests for authentication endpoints",
+      "priority_coverage": {
+        "P0": 3,
+        "P1": 2,
+        "P2": 1,
+        "P3": 0
+      }
+    },
+    {
+      "file": "tests/api/checkout.spec.ts",
+      "content": "[full TypeScript test file content]",
+      "description": "API tests for checkout endpoints",
+      "priority_coverage": {
+        "P0": 2,
+        "P1": 3,
+        "P2": 1,
+        "P3": 0
+      }
+    }
+  ],
+  "fixture_needs": ["authToken", "userDataFactory", "productDataFactory"],
+  "knowledge_fragments_used": ["api-request", "data-factories", "api-testing-patterns"],
+  "test_count": 12,
+  "summary": "Generated 12 API test cases covering 3 features"
+}
+```
+
+**On Error:**
+
+```json
+{
+  "success": false,
+  "subagent": "api-tests",
+  "error": "Error message describing what went wrong",
+  "partial_output": {
+    /* any tests generated before error */
+  }
+}
+```
+
+---
+
+## EXIT CONDITION
+
+Subagent completes when:
+
+- ✅ All API endpoints have test files generated
+- ✅ All tests follow knowledge fragment patterns
+- ✅ JSON output written to temp file
+- ✅ Fixture needs tracked
+
+**Subagent terminates here.** Parent workflow will read output and proceed to aggregation.
+
+---
+
+## 🚨 SUBAGENT SUCCESS METRICS
+
+### ✅ SUCCESS:
+
+- All API tests generated following patterns
+- JSON output valid and complete
+- No E2E/component/unit tests included (out of scope)
+
+### ❌ FAILURE:
+
+- Generated tests other than API tests
+- Did not follow knowledge fragment patterns
+- Invalid or missing JSON output
+- Ran tests (not subagent responsibility)