@cregis-dev/cckit 0.2.0

package/templates/bmad/tea/workflows/testarch/ci/harness-pipeline-template.yaml

@@ -0,0 +1,159 @@
+# Harness CI 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)
+
+pipeline:
+  name: Test Pipeline
+  identifier: test_pipeline
+  projectIdentifier: default
+  orgIdentifier: default
+  stages:
+    # Lint stage - Code quality checks
+    - stage:
+        name: Lint
+        identifier: lint
+        type: CI
+        spec:
+          cloneCodebase: true
+          infrastructure:
+            type: KubernetesDirect
+            spec:
+              connectorRef: account.harnessImage
+              namespace: default
+          execution:
+            steps:
+              - step:
+                  type: Run
+                  name: Install dependencies
+                  identifier: install
+                  spec:
+                    connectorRef: account.harnessImage
+                    image: node:24
+                    shell: Sh
+                    command: npm ci # Replace with INSTALL_CMD
+
+              - step:
+                  type: Run
+                  name: Run linter
+                  identifier: lint
+                  spec:
+                    connectorRef: account.harnessImage
+                    image: node:24
+                    shell: Sh
+                    command: npm run lint # Replace with LINT_CMD
+
+    # Test stage - Parallel execution with sharding
+    - stage:
+        name: Test
+        identifier: test
+        type: CI
+        spec:
+          cloneCodebase: true
+          infrastructure:
+            type: KubernetesDirect
+            spec:
+              connectorRef: account.harnessImage
+              namespace: default
+          execution:
+            steps:
+              - step:
+                  type: Run
+                  name: Install dependencies
+                  identifier: install
+                  spec:
+                    connectorRef: account.harnessImage
+                    image: node:24
+                    shell: Sh
+                    command: npm ci # Replace with INSTALL_CMD
+
+              # Frontend/Fullstack only — remove this step for backend-only stacks
+              - step:
+                  type: Run
+                  name: Install browsers
+                  identifier: browsers
+                  spec:
+                    connectorRef: account.harnessImage
+                    image: mcr.microsoft.com/playwright:v1.50.0-noble
+                    shell: Sh
+                    command: npx playwright install --with-deps chromium # Replace with BROWSER_INSTALL
+
+              - parallel:
+                  - step:
+                      type: Run
+                      name: Test Shard 1
+                      identifier: shard_1
+                      spec:
+                        connectorRef: account.harnessImage
+                        image: mcr.microsoft.com/playwright:v1.50.0-noble
+                        shell: Sh
+                        command: npm run test:e2e -- --shard=1/4 # Replace with TEST_CMD + shard args
+                  - step:
+                      type: Run
+                      name: Test Shard 2
+                      identifier: shard_2
+                      spec:
+                        connectorRef: account.harnessImage
+                        image: mcr.microsoft.com/playwright:v1.50.0-noble
+                        shell: Sh
+                        command: npm run test:e2e -- --shard=2/4 # Replace with TEST_CMD + shard args
+                  - step:
+                      type: Run
+                      name: Test Shard 3
+                      identifier: shard_3
+                      spec:
+                        connectorRef: account.harnessImage
+                        image: mcr.microsoft.com/playwright:v1.50.0-noble
+                        shell: Sh
+                        command: npm run test:e2e -- --shard=3/4 # Replace with TEST_CMD + shard args
+                  - step:
+                      type: Run
+                      name: Test Shard 4
+                      identifier: shard_4
+                      spec:
+                        connectorRef: account.harnessImage
+                        image: mcr.microsoft.com/playwright:v1.50.0-noble
+                        shell: Sh
+                        command: npm run test:e2e -- --shard=4/4 # Replace with TEST_CMD + shard args
+
+    # Burn-in stage - Flaky test detection
+    # Note: Burn-in targets UI flakiness. For backend-only stacks, remove this stage entirely.
+    - stage:
+        name: Burn-In
+        identifier: burn_in
+        type: CI
+        when:
+          condition: <+pipeline.triggerType> == "WEBHOOK" || <+pipeline.triggerType> == "SCHEDULER"
+        spec:
+          cloneCodebase: true
+          infrastructure:
+            type: KubernetesDirect
+            spec:
+              connectorRef: account.harnessImage
+              namespace: default
+          execution:
+            steps:
+              - step:
+                  type: Run
+                  name: Install and burn-in
+                  identifier: burn_in_loop
+                  spec:
+                    connectorRef: account.harnessImage
+                    image: mcr.microsoft.com/playwright:v1.50.0-noble
+                    shell: Sh
+                    command: |
+                      npm ci
+                      npx playwright install --with-deps chromium
+                      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"
+                    # Replace npm ci with INSTALL_CMD, npm run test:e2e with TEST_CMD

