@cregis-dev/cckit 0.2.0

package/templates/bmad/tea/workflows/testarch/automate/steps-e/step-01-assess.md

@@ -0,0 +1,65 @@
+---
+name: 'step-01-assess'
+description: 'Load an existing output for editing'
+nextStepFile: './step-02-apply-edit.md'
+---
+
+# Step 1: Assess Edit Target
+
+## STEP GOAL:
+
+Identify which output should be edited and load it.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are the Master Test Architect
+
+### Step-Specific Rules:
+
+- 🎯 Ask the user which output file to edit
+- 🚫 Do not edit until target is confirmed
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+
+## CONTEXT BOUNDARIES:
+
+- Available context: existing outputs
+- Focus: select edit target
+- Limits: no edits yet
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly.
+
+### 1. Identify Target
+
+Ask the user to provide the output file path or select from known outputs.
+
+### 2. Load Target
+
+Read the provided output file in full.
+
+### 3. Confirm
+
+Confirm the target and proceed to edit.
+
+Load next step: `{nextStepFile}`
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Target identified and loaded
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding without a confirmed target

package/templates/bmad/tea/workflows/testarch/automate/steps-e/step-02-apply-edit.md

@@ -0,0 +1,60 @@
+---
+name: 'step-02-apply-edit'
+description: 'Apply edits to the selected output'
+---
+
+# Step 2: Apply Edits
+
+## STEP GOAL:
+
+Apply the requested edits to the selected output and confirm changes.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are the Master Test Architect
+
+### Step-Specific Rules:
+
+- 🎯 Only apply edits explicitly requested by the user
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+
+## CONTEXT BOUNDARIES:
+
+- Available context: selected output and user changes
+- Focus: apply edits only
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly.
+
+### 1. Confirm Requested Changes
+
+Restate what will be changed and confirm.
+
+### 2. Apply Changes
+
+Update the output file accordingly.
+
+### 3. Report
+
+Summarize the edits applied.
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Changes applied and confirmed
+
+### ❌ SYSTEM FAILURE:
+
+- Unconfirmed edits or missing update

package/templates/bmad/tea/workflows/testarch/automate/steps-v/step-01-validate.md

@@ -0,0 +1,67 @@
+---
+name: 'step-01-validate'
+description: 'Validate workflow outputs against checklist'
+outputFile: '{test_artifacts}/automate-validation-report.md'
+validationChecklist: '../checklist.md'
+---
+
+# Step 1: Validate Outputs
+
+## STEP GOAL:
+
+Validate outputs using the workflow checklist and record findings.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are the Master Test Architect
+
+### Step-Specific Rules:
+
+- 🎯 Validate against `{validationChecklist}`
+- 🚫 Do not skip checks
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Write findings to `{outputFile}`
+
+## CONTEXT BOUNDARIES:
+
+- Available context: workflow outputs and checklist
+- Focus: validation only
+- Limits: do not modify outputs in this step
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly.
+
+### 1. Load Checklist
+
+Read `{validationChecklist}` and list all criteria.
+
+### 2. Validate Outputs
+
+Evaluate outputs against each checklist item.
+
+### 3. Write Report
+
+Write a validation report to `{outputFile}` with PASS/WARN/FAIL per section.
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Validation report written
+- All checklist items evaluated
+
+### ❌ SYSTEM FAILURE:
+
+- Skipped checklist items
+- No report produced

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

@@ -0,0 +1,72 @@
+---
+validationDate: 2026-01-27
+workflowName: testarch-automate
+workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/automate
+validationStatus: COMPLETE
+completionDate: 2026-01-27 10:03:10
+---
+
+# Validation Report: testarch-automate
+
+**Validation Started:** 2026-01-27 09:50:21
+**Validator:** BMAD Workflow Validation System (Codex)
+**Standards Version:** BMAD Workflow Standards
+
+## File Structure & Size
+
+- workflow.md present: YES
+- instructions.md present: YES
+- workflow.yaml present: YES
+- step files found: 7
+
+**Step File Sizes:**
+
+- steps-c/step-01-preflight-and-context.md: 113 lines [GOOD]
+- steps-c/step-02-identify-targets.md: 85 lines [GOOD]
+- steps-c/step-03-generate-tests.md: 76 lines [GOOD]
+- steps-c/step-04-validate-and-summarize.md: 62 lines [GOOD]
+- steps-e/step-01-assess.md: 51 lines [GOOD]
+- steps-e/step-02-apply-edit.md: 46 lines [GOOD]
+- steps-v/step-01-validate.md: 53 lines [GOOD]
+- workflow-plan.md present: YES
+
+## Frontmatter Validation
+
+- No frontmatter violations found
+
+## Critical Path Violations
+
+- No {project-root} hardcoded paths detected in body
+- No dead relative links detected
+
+## Menu Handling Validation
+
+- No menu structures detected (linear step flow) [N/A]
+
+## Step Type Validation
+
+- Last step steps-v/step-01-validate.md has no nextStepFile (final step OK)
+- Step type validation assumes linear sequence (no branching/menu). Workflow-plan.md present for reference. [INFO]
+
+## Output Format Validation
+
+- No templates found in workflow root
+- Steps with outputFile in frontmatter:
+  - steps-c/step-04-validate-and-summarize.md
+  - steps-v/step-01-validate.md
+
+## Validation Design Check
+
+- checklist.md present: YES
+- Validation steps folder (steps-v) present: YES
+
+## Instruction Style Check
+
+- All steps include STEP GOAL, MANDATORY EXECUTION RULES, EXECUTION PROTOCOLS, CONTEXT BOUNDARIES, and SUCCESS/FAILURE metrics
+
+## Summary
+
+- Validation completed: 2026-01-27 10:03:10
+- Critical issues: 0
+- Warnings: 0 (informational notes only)
+- Readiness: READY (manual review optional)

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

