@cregis-dev/cckit 0.3.0 → 0.4.0

package/templates/bmad/tea/workflows/testarch/nfr-assess/steps-c/step-04e-aggregate-nfr.md

@@ -9,7 +9,7 @@ outputFile: '{test_artifacts}/nfr-assessment.md'
 
 ## STEP GOAL
 
-Read outputs from 4 parallel NFR subprocesses, calculate overall risk level, aggregate compliance status, and identify cross-domain risks.
+Read outputs from 4 parallel NFR subagents, calculate overall risk level, aggregate compliance status, and identify cross-domain risks.
 
 ---
 
@@ -17,15 +17,15 @@ Read outputs from 4 parallel NFR subprocesses, calculate overall risk level, agg
 
 - 📖 Read the entire step file before acting
 - ✅ Speak in `{communication_language}`
-- ✅ Read all 4 subprocess outputs
+- ✅ Read all 4 subagent outputs
 - ✅ Calculate overall risk level
-- ❌ Do NOT re-assess NFRs (use subprocess outputs)
+- ❌ Do NOT re-assess NFRs (use subagent outputs)
 
 ---
 
 ## MANDATORY SEQUENCE
 
-### 1. Read All Subprocess Outputs
+### 1. Read All Subagent Outputs
 
 ```javascript
 const domains = ['security', 'performance', 'reliability', 'scalability'];
@@ -137,6 +137,23 @@ const prioritizedActions = allPriorityActions.sort((a, b) => (a.urgency === 'URG
 ### 6. Generate Executive Summary
 
 ```javascript
+const resolvedMode = subagentContext?.execution?.resolvedMode ?? 'unknown';
+const subagentExecutionLabel =
+  resolvedMode === 'sequential'
+    ? 'SEQUENTIAL (4 NFR domains)'
+    : resolvedMode === 'agent-team'
+      ? 'AGENT-TEAM (4 NFR domains)'
+      : resolvedMode === 'subagent'
+        ? 'SUBAGENT (4 NFR domains)'
+        : 'MODE-DEPENDENT (4 NFR domains)';
+
+const performanceGainLabel =
+  resolvedMode === 'sequential'
+    ? 'baseline (no parallel speedup)'
+    : resolvedMode === 'agent-team' || resolvedMode === 'subagent'
+      ? '~67% faster than sequential'
+      : 'mode-dependent';
+
 const executiveSummary = {
   overall_risk: overallRisk,
   assessment_date: new Date().toISOString(),
@@ -156,8 +173,8 @@ const executiveSummary = {
     scalability: assessments.scalability.risk_level,
   },
 
-  subprocess_execution: 'PARALLEL (4 NFR domains)',
-  performance_gain: '~67% faster than sequential',
+  subagent_execution: subagentExecutionLabel,
+  performance_gain: performanceGainLabel,
 };
 
 // Save for Step 5 (report generation)