package/templates/bmad/tea/workflows/testarch/ci/instructions.md

@@ -0,0 +1,45 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# CI/CD Pipeline Setup
+
+**Workflow ID**: `_bmad/tea/testarch/ci`
+**Version**: 5.0 (Step-File Architecture)
+
+---
+
+## Overview
+
+Scaffold a production-ready CI/CD quality pipeline with test execution, burn-in loops for flaky detection, parallel sharding, artifact collection, and notifications.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This workflow uses **step-file architecture**:
+
+- **Micro-file Design**: Each step is self-contained
+- **JIT Loading**: Only the current step file is in memory
+- **Sequential Enforcement**: Execute steps in order
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+From `workflow.yaml`, resolve:
+
+- `config_source`, `test_artifacts`, `user_name`, `communication_language`, `document_output_language`, `date`
+- `ci_platform`, `test_dir`
+
+### 2. First Step
+
+Load, read completely, and execute:
+`{project-root}/_bmad/tea/workflows/testarch/ci/steps-c/step-01-preflight.md`
+
+### 3. Resume Support
+
+If the user selects **Resume** mode, load, read completely, and execute:
+`{project-root}/_bmad/tea/workflows/testarch/ci/steps-c/step-01b-resume.md`
+
+This checks the output document for progress tracking frontmatter and routes to the next incomplete step.

package/templates/bmad/tea/workflows/testarch/ci/jenkins-pipeline-template.groovy

@@ -0,0 +1,129 @@
+// Jenkinsfile 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)
+//
+// Node.js version management — choose one:
+//   Option A (recommended): Configure NodeJS Plugin in Jenkins Global Tool Configuration,
+//     then add to pipeline:  tools { nodejs 'NodeJS-24' }
+//   Option B: Use nvm (pre-installed on agent) — this template uses nvm as the default
+//   Option C: Use a Docker agent — agent { docker { image 'node:24' } }
+
+pipeline {
+    agent any
+
+    environment {
+        CI = 'true'
+    }
+
+    options {
+        timeout(time: 45, unit: 'MINUTES')
+        disableConcurrentBuilds()
+    }
+
+    stages {
+        stage('Checkout') {
+            steps {
+                checkout scm
+            }
+        }
+
+        stage('Install') {
+            steps {
+                // Detect and apply Node.js version from .nvmrc (falls back to v24)
+                // If using NodeJS Plugin instead, remove this block and add: tools { nodejs 'NodeJS-24' }
+                sh '''
+                    export NVM_DIR="$HOME/.nvm"
+                    [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
+                    NODE_VERSION=$(cat .nvmrc 2>/dev/null || echo "24")
+                    nvm install "$NODE_VERSION" 2>/dev/null || true
+                    nvm use "$NODE_VERSION" 2>/dev/null || true
+                    node --version
+                    npm ci
+                ''' // Replace npm ci with INSTALL_CMD
+                // Stash installed dependencies so parallel shards can restore them
+                stash includes: 'node_modules/**', name: 'deps'
+            }
+        }
+
+        stage('Lint') {
+            steps {
+                sh 'npm run lint' // Replace with LINT_CMD
+            }
+        }
+
+        // Test stage - Parallel execution with sharding
+        // Each shard restores dependencies via unstash for workspace safety
+        stage('Test') {
+            parallel {
+                stage('Shard 1') {
+                    steps {
+                        unstash 'deps'
+                        // Frontend/Fullstack only — remove browser install for backend-only stacks
+                        sh 'npx playwright install --with-deps chromium' // Replace with BROWSER_INSTALL
+                        sh 'npm run test:e2e -- --shard=1/4' // Replace with TEST_CMD + shard args
+                    }
+                }
+                stage('Shard 2') {
+                    steps {
+                        unstash 'deps'
+                        sh 'npx playwright install --with-deps chromium' // Replace with BROWSER_INSTALL
+                        sh 'npm run test:e2e -- --shard=2/4' // Replace with TEST_CMD + shard args
+                    }
+                }
+                stage('Shard 3') {
+                    steps {
+                        unstash 'deps'
+                        sh 'npx playwright install --with-deps chromium' // Replace with BROWSER_INSTALL
+                        sh 'npm run test:e2e -- --shard=3/4' // Replace with TEST_CMD + shard args
+                    }
+                }
+                stage('Shard 4') {
+                    steps {
+                        unstash 'deps'
+                        sh 'npx playwright install --with-deps chromium' // Replace with BROWSER_INSTALL
+                        sh 'npm run test:e2e -- --shard=4/4' // Replace with TEST_CMD + shard args
+                    }
+                }
+            }
+        }
+
+        // Burn-in stage - Flaky test detection
+        // Note: Burn-in targets UI flakiness. For backend-only stacks, remove this stage entirely.
+        stage('Burn-In') {
+            when {
+                anyOf {
+                    changeRequest()
+                    triggeredBy 'TimerTrigger'
+                }
+            }
+            steps {
+                sh '''
+                    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"
+                ''' // Replace npm run test:e2e with TEST_CMD
+            }
+        }
+    }
+
+    post {
+        always {
+            // Archive test results and reports
+            archiveArtifacts artifacts: 'test-results/**,playwright-report/**', allowEmptyArchive: true
+            junit testResults: 'test-results/**/*.xml', allowEmptyResults: true
+        }
+        failure {
+            echo 'Pipeline failed - check test results and artifacts'
+        }
+    }
+}

