bmad-method-test-architecture-enterprise 2.0.2 → 2.0.3

package/skills/bmad-testarch-framework/checklist.md

@@ -266,9 +266,9 @@ Per `playwright-utils-mandate.md`. Skip for Maestro, Cypress, and non-Playwright
 
 ### Workflow Dependencies
 
-- [ ] Can proceed to `ci` workflow after completion
+- [ ] Can proceed to Framework CI scope after completion
 - [ ] Can proceed to `test-design` workflow after completion
-- [ ] Can proceed to `atdd` workflow after completion
+- [ ] Can proceed to Automate red mode after completion
 - [ ] Framework setup compatible with downstream workflows
 
 ---
@@ -301,9 +301,9 @@ Per `playwright-utils-mandate.md`. Skip for Maestro, Cypress, and non-Playwright
 
 **Recommended next workflows:**
 
-1. [ ] Run `ci` workflow to set up CI/CD pipeline
+1. [ ] Run Framework with CI scope to set up the CI/CD pipeline
 2. [ ] Run `test-design` workflow to plan test coverage
-3. [ ] Run `atdd` workflow when ready to develop stories
+3. [ ] Run Automate in red mode when ready to develop stories
 
 ---
 

package/skills/bmad-testarch-framework/ci/checklist.md

@@ -193,7 +193,7 @@ Note: CI setup is typically a one-time task per repo and can be run any time aft
 ### Workflow Dependencies
 
 - [ ] Existing or newly created framework validated against the agreed contract in this run (CI-only existing; both-scope new or reused)
-- [ ] Can proceed to `atdd` workflow after CI setup
+- [ ] Can proceed to Automate red mode after CI setup
 - [ ] Can proceed to `automate` workflow
 - [ ] CI integrates with `gate` workflow
 
@@ -224,7 +224,7 @@ Note: CI setup is typically a one-time task per repo and can be run any time aft
 
 **Recommended next workflows:**
 
-1. [ ] Run `atdd` workflow for test generation
+1. [ ] Run Automate in red mode for acceptance test generation
 2. [ ] Run `automate` workflow for coverage expansion
 3. [ ] Run `gate` workflow for quality gates
 

package/skills/bmad-testarch-framework/ci/instructions.md

@@ -33,7 +33,7 @@ From `workflow.yaml`, resolve:
 
 ### 2. Canonical CI Activation
 
-If invoked through legacy workflow metadata, preset `setup_scope = ci` and `setup_entry = bmad-testarch-ci`, then load `{skill-root}/SKILL.md` and its shared router before executing a phase. Keep the original operation and legacy CI customization. CI instructions, templates and steps resolve under `{skill-root}/ci/`.
+If invoked through legacy workflow metadata, preset `setup_scope = ci`, then load `{skill-root}/SKILL.md` and its shared router before executing a phase. Keep the original operation and CI customization. CI instructions, templates and steps resolve under `{skill-root}/ci/`.
 
 ### 3. First Step
 

package/skills/bmad-testarch-framework/resources/setup-routing.md

@@ -1,6 +1,6 @@
 # Shared Setup Router
 
-Read this resource and `{skill-root}/resources/setup-state.md` completely before activation. `{skill-root}` always names `bmad-testarch-framework`; `{ci-skill-root}` names its sibling `bmad-testarch-ci` when installed. Keep the original request and supplied artifact paths through every handoff.
+Read this resource and `{skill-root}/resources/setup-state.md` completely before activation. `{skill-root}` always names `bmad-testarch-framework`. Keep the original request and supplied artifact paths through every handoff.
 
 ## 1. Read-Only Request Gate: Before Activation
 
