bmad-method-test-architecture-enterprise 2.0.2 → 2.0.3-next.0

package/skills/bmod-tea/knowledge/burn-in.md

@@ -232,7 +232,7 @@ jobs:
 
 ## Integration with CI Workflow
 
-When setting up CI with the `/bmad-testarch-ci` workflow, recommend burn-in for:
+When setting up CI with the `/bmad-testarch-framework` skill's CI scope, recommend burn-in for:
 
 - Pull request validation
 - Pre-merge checks

package/skills/bmod-tea/migration-1.toml

@@ -58,6 +58,6 @@ checklist = [
   "`risk_threshold`, `test_design_output`, `test_review_output` and `trace_output` are in no `[modules.tea]` layer.",
   "`ci_platform` and `tea_evaluations_folder` are in no `[modules.tea]` layer.",
   "`uv run _bmad/scripts/resolve_config.py --project-root . --key modules.tea` prints only supported v7 keys; omitted healing options use the shipped defaults.",
-  "`uv run _bmad/scripts/resolve_customization.py --skill <skill-root> --project-root . --key workflow` for `bmad-testarch-ci` and `bmad-testarch-evaluate` prints the migrated values.",
+  "`uv run _bmad/scripts/resolve_customization.py --skill <evaluate-skill-root> --project-root . --key workflow` prints the migrated Evaluate value; Framework CI scope merges `_bmad/custom/bmad-testarch-ci.toml` and its user layer to read the migrated CI value.",
   "Every file the plan listed for removal is either removed in the commit the user chose or reported as still present.",
 ]

package/skills/bmad-testarch-atdd/SKILL.md

@@ -1,16 +0,0 @@
----
-name: bmad-testarch-atdd
-description: 'Generate red-phase acceptance test scaffolds using the TDD cycle. Use when the user says "lets write acceptance tests" or "I want to do ATDD"'
----
-
-# Acceptance Test Generation
-
-`bmad-testarch-automate` owns test generation in red and expand modes.
-This entry preserves the ATDD command and AT menu code, with red as its default.
-
-1. Preserve the original request, supplied artifacts and Create, Resume, Validate or Edit operation. Set `test_entry = bmad-testarch-atdd`; default to red only when the task has no explicit mode signal.
-2. Set `skill-root` to the sibling `bmad-testarch-automate` directory. Require its `SKILL.md`, `resources/test-generation-routing.md`, `resources/run-and-heal.md`, and `red/steps-c/step-01-preflight-and-context.md`. If any are missing, explain that the canonical skill is missing or older than combined test generation and offer `npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-automate`. Continue only after installation succeeds and all required files exist.
-3. Read `{skill-root}/SKILL.md` completely and execute its router and activation with the original request. Keep `{skill-root}` canonical throughout. Run only the selected mode's customization hooks; do not activate twice or repeat its operation menu.
-
-Existing ATDD customization files and checklist paths keep working.
-Resume accepts interrupted 2.0.0 checklists and preserves their story identity and saved next step.

package/skills/bmad-testarch-atdd/bmod.toml

@@ -1,4 +0,0 @@
-[skill]
-bmod = "bmod-tea"
-source = "github:bmad-code-org/bmad-method-test-architecture-enterprise/skills"
-required_skills = ["bmad-testarch-automate"]

package/skills/bmad-testarch-atdd/customize.toml