package/templates/bmad/tea/workflows/testarch/ci/steps-c/step-01-preflight.md

@@ -0,0 +1,158 @@
+---
+name: 'step-01-preflight'
+description: 'Verify prerequisites and detect CI platform'
+nextStepFile: './step-02-generate-pipeline.md'
+outputFile: '{test_artifacts}/ci-pipeline-progress.md'
+---
+
+# Step 1: Preflight Checks
+
+## STEP GOAL
+
+Verify CI prerequisites and determine target CI platform.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the entire step file before acting
+- ✅ Speak in `{communication_language}`
+- 🚫 Halt if requirements fail
+
+---
+
+## 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. Verify Git Repository
+
+- `.git/` exists
+- Remote configured (if available)
+
+If missing: **HALT** with "Git repository required for CI/CD setup."
+
+---
+
+## 2. Detect Test Stack Type
+
+Determine the project's test stack type (`test_stack_type`) using the following algorithm:
+
+1. If `test_stack_type` is explicitly set in config (not `"auto"`), use that value.
+2. Otherwise, auto-detect by scanning project manifests:
+   - **Frontend indicators**: `playwright.config.*`, `cypress.config.*`, `vite.config.*`, `next.config.*`, `src/components/`, `src/pages/`, `src/app/`
+   - **Backend indicators**: `pyproject.toml`, `pom.xml`/`build.gradle`, `go.mod`, `*.csproj`/`*.sln`, `Gemfile`, `Cargo.toml`, `jest.config.*`, `vitest.config.*`, `src/routes/`, `src/controllers/`, `src/api/`, `Dockerfile`, `serverless.yml`
+   - **Both present** → `fullstack`
+   - **Only frontend** → `frontend`
+   - **Only backend** → `backend`
+   - **Cannot determine** → default to `fullstack` and note assumption
+
+Record detected `test_stack_type` in step output.
+
+---
+
+## 3. Verify Test Framework
+
+- Check for framework configuration based on detected stack:
+  - **Frontend/Fullstack**: `playwright.config.*` or `cypress.config.*` exists
+  - **Backend (Node.js)**: `jest.config.*` or `vitest.config.*` or test scripts in `package.json`
+  - **Backend (Python)**: `pyproject.toml` with `[tool.pytest]` or `pytest.ini` or `setup.cfg` with pytest config
+  - **Backend (Java/Kotlin)**: `pom.xml` with surefire/failsafe plugins or `build.gradle` with test task
+  - **Backend (Go)**: `*_test.go` files present (Go convention — no config file needed)
+  - **Backend (C#/.NET)**: `*.csproj` with xUnit/NUnit/MSTest references
+  - **Backend (Ruby)**: `Gemfile` with rspec or `.rspec` config file
+- If `test_framework` is `"auto"`, detect from config files and project manifests found
+- Verify test dependencies are installed (language-appropriate package manager)
+
+If missing: **HALT** with "Run `framework` workflow first."
+
+---
+
+## 4. Ensure Tests Pass Locally
+
+- Run the main test command based on detected stack and framework:
+  - **Node.js**: `npm test` or `npm run test:e2e`
+  - **Python**: `pytest` or `python -m pytest`
+  - **Java**: `mvn test` or `gradle test`
+  - **Go**: `go test ./...`
+  - **C#/.NET**: `dotnet test`
+  - **Ruby**: `bundle exec rspec`
+- If failing: **HALT** and request fixes before CI setup
+
+---
+
+## 5. Detect CI Platform
+
+- If `ci_platform` is explicitly set in config (not `"auto"`), use that value.
+- Otherwise, scan for existing CI configuration files:
+  - `.github/workflows/*.yml` → `github-actions`
+  - `.gitlab-ci.yml` → `gitlab-ci`
+  - `Jenkinsfile` → `jenkins`
+  - `azure-pipelines.yml` → `azure-devops`
+  - `.harness/*.yaml` → `harness`
+  - `.circleci/config.yml` → `circle-ci`
+- If found, ask whether to update or replace
+- If not found, infer from git remote (github.com → `github-actions`, gitlab.com → `gitlab-ci`)
+- If still unresolved, default to `github-actions`
+
+Record detected `ci_platform` in step output.
+
+---
+
+## 6. Read Environment Context
+
+- Read environment context based on detected stack:
+  - **Node.js**: Read `.nvmrc` if present (default to Node 24+ LTS if missing); read `package.json` for dependency caching strategy
+  - **Python**: Read `.python-version` or `pyproject.toml` for Python version; note `pip`/`poetry`/`pipenv` for caching
+  - **Java**: Read `pom.xml`/`build.gradle` for Java version; note Maven/Gradle for caching
+  - **Go**: Read `go.mod` for Go version; note Go module cache path
+  - **C#/.NET**: Read `*.csproj`/`global.json` for .NET SDK version; note NuGet cache
+  - **Ruby**: Read `.ruby-version` or `Gemfile` for Ruby version; note Bundler cache
+
+---
+
+### 7. 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-01-preflight']
+  lastStep: 'step-01-preflight'
+  lastSaved: '{date}'
+  ---
+  ```
+
+  Then write this step's output below the frontmatter.
+
+- **If `{outputFile}` already exists**, update:
+  - Add `'step-01-preflight'` to `stepsCompleted` array (only if not already present)
+  - Set `lastStep: 'step-01-preflight'`
+  - Set `lastSaved: '{date}'`
+  - Append this step's output to the appropriate section of the document.
+
+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/templates/bmad/tea/workflows/testarch/ci/steps-c/step-01b-resume.md

@@ -0,0 +1,110 @@
+---
+name: 'step-01b-resume'
+description: 'Resume interrupted workflow from last completed step'
+outputFile: '{test_artifacts}/ci-pipeline-progress.md'
+---
+
+# Step 1b: Resume Workflow
+
+## STEP GOAL
+
+Resume an interrupted workflow by loading the existing progress document, displaying progress, verifying previously created artifacts, 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. Do not skip, reorder, or improvise.
+
+### 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. Verify Previously Created Artifacts
+
+Since this is a file-creation workflow, verify that artifacts from completed steps still exist on disk:
+
+- If `step-02-generate-pipeline` is in `stepsCompleted`, check that the pipeline config file exists (e.g., `.github/workflows/test.yml` or equivalent)
+- If any expected artifact is missing, warn the user and suggest re-running from the step that creates it
+
+---
+
+### 3. Display Progress Dashboard
+
+Display:
+
+"📋 **Workflow Resume — CI/CD Pipeline Setup**
+
+**Last saved:** {lastSaved}
+**Steps completed:** {stepsCompleted.length} of 4
+
+1. Preflight Checks (step-01-preflight) — {✅ if in stepsCompleted, ⬜ otherwise}
+2. Generate Pipeline (step-02-generate-pipeline) — {✅ if in stepsCompleted, ⬜ otherwise}
+3. Configure Quality Gates (step-03-configure-quality-gates) — {✅ if in stepsCompleted, ⬜ otherwise}
+4. Validate & Summary (step-04-validate-and-summary) — {✅ if in stepsCompleted, ⬜ otherwise}"
+
+---
+
+### 4. Route to Next Step
+
+Based on `lastStep`, load the next incomplete step:
+
+- `'step-01-preflight'` → Load `./step-02-generate-pipeline.md`
+- `'step-02-generate-pipeline'` → Load `./step-03-configure-quality-gates.md`
+- `'step-03-configure-quality-gates'` → Load `./step-04-validate-and-summary.md`
+- `'step-04-validate-and-summary'` → **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. Use it as reference for remaining steps.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Output document loaded and parsed correctly
+- Previously created artifacts verified
+- Progress dashboard displayed accurately
+- Routed to correct next step
+
+### ❌ SYSTEM FAILURE:
+
+- Not loading output document
+- Incorrect progress display
+- Routing to wrong step
+- Re-executing completed steps
+
+**Master Rule:** Resume MUST route to the exact next incomplete step. Never re-execute completed steps.