@@ -11,7 +11,7 @@ Read effective config and all applicable run/phase history and execute `setup-st
 Resolve `setup_scope` as `framework`, `ci`, or `both`:
 
 - Explicit scope and a supplied operation take priority. Requests mentioning framework and pipeline setup select `both`.
-- A CI pipeline, quality gates, CI artifact target, or the CI entry/menu code presets `ci`.
+- A CI pipeline, quality gates, or CI artifact target selects `ci`.
 - Framework-only wording or a supplied framework artifact selects `framework`.
 - For setup requests whose CI intent remains unclear, ask exactly once: **“Do you want CI too?”** A yes selects `both`; a no selects `framework`. Record `ci_scope_answered = true`. Wait for the answer before any project writes, including custom activation hooks. An unattended/headless run with no scope answer defaults to `framework`, records `ci_scope_defaulted = true`, and says in its completion summary that CI was not included. Explicit or inferred CI intent still selects `ci` or `both` in unattended runs.
 
@@ -27,8 +27,8 @@ Before SKILL.md executes prepend hooks or greets, resolve settings for every req
 
 When scope includes CI:
 
-1. Start with canonical-owned CI defaults: `ci_platform = auto`, empty `activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, and `on_complete`. These defaults make canonical CI functional when the alias directory is absent.
-2. If `{ci-skill-root}/customize.toml` exists, resolve it through `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {ci-skill-root} --project-root {project-root} --key workflow`. If the alias is absent or the resolver fails, structurally merge the canonical-owned CI defaults, the legacy defaults when present, `_bmad/custom/bmad-testarch-ci.toml`, and `_bmad/custom/bmad-testarch-ci.user.toml`, skipping missing files. All legacy overrides, including migrated platform settings, remain effective even without the installed alias.
+1. Start with CI defaults: `ci_platform = auto`, empty `activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, and `on_complete`.
+2. Structurally merge the CI defaults, `_bmad/custom/bmad-testarch-ci.toml`, and `_bmad/custom/bmad-testarch-ci.user.toml`, skipping missing files. Existing CI overrides, including migrated platform settings, remain effective.
 3. Store the result as `ci_workflow`. SKILL.md executes applicable prepend entries before greeting, loads applicable facts/globs in lexical order, and executes append entries after greeting through `setup-state.md` section 3's individual durable hook protocol. On Resume, resolve current settings and reload applicable facts; skip completed hook entries and halt on uncertain started entries. Save each applicable phase in `activation_completed` only after its activation succeeds. This section resolves settings; it does not replay activation at phase or worker handoffs.
 4. Framework steps use canonical `workflow`. CI steps read `ci_workflow` for their legacy hooks/facts and the effective platform below. Keep `{skill-root}` bound to the canonical directory for every CI asset.
 

package/skills/bmad-testarch-test-design/checklist.md

@@ -188,11 +188,11 @@
 
 ### Workflow Dependencies
 
-- [ ] Can proceed to `/bmad-testarch-atdd` workflow with P0 scenarios
-- [ ] `/bmad-testarch-atdd` is a separate workflow and must be run explicitly (not auto-run)
+- [ ] Can proceed to `/bmad-testarch-automate` red mode with P0 scenarios
+- [ ] `/bmad-testarch-automate` is a separate workflow and must be run explicitly (not auto-run)
 - [ ] Can proceed to `automate` workflow with full coverage plan
 - [ ] Risk assessment informs `gate` workflow criteria
-- [ ] Integrates with `ci` workflow execution order
+- [ ] Integrates with Framework CI scope execution order
 
 ## Accountability & Logistics
 
@@ -415,15 +415,15 @@
 1. [ ] Review risk assessment with team
 2. [ ] Prioritize mitigation for high-priority risks (score ≥6)
 3. [ ] Allocate resources per estimates
-4. [ ] Run `/bmad-testarch-atdd` workflow to generate P0 tests (separate workflow; not auto-run)
+4. [ ] Run `/bmad-testarch-automate` in red mode to generate P0 tests
 5. [ ] Set up test data factories and fixtures
 6. [ ] Schedule team review of test design document
 
 **Recommended next workflows:**
 
-1. [ ] Run `atdd` workflow for P0 test generation
+1. [ ] Run Automate in red mode for P0 test generation
 2. [ ] Run `framework` workflow if not already done
-3. [ ] Run `ci` workflow to configure pipeline stages
+3. [ ] Run Framework with CI scope to configure pipeline stages
 
 ## Rollback Procedure
 

package/skills/bmad-testarch-test-design/resources/test-design-epic-3.example.md

@@ -258,7 +258,7 @@ P0, P1, P2, and P3 describe priority. Execution timing is defined separately bel
 
 ## Follow-on Workflows
 
-- Run `/bmad-testarch-atdd` explicitly for the four P0 scenarios.
+- Run `/bmad-testarch-automate` in red mode explicitly for the four P0 scenarios.
 - Run `/bmad-testarch-automate` for the remaining functional coverage after implementation exists.
 - Run `/bmad-testarch-nfr` when evidence exists for all four NFR domains.
 - Run `/bmad-testarch-trace` to map the approved oracle and apply the release gate.

package/skills/bmad-testarch-test-design/test-design-template.md

@@ -290,7 +290,7 @@ Do not re-list the individual tests here. They are already in the coverage plan.
 
 ## Follow-on Workflows (Manual)
 
-- Run `/bmad-testarch-atdd` to generate failing P0 tests (separate workflow; not auto-run).
+- Run `/bmad-testarch-automate` in red mode to generate failing P0 tests (separate workflow; not auto-run).
 - Run `/bmad-testarch-automate` for broader coverage once implementation exists.
 
 ---

package/skills/bmad-testarch-trace/checklist.md

@@ -16,7 +16,7 @@ This checklist covers **two sequential phases**:
 
 - [ ] A coverage oracle is available or inferred (formal requirements, spec, resolvable external pointer, or synthetic journeys)
 - [ ] Test suite exists (or gaps are acknowledged and documented)
-- [ ] If tests are missing, recommend `/bmad-testarch-atdd` (trace does not run it automatically)
+- [ ] If tests are missing, recommend `/bmad-testarch-automate` with the applicable red or expand mode (trace does not run it automatically)
 - [ ] Test directory path is correct (`test_dir` variable)
 - [ ] Story file is accessible (if using BMad mode)
 - [ ] Knowledge base is loaded (test-priorities, traceability, risk-governance)
@@ -673,7 +673,7 @@ This list is the definition of waiver validity. `steps-c/step-05-gate-decision.m
 
 - If PASS (both phases): Proceed to deployment
 - If WARN/CONCERNS: Address gaps/issues, proceed with monitoring