@@ -169,7 +186,7 @@ fs.writeFileSync('/tmp/tea-nfr-summary-{{timestamp}}.json', JSON.stringify(execu
 ### 7. Display Summary to User
 
 ```
-✅ NFR Assessment Complete (Parallel Execution)
+✅ NFR Assessment Complete ({subagentExecutionLabel})
 
 🎯 Overall Risk Level: {overallRisk}
 
@@ -186,7 +203,7 @@ fs.writeFileSync('/tmp/tea-nfr-summary-{{timestamp}}.json', JSON.stringify(execu
 
 🎯 Priority Actions: {priority_action_count}
 
-🚀 Performance: Parallel execution ~67% faster
+🚀 Performance: {performanceGainLabel}
 
 ✅ Ready for report generation (Step 5)
 ```
@@ -223,7 +240,7 @@ fs.writeFileSync('/tmp/tea-nfr-summary-{{timestamp}}.json', JSON.stringify(execu
 
 Proceed to Step 5 when:
 
-- ✅ All subprocess outputs read
+- ✅ All subagent outputs read
 - ✅ Overall risk calculated
 - ✅ Compliance aggregated
 - ✅ Summary saved
@@ -243,5 +260,5 @@ Load next step: `{nextStepFile}`
 
 ### ❌ FAILURE:
 
-- Failed to read subprocess outputs
+- Failed to read subagent outputs
 - Risk calculation incorrect

package/templates/bmad/tea/workflows/testarch/nfr-assess/validation-report-20260127-095021.md

@@ -1,7 +1,7 @@
 ---
 validationDate: 2026-01-27
 workflowName: testarch-nfr
-workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/nfr-assess
+workflowPath: {project-root}/src/workflows/testarch/nfr-assess
 validationStatus: COMPLETE
 completionDate: 2026-01-27 10:03:10
 ---

package/templates/bmad/tea/workflows/testarch/nfr-assess/validation-report-20260127-102401.md

@@ -1,7 +1,7 @@
 ---
 validationDate: 2026-01-27
 workflowName: testarch-nfr
-workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/nfr-assess
+workflowPath: {project-root}/src/workflows/testarch/nfr-assess
 validationStatus: COMPLETE
 completionDate: 2026-01-27 10:24:01
 ---
@@ -87,9 +87,9 @@ Standard BMAD config variables treated as valid exceptions: bmb_creations_output
 - Steps use progressive prompts and clear role reinforcement; no laundry-list interrogation detected
 - Flow progression is clear and aligned to workflow goals
 
-## Subprocess Optimization Opportunities
+## Subagent Optimization Opportunities
 
-- No high-priority subprocess optimizations identified; workflow already uses step-file architecture
+- No high-priority subagent optimizations identified; workflow already uses step-file architecture
 - Pattern 1 (grep/regex): N/A for most steps
 - Pattern 2 (per-file analysis): already aligned to validation structure
 - Pattern 3 (data ops): minimal data file loads

package/templates/bmad/tea/workflows/testarch/nfr-assess/workflow.yaml

@@ -1,6 +1,7 @@
 # Test Architect workflow: nfr-assess
 name: testarch-nfr
-description: "Assess NFRs like performance security and reliability. Use when the user says 'lets assess NFRs' or 'I want to evaluate non-functional requirements'"
+# prettier-ignore
+description: 'Assess NFRs like performance security and reliability. Use when the user says "lets assess NFRs" or "I want to evaluate non-functional requirements"'
 
 # Critical variables from config
 config_source: "{project-root}/_bmad/tea/config.yaml"
@@ -45,4 +46,3 @@ execution_hints:
   interactive: false # Minimize prompts
   autonomous: true # Proceed without user input unless blocked
   iterative: true
-

package/templates/bmad/tea/workflows/testarch/teach-me-testing/data/tea-resources-index.yaml

@@ -120,9 +120,9 @@ documentation:
       online: "/explanation/step-file-architecture/"
       topics: ["Micro-file design", "JIT loading", "Sequential enforcement"]
 
-    - name: "Subprocess Architecture"
-      local: "/docs/explanation/subprocess-architecture.md"
-      online: "/explanation/subprocess-architecture/"
+    - name: "Subagent Architecture"
+      local: "/docs/explanation/subagent-architecture.md"
+      online: "/explanation/subagent-architecture/"
       topics: ["Parallel execution", "Context optimization"]
 
   reference:

package/templates/bmad/tea/workflows/testarch/teach-me-testing/workflow-plan-teach-me-testing.md

@@ -60,7 +60,7 @@ Create an ongoing learning companion that teaches testing progressively through
 ## Classification Decisions
 
 **Workflow Name:** teach-me-testing
-**Target Path:** /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/teach-me-testing/
+**Target Path:** {project-root}/src/workflows/testarch/teach-me-testing/
 
 **4 Key Decisions:**
 
@@ -501,7 +501,7 @@ teach-me-testing/
 └── checklist.md                          ✓ Created
 ```
 
-**Location:** /Users/murat.ozcan/opensource/bmad-playground/\_bmad-output/bmb-creations/workflows/teach-me-testing/
+**Location:** {external-project-root}/\_bmad-output/bmb-creations/workflows/teach-me-testing/
 
 **Configuration:**
 
@@ -924,16 +924,16 @@ teach-me-testing/
 **DEPLOYMENT:** Move workflow from staging to TEA module
 
 **Source (Staging):**
-`/Users/murat.ozcan/opensource/bmad-playground/_bmad-output/bmb-creations/workflows/teach-me-testing/`
+`{external-project-root}/_bmad-output/bmb-creations/workflows/teach-me-testing/`
 
 **Target (Production):**
-`/Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/teach-me-testing/`
+`{project-root}/src/workflows/testarch/teach-me-testing/`
 
 **Command:**
 
 ```bash
-cp -r /Users/murat.ozcan/opensource/bmad-playground/_bmad-output/bmb-creations/workflows/teach-me-testing \
-      /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/
+cp -r {external-project-root}/_bmad-output/bmb-creations/workflows/teach-me-testing \
+      {project-root}/src/workflows/testarch/
 ```
 
 **After deployment:**

package/templates/bmad/tea/workflows/testarch/teach-me-testing/workflow.md

@@ -1,6 +1,6 @@
 ---
 name: teach-me-testing
-description: Teach testing progressively through structured sessions. Use when user says 'lets learn testing' or 'I want to study test practices'
+description: 'Teach testing progressively through structured sessions. Use when user says "lets learn testing" or "I want to study test practices"'
 web_bundle: true
 ---
 

package/templates/bmad/tea/workflows/testarch/test-design/steps-c/step-02-load-context.md

@@ -42,6 +42,8 @@ Load the required documents, config flags, and knowledge fragments needed to pro
 From `{config_source}`:
 
 - Read `tea_use_playwright_utils`
+- Read `tea_use_pactjs_utils`
+- Read `tea_pact_mcp`
 - Read `tea_browser_automation`
 - Read `test_stack_type` (if not set, default to `"auto"`)
 - Note `test_artifacts`
@@ -140,6 +142,22 @@ Load fragments based on their `tier` classification in `tea-index.csv`:
 
 **Detection**: Scan `{test_dir}` for files containing `page.goto` or `page.locator`. If none found, use API-only profile.
 
+### Pact.js Utils Loading
+
+**If `tea_use_pactjs_utils` is enabled** (and `{detected_stack}` is `backend` or `fullstack`, or microservices indicators detected):
+
+Load: `pactjs-utils-overview.md`, `pactjs-utils-consumer-helpers.md`, `pactjs-utils-provider-verifier.md`, `pactjs-utils-request-filter.md`
+
+**If `tea_use_pactjs_utils` is disabled** but contract testing is relevant:
+
+Load: `contract-testing.md`
+
+### Pact MCP Loading
+
+**If `tea_pact_mcp` is `"mcp"`:**
+
+Load: `pact-mcp.md` — enables agent to use SmartBear MCP "Fetch Provider States" and "Matrix" tools to understand existing contract landscape during test design.
+
 ## 4. Load Knowledge Base Fragments
 
 Use `{knowledgeIndex}` to select and load only relevant fragments.
@@ -166,6 +184,18 @@ Use `{knowledgeIndex}` to select and load only relevant fragments.
 
 - (existing MCP-related fragments, if any are added in future)
 
+**Pact.js Utils (if enabled — both System-Level and Epic-Level):**
+
+- `pactjs-utils-overview.md`, `pactjs-utils-consumer-helpers.md`, `pactjs-utils-provider-verifier.md`, `pactjs-utils-request-filter.md`
+
+**Contract Testing (if pactjs-utils disabled but relevant):**
+
+- `contract-testing.md`
+
+**Pact MCP (if tea_pact_mcp is "mcp"):**
+
+- `pact-mcp.md`
+
 ---
 
 ## 5. Confirm Loaded Inputs

package/templates/bmad/tea/workflows/testarch/test-design/steps-c/step-05-generate-output.md

@@ -1,6 +1,6 @@
 ---
 name: 'step-05-generate-output'
-description: 'Generate output documents and validate against checklist'
+description: 'Generate output documents with adaptive orchestration (agent-team, subagent, or sequential)'
 outputFile: '{test_artifacts}/test-design-epic-{epic_num}.md'
 progressFile: '{test_artifacts}/test-design-progress.md'
 ---
@@ -16,6 +16,8 @@ Write the final test-design document(s) using the correct template(s), then vali
 - 📖 Read the entire step file before acting
 - ✅ Speak in `{communication_language}`
 - ✅ Use the provided templates and output paths
+- ✅ Resolve execution mode from explicit user request first, then config
+- ✅ Apply fallback rules deterministically when requested mode is unsupported
 
 ---
 
@@ -36,6 +38,71 @@ Write the final test-design document(s) using the correct template(s), then vali
 
 **CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
 
+## 0. Resolve Execution Mode (User Override First)
+
+```javascript
+const orchestrationContext = {
+  config: {
+    execution_mode: config.tea_execution_mode || 'auto', // "auto" | "subagent" | "agent-team" | "sequential"
+    capability_probe: config.tea_capability_probe !== false, // true by default
+  },
+  timestamp: new Date().toISOString().replace(/[:.]/g, '-'),
+};
+
+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(orchestrationContext.config.execution_mode) || 'auto';
+const probeEnabled = orchestrationContext.config.capability_probe;
+
+const supports = { subagent: false, agentTeam: false };
+if (probeEnabled) {
+  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';
+}
+```
+
+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)
+
 ## 1. Select Output Template(s)
 
 ### System-Level Mode (Phase 3)
@@ -45,6 +112,8 @@ Generate **two** documents:
 - `{test_artifacts}/test-design-architecture.md` using `test-design-architecture-template.md`
 - `{test_artifacts}/test-design-qa.md` using `test-design-qa-template.md`
 
+If `resolvedMode` is `agent-team` or `subagent`, these two documents can be generated in parallel as independent workers, then reconciled for consistency.
+
 ### Epic-Level Mode (Phase 4)
 
 Generate **one** document:
@@ -52,6 +121,8 @@ Generate **one** document:
 - `{outputFile}` using `test-design-template.md`
 - If `epic_num` is unclear, ask the user
 
+Epic-level mode remains single-worker by default (one output artifact).
+
 ---
 
 ## 2. Populate Templates

package/templates/bmad/tea/workflows/testarch/test-design/validation-report-20260127-095021.md

@@ -1,7 +1,7 @@
 ---
 validationDate: 2026-01-27
 workflowName: testarch-test-design
-workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/test-design
+workflowPath: {project-root}/src/workflows/testarch/test-design
 validationStatus: COMPLETE
 completionDate: 2026-01-27 10:03:10
 ---

package/templates/bmad/tea/workflows/testarch/test-design/validation-report-20260127-102401.md

@@ -1,7 +1,7 @@
 ---
 validationDate: 2026-01-27
 workflowName: testarch-test-design
-workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/test-design
+workflowPath: {project-root}/src/workflows/testarch/test-design
 validationStatus: COMPLETE
 completionDate: 2026-01-27 10:24:01
 ---
@@ -87,9 +87,9 @@ Standard BMAD config variables treated as valid exceptions: bmb_creations_output
 - Steps use progressive prompts and clear role reinforcement; no laundry-list interrogation detected
 - Flow progression is clear and aligned to workflow goals
 
-## Subprocess Optimization Opportunities
+## Subagent Optimization Opportunities
 
-- No high-priority subprocess optimizations identified; workflow already uses step-file architecture
+- No high-priority subagent optimizations identified; workflow already uses step-file architecture
 - Pattern 1 (grep/regex): N/A for most steps
 - Pattern 2 (per-file analysis): already aligned to validation structure
 - Pattern 3 (data ops): minimal data file loads

package/templates/bmad/tea/workflows/testarch/test-design/workflow.yaml

@@ -1,6 +1,7 @@
 # Test Architect workflow: test-design
 name: testarch-test-design
-description: "Create system-level or epic-level test plans. Use when the user says 'lets design test plan' or 'I want to create test strategy'"
+# prettier-ignore
+description: 'Create system-level or epic-level test plans. Use when the user says "lets design test plan" or "I want to create test strategy"'
 
 # Critical variables from config
 config_source: "{project-root}/_bmad/tea/config.yaml"
@@ -74,4 +75,3 @@ execution_hints:
   interactive: false # Minimize prompts
   autonomous: true # Proceed without user input unless blocked
   iterative: true
-

package/templates/bmad/tea/workflows/testarch/test-review/steps-c/step-01-load-context.md

@@ -79,11 +79,27 @@ Load fragments based on their `tier` classification in `tea-index.csv`:
 
 **Detection**: Scan `{test_dir}` for files containing `page.goto` or `page.locator`. If none found, use API-only profile.
 
+### Pact.js Utils Loading
+
+**If `tea_use_pactjs_utils` is enabled** (and contract tests detected in review scope):
+
+Load: `pactjs-utils-overview.md`, `pactjs-utils-provider-verifier.md`, `pactjs-utils-request-filter.md` (the 3 most relevant for reviewing provider verification tests)
+
+**If `tea_use_pactjs_utils` is disabled** but contract tests are in review scope:
+
+Load: `contract-testing.md`
+
+### Pact MCP Loading
+
+**If `tea_pact_mcp` is `"mcp"`:**
+
+Load: `pact-mcp.md` — enables agent to use SmartBear MCP "Review Pact Tests" tool for automated best-practice feedback during test review.
+
 ## 2. Load Knowledge Base
 
 From `{knowledgeIndex}` load:
 
-Read `{config_source}` and check `tea_use_playwright_utils` and `tea_browser_automation` to select the correct fragment set.
+Read `{config_source}` and check `tea_use_playwright_utils`, `tea_use_pactjs_utils`, `tea_pact_mcp`, and `tea_browser_automation` to select the correct fragment set.
 
 **Core:**
 
@@ -115,6 +131,18 @@ Read `{config_source}` and check `tea_use_playwright_utils` and `tea_browser_aut
 
 - (existing MCP-related fragments, if any are added in future)
 
+**Pact.js Utils (if enabled and contract tests in review scope):**
+
+- `pactjs-utils-overview.md`, `pactjs-utils-provider-verifier.md`, `pactjs-utils-request-filter.md`
+
+**Contract Testing (if pactjs-utils disabled but contract tests in review scope):**
+
+- `contract-testing.md`
+
+**Pact MCP (if tea_pact_mcp is "mcp"):**
+
+- `pact-mcp.md`
+
 ---
 
 ## 3. Gather Context Artifacts