@@ -1,38 +0,0 @@
-# DO NOT EDIT -- overwritten on every update.
-#
-# Workflow customization surface for bmad-testarch-atdd. Mirrors the
-# agent customization shape under the [workflow] namespace.
-
-[workflow]
-
-# --- Configurable below. Overrides merge per BMad structural rules: ---
-#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
-
-# Steps to run before the standard activation (config load, greet).
-# Overrides append. Use for pre-flight loads, compliance checks, etc.
-
-activation_steps_prepend = []
-
-# Steps to run after greet but before the workflow begins.
-# Overrides append. Use for context-heavy setup that should happen
-# once the user has been acknowledged.
-
-activation_steps_append = []
-
-# Persistent facts the workflow keeps in mind for the whole run
-# (testing standards, framework conventions, compliance constraints).
-# Distinct from the runtime memory sidecar — these are static context
-# loaded on activation. Overrides append.
-#
-# Each entry is either:
-#   - a literal sentence, e.g. "Every test must run deterministically in CI."
-#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/test-standards.md"
-#     (glob patterns are supported; matching files load in lexical path order as facts).
-
-persistent_facts = []
-
-# Scalar: executed when the workflow reaches its terminal step in any
-# mode (create, validate, edit), after the final outputs are produced.
-# Override wins. Leave empty for no custom post-completion behavior.
-
-on_complete = ""

package/skills/bmad-testarch-atdd/workflow.yaml

@@ -1,40 +0,0 @@
-# Test Architect workflow: bmad-testarch-atdd
-name: bmad-testarch-atdd
-# prettier-ignore
-description: 'Generate red-phase acceptance test scaffolds using TDD cycle. Use when the user says "lets write acceptance tests" or "I want to do ATDD"'
-
-# Config (test_artifacts, user_name, languages) is resolved at activation in SKILL.md from modules.tea and core.
-date: system-generated
-
-# Workflow components
-installed_path: "../bmad-testarch-automate/red"
-instructions: "../bmad-testarch-automate/red/instructions.md"
-validation: "../bmad-testarch-automate/red/checklist.md"
-template: "../bmad-testarch-automate/red/atdd-checklist-template.md"
-
-# Variables and inputs
-variables:
-  test_dir: "{project-root}/tests" # Root test directory
-
-# Output configuration
-default_output_file: "{test_artifacts}/atdd/atdd-checklist-{story_key}.md"
-
-# Required tools
-required_tools:
-  - read_file # Read story markdown, framework config
-  - write_file # Create test files, checklist, factory stubs
-  - create_directory # Create test directories
-  - list_files # Find existing fixtures and helpers
-  - search_repo # Search for similar test patterns
-
-tags:
-  - qa
-  - atdd
-  - test-architect
-  - tdd
-  - red-green-refactor
-
-execution_hints:
-  interactive: false # Minimize prompts
-  autonomous: true # Proceed without user input unless blocked
-  iterative: true

package/skills/bmad-testarch-ci/SKILL.md

@@ -1,14 +0,0 @@
----
-name: bmad-testarch-ci
-description: 'Scaffold CI/CD quality pipeline with test execution. Use when the user says "lets setup CI pipeline" or "I want to create quality gates"'
----
-
-# CI/CD Setup Compatibility Entry
-
-`bmad-testarch-framework` owns framework and CI setup. This installed name and the CI menu code forward to its CI phase.
-
-1. Preserve the original request, its supplied artifacts, and its create/resume/validate/edit operation. Preset `setup_scope = ci` and `setup_entry = bmad-testarch-ci`. An explicit request for both scopes sets `setup_scope = both`.
-2. Set `ci-skill-root` to this directory. Set `skill-root` to its sibling `bmad-testarch-framework` directory. Require its `SKILL.md`, `{skill-root}/resources/setup-routing.md`, and `{skill-root}/ci/steps-c/step-01-preflight.md`. If any are missing, explain that the canonical framework skill is missing or older than combined setup support and offer to install/update it with `npx skills add bmad-code-org/bmad-method-test-architecture-enterprise --skill bmad-testarch-framework`; continue only after installation succeeds and all three required files exist.
-3. Load `{skill-root}/SKILL.md` completely and execute its activation and shared router with the preset scope and original operation. Keep `{skill-root}` bound to that canonical directory throughout all phases. Do not run a second mode menu or CI-scope question.
-
-The canonical router resolves this entry's `customize.toml`, `_bmad/custom/bmad-testarch-ci.toml`, and `_bmad/custom/bmad-testarch-ci.user.toml` when the CI phase activates. It preserves legacy activation steps, persistent facts, `ci_platform`, and `on_complete` hooks. Existing CI checkpoint and validation-report paths remain under `{test_artifacts}/ci/`, including their legacy migration rules.