-- If FAIL (either phase): Run `/bmad-testarch-atdd` for missing tests, fix issues, re-run `/bmad-testarch-trace`
+- If FAIL (either phase): Run `/bmad-testarch-automate` for missing tests, fix issues, re-run `/bmad-testarch-trace`
 - If WAIVED: Deploy with approved waiver, schedule remediation
 
 ---

package/skills/bmad-testarch-trace/steps-c/step-04-analyze-gaps.md

@@ -374,7 +374,7 @@ const recommendations = [];
 if (criticalGaps.length > 0) {
   recommendations.push({
     priority: 'URGENT',
-    action: `Run /bmad-testarch-atdd for ${criticalGaps.length} P0 requirements`,
+    action: `Run /bmad-testarch-automate for ${criticalGaps.length} P0 requirements: red mode where behavior is missing; expand mode where behavior exists but tests are incomplete`,
     requirements: criticalGaps.map((r) => r.id),
   });
 }

package/skills/bmad-testarch-trace/trace-template.md

@@ -29,7 +29,7 @@ oracleLedger: []
 
 ---
 
-Note: This workflow does not generate tests. If gaps exist, run `/bmad-testarch-atdd` or `/bmad-testarch-automate` to create coverage.
+Note: This workflow does not generate tests. If gaps exist, run `/bmad-testarch-automate` in red mode before implementation or expand mode for existing code.
 
 ## PHASE 1: REQUIREMENTS TRACEABILITY
 

package/skills/bmod-tea/bmod.toml

@@ -2,14 +2,12 @@
 
 [bmod]
 code = "tea"