@@ -0,0 +1,114 @@
+---
+validationDate: 2026-01-27
+workflowName: testarch-automate
+workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/automate
+validationStatus: COMPLETE
+completionDate: 2026-01-27 10:24:01
+---
+
+# Validation Report: testarch-automate
+
+**Validation Started:** 2026-01-27 10:24:01
+**Validator:** BMAD Workflow Validation System (Codex)
+**Standards Version:** BMAD Workflow Standards
+
+## File Structure & Size
+
+- workflow.md present: YES
+- instructions.md present: YES
+- workflow.yaml present: YES
+- step files found: 7
+
+**Step File Sizes:**
+
+- steps-c/step-01-preflight-and-context.md: 112 lines [GOOD]
+- steps-c/step-02-identify-targets.md: 84 lines [GOOD]
+- steps-c/step-03-generate-tests.md: 75 lines [GOOD]
+- steps-c/step-04-validate-and-summarize.md: 61 lines [GOOD]
+- steps-e/step-01-assess.md: 50 lines [GOOD]
+- steps-e/step-02-apply-edit.md: 45 lines [GOOD]
+- steps-v/step-01-validate.md: 52 lines [GOOD]
+- workflow-plan.md present: YES
+
+## Frontmatter Validation
+
+- No frontmatter violations found
+
+## Critical Path Violations
+
+### Config Variables (Exceptions)
+
+Standard BMAD config variables treated as valid exceptions: bmb_creations_output_folder, communication_language, document_output_language, output_folder, planning_artifacts, project-root, project_name, test_artifacts, user_name
+
+- No {project-root} hardcoded paths detected in body
+
+- No dead relative links detected
+
+- No module path assumptions detected
+
+**Status:** ✅ PASS - No critical violations
+
+## Menu Handling Validation
+
+- No menu structures detected (linear step flow) [N/A]
+
+## Step Type Validation
+
+- steps-c/step-01-preflight-and-context.md: Init [PASS]
+- steps-c/step-02-identify-targets.md: Middle [PASS]
+- steps-c/step-03-generate-tests.md: Middle [PASS]
+- steps-c/step-04-validate-and-summarize.md: Final [PASS]
+- Step type validation assumes linear sequence (no branching/menu). Workflow-plan.md present for reference. [INFO]
+
+## Output Format Validation
+
+- Templates present: NONE
+- Steps with outputFile in frontmatter:
+  - steps-c/step-04-validate-and-summarize.md
+  - steps-v/step-01-validate.md
+- checklist.md present: YES
+
+## Validation Design Check
+
+- Validation steps folder (steps-v) present: YES
+- Validation step(s) present: step-01-validate.md
+- Validation steps reference checklist data and auto-proceed
+
+## Instruction Style Check
+
+- Instruction style: Prescriptive (appropriate for TEA quality/compliance workflows)
+- Steps emphasize mandatory sequence, explicit success/failure metrics, and risk-based guidance
+
+## Collaborative Experience Check
+
+- Overall facilitation quality: GOOD
+- 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
+
+- No high-priority subprocess 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
+- Pattern 4 (parallel): optional for validation only
+
+## Cohesive Review
+
+- Overall assessment: GOOD
+- Flow is linear, goals are clear, and outputs map to TEA artifacts
+- Voice and tone consistent with Test Architect persona
+- Recommendation: READY (minor refinements optional)
+
+## Plan Quality Validation
+
+- Plan file present: workflow-plan.md
+- Planned steps found: 7 (all implemented)
+- Plan implementation status: Fully Implemented
+
+## Summary
+
+- Validation completed: 2026-01-27 10:24:01
+- Critical issues: 0
+- Warnings: 0 (informational notes only)
+- Readiness: READY (manual review optional)

package/templates/bmad/tea/workflows/testarch/automate/workflow-plan.md