package/skills/bmad-testarch-ci/bmod.toml

@@ -1,4 +0,0 @@
-[skill]
-bmod = "bmod-tea"
-source = "github:bmad-code-org/bmad-method-test-architecture-enterprise/skills"
-required_skills = ["bmad-testarch-framework"]

package/skills/bmad-testarch-ci/customize.toml

@@ -1,43 +0,0 @@
-# DO NOT EDIT -- overwritten on every update.
-#
-# Workflow customization surface for bmad-testarch-ci. Mirrors the
-# agent customization shape under the [workflow] namespace.
-
-[workflow]
-
-# --- Configurable below. Overrides merge per BMad structural rules: ---
-#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
-
-# Steps to run before the standard activation (config load, greet).
-# Overrides append. Use for pre-flight loads, compliance checks, etc.
-
-activation_steps_prepend = []
-
-# Steps to run after greet but before the workflow begins.
-# Overrides append. Use for context-heavy setup that should happen
-# once the user has been acknowledged.
-
-activation_steps_append = []
-
-# Persistent facts the workflow keeps in mind for the whole run
-# (testing standards, framework conventions, compliance constraints).
-# Distinct from the runtime memory sidecar — these are static context
-# loaded on activation. Overrides append.
-#
-# Each entry is either:
-#   - a literal sentence, e.g. "Every test must run deterministically in CI."
-#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/test-standards.md"
-#     (glob patterns are supported; matching files load in lexical path order as facts).
-
-persistent_facts = []
-
-# Scalar: executed when the workflow reaches its terminal step in any
-# mode (create, validate, edit), after the final outputs are produced.
-# Override wins. Leave empty for no custom post-completion behavior.
-
-on_complete = ""
-
-# CI platform to generate for: auto (detect from the repository), github-actions, gitlab-ci,
-# jenkins, azure-devops, harness, circle-ci or other. Anything but auto skips detection.
-
-ci_platform = "auto"

package/skills/bmad-testarch-ci/workflow.yaml

@@ -1,44 +0,0 @@
-# Test Architect workflow: bmad-testarch-ci
-name: bmad-testarch-ci
-# prettier-ignore
-description: 'Scaffold CI/CD quality pipeline with test execution. Use when the user says "lets setup CI pipeline" or "I want to create quality gates"'
-
-# Config (test_artifacts, user_name, languages) is resolved at activation in SKILL.md from modules.tea and core.
-date: system-generated
-
-# Compatibility metadata. Canonical framework SKILL.md activates shared routing with CI scope.
-# Workflow components
-installed_path: "../bmad-testarch-framework"
-instructions: "../bmad-testarch-framework/ci/instructions.md"
-validation: "../bmad-testarch-framework/ci/checklist.md"
-
-# Variables and inputs
-variables:
-  setup_scope: "ci" # preset by compatibility entry
-  setup_entry: "bmad-testarch-ci"
-  test_dir: "{project-root}/tests" # Root test directory
-  test_stack_type: "auto" # auto, frontend, backend, fullstack, mobile - detected or user override
-  test_framework: "auto" # auto, playwright, cypress, jest, vitest - detected or user override
-
-# Output configuration (resolved dynamically based on ci_platform detection)
-default_output_file: "{project-root}/.github/workflows/test.yml" # GitHub Actions default; overridden per platform
-
-# Required tools
-required_tools:
-  - read_file # Read .nvmrc, package.json, framework config
-  - write_file # Create CI config, scripts, documentation
-  - create_directory # Create .github/workflows/ or .gitlab-ci/ directories
-  - list_files # Detect existing CI configuration
-  - search_repo # Find test files for selective testing
-
-tags:
-  - qa
-  - ci-cd
-  - test-architect
-  - pipeline
-  - automation
-
-execution_hints:
-  interactive: false # Minimize prompts, auto-detect when possible
-  autonomous: true # Proceed without user input unless blocked
-  iterative: true