@cregis-dev/cckit 0.4.0 → 0.5.0

package/templates/bmad/tea/workflows/testarch/atdd/steps-c/step-04b-subprocess-e2e-failing.md

@@ -1,244 +0,0 @@
----
-name: 'step-04b-subprocess-e2e-failing'
-description: 'Subprocess: Generate FAILING E2E tests (TDD red phase)'
-subprocess: true
-outputFile: '/tmp/tea-atdd-e2e-tests-{{timestamp}}.json'
----
-
-# Subprocess 4B: Generate Failing E2E Tests (TDD Red Phase)
-
-## SUBPROCESS CONTEXT
-
-This is an **isolated subprocess** running in parallel with API failing test generation.
-
-**What you have from parent workflow:**
-
-- Story acceptance criteria from Step 1
-- Test strategy and user journey scenarios from Step 3
-- Knowledge fragments loaded: fixture-architecture, network-first, selector-resilience
-- Config: test framework, Playwright Utils enabled/disabled
-
-**Your task:** Generate E2E tests that will FAIL because the feature UI is not implemented yet (TDD RED PHASE).
-
----
-
-## MANDATORY EXECUTION RULES
-
-- 📖 Read this entire subprocess file before acting
-- ✅ Generate FAILING E2E tests ONLY
-- ✅ Tests MUST fail when run (UI not implemented yet)
-- ✅ Output structured JSON to temp file
-- ✅ Follow knowledge fragment patterns
-- ❌ Do NOT generate API tests (that's subprocess 4A)
-- ❌ Do NOT generate passing tests (this is TDD red phase)
-- ❌ Do NOT run tests (that's step 5)
-
----
-
-## SUBPROCESS TASK
-
-### 1. Identify User Journeys from Acceptance Criteria
-
-From the story acceptance criteria (Step 1 output), identify:
-
-- Which UI flows will be created for this story
-- User interactions required
-- Expected visual states
-- Success/error messages expected
-
-**Example Acceptance Criteria:**
-
-```
-Story: User Registration
-- As a user, I can navigate to /register page
-- I can fill in email and password fields
-- I can click "Register" button
-- System shows success message and redirects to dashboard
-- System shows error if email already exists
-```
-
-### 2. Browser Interaction (Selector Verification)
-
-**Automation mode:** `config.tea_browser_automation`
-
-If `auto` (fall back to MCP if CLI unavailable; if neither available, generate from best practices):
-
-- Open the target page first, then verify selectors with a snapshot:
-  `playwright-cli -s=tea-atdd-{{timestamp}} open <target_url>`
-  `playwright-cli -s=tea-atdd-{{timestamp}} snapshot` → map refs to Playwright locators
-  - ref `{role: "button", name: "Submit"}` → `page.getByRole('button', { name: 'Submit' })`
-  - ref `{role: "textbox", name: "Email"}` → `page.getByRole('textbox', { name: 'Email' })`
-- `playwright-cli -s=tea-atdd-{{timestamp}} close` when done
-
-If `cli` (CLI only — do NOT fall back to MCP; generate from best practices if CLI unavailable):
-
-- Open the target page first, then verify selectors with a snapshot:
-  `playwright-cli -s=tea-atdd-{{timestamp}} open <target_url>`
-  `playwright-cli -s=tea-atdd-{{timestamp}} snapshot` → map refs to Playwright locators
-  - ref `{role: "button", name: "Submit"}` → `page.getByRole('button', { name: 'Submit' })`
-  - ref `{role: "textbox", name: "Email"}` → `page.getByRole('textbox', { name: 'Email' })`
-- `playwright-cli -s=tea-atdd-{{timestamp}} close` when done
-
-> **Session Hygiene:** Always close sessions using `playwright-cli -s=tea-atdd-{{timestamp}} close`. Do NOT use `close-all` — it kills every session on the machine and breaks parallel execution.
-
-If `mcp`:
-
-- Use MCP tools for selector verification (current behavior)
-
-If `none`:
-
-- Generate selectors from best practices without browser verification
-
-### 3. Generate FAILING E2E Test Files
-
-For each user journey, create test file in `tests/e2e/[feature].spec.ts`:
-
-**Test Structure (ATDD - Red Phase):**
-
-```typescript
-import { test, expect } from '@playwright/test';
-
-test.describe('[Story Name] E2E User Journey (ATDD)', () => {
-  test.skip('[P0] should complete user registration successfully', async ({ page }) => {
-    // THIS TEST WILL FAIL - UI not implemented yet
-    await page.goto('/register');
-
-    // Expect registration form but will get 404 or missing elements
-    await page.fill('[name="email"]', 'newuser@example.com');
-    await page.fill('[name="password"]', 'SecurePass123!');
-    await page.click('button:has-text("Register")');
-
-    // Expect success message and redirect
-    await expect(page.getByText('Registration successful!')).toBeVisible();
-    await page.waitForURL('/dashboard');
-  });
-
-  test.skip('[P1] should show error if email exists', async ({ page }) => {
-    // THIS TEST WILL FAIL - UI not implemented yet
-    await page.goto('/register');
-
-    await page.fill('[name="email"]', 'existing@example.com');
-    await page.fill('[name="password"]', 'SecurePass123!');
-    await page.click('button:has-text("Register")');
-
-    // Expect error message
-    await expect(page.getByText('Email already exists')).toBeVisible();
-  });
-});
-```
-
-**CRITICAL ATDD Requirements:**
-
-- ✅ Use `test.skip()` to mark tests as intentionally failing (red phase)
-- ✅ Write assertions for EXPECTED UI behavior (even though not implemented)
-- ✅ Use resilient selectors: getByRole, getByText, getByLabel (from selector-resilience)
-- ✅ Follow network-first patterns if API calls involved (from network-first)
-- ✅ Test complete user journeys from acceptance criteria
-- ✅ Include priority tags [P0], [P1], [P2], [P3]
-- ✅ Use proper TypeScript types
-- ✅ Deterministic waits (no hard sleeps)
-
-**Why test.skip():**
-
-- Tests are written correctly for EXPECTED UI behavior
-- But we know they'll fail because UI isn't implemented
-- `test.skip()` documents this is intentional (TDD red phase)
-- Once UI is implemented, remove `test.skip()` to verify green phase
-
-### 4. Track Fixture Needs
-
-Identify fixtures needed for E2E tests:
-
-- Authentication fixtures (if journey requires logged-in state)
-- Network mocks (if API calls involved)
-- Test data fixtures
-
-**Do NOT create fixtures yet** - just track what's needed for aggregation step.
-
----
-
-## OUTPUT FORMAT
-
-Write JSON to temp file: `/tmp/tea-atdd-e2e-tests-{{timestamp}}.json`
-
-```json
-{
-  "success": true,
-  "subprocess": "atdd-e2e-tests",
-  "tests": [
-    {
-      "file": "tests/e2e/user-registration.spec.ts",
-      "content": "[full TypeScript test file content with test.skip()]",
-      "description": "ATDD E2E tests for user registration journey (RED PHASE)",
-      "expected_to_fail": true,
-      "acceptance_criteria_covered": [
-        "User can navigate to /register",
-        "User can fill registration form",
-        "System shows success message on registration",
-        "System shows error if email exists"
-      ],
-      "priority_coverage": {
-        "P0": 1,
-        "P1": 1,
-        "P2": 0,
-        "P3": 0
-      }
-    }
-  ],
-  "fixture_needs": ["registrationPageMock"],
-  "knowledge_fragments_used": ["fixture-architecture", "network-first", "selector-resilience"],
-  "test_count": 2,
-  "tdd_phase": "RED",
-  "summary": "Generated 2 FAILING E2E tests for user registration story"
-}
-```
-
-**On Error:**
-
-```json
-{
-  "success": false,
-  "subprocess": "atdd-e2e-tests",
-  "error": "Error message describing what went wrong",
-  "partial_output": {
-    /* any tests generated before error */
-  }
-}
-```
-
----
-
-## EXIT CONDITION
-
-Subprocess completes when:
-
-- ✅ All user journeys from acceptance criteria have test files
-- ✅ All tests use `test.skip()` (documented failing tests)
-- ✅ All tests assert EXPECTED UI behavior (not placeholder assertions)
-- ✅ Resilient selectors used (getByRole, getByText)
-- ✅ JSON output written to temp file
-- ✅ Fixture needs tracked
-
-**Subprocess terminates here.** Parent workflow will read output and proceed to aggregation.
-
----
-
-## 🚨 SUBPROCESS SUCCESS METRICS
-
-### ✅ SUCCESS:
-
-- All E2E tests generated with test.skip()
-- Tests assert expected UI behavior (not placeholders)
-- Resilient selectors used (getByRole, getByText)
-- JSON output valid and complete
-- No API/component/unit tests included (out of scope)
-- Tests follow knowledge fragment patterns
-
-### ❌ FAILURE:
-
-- Generated passing tests (wrong - this is RED phase)
-- Tests without test.skip() (will break CI)
-- Placeholder assertions (expect(true).toBe(true))
-- Brittle selectors used (CSS classes, XPath)
-- Did not follow knowledge fragment patterns
-- Invalid or missing JSON output

package/templates/bmad/tea/workflows/testarch/atdd/steps-c/step-04c-aggregate.md

@@ -1,370 +0,0 @@
----
-name: 'step-04c-aggregate'
-description: 'Aggregate subagent outputs and complete ATDD test infrastructure'
-outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
-nextStepFile: './step-05-validate-and-complete.md'
----
-
-# Step 4C: Aggregate ATDD Test Generation Results
-
-## STEP GOAL
-
-Read outputs from parallel subagents (API + E2E failing test generation), aggregate results, verify TDD red phase compliance, and create supporting infrastructure.
-
----
-
-## MANDATORY EXECUTION RULES
-
-- 📖 Read the entire step file before acting
-- ✅ Speak in `{communication_language}`
-- ✅ Read subagent outputs from temp files
-- ✅ Verify all tests are marked with test.skip() (TDD red phase)
-- ✅ Generate shared fixtures based on fixture needs
-- ✅ Write all generated test files to disk
-- ❌ Do NOT remove test.skip() (that's done after feature implementation)
-- ❌ Do NOT run tests yet (that's step 5 - verify they fail)
-
----
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow the MANDATORY SEQUENCE exactly
-- 💾 Record outputs before proceeding
-- 📖 Load the next step only when instructed
-
-## CONTEXT BOUNDARIES:
-
-- Available context: config, subagent outputs from temp files
-- Focus: aggregation and TDD validation
-- Limits: do not execute future steps
-- Dependencies: Step 4A and 4B subagent outputs
-
----
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-### 1. Read Subagent Outputs
-
-**Read API test subagent output:**
-
-```javascript
-const apiTestsPath = '/tmp/tea-atdd-api-tests-{{timestamp}}.json';
-const apiTestsOutput = JSON.parse(fs.readFileSync(apiTestsPath, 'utf8'));
-```
-
-**Read E2E test subagent output:**
-
-```javascript
-const e2eTestsPath = '/tmp/tea-atdd-e2e-tests-{{timestamp}}.json';
-const e2eTestsOutput = JSON.parse(fs.readFileSync(e2eTestsPath, 'utf8'));
-```
-
-**Verify both subagents succeeded:**
-
-- Check `apiTestsOutput.success === true`
-- Check `e2eTestsOutput.success === true`
-- If either failed, report error and stop (don't proceed)
-
----
-
-### 2. Verify TDD Red Phase Compliance
-
-**CRITICAL TDD Validation:**
-
-**Check API tests:**
-
-```javascript
-apiTestsOutput.tests.forEach((test) => {
-  // Verify test.skip() is present
-  if (!test.content.includes('test.skip(')) {
-    throw new Error(`ATDD ERROR: ${test.file} missing test.skip() - tests MUST be skipped in red phase!`);
-  }
-
-  // Verify not placeholder assertions
-  if (test.content.includes('expect(true).toBe(true)')) {
-    throw new Error(`ATDD ERROR: ${test.file} has placeholder assertions - must assert EXPECTED behavior!`);
-  }
-
-  // Verify expected_to_fail flag
-  if (!test.expected_to_fail) {
-    throw new Error(`ATDD ERROR: ${test.file} not marked as expected_to_fail!`);
-  }
-});
-```
-
-**Check E2E tests:**
-
-```javascript
-e2eTestsOutput.tests.forEach((test) => {
-  // Same validation as API tests
-  if (!test.content.includes('test.skip(')) {
-    throw new Error(`ATDD ERROR: ${test.file} missing test.skip() - tests MUST be skipped in red phase!`);
-  }
-
-  if (test.content.includes('expect(true).toBe(true)')) {
-    throw new Error(`ATDD ERROR: ${test.file} has placeholder assertions!`);
-  }
-
-  if (!test.expected_to_fail) {
-    throw new Error(`ATDD ERROR: ${test.file} not marked as expected_to_fail!`);
-  }
-});
-```
-
-**If validation passes:**
-
-```
-✅ TDD Red Phase Validation: PASS
-- All tests use test.skip()
-- All tests assert expected behavior (not placeholders)
-- All tests marked as expected_to_fail
-```
-
----
-
-### 3. Write All Test Files to Disk
-
-**Write API test files:**
-
-```javascript
-apiTestsOutput.tests.forEach((test) => {
-  fs.writeFileSync(test.file, test.content, 'utf8');
-  console.log(`✅ Created (RED): ${test.file}`);
-});
-```
-
-**Write E2E test files:**
-
-```javascript
-e2eTestsOutput.tests.forEach((test) => {
-  fs.writeFileSync(test.file, test.content, 'utf8');
-  console.log(`✅ Created (RED): ${test.file}`);
-});
-```
-
----
-
-### 4. Aggregate Fixture Needs
-
-**Collect all fixture needs from both subagents:**
-
-```javascript
-const allFixtureNeeds = [...apiTestsOutput.fixture_needs, ...e2eTestsOutput.fixture_needs];
-
-// Remove duplicates
-const uniqueFixtures = [...new Set(allFixtureNeeds)];
-```
-
----
-
-### 5. Generate Fixture Infrastructure
-
-**Create fixtures needed by ATDD tests:**
-(Similar to automate workflow, but may be simpler for ATDD since feature not implemented)
-
-**Minimal fixtures for TDD red phase:**
-
-```typescript
-// tests/fixtures/test-data.ts
-export const testUserData = {
-  email: 'test@example.com',
-  password: 'SecurePass123!',
-};
-```
-
-Note: More complete fixtures will be needed when moving to green phase.
-
----
-
-### 6. Generate ATDD Checklist
-
-**Create ATDD checklist document:**
-
-```markdown
-# ATDD Checklist: [Story Name]
-
-## TDD Red Phase (Current)
-
-✅ Failing tests generated
-
-- API Tests: {api_test_count} tests (all skipped)
-- E2E Tests: {e2e_test_count} tests (all skipped)
-
-## Acceptance Criteria Coverage
-
-{list all acceptance criteria with test coverage}
-
-## Next Steps (TDD Green Phase)
-
-After implementing the feature:
-
-1. Remove `test.skip()` from all test files
-2. Run tests: `npm test`
-3. Verify tests PASS (green phase)
-4. If any tests fail:
-   - Either fix implementation (feature bug)
-   - Or fix test (test bug)
-5. Commit passing tests
-
-## Implementation Guidance
-
-Feature endpoints to implement:
-{list endpoints from API tests}
-
-UI components to implement:
-{list UI flows from E2E tests}
-```
-
-**Save checklist:**
-
-```javascript
-fs.writeFileSync(`{test_artifacts}/atdd-checklist-{story-id}.md`, checklistContent, 'utf8');
-```
-
----
-
-### 7. Calculate Summary Statistics
-
-**Aggregate test counts:**
-
-```javascript
-const resolvedMode = subagentContext?.execution?.resolvedMode; // Provided by Step 4's orchestration context
-const subagentExecutionLabel =
-  resolvedMode === 'sequential'
-    ? 'SEQUENTIAL (API → E2E)'
-    : resolvedMode === 'agent-team'
-      ? 'AGENT-TEAM (API + E2E)'
-      : resolvedMode === 'subagent'
-        ? 'SUBAGENT (API + E2E)'
-        : 'PARALLEL (API + E2E)';
-const performanceGainLabel =
-  resolvedMode === 'sequential'
-    ? 'baseline (no parallel speedup)'
-    : resolvedMode === 'agent-team' || resolvedMode === 'subagent'
-      ? '~50% faster than sequential'
-      : 'mode-dependent';
-
-const summary = {
-  tdd_phase: 'RED',
-  total_tests: apiTestsOutput.test_count + e2eTestsOutput.test_count,
-  api_tests: apiTestsOutput.test_count,
-  e2e_tests: e2eTestsOutput.test_count,
-  all_tests_skipped: true,
-  expected_to_fail: true,
-  fixtures_created: uniqueFixtures.length,
-  acceptance_criteria_covered: [
-    ...apiTestsOutput.tests.flatMap((t) => t.acceptance_criteria_covered),
-    ...e2eTestsOutput.tests.flatMap((t) => t.acceptance_criteria_covered),
-  ],
-  knowledge_fragments_used: [...apiTestsOutput.knowledge_fragments_used, ...e2eTestsOutput.knowledge_fragments_used],
-  subagent_execution: subagentExecutionLabel,
-  performance_gain: performanceGainLabel,
-};
-```
-
-**Store summary for Step 5:**
-
-```javascript
-fs.writeFileSync('/tmp/tea-atdd-summary-{{timestamp}}.json', JSON.stringify(summary, null, 2), 'utf8');
-```
-
----
-
-## OUTPUT SUMMARY
-
-Display to user:
-
-```
-✅ ATDD Test Generation Complete (TDD RED PHASE)
-
-🔴 TDD Red Phase: Failing Tests Generated
-
-📊 Summary:
-- Total Tests: {total_tests} (all with test.skip())
-  - API Tests: {api_tests} (RED)
-  - E2E Tests: {e2e_tests} (RED)
-- Fixtures Created: {fixtures_created}
-- All tests will FAIL until feature implemented
-
-✅ Acceptance Criteria Coverage:
-{list all covered criteria}
-
-🚀 Performance: {performance_gain}
-
-📂 Generated Files:
-- tests/api/[feature].spec.ts (with test.skip())
-- tests/e2e/[feature].spec.ts (with test.skip())
-- tests/fixtures/test-data.ts
-- {test_artifacts}/atdd-checklist-{story-id}.md
-
-📝 Next Steps:
-1. Implement the feature
-2. Remove test.skip() from tests
-3. Run tests → verify PASS (green phase)
-4. Commit passing tests
-
-✅ Ready for validation (Step 5 - verify tests fail as expected)
-```
-
----
-
-## EXIT CONDITION
-
-Proceed to Step 5 when:
-
-- ✅ All test files written to disk (API + E2E)
-- ✅ All tests verified to have test.skip()
-- ✅ All fixtures created
-- ✅ ATDD checklist generated
-- ✅ Summary statistics calculated and saved
-- ✅ Output displayed to user
-
----
-
-### 8. 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-04c-aggregate']
-  lastStep: 'step-04c-aggregate'
-  lastSaved: '{date}'
-  ---
-  ```
-
-  Then write this step's output below the frontmatter.
-
-- **If `{outputFile}` already exists**, update:
-  - Add `'step-04c-aggregate'` to `stepsCompleted` array (only if not already present)
-  - Set `lastStep: 'step-04c-aggregate'`
-  - Set `lastSaved: '{date}'`
-  - Append this step's output to the appropriate section.
-
-Load next step: `{nextStepFile}`
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
-
-### ✅ SUCCESS:
-
-- Both subagents succeeded
-- All tests have test.skip() (TDD red phase compliant)
-- All tests assert expected behavior (not placeholders)
-- All test files written to disk
-- ATDD checklist generated
-
-### ❌ SYSTEM FAILURE:
-
-- One or both subagents failed
-- Tests missing test.skip() (would break CI)
-- Tests have placeholder assertions
-- Test files not written to disk
-- ATDD checklist missing
-
-**Master Rule:** TDD RED PHASE requires ALL tests to use test.skip() and assert expected behavior.

package/templates/bmad/tea/workflows/testarch/atdd/steps-c/step-05-validate-and-complete.md

@@ -1,106 +0,0 @@
----
-name: 'step-05-validate-and-complete'
-description: 'Validate ATDD outputs and summarize'
-outputFile: '{test_artifacts}/atdd-checklist-{story_id}.md'
----
-
-# Step 5: Validate & Complete
-
-## STEP GOAL
-
-Validate ATDD outputs and provide a completion summary.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 Read the entire step file before acting
-- ✅ Speak in `{communication_language}`
-- ✅ Validate against the checklist
-
----
-
-## 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
-
-Use `checklist.md` to validate:
-
-- Prerequisites satisfied
-- Test files created correctly
-- Checklist matches acceptance criteria
-- Tests are designed to fail before implementation
-- [ ] CLI sessions cleaned up (no orphaned browsers)
-- [ ] Temp artifacts stored in `{test_artifacts}/` not random locations
-
-Fix any gaps before completion.
-
----
-
-## 2. Polish Output
-
-Before finalizing, review the complete output document for quality:
-
-1. **Remove duplication**: Progressive-append workflow may have created repeated sections — consolidate
-2. **Verify consistency**: Ensure terminology, risk scores, and references are consistent throughout
-3. **Check completeness**: All template sections should be populated or explicitly marked N/A
-4. **Format cleanup**: Ensure markdown formatting is clean (tables aligned, headers consistent, no orphaned references)
-
----
-
-## 3. Completion Summary
-
-Report:
-
-- Test files created
-- Checklist output path
-- Key risks or assumptions
-- Next recommended workflow (e.g., implementation or `automate`)
-
----
-
-## 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-05-validate-and-complete']
-  lastStep: 'step-05-validate-and-complete'
-  lastSaved: '{date}'
-  ---
-  ```
-
-  Then write this step's output below the frontmatter.
-
-- **If `{outputFile}` already exists**, update:
-  - Add `'step-05-validate-and-complete'` to `stepsCompleted` array (only if not already present)
-  - Set `lastStep: 'step-05-validate-and-complete'`
-  - Set `lastSaved: '{date}'`
-  - Append this step's output to the appropriate section.
-
-## 🚨 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.