bmad-method-test-architecture-enterprise 1.19.1 → 1.19.2-next.0

package/.claude-plugin/marketplace.json

@@ -6,13 +6,21 @@
   "license": "MIT",
   "homepage": "https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise",
   "repository": "https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise",
-  "keywords": ["bmad", "test-architect", "testing", "quality", "automation", "playwright", "test-engineering"],
+  "keywords": [
+    "bmad",
+    "test-architect",
+    "testing",
+    "quality",
+    "automation",
+    "playwright",
+    "test-engineering"
+  ],
   "plugins": [
     {
       "name": "bmad-method-test-architecture-enterprise",
       "source": "./",
       "description": "Master Test Architect module for quality strategy, test automation, CI/CD quality gates, and structured testing education. Part of the BMad Method ecosystem.",
-      "version": "1.19.1",
+      "version": "1.19.2-next.0",
       "author": {
         "name": "Murat K Ozcan (TEA Creator) & Brian (BMad) Madison"
       },

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method-test-architecture-enterprise",
-  "version": "1.19.1",
+  "version": "1.19.2-next.0",
   "description": "Master Test Architect for quality strategy, test automation, and release gates",
   "keywords": [
     "bmad",

package/src/workflows/testarch/README.md

@@ -1,77 +0,0 @@
-# TEA Workflow Step Files
-
-This folder contains the Test Architect (TEA) workflows converted to skill-driven step-file architecture for strict LLM compliance. Each workflow is tri-modal (create, edit, validate) and uses small, ordered step files routed from `SKILL.md` instead of a single monolithic instruction file.
-
-## Why Step Files
-
-- Enforces sequential execution and prevents improvisation
-- Keeps context small and focused per step
-- Makes validation and edits deterministic
-
-## Standard Layout (per workflow)
-
-```
-<workflow>/
-├── SKILL.md                # Canonical entrypoint and mode routing
-├── customize.toml          # Workflow customization surface
-├── workflow-plan.md        # Design reference for step order and intent
-├── workflow.yaml           # Installer metadata
-├── instructions.md         # Short entrypoint / summary
-├── checklist.md            # Validation criteria for outputs
-├── steps-c/                # Create mode steps
-├── steps-e/                # Edit mode steps
-├── steps-v/                # Validate mode steps
-├── templates/              # Output templates (if applicable)
-└── validation-report-*.md  # Validator outputs (latest run)
-```
-
-## Modes
-
-- **Create (steps-c/):** Primary execution flow to generate outputs
-- **Edit (steps-e/):** Structured edits to existing outputs
-- **Validate (steps-v/):** Checklist-based validation of outputs
-
-## Execution Rules (Summary)
-
-- Load **one step at a time**. Do not preload future steps.
-- Follow the **MANDATORY SEQUENCE** exactly in each step.
-- Do not skip steps, reorder, or improvise.
-- If a step writes outputs, do so **before** loading the next step.
-
-## Step Naming Conventions
-
-- `step-01-*.md` is the init step (no menus unless explicitly required).
-- `step-01b-*.md` is a continuation/resume step if the workflow is continuable.
-- `step-0X-*.md` are sequential create-mode steps.
-- `steps-v/step-01-validate.md` is the validate mode entrypoint.
-- `steps-e/step-01-assess.md` is the edit mode entrypoint.
-
-## Validation
-
-- Each workflow has a latest `validation-report-*.md` in its folder.
-- Validation uses the BMad Builder workflow validator (workflow-builder).
-- The goal is 100% compliance with no warnings.
-
-## References
-
-- Step-file architecture: `docs/explanation/step-file-architecture.md`
-- Subagent patterns: `docs/explanation/subagent-architecture.md`
-
-## TEA Workflows
-
-- teach-me-testing
-- test-design
-- framework
-- ci
-- atdd
-- automate
-- test-review
-- nfr-assess
-- trace
-
-## Notes
-
-- `SKILL.md` is the canonical entrypoint. `instructions.md` is a short summary for quick context.
-- `customize.toml` defines activation hooks, persistent facts, and the optional `on_complete` hook.
-- Output files typically use `{test_artifacts}` or `{project-root}` variables.
-- If a workflow produces multiple artifacts (e.g., system-level vs epic-level), the step file will specify which templates and output paths to use.