@cregis-dev/cckit 0.2.0

package/templates/bmad/tea/workflows/testarch/atdd/steps-c/step-01b-resume.md

@@ -0,0 +1,96 @@
+---
+name: 'step-01b-resume'
+description: 'Resume interrupted workflow from last completed step'
+outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
+---
+
+# Step 1b: Resume Workflow
+
+## STEP GOAL
+
+Resume an interrupted workflow by loading the existing output document, displaying progress, 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.
+
+### 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. Display Progress Dashboard
+
+Display progress with ✅/⬜ indicators:
+
+1. ✅/⬜ Preflight & Context (step-01-preflight-and-context)
+2. ✅/⬜ Generation Mode (step-02-generation-mode)
+3. ✅/⬜ Test Strategy (step-03-test-strategy)
+4. ✅/⬜ Generate Tests + Aggregate (step-04c-aggregate)
+5. ✅/⬜ Validate & Complete (step-05-validate-and-complete)
+
+---
+
+### 3. Route to Next Step
+
+Based on `lastStep`, load the next incomplete step:
+
+- `'step-01-preflight-and-context'` → load `./step-02-generation-mode.md`
+- `'step-02-generation-mode'` → load `./step-03-test-strategy.md`
+- `'step-03-test-strategy'` → load `./step-04-generate-tests.md`
+- `'step-04c-aggregate'` → load `./step-05-validate-and-complete.md`
+- `'step-05-validate-and-complete'` → **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.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Output document loaded and parsed correctly
+- Progress dashboard displayed accurately
+- Routed to correct next step
+
+### ❌ SYSTEM FAILURE:
+
+- Not loading output document
+- Incorrect progress display
+- Routing to wrong step
+
+**Master Rule:** Resume MUST route to the exact next incomplete step. Never re-execute completed steps.

package/templates/bmad/tea/workflows/testarch/atdd/steps-c/step-02-generation-mode.md

@@ -0,0 +1,125 @@
+---
+name: 'step-02-generation-mode'
+description: 'Choose AI generation or recording mode'
+outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
+nextStepFile: './step-03-test-strategy.md'
+---
+
+# Step 2: Generation Mode Selection
+
+## STEP GOAL
+
+Choose the appropriate generation mode for ATDD tests.
+
+## 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. Default Mode: AI Generation
+
+Use AI generation when:
+
+- Acceptance criteria are clear
+- Scenarios are standard (CRUD, auth, API, navigation)
+- **If {detected_stack} is `backend`:** Always use AI generation (no browser recording needed)
+
+Proceed directly to test strategy if this applies.
+
+---
+
+## 2. Optional Mode: Recording (Complex UI)
+
+**Skip this section entirely if {detected_stack} is `backend`.** For backend projects, use AI generation from API documentation, OpenAPI/Swagger specs, or source code analysis instead.
+
+**If {detected_stack} is `frontend` or `fullstack`:**
+
+Use recording when UI interactions need live browser verification.
+
+**Tool selection based on `config.tea_browser_automation`:**
+
+If `auto`:
+
+> **Note:** `${timestamp}` is a placeholder the agent should replace with a unique value (e.g., epoch seconds) for session isolation.
+
+- **Simple recording** (snapshot selectors, capture structure): Use CLI
+  - `playwright-cli -s=tea-atdd-${timestamp} open <url>` → `playwright-cli -s=tea-atdd-${timestamp} snapshot` → extract refs
+- **Complex recording** (drag/drop, wizards, multi-step state): Use MCP
+  - Full browser automation with rich tool semantics
+- **Fallback:** If preferred tool unavailable, use the other; if neither, skip recording
+
+If `cli`:
+
+- Use Playwright CLI for all recording
+- `playwright-cli -s=tea-atdd-${timestamp} open <url>`, `snapshot`, `screenshot`, `click <ref>`, etc.
+
+If `mcp`:
+
+- Use Playwright MCP tools for all recording (current behavior)
+- Confirm MCP availability, record selectors and interactions
+
+If `none`:
+
+- Skip recording mode entirely, use AI generation from documentation
+
+---
+
+## 3. Confirm Mode
+
+State the chosen mode and why. Then proceed.
+
+---
+
+## 4. 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-02-generation-mode']
+  lastStep: 'step-02-generation-mode'
+  lastSaved: '{date}'
+  ---
+  ```
+
+  Then write this step's output below the frontmatter.
+
+- **If `{outputFile}` already exists**, update:
+  - Add `'step-02-generation-mode'` to `stepsCompleted` array (only if not already present)
+  - Set `lastStep: 'step-02-generation-mode'`
+  - Set `lastSaved: '{date}'`
+  - Append this step's output to the appropriate section.
+
+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/atdd/steps-c/step-03-test-strategy.md

@@ -0,0 +1,110 @@
+---
+name: 'step-03-test-strategy'
+description: 'Map acceptance criteria to test levels and priorities'
+outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
+nextStepFile: './step-04-generate-tests.md'
+---
+
+# Step 3: Test Strategy
+
+## STEP GOAL
+
+Translate acceptance criteria into a prioritized, level-appropriate test plan.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the entire step file before acting
+- ✅ Speak in `{communication_language}`
+- 🚫 Avoid duplicate coverage across levels
+
+---
+
+## 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. Map Acceptance Criteria
+
+- Convert each acceptance criterion into test scenarios
+- Include negative and edge cases where risk is high
+
+---
+
+## 2. Select Test Levels
+
+Choose the best level per scenario based on `{detected_stack}`:
+
+**If {detected_stack} is `frontend` or `fullstack`:**
+
+- **E2E** for critical user journeys
+- **API** for business logic and service contracts
+- **Component** for UI behavior
+
+**If {detected_stack} is `backend` or `fullstack`:**
+
+- **Unit** for pure functions, business logic, and edge cases
+- **Integration** for service interactions, database queries, and middleware
+- **API/Contract** for endpoint validation, request/response schemas, and Pact contracts
+- **No E2E** for pure backend projects (no browser-based testing needed)
+
+---
+
+## 3. Prioritize Tests
+
+Assign P0–P3 priorities using risk and business impact.
+
+---
+
+## 4. Confirm Red Phase Requirements
+
+Ensure all tests are designed to **fail before implementation** (TDD red phase).
+
+---
+
+## 5. 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-03-test-strategy']
+  lastStep: 'step-03-test-strategy'
+  lastSaved: '{date}'
+  ---
+  ```
+
+  Then write this step's output below the frontmatter.
+
+- **If `{outputFile}` already exists**, update:
+  - Add `'step-03-test-strategy'` to `stepsCompleted` array (only if not already present)
+  - Set `lastStep: 'step-03-test-strategy'`
+  - Set `lastSaved: '{date}'`
+  - Append this step's output to the appropriate section.
+
+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/atdd/steps-c/step-04-generate-tests.md

