create-byan-agent 2.1.0 → 2.1.1

package/_bmad/tea/workflows/testarch/trace/validation-report-20260127-095021.md

@@ -1,73 +0,0 @@
----
-validationDate: 2026-01-27
-workflowName: testarch-trace
-workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/trace
-validationStatus: COMPLETE
-completionDate: 2026-01-27 10:03:10
----
-
-# Validation Report: testarch-trace
-
-**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: 73 lines [GOOD]
-- steps-c/step-02-discover-tests.md: 62 lines [GOOD]
-- steps-c/step-03-map-criteria.md: 58 lines [GOOD]
-- steps-c/step-04-analyze-gaps.md: 57 lines [GOOD]
-- steps-c/step-05-gate-decision.md: 66 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: trace-template.md
-- Steps with outputFile in frontmatter:
-  - steps-c/step-05-gate-decision.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/_bmad/tea/workflows/testarch/trace/validation-report-20260127-102401.md

@@ -1,116 +0,0 @@
----
-validationDate: 2026-01-27
-workflowName: testarch-trace
-workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/trace
-validationStatus: COMPLETE
-completionDate: 2026-01-27 10:24:01
----
-
-# Validation Report: testarch-trace
-
-**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-load-context.md: 72 lines [GOOD]
-- steps-c/step-02-discover-tests.md: 61 lines [GOOD]
-- steps-c/step-03-map-criteria.md: 57 lines [GOOD]
-- steps-c/step-04-analyze-gaps.md: 56 lines [GOOD]
-- steps-c/step-05-gate-decision.md: 65 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-load-context.md: Init [PASS]
-- steps-c/step-02-discover-tests.md: Middle [PASS]
-- steps-c/step-03-map-criteria.md: Middle [PASS]
-- steps-c/step-04-analyze-gaps.md: Middle [PASS]
-- steps-c/step-05-gate-decision.md: Final [PASS]
-- Step type validation assumes linear sequence (no branching/menu). Workflow-plan.md present for reference. [INFO]
-
-## Output Format Validation
-
-- Templates present: trace-template.md
-- Steps with outputFile in frontmatter:
-  - steps-c/step-05-gate-decision.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
-
-## Subprocess Optimization Opportunities
-
-- No high-priority subprocess 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/_bmad/tea/workflows/testarch/trace/workflow-plan.md

@@ -1,21 +0,0 @@
-    # Workflow Plan: testarch-trace
-
-    ## Create Mode (steps-c)
-    - step-01-load-context.md
-
-- step-02-discover-tests.md
-- step-03-map-criteria.md
-- step-04-analyze-gaps.md
-- step-05-gate-decision.md
-
-  ## Validate Mode (steps-v)
-  - step-01-validate.md
-
-  ## Edit Mode (steps-e)
-  - step-01-assess.md
-  - step-02-apply-edit.md
-
-  ## Outputs
-  - {output_folder}/traceability-matrix.md
-
-- Gate decision summary (if evidence available)

package/_bmad/tea/workflows/testarch/trace/workflow.md

@@ -1,39 +0,0 @@
----
-name: testarch-trace
-description: 'Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)'
-web_bundle: true
----
-
-# Requirements Traceability & Quality Gate
-
-**Goal:** Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)
-
-**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
-- **[V] Validate** — Validate existing outputs
-- **[E] Edit** — Edit existing outputs
-
-### 2. Route to First Step
-
-- **If C:** Load `steps-c/step-01-load-context.md`
-- **If V:** Load `steps-v/step-01-validate.md`
-- **If E:** Load `steps-e/step-01-assess.md`

package/_bmad/tea/workflows/testarch/trace/workflow.yaml

@@ -1,55 +0,0 @@
-# Test Architect workflow: trace (enhanced with gate decision)
-name: testarch-trace
-description: "Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)"
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/_bmad/tea/config.yaml"
-output_folder: "{config_source}:output_folder"
-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/trace"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-template: "{installed_path}/trace-template.md"
-
-# Variables and inputs
-variables:
-  # Directory paths
-  test_dir: "{project-root}/tests" # Root test directory
-  source_dir: "{project-root}" # Source code directory (customize if needed, e.g., {project-root}/src or {project-root}/lib)
-
-  # Workflow behavior
-  coverage_levels: "e2e,api,component,unit" # Which test levels to trace
-  gate_type: "story" # story | epic | release | hotfix - determines gate scope
-  decision_mode: "deterministic" # deterministic (rule-based) | manual (team decision)
-
-# Output configuration
-default_output_file: "{output_folder}/traceability-matrix.md"
-
-# Required tools
-required_tools:
-  - read_file # Read story, test files, BMad artifacts
-  - write_file # Create traceability matrix, gate YAML
-  - list_files # Discover test files
-  - search_repo # Find tests by test ID, describe blocks
-  - glob # Find test files matching patterns
-
-tags:
-  - qa
-  - traceability
-  - test-architect
-  - coverage
-  - requirements
-  - gate
-  - decision
-  - release
-
-execution_hints:
-  interactive: false # Minimize prompts
-  autonomous: true # Proceed without user input unless blocked
-  iterative: true