@cregis-dev/cckit 0.4.1 → 0.6.1

package/templates/bmad/tea/workflows/testarch/trace/steps-c/step-01-load-context.md

@@ -1,105 +0,0 @@
----
-name: 'step-01-load-context'
-description: 'Load requirements, knowledge base, and related artifacts'
-nextStepFile: './step-02-discover-tests.md'
-knowledgeIndex: '{project-root}/_bmad/tea/testarch/tea-index.csv'
-outputFile: '{test_artifacts}/traceability-report.md'
----
-
-# Step 1: Load Context & Knowledge Base
-
-## STEP GOAL
-
-Gather acceptance criteria, priorities, and supporting artifacts for traceability.
-
-## 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. Prerequisites
-
-- Acceptance criteria available (story or provided inline)
-- Tests exist OR gaps explicitly acknowledged
-
-If acceptance criteria are missing, **HALT** and request them.
-
----
-
-## 2. Load Knowledge Base
-
-From `{knowledgeIndex}` load:
-
-- `test-priorities-matrix.md`
-- `risk-governance.md`
-- `probability-impact.md`
-- `test-quality.md`
-- `selective-testing.md`
-
----
-
-## 3. Load Artifacts
-
-If available:
-
-- Story file and acceptance criteria
-- Test design doc (priorities)
-- Tech spec / PRD
-
-Summarize what was found.
-
----
-
-### 4. Save Progress
-
-**Save this step's accumulated work to `{outputFile}`.**
-
-- **If `{outputFile}` does not exist** (first save), create it using the workflow template (if available) with YAML frontmatter:
-
-  ```yaml
-  ---
-  stepsCompleted: ['step-01-load-context']
-  lastStep: 'step-01-load-context'
-  lastSaved: '{date}'
-  ---
-  ```
-
-  Then write this step's output below the frontmatter.
-
-- **If `{outputFile}` already exists**, update:
-  - Add `'step-01-load-context'` to `stepsCompleted` array (only if not already present)
-  - Set `lastStep: 'step-01-load-context'`
-  - 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/trace/steps-c/step-01b-resume.md

@@ -1,102 +0,0 @@
----
-name: 'step-01b-resume'
-description: 'Resume interrupted workflow from last completed step'
-outputFile: '{test_artifacts}/traceability-report.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. 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. Display Progress Dashboard
-
-Display:
-
-"📋 **Workflow Resume — Requirements Traceability & Quality Gate**
-
-**Last saved:** {lastSaved}
-**Steps completed:** {stepsCompleted.length} of 5
-
-1. Load Context (step-01-load-context) — {✅ if in stepsCompleted, ⬜ otherwise}
-2. Discover Tests (step-02-discover-tests) — {✅ if in stepsCompleted, ⬜ otherwise}
-3. Map Criteria (step-03-map-criteria) — {✅ if in stepsCompleted, ⬜ otherwise}
-4. Analyze Gaps (step-04-analyze-gaps) — {✅ if in stepsCompleted, ⬜ otherwise}
-5. Gate Decision (step-05-gate-decision) — {✅ if in stepsCompleted, ⬜ otherwise}"
-
----
-
-### 3. Route to Next Step
-
-Based on `lastStep`, load the next incomplete step:
-
-- `'step-01-load-context'` → Load `./step-02-discover-tests.md`
-- `'step-02-discover-tests'` → Load `./step-03-map-criteria.md`
-- `'step-03-map-criteria'` → Load `./step-04-analyze-gaps.md`
-- `'step-04-analyze-gaps'` → Load `./step-05-gate-decision.md`
-- `'step-05-gate-decision'` → **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
-- 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.

package/templates/bmad/tea/workflows/testarch/trace/steps-c/step-02-discover-tests.md

