create-byan-agent 2.1.0 → 2.1.1

package/_bmad/tea/workflows/testarch/automate/steps-v/step-01-validate.md

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

@@ -1,72 +0,0 @@
----
-validationDate: 2026-01-27
-workflowName: testarch-automate
-workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/automate
-validationStatus: COMPLETE
-completionDate: 2026-01-27 10:03:10
----
-
-# Validation Report: testarch-automate
-
-**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: 7
-
-**Step File Sizes:**
-
-- steps-c/step-01-preflight-and-context.md: 113 lines [GOOD]
-- steps-c/step-02-identify-targets.md: 85 lines [GOOD]
-- steps-c/step-03-generate-tests.md: 76 lines [GOOD]
-- steps-c/step-04-validate-and-summarize.md: 62 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
-
-- No templates found in workflow root
-- Steps with outputFile in frontmatter:
-  - steps-c/step-04-validate-and-summarize.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/automate/validation-report-20260127-102401.md

@@ -1,114 +0,0 @@
----
-validationDate: 2026-01-27
-workflowName: testarch-automate
-workflowPath: /Users/murat.ozcan/opensource/bmad-method-test-architecture-enterprise/src/workflows/testarch/automate
-validationStatus: COMPLETE
-completionDate: 2026-01-27 10:24:01
----
-
-# Validation Report: testarch-automate
-
-**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: 7
-
-**Step File Sizes:**
-
-- steps-c/step-01-preflight-and-context.md: 112 lines [GOOD]
-- steps-c/step-02-identify-targets.md: 84 lines [GOOD]
-- steps-c/step-03-generate-tests.md: 75 lines [GOOD]
-- steps-c/step-04-validate-and-summarize.md: 61 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-preflight-and-context.md: Init [PASS]
-- steps-c/step-02-identify-targets.md: Middle [PASS]
-- steps-c/step-03-generate-tests.md: Middle [PASS]
-- steps-c/step-04-validate-and-summarize.md: Final [PASS]
-- Step type validation assumes linear sequence (no branching/menu). Workflow-plan.md present for reference. [INFO]
-
-## Output Format Validation
-
-- Templates present: NONE
-- Steps with outputFile in frontmatter:
-  - steps-c/step-04-validate-and-summarize.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: 7 (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/automate/workflow-plan.md

@@ -1,20 +0,0 @@
-    # Workflow Plan: testarch-automate
-
-    ## Create Mode (steps-c)
-    - step-01-preflight-and-context.md
-
-- step-02-identify-targets.md
-- step-03-generate-tests.md
-- step-04-validate-and-summarize.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}/automation-summary.md
-
-- Test files under {project-root}/tests

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

@@ -1,39 +0,0 @@
----
-name: testarch-automate
-description: 'Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite'
-web_bundle: true
----
-
-# Test Automation Expansion
-
-**Goal:** Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite
-
-**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-preflight-and-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/automate/workflow.yaml

@@ -1,52 +0,0 @@
-# Test Architect workflow: automate
-name: testarch-automate
-description: "Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite"
-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/automate"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-template: false
-
-# Variables and inputs
-variables:
-  # Execution mode and targeting
-  standalone_mode: true # Can work without BMad artifacts (true) or integrate with BMad (false)
-  coverage_target: "critical-paths" # critical-paths, comprehensive, selective
-
-  # 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)
-
-# Output configuration
-default_output_file: "{output_folder}/automation-summary.md"
-
-# Required tools
-required_tools:
-  - read_file # Read source code, existing tests, BMad artifacts
-  - write_file # Create test files, fixtures, factories, summaries
-  - create_directory # Create test directories
-  - list_files # Discover features and existing tests
-  - search_repo # Find coverage gaps and patterns
-  - glob # Find test files and source files
-
-tags:
-  - qa
-  - automation
-  - test-architect
-  - regression
-  - coverage
-
-execution_hints:
-  interactive: false # Minimize prompts
-  autonomous: true # Proceed without user input unless blocked
-  iterative: true

package/_bmad/tea/workflows/testarch/ci/checklist.md