@@ -0,0 +1,229 @@
+---
+name: 'step-04-generate-tests'
+description: 'Orchestrate parallel FAILING test generation (TDD red phase)'
+nextStepFile: './step-04c-aggregate.md'
+---
+
+# Step 4: Orchestrate Parallel FAILING Test Generation
+
+## STEP GOAL
+
+Launch parallel subprocesses to generate FAILING API and E2E tests simultaneously (TDD RED PHASE) for maximum performance.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the entire step file before acting
+- ✅ Speak in `{communication_language}`
+- ✅ Launch TWO subprocesses in PARALLEL
+- ✅ Generate FAILING tests only (TDD red phase)
+- ✅ Wait for BOTH subprocesses to complete
+- ❌ Do NOT generate sequential tests (use subprocesses)
+- ❌ Do NOT generate passing tests (this is red phase)
+- ❌ Do NOT proceed until both subprocesses finish
+
+---
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Wait for subprocess outputs
+- 📖 Load the next step only when instructed
+
+## CONTEXT BOUNDARIES:
+
+- Available context: config, acceptance criteria from Step 1, test strategy from Step 3
+- Focus: subprocess orchestration only
+- Limits: do not generate tests directly (delegate to subprocesses)
+- Dependencies: Steps 1-3 outputs
+
+---
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Prepare Subprocess Inputs
+
+**Generate unique timestamp** for temp file naming:
+
+```javascript
+const timestamp = new Date().toISOString().replace(/[:.]/g, '-');
+```
+
+**Prepare input context for both subprocesses:**
+
+```javascript
+const subprocessContext = {
+  story_acceptance_criteria: /* from Step 1 */,
+  test_strategy: /* from Step 3 */,
+  knowledge_fragments_loaded: /* list of fragments */,
+  config: {
+    test_framework: config.test_framework,
+    use_playwright_utils: config.tea_use_playwright_utils,
+    browser_automation: config.tea_browser_automation
+  },
+  timestamp: timestamp
+};
+```
+
+---
+
+### 2. Launch Subprocess A: Failing API Test Generation
+
+**Launch subprocess in parallel:**
+
+- **Subprocess File:** `./step-04a-subprocess-api-failing.md`
+- **Output File:** `/tmp/tea-atdd-api-tests-${timestamp}.json`
+- **Context:** Pass `subprocessContext`
+- **Execution:** PARALLEL (non-blocking)
+- **TDD Phase:** RED (failing tests)
+
+**System Action:**
+
+```
+🚀 Launching Subprocess A: FAILING API Test Generation (RED PHASE)
+📝 Output: /tmp/tea-atdd-api-tests-${timestamp}.json
+🔴 TDD Phase: RED (tests will fail until feature implemented)
+⏳ Status: Running in parallel...
+```
+
+---
+
+### 3. Launch Subprocess B: Failing E2E Test Generation
+
+**Launch subprocess in parallel:**
+
+- **Subprocess File:** `./step-04b-subprocess-e2e-failing.md`
+- **Output File:** `/tmp/tea-atdd-e2e-tests-${timestamp}.json`
+- **Context:** Pass `subprocessContext`
+- **Execution:** PARALLEL (non-blocking)
+- **TDD Phase:** RED (failing tests)
+
+**System Action:**
+
+```
+🚀 Launching Subprocess B: FAILING E2E Test Generation (RED PHASE)
+📝 Output: /tmp/tea-atdd-e2e-tests-${timestamp}.json
+🔴 TDD Phase: RED (tests will fail until feature implemented)
+⏳ Status: Running in parallel...
+```
+
+---
+
+### 4. Wait for Both Subprocesses to Complete
+
+**Monitor subprocess execution:**
+
+```
+⏳ Waiting for subprocesses to complete...
+  ├── Subprocess A (API RED): Running... ⟳
+  └── Subprocess B (E2E RED): Running... ⟳
+
+[... time passes ...]
+
+  ├── Subprocess A (API RED): Complete ✅
+  └── Subprocess B (E2E RED): Complete ✅
+
+✅ All subprocesses completed successfully!
+```
+
+**Verify both outputs exist:**
+
+```javascript
+const apiOutputExists = fs.existsSync(`/tmp/tea-atdd-api-tests-${timestamp}.json`);
+const e2eOutputExists = fs.existsSync(`/tmp/tea-atdd-e2e-tests-${timestamp}.json`);
+
+if (!apiOutputExists || !e2eOutputExists) {
+  throw new Error('One or both subprocess outputs missing!');
+}
+```
+
+---
+
+### 5. TDD Red Phase Report
+
+**Display TDD status:**
+
+```
+🔴 TDD RED PHASE: Failing Tests Generated
+
+✅ Both subprocesses completed:
+- API Tests: Generated with test.skip()
+- E2E Tests: Generated with test.skip()
+
+📋 All tests assert EXPECTED behavior
+📋 All tests will FAIL until feature implemented
+📋 This is INTENTIONAL (TDD red phase)
+
+Next: Aggregation will verify TDD compliance
+```
+
+---
+
+### 6. Performance Report
+
+**Display performance metrics:**
+
+```
+🚀 Performance Report:
+- Execution Mode: PARALLEL (2 subprocesses)
+- API Test Generation: ~X minutes
+- E2E Test Generation: ~Y minutes
+- Total Elapsed: ~max(X, Y) minutes
+- Sequential Would Take: ~(X + Y) minutes
+- Performance Gain: ~50% faster!
+```
+
+---
+
+### 7. Proceed to Aggregation
+
+**Load aggregation step:**
+Load next step: `{nextStepFile}`
+
+The aggregation step (4C) will:
+
+- Read both subprocess outputs
+- Verify TDD red phase compliance (all tests have test.skip())
+- Write all test files to disk
+- Generate ATDD checklist
+- Calculate summary statistics
+
+---
+
+## EXIT CONDITION
+
+Proceed to Step 4C (Aggregation) when:
+
+- ✅ Subprocess A (API failing tests) completed successfully
+- ✅ Subprocess B (E2E failing tests) completed successfully
+- ✅ Both output files exist and are valid JSON
+- ✅ TDD red phase status reported
+
+**Do NOT proceed if:**
+
+- ❌ One or both subprocesses failed
+- ❌ Output files missing or corrupted
+- ❌ Subprocess generated passing tests (wrong - must be failing)
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Both subprocesses launched successfully
+- Both subprocesses completed without errors
+- Output files generated and valid
+- Tests generated with test.skip() (TDD red phase)
+- Parallel execution achieved ~50% performance gain
+
+### ❌ SYSTEM FAILURE:
+
+- Failed to launch subprocesses
+- One or both subprocesses failed
+- Output files missing or invalid
+- Tests generated without test.skip() (wrong phase)
+- Attempted sequential generation instead of parallel
+
+**Master Rule:** TDD RED PHASE requires FAILING tests (with test.skip()). Parallel subprocess execution is MANDATORY for performance.