@@ -1,112 +0,0 @@
----
-name: 'step-02-discover-tests'
-description: 'Discover and catalog tests by level'
-nextStepFile: './step-03-map-criteria.md'
-outputFile: '{test_artifacts}/traceability-report.md'
----
-
-# Step 2: Discover & Catalog Tests
-
-## STEP GOAL
-
-Identify tests relevant to the requirements and classify by test level.
-
-## 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. Discover Tests
-
-Search `{test_dir}` for:
-
-- Test IDs (e.g., `1.3-E2E-001`)
-- Feature name matches
-- Spec patterns (`*.spec.*`, `*.test.*`)
-
----
-
-## 2. Categorize by Level
-
-Classify as:
-
-- E2E
-- API
-- Component
-- Unit
-
-Record test IDs, describe blocks, and priority markers if present.
-
----
-
-## 3. Build Coverage Heuristics Inventory
-
-Capture explicit coverage signals so Phase 1 can detect common blind spots:
-
-- API endpoint coverage
-  - Inventory endpoints referenced by requirements/specs and endpoints exercised by API tests
-  - Mark endpoints with no direct tests
-- Authentication/authorization coverage
-  - Detect tests for login/session/token flows and permission-denied paths
-  - Mark auth/authz requirements with missing negative-path tests
-- Error-path coverage
-  - Detect validation, timeout, network-failure, and server-error scenarios
-  - Mark criteria with happy-path-only tests
-
-Record these findings in step output as `coverage_heuristics` for Step 3/4.
-
----
-
-### 4. Save Progress
-
-**Save this step's accumulated work to `{outputFile}`.**
-
-- **If `{outputFile}` does not exist** (first save), create it using the workflow template (if available) with YAML frontmatter:
-
-  ```yaml
-  ---
-  stepsCompleted: ['step-02-discover-tests']
-  lastStep: 'step-02-discover-tests'
-  lastSaved: '{date}'
-  ---
-  ```
-
-  Then write this step's output below the frontmatter.
-
-- **If `{outputFile}` already exists**, update:
-  - Add `'step-02-discover-tests'` to `stepsCompleted` array (only if not already present)
-  - Set `lastStep: 'step-02-discover-tests'`
-  - 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/trace/steps-c/step-03-map-criteria.md

@@ -1,97 +0,0 @@
----
-name: 'step-03-map-criteria'
-description: 'Map acceptance criteria to tests and build traceability matrix'
-nextStepFile: './step-04-analyze-gaps.md'
-outputFile: '{test_artifacts}/traceability-report.md'
----
-
-# Step 3: Map Criteria to Tests
-
-## STEP GOAL
-
-Create the traceability matrix linking requirements to 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. Build Matrix
-
-For each acceptance criterion:
-
-- Map to matching tests
-- Mark coverage status: FULL / PARTIAL / NONE / UNIT-ONLY / INTEGRATION-ONLY
-- Record test level and priority
-- Record heuristic signals:
-  - Endpoint coverage present/missing (for API-impacting criteria)
-  - Auth/authz coverage present/missing (positive and negative paths)
-  - Error-path coverage present/missing (validation, timeout, network/server failures)
-
----
-
-## 2. Validate Coverage Logic
-
-Ensure:
-
-- P0/P1 criteria have coverage
-- No duplicate coverage across levels without justification
-- Criteria are not happy-path-only when requirements imply error handling
-- API criteria are not marked FULL if endpoint-level checks are missing
-- Auth/authz criteria include at least one denied/invalid-path test where applicable
-
----
-
-### 3. Save Progress
-
-**Save this step's accumulated work to `{outputFile}`.**
-
-- **If `{outputFile}` does not exist** (first save), create it using the workflow template (if available) with YAML frontmatter:
-
-  ```yaml
-  ---
-  stepsCompleted: ['step-03-map-criteria']
-  lastStep: 'step-03-map-criteria'
-  lastSaved: '{date}'
-  ---
-  ```
-
-  Then write this step's output below the frontmatter.
-
-- **If `{outputFile}` already exists**, update:
-  - Add `'step-03-map-criteria'` to `stepsCompleted` array (only if not already present)
-  - Set `lastStep: 'step-03-map-criteria'`
-  - 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.