@@ -1,247 +0,0 @@
-# CI/CD Pipeline Setup - Validation Checklist
-
-## Prerequisites
-
-- [ ] Git repository initialized (`.git/` exists)
-- [ ] Git remote configured (`git remote -v` shows origin)
-- [ ] Test framework configured (`playwright.config._` or `cypress.config._`)
-- [ ] Local tests pass (`npm run test:e2e` succeeds)
-- [ ] Team agrees on CI platform
-- [ ] Access to CI platform settings (if updating)
-
-Note: CI setup is typically a one-time task per repo and can be run any time after the test framework is configured.
-
-## Process Steps
-
-### Step 1: Preflight Checks
-
-- [ ] Git repository validated
-- [ ] Framework configuration detected
-- [ ] Local test execution successful
-- [ ] CI platform detected or selected
-- [ ] Node version identified (.nvmrc or default)
-- [ ] No blocking issues found
-
-### Step 2: CI Pipeline Configuration
-
-- [ ] CI configuration file created (`.github/workflows/test.yml` or `.gitlab-ci.yml`)
-- [ ] File is syntactically valid (no YAML errors)
-- [ ] Correct framework commands configured
-- [ ] Node version matches project
-- [ ] Test directory paths correct
-
-### Step 3: Parallel Sharding
-
-- [ ] Matrix strategy configured (4 shards default)
-- [ ] Shard syntax correct for framework
-- [ ] fail-fast set to false
-- [ ] Shard count appropriate for test suite size
-
-### Step 4: Burn-In Loop
-
-- [ ] Burn-in job created
-- [ ] 10 iterations configured
-- [ ] Proper exit on failure (`|| exit 1`)
-- [ ] Runs on appropriate triggers (PR, cron)
-- [ ] Failure artifacts uploaded
-
-### Step 5: Caching Configuration
-
-- [ ] Dependency cache configured (npm/yarn)
-- [ ] Cache key uses lockfile hash
-- [ ] Browser cache configured (Playwright/Cypress)
-- [ ] Restore-keys defined for fallback
-- [ ] Cache paths correct for platform
-
-### Step 6: Artifact Collection
-
-- [ ] Artifacts upload on failure only
-- [ ] Correct artifact paths (test-results/, traces/, etc.)
-- [ ] Retention days set (30 default)
-- [ ] Artifact names unique per shard
-- [ ] No sensitive data in artifacts
-
-### Step 7: Retry Logic
-
-- [ ] Retry action/strategy configured
-- [ ] Max attempts: 2-3
-- [ ] Timeout appropriate (30 min)
-- [ ] Retry only on transient errors
-
-### Step 8: Helper Scripts
-
-- [ ] `scripts/test-changed.sh` created
-- [ ] `scripts/ci-local.sh` created
-- [ ] `scripts/burn-in.sh` created (optional)
-- [ ] Scripts are executable (`chmod +x`)
-- [ ] Scripts use correct test commands
-- [ ] Shebang present (`#!/bin/bash`)
-
-### Step 9: Documentation
-
-- [ ] `docs/ci.md` created with pipeline guide
-- [ ] `docs/ci-secrets-checklist.md` created
-- [ ] Required secrets documented
-- [ ] Setup instructions clear
-- [ ] Troubleshooting section included
-- [ ] Badge URLs provided (optional)
-
-## Output Validation
-
-### Configuration Validation
-
-- [ ] CI file loads without errors
-- [ ] All paths resolve correctly
-- [ ] No hardcoded values (use env vars)
-- [ ] Triggers configured (push, pull_request, schedule)
-- [ ] Platform-specific syntax correct
-
-### Execution Validation
-
-- [ ] First CI run triggered (push to remote)
-- [ ] Pipeline starts without errors
-- [ ] All jobs appear in CI dashboard
-- [ ] Caching works (check logs for cache hit)
-- [ ] Tests execute in parallel
-- [ ] Artifacts collected on failure
-
-### Performance Validation
-
-- [ ] Lint stage: <2 minutes
-- [ ] Test stage (per shard): <10 minutes
-- [ ] Burn-in stage: <30 minutes
-- [ ] Total pipeline: <45 minutes
-- [ ] Cache reduces install time by 2-5 minutes
-
-## Quality Checks
-
-### Best Practices Compliance
-
-- [ ] Burn-in loop follows production patterns
-- [ ] Parallel sharding configured optimally
-- [ ] Failure-only artifact collection
-- [ ] Selective testing enabled (optional)
-- [ ] Retry logic handles transient failures only
-- [ ] No secrets in configuration files
-
-### Knowledge Base Alignment
-
-- [ ] Burn-in pattern matches `ci-burn-in.md`
-- [ ] Selective testing matches `selective-testing.md`
-- [ ] Artifact collection matches `visual-debugging.md`
-- [ ] Test quality matches `test-quality.md`
-
-### Security Checks
-
-- [ ] No credentials in CI configuration
-- [ ] Secrets use platform secret management
-- [ ] Environment variables for sensitive data
-- [ ] Artifact retention appropriate (not too long)
-- [ ] No debug output exposing secrets
-
-## Integration Points
-
-### Status File Integration
-
-- [ ] CI setup logged in Quality & Testing Progress section
-- [ ] Status updated with completion timestamp
-- [ ] Platform and configuration noted
-
-### Knowledge Base Integration
-
-- [ ] Relevant knowledge fragments loaded
-- [ ] Patterns applied from knowledge base
-- [ ] Documentation references knowledge base
-- [ ] Knowledge base references in README
-
-### Workflow Dependencies
-
-- [ ] `framework` workflow completed first
-- [ ] Can proceed to `atdd` workflow after CI setup
-- [ ] Can proceed to `automate` workflow
-- [ ] CI integrates with `gate` workflow
-
-## Completion Criteria
-
-**All must be true:**
-
-- [ ] All prerequisites met
-- [ ] All process steps completed
-- [ ] All output validations passed
-- [ ] All quality checks passed
-- [ ] All integration points verified
-- [ ] First CI run successful
-- [ ] Performance targets met
-- [ ] Documentation complete
-
-## Post-Workflow Actions
-
-**User must complete:**
-
-1. [ ] Commit CI configuration
-2. [ ] Push to remote repository
-3. [ ] Configure required secrets in CI platform
-4. [ ] Open PR to trigger first CI run
-5. [ ] Monitor and verify pipeline execution
-6. [ ] Adjust parallelism if needed (based on actual run times)
-7. [ ] Set up notifications (optional)
-
-**Recommended next workflows:**
-
-1. [ ] Run `atdd` workflow for test generation
-2. [ ] Run `automate` workflow for coverage expansion
-3. [ ] Run `gate` workflow for quality gates
-
-## Rollback Procedure
-
-If workflow fails:
-
-1. [ ] Delete CI configuration file
-2. [ ] Remove helper scripts directory
-3. [ ] Remove documentation (docs/ci.md, etc.)
-4. [ ] Clear CI platform secrets (if added)
-5. [ ] Review error logs
-6. [ ] Fix issues and retry workflow
-
-## Notes
-
-### Common Issues
-
-**Issue**: CI file syntax errors
-
-- **Solution**: Validate YAML syntax online or with linter
-
-**Issue**: Tests fail in CI but pass locally
-
-- **Solution**: Use `scripts/ci-local.sh` to mirror CI environment
-
-**Issue**: Caching not working
-
-- **Solution**: Check cache key formula, verify paths
-
-**Issue**: Burn-in too slow
-
-- **Solution**: Reduce iterations or run on cron only
-
-### Platform-Specific
-
-**GitHub Actions:**
-
-- Secrets: Repository Settings → Secrets and variables → Actions
-- Runners: Ubuntu latest recommended
-- Concurrency limits: 20 jobs for free tier
-
-**GitLab CI:**
-
-- Variables: Project Settings → CI/CD → Variables
-- Runners: Shared or project-specific
-- Pipeline quota: 400 minutes/month free tier
-
----
-
-**Checklist Complete**: Sign off when all items validated.
-
-**Completed by:** {name}
-**Date:** {date}
-**Platform:** {GitHub Actions, GitLab CI, Other}
-**Notes:** {notes}