@cregis-dev/cckit 0.4.1 → 0.6.1

package/templates/bmad/tea/workflows/testarch/framework/steps-c/step-04-docs-and-scripts.md

@@ -1,105 +0,0 @@
----
-name: 'step-04-docs-and-scripts'
-description: 'Document setup and add package.json scripts'
-nextStepFile: './step-05-validate-and-summary.md'
-outputFile: '{test_dir}/README.md'
-progressFile: '{test_artifacts}/framework-setup-progress.md'
----
-
-# Step 4: Documentation & Scripts
-
-## STEP GOAL
-
-Create test documentation and add build/test scripts appropriate for `{detected_stack}`.
-
-## 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. tests/README.md
-
-Create `{outputFile}` and include:
-
-- Setup instructions
-- Running tests (local/headed/debug)
-- Architecture overview (fixtures, factories, helpers)
-- Best practices (selectors, isolation, cleanup)
-- CI integration notes
-- Knowledge base references
-
----
-
-## 2. Build & Test Scripts
-
-**If {detected_stack} is `frontend` or `fullstack`:**
-
-Add to `package.json` at minimum:
-
-- `test:e2e`: framework execution command (e.g., `npx playwright test`)
-
-**If {detected_stack} is `backend` or `fullstack`:**
-
-Add the idiomatic test commands for the detected framework:
-
-- **Python (pytest)**: Add to `pyproject.toml` scripts or `Makefile`: `pytest`, `pytest --cov`, `pytest -m integration`
-- **Java (JUnit)**: Add to `build.gradle`/`pom.xml`: `./gradlew test`, `mvn test`, `mvn verify` (integration)
-- **Go**: Add to `Makefile`: `go test ./...`, `go test -race ./...`, `go test -cover ./...`
-- **C#/.NET**: Add to CI scripts or `Makefile`: `dotnet test`, `dotnet test --collect:"XPlat Code Coverage"`
-- **Ruby (RSpec)**: Add to `Gemfile` binstubs or `Makefile`: `bundle exec rspec`, `bundle exec rspec spec/integration`
-
----
-
-### 3. Save Progress
-
-**Save this step's accumulated work to `{progressFile}`.**
-
-- **If `{progressFile}` does not exist** (first save), create it with YAML frontmatter:
-
-  ```yaml
-  ---
-  stepsCompleted: ['step-04-docs-and-scripts']
-  lastStep: 'step-04-docs-and-scripts'
-  lastSaved: '{date}'
-  ---
-  ```
-
-  Then write this step's output below the frontmatter.
-
-- **If `{progressFile}` already exists**, update:
-  - Add `'step-04-docs-and-scripts'` to `stepsCompleted` array (only if not already present)
-  - Set `lastStep: 'step-04-docs-and-scripts'`
-  - 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/framework/steps-c/step-05-validate-and-summary.md