-version = "2.0.2"
+version = "2.0.3"
 update_source = "github:bmad-code-org/bmad-method-test-architecture-enterprise/skills"
 skills = [
   "bmad-tea",
   "bmad-teach-me-testing",
-  "bmad-testarch-atdd",
   "bmad-testarch-automate",
-  "bmad-testarch-ci",
   "bmad-testarch-evaluate",
   "bmad-testarch-framework",
   "bmad-testarch-nfr",
@@ -22,7 +20,7 @@ pre_install_message = ""
 post_install_message = '''
 TEA is ready. Talk to Murat (bmad-tea) or start with Test Design (bmad-testarch-test-design).
 
-Playwright Utils, Pact.js Utils, the Playwright CLI or MCP servers, and the SmartBear MCP each need their own install. Test Framework (bmad-testarch-framework) installs the utils packages and owns framework and CI setup. Continuous Integration (bmad-testarch-ci) remains its CI entry. Test Automation (bmad-testarch-automate) owns red and expand test generation with run-and-heal enabled by default; ATDD (bmad-testarch-atdd) starts red mode. Existing commands and customizations keep working. Ask bmad how to set up the rest.
+Playwright Utils, Pact.js Utils, the Playwright CLI or MCP servers, and the SmartBear MCP each need their own install. Test Framework (bmad-testarch-framework) installs the utils packages and owns framework and CI setup. Test Automation (bmad-testarch-automate) owns red and expand test generation with run-and-heal enabled by default. Existing CI and ATDD customizations keep working through their respective modes. Ask bmad how to set up the rest.
 '''
 
 # Asked by `bmad setup` in this order. Members read each answer as modules.tea.<key>.

package/skills/bmod-tea/help/help.md

@@ -8,9 +8,7 @@ This document covers the skills of the `tea` module: what each one gives the use
 - `bmad-teach-me-testing`: teaches testing fundamentals in 7 sessions (TEA Academy), with a progress file, session notes and a completion summary. Recommend it to someone learning testing, at any phase.
 - `bmad-testarch-test-design`: risk-based test planning, producing a test design document. Recommend it during solutioning, before tests or a framework exist. Afterwards offer `bmad-testarch-framework`.
 - `bmad-testarch-framework`: owns production-ready framework and CI setup, with framework-only, CI-only, or both scope. It installs Playwright Utils or Pact.js Utils when enabled. Recommend it during solutioning, after test design. When CI scope cannot be inferred from the request, interactive runs ask whether to include CI. Unattended runs default to framework only and state in the summary that CI was excluded.
-- `bmad-testarch-ci`: starts the framework skill with CI scope preset. Recommend it when the user asks only for CI. It keeps existing CI customizations and saved progress and offers framework setup in the same run when a framework is missing.
-- `bmad-testarch-atdd`: starts the combined test-generation skill in red mode, writes failing acceptance tests and an ATDD checklist before a story is implemented, and verifies the intended missing behavior. Recommend it after a story is created. Afterwards offer the dev story skill.
-- `bmad-testarch-automate`: owns test generation in red or expand mode. Expand mode writes tests for implemented code, runs them, heals test defects for up to three rounds by default, and reports product defects. Recommend it during implementation, after ATDD or once code exists. Recommend it with red mode when the user asks for acceptance tests before implementation.
+- `bmad-testarch-automate`: owns test generation in red or expand mode. Red mode writes failing acceptance tests and an ATDD checklist before implementation, then verifies the intended missing behavior. Expand mode writes tests for implemented code, runs them, heals test defects for up to three rounds by default, and reports product defects. Recommend red mode after a story is created and expand mode once code exists.
 - `bmad-testarch-evaluate`: builds and runs a scored, evidence-backed evaluation of an agent, skill, workflow or tool-use system. Recommend it after automation when the target's behavior needs proof. Afterwards offer `bmad-testarch-framework` with CI scope to enforce it.
 - `bmad-testarch-test-review`: audits test quality with a 0-100 score and a review report. Recommend it after tests are written. Afterwards offer `bmad-testarch-trace`.
 - `bmad-testarch-nfr`: audits the evidence for non-functional requirements and writes an NFR report. Recommend it after automation, before a release.

package/skills/bmod-tea/help/integrations.md

@@ -6,7 +6,7 @@ Each setup answer is `modules.tea.<key>` in `_bmad/config.toml`. `bmad setup tea
 
 - `test_stack_type = "auto"` detects the project type from manifest files. Mobile: `.maestro/` or `maestro/` flows, `app.json` with expo or react-native, `Podfile`, `android/app/build.gradle`, `*.xcodeproj`, `pubspec.yaml`. Frontend: `package.json` with react, vue or angular, `playwright.config.*`, `vite.config.*`. Backend: `pyproject.toml`, `pom.xml`, `go.mod`, `*.csproj`, `Gemfile`, `Cargo.toml`. Full-stack: both frontend and backend indicators. Mobile is checked first, because a React Native project also has `package.json` with react.
 - `test_framework = "auto"` detects the framework the same way.
-- The CI platform is detected by `bmad-testarch-ci` from `.github/workflows/`, `.gitlab-ci.yml`, `Jenkinsfile`, `azure-pipelines.yml`, `.harness/` or `.circleci/config.yml`. To fix one, set `ci_platform` in `_bmad/custom/bmad-testarch-ci.toml`.
+- The CI platform is detected by `bmad-testarch-framework` from `.github/workflows/`, `.gitlab-ci.yml`, `Jenkinsfile`, `azure-pipelines.yml`, `.harness/` or `.circleci/config.yml`. To override detection, set `ci_platform` in `_bmad/custom/bmad-testarch-framework.toml`.
 
 ## Execution mode
 

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