@@ -0,0 +1,20 @@
+    # Workflow Plan: testarch-automate
+
+    ## Create Mode (steps-c)
+    - step-01-preflight-and-context.md
+
+- step-02-identify-targets.md
+- step-03-generate-tests.md
+- step-04-validate-and-summarize.md
+
+  ## Validate Mode (steps-v)
+  - step-01-validate.md
+
+  ## Edit Mode (steps-e)
+  - step-01-assess.md
+  - step-02-apply-edit.md
+
+  ## Outputs
+  - {test_artifacts}/automation-summary.md
+
+- Test files under {project-root}/tests

package/templates/bmad/tea/workflows/testarch/automate/workflow.md

@@ -0,0 +1,41 @@
+---
+name: testarch-automate
+description: Expand test automation coverage for codebase. Use when user says 'lets expand test coverage' or 'I want to automate tests'
+web_bundle: true
+---
+
+# Test Automation Expansion
+
+**Goal:** Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite
+
+**Role:** You are the Master Test Architect.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This workflow uses **tri-modal step-file architecture**:
+
+- **Create mode (steps-c/)**: primary execution flow
+- **Validate mode (steps-v/)**: validation against checklist
+- **Edit mode (steps-e/)**: revise existing outputs
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Mode Determination
+
+"Welcome to the workflow. What would you like to do?"
+
+- **[C] Create** — Run the workflow
+- **[R] Resume** — Resume an interrupted workflow
+- **[V] Validate** — Validate existing outputs
+- **[E] Edit** — Edit existing outputs
+
+### 2. Route to First Step
+
+- **If C:** Load `steps-c/step-01-preflight-and-context.md`
+- **If R:** Load `steps-c/step-01b-resume.md`
+- **If V:** Load `steps-v/step-01-validate.md`
+- **If E:** Load `steps-e/step-01-assess.md`

package/templates/bmad/tea/workflows/testarch/automate/workflow.yaml

@@ -0,0 +1,53 @@
+# Test Architect workflow: automate
+name: testarch-automate
+description: "Expand test automation coverage for codebase. Use when the user says 'lets expand test coverage' or 'I want to automate tests'"
+
+# Critical variables from config
+config_source: "{project-root}/_bmad/tea/config.yaml"
+output_folder: "{config_source}:output_folder"
+test_artifacts: "{config_source}:test_artifacts"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/_bmad/tea/workflows/testarch/automate"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+template: false
+
+# Variables and inputs
+variables:
+  # Execution mode and targeting
+  standalone_mode: true # Can work without BMad artifacts (true) or integrate with BMad (false)
+  coverage_target: "critical-paths" # critical-paths, comprehensive, selective
+
+  # Directory paths
+  test_dir: "{project-root}/tests" # Root test directory
+  source_dir: "{project-root}" # Source code directory (customize if needed, e.g., {project-root}/src or {project-root}/lib)
+
+# Output configuration
+default_output_file: "{test_artifacts}/automation-summary.md"
+
+# Required tools
+required_tools:
+  - read_file # Read source code, existing tests, BMad artifacts
+  - write_file # Create test files, fixtures, factories, summaries
+  - create_directory # Create test directories
+  - list_files # Discover features and existing tests
+  - search_repo # Find coverage gaps and patterns
+  - glob # Find test files and source files
+
+tags:
+  - qa
+  - automation
+  - test-architect
+  - regression
+  - coverage
+
+execution_hints:
+  interactive: false # Minimize prompts
+  autonomous: true # Proceed without user input unless blocked
+  iterative: true
+

package/templates/bmad/tea/workflows/testarch/ci/azure-pipelines-template.yaml