@@ -1,93 +0,0 @@
----
-name: 'step-05-validate-and-summary'
-description: 'Validate against checklist and summarize'
-outputFile: '{test_artifacts}/framework-setup-progress.md'
----
-
-# Step 5: Validate & Summarize
-
-## STEP GOAL
-
-Validate framework setup and provide a completion summary.
-
-## 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. Validation
-
-Validate against `checklist.md`:
-
-- Preflight success
-- Directory structure created
-- Config correctness
-- Fixtures/factories created
-- Docs and scripts present
-
-Fix any gaps before completion.
-
----
-
-## 2. Completion Summary
-
-Report:
-
-- Framework selected
-- Artifacts created
-- Next steps (install deps, run tests)
-- Knowledge fragments applied
-
----
-
-### 3. 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-05-validate-and-summary']
-  lastStep: 'step-05-validate-and-summary'
-  lastSaved: '{date}'
-  ---
-  ```
-
-  Then write this step's output below the frontmatter.
-
-- **If `{outputFile}` already exists**, update:
-  - Add `'step-05-validate-and-summary'` to `stepsCompleted` array (only if not already present)
-  - Set `lastStep: 'step-05-validate-and-summary'`
-  - Set `lastSaved: '{date}'`
-  - Append this step's output to the appropriate section of the document.
-
-## 🚨 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/framework/steps-e/step-01-assess.md

@@ -1,65 +0,0 @@
----
-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/framework/steps-e/step-02-apply-edit.md

@@ -1,60 +0,0 @@
----
-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/framework/steps-v/step-01-validate.md

@@ -1,67 +0,0 @@
----
-name: 'step-01-validate'
-description: 'Validate workflow outputs against checklist'
-outputFile: '{test_artifacts}/framework-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/framework/validation-report-20260127-095021.md

@@ -1,73 +0,0 @@
----
-validationDate: 2026-01-27
-workflowName: testarch-framework
-workflowPath: {project-root}/src/workflows/testarch/framework
-validationStatus: COMPLETE
-completionDate: 2026-01-27 10:03:10
----
-
-# Validation Report: testarch-framework
-
-**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: 8
-
-**Step File Sizes:**
-
-- steps-c/step-01-preflight.md: 69 lines [GOOD]
-- steps-c/step-02-select-framework.md: 66 lines [GOOD]
-- steps-c/step-03-scaffold-framework.md: 107 lines [GOOD]
-- steps-c/step-04-docs-and-scripts.md: 63 lines [GOOD]
-- steps-c/step-05-validate-and-summary.md: 61 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-docs-and-scripts.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/framework/validation-report-20260127-102401.md

@@ -1,116 +0,0 @@
----
-validationDate: 2026-01-27
-workflowName: testarch-framework
-workflowPath: {project-root}/src/workflows/testarch/framework
-validationStatus: COMPLETE
-completionDate: 2026-01-27 10:24:01
----
-
-# Validation Report: testarch-framework
-
-**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: 8
-
-**Step File Sizes:**
-
-- steps-c/step-01-preflight.md: 68 lines [GOOD]
-- steps-c/step-02-select-framework.md: 65 lines [GOOD]
-- steps-c/step-03-scaffold-framework.md: 106 lines [GOOD]
-- steps-c/step-04-docs-and-scripts.md: 62 lines [GOOD]
-- steps-c/step-05-validate-and-summary.md: 60 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.md: Init [PASS]
-- steps-c/step-02-select-framework.md: Middle [PASS]
-- steps-c/step-03-scaffold-framework.md: Middle [PASS]
-- steps-c/step-04-docs-and-scripts.md: Middle [PASS]
-- steps-c/step-05-validate-and-summary.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-docs-and-scripts.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
-
-## Subagent Optimization Opportunities
-
-- 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
-- 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: 8 (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/framework/workflow-plan.md

@@ -1,22 +0,0 @@
-    # Workflow Plan: testarch-framework
-
-    ## Create Mode (steps-c)
-    - step-01-preflight.md
-
-- step-02-select-framework.md
-- step-03-scaffold-framework.md
-- step-04-docs-and-scripts.md
-- step-05-validate-and-summary.md
-
-  ## Validate Mode (steps-v)
-  - step-01-validate.md
-
-  ## Edit Mode (steps-e)
-  - step-01-assess.md
-  - step-02-apply-edit.md
-
-  ## Outputs
-  - Framework config (playwright.config.ts or cypress.config.ts)
-
-- {project-root}/tests/README.md
-- Test support scaffolding under {project-root}/tests

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

@@ -1,41 +0,0 @@
----
-name: testarch-framework
-description: Initialize test framework with Playwright or Cypress. Use when user says 'lets setup test framework' or 'I want to initialize testing framework'
-web_bundle: true
----
-
-# Test Framework Setup
-
-**Goal:** Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration
-
-**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.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/framework/workflow.yaml

@@ -1,48 +0,0 @@
-# Test Architect workflow: framework
-name: testarch-framework
-# prettier-ignore
-description: 'Initialize test framework with Playwright or Cypress. Use when the user says "lets setup test framework" or "I want to initialize testing framework"'
-
-# 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/framework"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# Variables and inputs
-variables:
-  test_dir: "{project-root}/tests" # Root test directory
-  use_typescript: true # Prefer TypeScript configuration
-  framework_preference: "auto" # auto, playwright, cypress - user can override auto-detection
-  project_size: "auto" # auto, small, large - influences framework recommendation
-
-# Output configuration
-default_output_file: "{test_dir}/README.md" # Main deliverable is test setup README
-
-# Required tools
-required_tools:
-  - read_file # Read package.json, existing configs
-  - write_file # Create config files, helpers, fixtures, tests
-  - create_directory # Create test directory structure
-  - list_files # Check for existing framework
-  - search_repo # Find architecture docs
-
-tags:
-  - qa
-  - setup
-  - test-architect
-  - framework
-  - initialization
-
-execution_hints:
-  interactive: false # Minimize prompts; auto-detect when possible
-  autonomous: true # Proceed without user input unless blocked
-  iterative: true