@cregis-dev/cckit 0.4.1 → 0.6.1

package/templates/bmad/tea/workflows/testarch/nfr-assess/steps-c/step-04e-aggregate-nfr.md

@@ -1,264 +0,0 @@
----
-name: 'step-04e-aggregate-nfr'
-description: 'Aggregate NFR domain assessments into executive summary'
-nextStepFile: './step-05-generate-report.md'
-outputFile: '{test_artifacts}/nfr-assessment.md'
----
-
-# Step 4E: Aggregate NFR Assessment Results
-
-## STEP GOAL
-
-Read outputs from 4 parallel NFR subagents, calculate overall risk level, aggregate compliance status, and identify cross-domain risks.
-
----
-
-## MANDATORY EXECUTION RULES
-
-- 📖 Read the entire step file before acting
-- ✅ Speak in `{communication_language}`
-- ✅ Read all 4 subagent outputs
-- ✅ Calculate overall risk level
-- ❌ Do NOT re-assess NFRs (use subagent outputs)
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Read All Subagent Outputs
-
-```javascript
-const domains = ['security', 'performance', 'reliability', 'scalability'];
-const assessments = {};
-
-domains.forEach((domain) => {
-  const outputPath = `/tmp/tea-nfr-${domain}-{{timestamp}}.json`;
-  assessments[domain] = JSON.parse(fs.readFileSync(outputPath, 'utf8'));
-});
-```
-
----
-
-### 2. Calculate Overall Risk Level
-
-**Risk hierarchy:** HIGH > MEDIUM > LOW > NONE
-
-```javascript
-const riskLevels = { HIGH: 3, MEDIUM: 2, LOW: 1, NONE: 0 };
-const domainRisks = domains.map((d) => assessments[d].risk_level);
-const maxRiskValue = Math.max(...domainRisks.map((r) => riskLevels[r]));
-const overallRisk = Object.keys(riskLevels).find((k) => riskLevels[k] === maxRiskValue);
-```
-
-**Risk assessment:**
-
-- If ANY domain is HIGH → overall is HIGH
-- If ANY domain is MEDIUM (and none HIGH) → overall is MEDIUM
-- If ALL domains are LOW/NONE → overall is LOW
-
----
-
-### 3. Aggregate Compliance Status
-
-```javascript
-const allCompliance = {};
-
-domains.forEach((domain) => {
-  const compliance = assessments[domain].compliance;
-  Object.entries(compliance).forEach(([standard, status]) => {
-    if (!allCompliance[standard]) {
-      allCompliance[standard] = [];
-    }
-    allCompliance[standard].push({ domain, status });
-  });
-});
-
-// Determine overall compliance per standard
-const complianceSummary = {};
-Object.entries(allCompliance).forEach(([standard, statuses]) => {
-  const hasFail = statuses.some((s) => s.status === 'FAIL');
-  const hasPartial = statuses.some((s) => s.status === 'PARTIAL' || s.status === 'CONCERN');
-
-  complianceSummary[standard] = hasFail ? 'FAIL' : hasPartial ? 'PARTIAL' : 'PASS';
-});
-```
-
----
-
-### 4. Identify Cross-Domain Risks
-
-**Look for risks that span multiple domains:**
-
-```javascript
-const crossDomainRisks = [];
-
-// Example: Performance + Scalability issue
-const perfConcerns = assessments.performance.findings.filter((f) => f.status !== 'PASS');
-const scaleConcerns = assessments.scalability.findings.filter((f) => f.status !== 'PASS');
-if (perfConcerns.length > 0 && scaleConcerns.length > 0) {
-  crossDomainRisks.push({
-    domains: ['performance', 'scalability'],
-    description: 'Performance issues may worsen under scale',
-    impact: 'HIGH',
-  });
-}
-
-// Example: Security + Reliability issue
-const securityFails = assessments.security.findings.filter((f) => f.status === 'FAIL');
-const reliabilityConcerns = assessments.reliability.findings.filter((f) => f.status !== 'PASS');
-if (securityFails.length > 0 && reliabilityConcerns.length > 0) {
-  crossDomainRisks.push({
-    domains: ['security', 'reliability'],
-    description: 'Security vulnerabilities may cause reliability incidents',
-    impact: 'CRITICAL',
-  });
-}
-```
-
----
-
-### 5. Aggregate Priority Actions
-
-```javascript
-const allPriorityActions = domains.flatMap((domain) =>
-  assessments[domain].priority_actions.map((action) => ({
-    domain,
-    action,
-    urgency: assessments[domain].risk_level === 'HIGH' ? 'URGENT' : 'NORMAL',
-  })),
-);
-
-// Sort by urgency
-const prioritizedActions = allPriorityActions.sort((a, b) => (a.urgency === 'URGENT' ? -1 : 1));
-```
-
----
-
-### 6. Generate Executive Summary
-
-```javascript
-const resolvedMode = subagentContext?.execution?.resolvedMode ?? 'unknown';
-const subagentExecutionLabel =
-  resolvedMode === 'sequential'
-    ? 'SEQUENTIAL (4 NFR domains)'
-    : resolvedMode === 'agent-team'
-      ? 'AGENT-TEAM (4 NFR domains)'
-      : resolvedMode === 'subagent'
-        ? 'SUBAGENT (4 NFR domains)'
-        : 'MODE-DEPENDENT (4 NFR domains)';
-
-const performanceGainLabel =
-  resolvedMode === 'sequential'
-    ? 'baseline (no parallel speedup)'
-    : resolvedMode === 'agent-team' || resolvedMode === 'subagent'
-      ? '~67% faster than sequential'
-      : 'mode-dependent';
-
-const executiveSummary = {
-  overall_risk: overallRisk,
-  assessment_date: new Date().toISOString(),
-
-  domain_assessments: assessments,
-
-  compliance_summary: complianceSummary,
-
-  cross_domain_risks: crossDomainRisks,
-
-  priority_actions: prioritizedActions,
-
-  risk_breakdown: {
-    security: assessments.security.risk_level,
-    performance: assessments.performance.risk_level,
-    reliability: assessments.reliability.risk_level,
-    scalability: assessments.scalability.risk_level,
-  },
-
-  subagent_execution: subagentExecutionLabel,
-  performance_gain: performanceGainLabel,
-};
-
-// Save for Step 5 (report generation)
-fs.writeFileSync('/tmp/tea-nfr-summary-{{timestamp}}.json', JSON.stringify(executiveSummary, null, 2), 'utf8');
-```
-
----
-
-### 7. Display Summary to User
-
-```
-✅ NFR Assessment Complete ({subagentExecutionLabel})
-
-🎯 Overall Risk Level: {overallRisk}
-
-📊 Domain Risk Breakdown:
-- Security:      {security_risk}
-- Performance:   {performance_risk}
-- Reliability:   {reliability_risk}
-- Scalability:   {scalability_risk}
-
-✅ Compliance Summary:
-{list standards with PASS/PARTIAL/FAIL}
-
-⚠️ Cross-Domain Risks: {cross_domain_risk_count}
-
-🎯 Priority Actions: {priority_action_count}
-
-🚀 Performance: {performanceGainLabel}
-
-✅ Ready for report generation (Step 5)
-```
-
----
-
----
-
-### 8. 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-04e-aggregate-nfr']
-  lastStep: 'step-04e-aggregate-nfr'
-  lastSaved: '{date}'
-  ---
-  ```
-
-  Then write this step's output below the frontmatter.
-
-- **If `{outputFile}` already exists**, update:
-  - Add `'step-04e-aggregate-nfr'` to `stepsCompleted` array (only if not already present)
-  - Set `lastStep: 'step-04e-aggregate-nfr'`
-  - Set `lastSaved: '{date}'`
-  - Append this step's output to the appropriate section of the document.
-
----
-
-## EXIT CONDITION
-
-Proceed to Step 5 when:
-
-- ✅ All subagent outputs read
-- ✅ Overall risk calculated
-- ✅ Compliance aggregated
-- ✅ Summary saved
-- ✅ Progress saved to output document
-
-Load next step: `{nextStepFile}`
-
----
-
-## 🚨 SYSTEM SUCCESS METRICS
-
-### ✅ SUCCESS:
-
-- All 4 NFR domains aggregated correctly
-- Overall risk level determined
-- Executive summary complete
-
-### ❌ FAILURE:
-
-- Failed to read subagent outputs
-- Risk calculation incorrect

package/templates/bmad/tea/workflows/testarch/nfr-assess/steps-c/step-05-generate-report.md

@@ -1,108 +0,0 @@
----
-name: 'step-05-generate-report'
-description: 'Create NFR report and validation summary'
-outputFile: '{test_artifacts}/nfr-assessment.md'
----
-
-# Step 5: Generate Report & Validate
-
-## STEP GOAL
-
-Produce the NFR assessment report and validate completeness.
-
-## 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. Report Generation
-
-Use `nfr-report-template.md` to produce `{outputFile}` containing:
-
-- Category results (PASS/CONCERNS/FAIL)
-- Evidence summary
-- Remediation actions
-- Gate-ready YAML snippet (if applicable)
-
----
-
-## 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. Validation
-
-Validate against `checklist.md` and fix gaps.
-
-- [ ] CLI sessions cleaned up (no orphaned browsers)
-
----
-
-## 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-05-generate-report']
-  lastStep: 'step-05-generate-report'
-  lastSaved: '{date}'
-  ---
-  ```
-
-  Then write this step's output below the frontmatter.
-
-- **If `{outputFile}` already exists**, update:
-  - Add `'step-05-generate-report'` to `stepsCompleted` array (only if not already present)
-  - Set `lastStep: 'step-05-generate-report'`
-  - Set `lastSaved: '{date}'`
-  - Append this step's output to the appropriate section of the document.
-
----
-
-## 5. Completion Summary
-
-Report:
-
-- Overall NFR status
-- Critical blockers or waivers needed
-- Next recommended workflow (`trace` or release gate)
-
-## 🚨 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/nfr-assess/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/nfr-assess/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/nfr-assess/steps-v/step-01-validate.md

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

@@ -1,73 +0,0 @@
----
-validationDate: 2026-01-27
-workflowName: testarch-nfr
-workflowPath: {project-root}/src/workflows/testarch/nfr-assess
-validationStatus: COMPLETE
-completionDate: 2026-01-27 10:03:10
----
-
-# Validation Report: testarch-nfr
-
-**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-load-context.md: 78 lines [GOOD]
-- steps-c/step-02-define-thresholds.md: 75 lines [GOOD]
-- steps-c/step-03-gather-evidence.md: 58 lines [GOOD]
-- steps-c/step-04-evaluate-and-score.md: 61 lines [GOOD]
-- steps-c/step-05-generate-report.md: 64 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
-
-- Templates present: nfr-report-template.md
-- Steps with outputFile in frontmatter:
-  - steps-c/step-05-generate-report.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)