@@ -0,0 +1,155 @@
+# Azure DevOps CI/CD Pipeline for Test Execution
+# Generated by BMad TEA Agent - Test Architect Module
+# Optimized for: Parallel Sharding, Burn-In Loop
+# Stack: {test_stack_type} | Framework: {test_framework}
+#
+# Variables to customize per project:
+#   INSTALL_CMD       - dependency install command (e.g., npm ci, pnpm install --frozen-lockfile)
+#   TEST_CMD          - main test command (e.g., npm run test:e2e, npm test, npx vitest)
+#   LINT_CMD          - lint command (e.g., npm run lint)
+#   BROWSER_INSTALL   - browser install command (frontend/fullstack only; omit for backend)
+#   DEFAULT_NODE_VERSION - Node.js version (read from .nvmrc or default to 24)
+
+trigger:
+  branches:
+    include:
+      - main
+      - develop
+
+pr:
+  branches:
+    include:
+      - main
+      - develop
+
+variables:
+  DEFAULT_NODE_VERSION: "24"
+  npm_config_cache: $(Pipeline.Workspace)/.npm
+  # Set TEST_STACK_TYPE to 'backend' to skip Playwright browser installs
+  TEST_STACK_TYPE: "" # Values: frontend, backend, fullstack (leave empty for auto)
+
+stages:
+  # Lint stage - Code quality checks
+  - stage: Lint
+    displayName: "Lint"
+    jobs:
+      - job: LintJob
+        displayName: "Code Quality"
+        pool:
+          vmImage: "ubuntu-latest"
+        timeoutInMinutes: 5
+        steps:
+          - task: NodeTool@0
+            inputs:
+              versionSpec: $(DEFAULT_NODE_VERSION)
+            displayName: "Setup Node.js"
+
+          - task: Cache@2
+            inputs:
+              key: 'npm | "$(Agent.OS)" | package-lock.json'
+              restoreKeys: 'npm | "$(Agent.OS)"'
+              path: $(npm_config_cache)
+            displayName: "Cache npm"
+
+          - script: npm ci
+            displayName: "Install dependencies" # Replace with INSTALL_CMD
+
+          - script: npm run lint
+            displayName: "Run linter" # Replace with LINT_CMD
+
+  # Test stage - Parallel execution with sharding
+  - stage: Test
+    displayName: "Test"
+    dependsOn: Lint
+    jobs:
+      - job: TestShard
+        displayName: "Test Shard"
+        pool:
+          vmImage: "ubuntu-latest"
+        timeoutInMinutes: 30
+        strategy:
+          matrix:
+            Shard1:
+              SHARD_INDEX: 1
+            Shard2:
+              SHARD_INDEX: 2
+            Shard3:
+              SHARD_INDEX: 3
+            Shard4:
+              SHARD_INDEX: 4
+        steps:
+          - task: NodeTool@0
+            inputs:
+              versionSpec: $(DEFAULT_NODE_VERSION)
+            displayName: "Setup Node.js"
+
+          - task: Cache@2
+            inputs:
+              key: 'npm | "$(Agent.OS)" | package-lock.json'
+              restoreKeys: 'npm | "$(Agent.OS)"'
+              path: $(npm_config_cache)
+            displayName: "Cache npm"
+
+          - script: npm ci
+            displayName: "Install dependencies" # Replace with INSTALL_CMD
+
+          # Frontend/Fullstack only — skipped for backend-only stacks
+          - script: npx playwright install --with-deps chromium
+            condition: ne(variables['TEST_STACK_TYPE'], 'backend')
+            displayName: "Install Playwright browsers" # Replace with BROWSER_INSTALL
+
+          - script: npm run test:e2e -- --shard=$(SHARD_INDEX)/4
+            displayName: "Run tests (shard $(SHARD_INDEX)/4)" # Replace with TEST_CMD + shard args
+
+          - task: PublishTestResults@2
+            condition: always()
+            inputs:
+              testResultsFormat: "JUnit"
+              testResultsFiles: "test-results/**/*.xml"
+              mergeTestResults: true
+            displayName: "Publish test results"
+
+          - publish: test-results/
+            artifact: test-results-$(SHARD_INDEX)
+            condition: failed()
+            displayName: "Upload failure artifacts"
+
+  # Burn-in stage - Flaky test detection
+  # Note: Burn-in targets UI flakiness. For backend-only stacks, remove this stage entirely.
+  - stage: BurnIn
+    displayName: "Burn-In (Flaky Detection)"
+    dependsOn: Test
+    condition: and(succeeded(), or(eq(variables['Build.Reason'], 'PullRequest'), eq(variables['Build.CronSchedule.DisplayName'], 'Weekly burn-in')))
+    jobs:
+      - job: BurnInJob
+        displayName: "Burn-In Loop"
+        pool:
+          vmImage: "ubuntu-latest"
+        timeoutInMinutes: 60
+        steps:
+          - task: NodeTool@0
+            inputs:
+              versionSpec: $(DEFAULT_NODE_VERSION)
+            displayName: "Setup Node.js"
+
+          - script: npm ci
+            displayName: "Install dependencies" # Replace with INSTALL_CMD
+
+          # Frontend/Fullstack only — skipped for backend-only stacks
+          - script: npx playwright install --with-deps chromium
+            condition: ne(variables['TEST_STACK_TYPE'], 'backend')
+            displayName: "Install Playwright browsers" # Replace with BROWSER_INSTALL
+
+          - script: |
+              echo "Starting burn-in loop - detecting flaky tests"
+              for i in $(seq 1 10); do
+                echo "Burn-in iteration $i/10"
+                npm run test:e2e || exit 1
+              done
+              echo "Burn-in complete - no flaky tests detected"
+            displayName: "Run burn-in loop (10 iterations)" # Replace npm run test:e2e with TEST_CMD
+
+          - publish: test-results/
+            artifact: burn-in-failures
+            condition: failed()
+            displayName: "Upload burn-in failure artifacts"