ma-agents 2.22.1 → 3.0.0

package/lib/bmad-cache/cis/src/workflows/README.md

@@ -1,175 +0,0 @@
-# CIS Workflows
-
-Five interactive workflows facilitating creative and strategic processes through curated technique libraries and structured facilitation.
-
-## Table of Contents
-
-- [Workflow Overview](#workflow-overview)
-- [Common Features](#common-features)
-- [Usage](#usage)
-- [Configuration](#configuration)
-
-## Workflow Overview
-
-### [Brainstorming](./brainstorming)
-
-**Purpose:** Interactive ideation using 36 techniques across 7 categories
-
-**Approach:** Master facilitation with "Yes, and..." methodology
-
-**Techniques:** Collaborative, structured, creative, deep, theatrical, wild, introspective
-
-**Selection Modes:** User-selected, AI-recommended, random, or progressive
-
-### [Design Thinking](./bmad-cis-design-thinking)
-
-**Purpose:** Human-centered design through five phases
-
-**Process:** Empathize → Define → Ideate → Prototype → Test
-
-**Focus:** Divergent thinking before convergent action
-
-**Output:** User empathy insights and rapid prototypes
-
-### [Innovation Strategy](./bmad-cis-innovation-strategy)
-
-**Purpose:** Identify disruption opportunities and business model innovation
-
-**Frameworks:** Jobs-to-be-Done, Blue Ocean Strategy, Value Chain Analysis
-
-**Focus:** Sustainable competitive advantage over features
-
-**Output:** Strategic innovation roadmap
-
-### [Problem Solving](./bmad-cis-problem-solving)
-
-**Purpose:** Systematic challenge resolution
-
-**Methods:** TRIZ, Theory of Constraints, Systems Thinking, Root Cause Analysis
-
-**Approach:** Detective-style puzzle solving
-
-**Output:** Root cause identification and solution strategies
-
-### [Storytelling](./bmad-cis-storytelling)
-
-**Purpose:** Craft compelling narratives
-
-**Frameworks:** Hero's Journey, Three-Act Structure, Story Brand (25 total)
-
-**Customization:** Platform and audience-specific adaptation
-
-**Style:** Whimsical master storyteller facilitation
-
-## Common Features
-
-All workflows share:
-
-- **Interactive Facilitation** - AI guides through questions, not generation
-- **Technique Libraries** - CSV databases of proven methods
-- **Context Integration** - Optional document input for domain relevance
-- **Structured Output** - Comprehensive reports with insights and actions
-- **Energy Monitoring** - Adaptive pacing based on engagement
-
-## Usage
-
-### Basic Invocation
-
-```bash
-workflow brainstorming
-workflow design-thinking
-workflow innovation-strategy
-workflow problem-solving
-workflow storytelling
-```
-
-### With Context
-
-```bash
-workflow [workflow-name] --data /path/to/context.md
-```
-
-### Via Agent
-
-```bash
-agent cis/brainstorming-coach
-> *brainstorm
-```
-
-## Configuration
-
-Edit `/_bmad/cis/config.yaml`:
-
-| Setting                | Purpose                 | Default            |
-| ---------------------- | ----------------------- | ------------------ |
-| output_folder          | Result storage location | ./creative-outputs |
-| user_name              | Session participant     | User               |
-| communication_language | Facilitation language   | english            |
-
-## Workflow Structure
-
-Source workflows currently use two shapes during the native-skill transition:
-
-```text
-legacy-workflow/
-├── workflow.yaml      # Configuration
-├── instructions.md    # Facilitation guide
-├── techniques.csv     # Method library
-└── README.md          # Documentation
-```
-
-```text
-bmad-cis-design-thinking/
-├── SKILL.md
-├── workflow.md
-├── bmad-skill-manifest.yaml
-├── design-methods.csv
-└── template.md
-```
-
-```text
-bmad-cis-innovation-strategy/
-├── SKILL.md
-├── workflow.md
-├── bmad-skill-manifest.yaml
-├── innovation-frameworks.csv
-└── template.md
-```
-
-```text
-bmad-cis-problem-solving/
-├── SKILL.md
-├── workflow.md
-├── bmad-skill-manifest.yaml
-├── solving-methods.csv
-└── template.md
-```
-
-```text
-bmad-cis-storytelling/
-├── SKILL.md
-├── workflow.md
-├── bmad-skill-manifest.yaml
-├── story-types.csv
-└── template.md
-```
-
-## Best Practices
-
-1. **Prepare context** - Provide background documents for better results
-2. **Set clear objectives** - Define goals before starting
-3. **Trust the process** - Let facilitation guide discovery
-4. **Capture everything** - Document insights as they emerge
-5. **Take breaks** - Pause when energy drops
-
-## Integration
-
-CIS workflows integrate with:
-
-- **BMM** - Project brainstorming and ideation
-- **BMB** - Creative module design
-- **Custom Modules** - Shared creative resource
-
----
-
-For detailed workflow instructions, see individual workflow directories.

package/lib/bmad-cache/gds/_git_preserved/refs/tags/v0.2.2

@@ -1 +0,0 @@
-de35f329fd0583066c3f18909162fa55301cba47

package/lib/bmad-cache/tea/_git_preserved/refs/tags/v1.7.0

@@ -1 +0,0 @@
-c712133a93668878936c0cff5337bfc99a96e888

package/lib/bmad-cache/tea/docs/MIGRATION.md

@@ -1,488 +0,0 @@
----
-title: Migration Guide
-description: Migrate from BMM-embedded TEA to standalone TEA module (v1.0.0+)
----
-
-# Migration Guide: BMM-Embedded TEA → Standalone TEA Module
-
-This guide helps you migrate from the BMM-embedded version of TEA to the standalone TEA module (v1.0.0+).
-
-## Overview
-
-TEA (Test Engineering Architect) has been extracted from the BMAD Method (BMM) core repository into a standalone, independently installable module. This allows:
-
-- **Independent versioning** and release cycles
-- **Optional installation** - use TEA only when needed
-- **Cleaner separation** of concerns
-- **Easier maintenance** and contribution
-
-## Breaking Changes
-
-### 1. Command Namespace
-
-All TEA commands have changed namespace from `/bmad:bmm:tea:*` to `/bmad:tea:*`.
-
-| Old Command (BMM-embedded)     | New Command (Standalone) |
-| ------------------------------ | ------------------------ |
-| `/bmad:bmm:tea:framework`      | `/bmad:tea:framework`    |
-| `/bmad:bmm:tea:ci`             | `/bmad:tea:ci`           |
-| `/bmad:bmm:tea:test-design`    | `/bmad:tea:test-design`  |
-| `/bmad:bmm:tea:atdd`           | `/bmad:tea:atdd`         |
-| `/bmad:bmm:tea:automate`       | `/bmad:tea:automate`     |
-| `/bmad:bmm:tea:test-review`    | `/bmad:tea:test-review`  |
-| `/bmad:bmm:tea:trace`          | `/bmad:tea:trace`        |
-| `/bmad:bmm:tea:nfr-assess`     | `/bmad:tea:nfr-assess`   |
-| **Short triggers** (unchanged) |                          |
-| `TF`, `CI`, `TD`, `AT`, `TA`   | Same                     |
-| `RV`, `TR`, `NR`               | Same                     |
-
-Codex skill-mode workflow equivalents: `framework` → `$bmad-tea-testarch-framework`, `ci` → `$bmad-tea-testarch-ci`, `test-design` → `$bmad-tea-testarch-test-design`, `atdd` → `$bmad-tea-testarch-atdd`, `automate` → `$bmad-tea-testarch-automate`, `test-review` → `$bmad-tea-testarch-test-review`, `trace` → `$bmad-tea-testarch-trace`, `nfr-assess` → `$bmad-tea-testarch-nfr`, `teach-me-testing` → `$bmad-tea-teach-me-testing`.
-
-Clarification: short triggers like `TD` and `TA` are agent menu triggers after TEA activation; invocation differs by tool (slash commands vs Codex skill calls).
-
-**Action Required**: Update any saved prompts, scripts, or documentation that reference the old commands.
-
-### 2. Module Installation
-
-TEA is no longer bundled with BMM by default. You must install it separately.
-
-#### Old Behavior (BMM-embedded)
-
-```bash
-# TEA automatically included
-npx bmad-method install
-```
-
-#### New Behavior (Standalone)
-
-```bash
-# Install BMAD Method first
-npx bmad-method install
-# Select modules (BMM, TEA, etc.)
-
-# Or install TEA separately later
-npx bmad-method install
-# Select: Test Architect (TEA)
-```
-
-**Action Required**: Install TEA module explicitly if not already installed.
-
-### 3. File Path Changes
-
-Internal file paths have changed to reflect TEA's standalone structure.
-
-| Old Path (BMM-embedded)         | New Path (Standalone)       |
-| ------------------------------- | --------------------------- |
-| `src/bmm/agents/tea.agent.yaml` | `src/agents/tea.agent.yaml` |
-| `src/bmm/testarch/knowledge/`   | `src/testarch/knowledge/`   |
-| `src/bmm/workflows/testarch/`   | `src/workflows/testarch/`   |
-| `_bmad/bmm/tea`                 | `_bmad/tea/`                |
-
-**Action Required**: None for end users. This only affects contributors and maintainers.
-
-### 4. Configuration Variables
-
-TEA configuration is now in its own `src/module.yaml` instead of BMM's configuration.
-
-#### Old Configuration (BMM-embedded)
-
-Configuration was embedded in BMM's module.yaml:
-
-```yaml
-# In BMM module.yaml
-variables:
-  bmm_test_artifacts: test-results
-  # TEA variables mixed with BMM
-```
-
-#### New Configuration (Standalone)
-
-TEA has its own configuration file:
-
-```yaml
-# In TEA src/module.yaml
-variables:
-  test_artifacts:
-    description: Base folder for test artifacts
-    default: test-results
-    prompt: true
-
-  tea_use_playwright_utils:
-    description: Enable Playwright Utils integration
-    default: false
-    prompt: true
-
-  tea_browser_automation:
-    description: Browser automation strategy (auto/cli/mcp/none)
-    default: 'auto'
-    prompt: true
-
-  test_design_output:
-    description: Test design documents folder
-    default: test-design
-    prompt: false
-
-  test_review_output:
-    description: Test review reports folder
-    default: test-review
-    prompt: false
-
-  trace_output:
-    description: Traceability reports folder
-    default: trace
-    prompt: false
-```
-
-**Action Required**: Reconfigure TEA variables during installation or update `_bmad/tea/module.yaml` manually.
-
-## Migration Steps
-
-### Step 1: Check Current BMAD Version
-
-Ensure you have BMAD Method v7.0.0+ (upcoming) or the latest version that supports modular installation.
-
-```bash
-# Check BMAD version
-bmad --version
-```
-
-### Step 2: Install Standalone TEA
-
-Run the BMAD installer and select TEA:
-
-```bash
-npx bmad-method install
-# When prompted, select:
-# ✓ Test Architect (TEA)
-```
-
-Follow the installation prompts to configure TEA variables:
-
-1. **test_artifacts**: Base folder for test outputs (default: `test-results`)
-2. **tea_use_playwright_utils**: Enable Playwright Utils integration (yes/no)
-3. **tea_browser_automation**: Browser automation strategy (auto/cli/mcp/none)
-
-### Step 3: Update Command References
-
-Update any saved prompts, documentation, or scripts:
-
-**Example: Updating CI/CD Scripts**
-
-```bash
-# Old
-claude "/bmad:bmm:tea:test-design"
-
-# New
-claude "/bmad:tea:test-design"
-```
-
-Codex skill mode (in Codex chat): `$bmad-tea-testarch-test-design`
-
-**Example: Updating Documentation**
-
-```markdown
-<!-- Old -->
-
-Run `/bmad:bmm:tea:automate` to expand test coverage.
-
-<!-- New -->
-
-Run `/bmad:tea:automate` to expand test coverage.
-```
-
-Codex skill-mode equivalent: use `$bmad-tea-testarch-automate`.
-
-### Step 4: Verify Installation
-
-Load the TEA agent and run a test command:
-
-```bash
-# Start Claude Code or Claude Desktop
-claude
-
-# Load TEA agent
-tea
-
-# Test a workflow
-test-design
-```
-
-You should see TEA load successfully with the message:
-
-```
-✓ Loaded agent: Murat (Master Test Architect and Quality Advisor)
-```
-
-### Step 5: Validate Configuration
-
-Check that TEA variables are correctly configured:
-
-```bash
-# Check _bmad directory
-ls -la _bmad/tea/
-
-# Verify module.yaml
-cat _bmad/tea/module.yaml
-```
-
-Expected contents:
-
-```
-_bmad/tea/
-├── module.yaml         # TEA configuration
-├── agents/
-│   └── tea.agent.yaml
-├── workflows/
-│   └── testarch/       # 9 workflows
-└── testarch/
-    ├── tea-index.csv   # Knowledge base index
-    └── knowledge/      # 35 fragments
-```
-
-## What Stays the Same
-
-Despite the migration, these aspects remain **unchanged**:
-
-✅ **Short Trigger Commands**: `TMT`, `TF`, `CI`, `TD`, `AT`, `TA`, `RV`, `TR`, `NR` work exactly the same
-
-✅ **Workflow Behavior**: All 9 workflows function identically
-
-✅ **Knowledge Base**: Same 35 knowledge fragments with identical content
-
-✅ **Output Formats**: Test designs, reports, and checklists maintain the same structure
-
-✅ **Playwright Utils Integration**: Same integration patterns and utilities
-
-✅ **Browser Automation**: CLI and MCP enhancements available via `tea_browser_automation` config
-
-✅ **Quality Standards**: Same testing best practices and quality gates
-
-## Configuration Differences
-
-### Old: BMM-Embedded Configuration
-
-```yaml
-# Variables were part of BMM module
-variables:
-  bmm_test_artifacts: test-results
-  # Mixed BMM and TEA config
-```
-
-### New: Standalone Configuration
-
-```yaml
-# TEA has its own module.yaml
-code: tea
-name: Test Architect (TEA)
-
-variables:
-  test_artifacts:
-    description: Base folder for test artifacts
-    default: test-results
-    prompt: true
-
-  tea_use_playwright_utils:
-    description: Enable Playwright Utils integration
-    default: false
-    prompt: true
-
-  tea_browser_automation:
-    description: Browser automation strategy (auto/cli/mcp/none)
-    default: 'auto'
-    prompt: true
-
-  test_design_output:
-    description: Test design documents folder
-    default: test-design
-    prompt: false
-
-  test_review_output:
-    description: Test review reports folder
-    default: test-review
-    prompt: false
-
-  trace_output:
-    description: Traceability reports folder
-    default: trace
-    prompt: false
-```
-
-### 5. Browser Automation Config Migration
-
-The `tea_use_mcp_enhancements` boolean flag has been replaced by `tea_browser_automation` string config:
-
-| Old Setting                       | New Setting                      | Notes                              |
-| --------------------------------- | -------------------------------- | ---------------------------------- |
-| `tea_use_mcp_enhancements: true`  | `tea_browser_automation: "auto"` | Auto-selects CLI or MCP per action |
-| `tea_use_mcp_enhancements: false` | `tea_browser_automation: "none"` | No browser interaction             |
-
-**New modes available:**
-
-- `"auto"` — Smart CLI/MCP selection with fallback (recommended)
-- `"cli"` — Playwright CLI only
-- `"mcp"` — Playwright MCP only (equivalent to old `true`)
-- `"none"` — No browser interaction (equivalent to old `false`)
-
-**Action Required:** Update `_bmad/tea/config.yaml`:
-
-```yaml
-# Old
-tea_use_mcp_enhancements: true
-
-# New
-tea_browser_automation: 'auto'
-```
-
-The BMAD installer will auto-migrate existing configs during the next installation.
-
-See [Configure Browser Automation](/docs/how-to/customization/configure-browser-automation.md) for full details.
-
-## Troubleshooting
-
-### Issue: "Agent Not Found" Error
-
-**Symptom**: `Error: Agent '_bmad/tea' not found`
-
-**Solution**:
-
-1. Verify TEA is installed:
-   ```bash
-   ls -la _bmad/tea/
-   ```
-2. If missing, reinstall TEA:
-   ```bash
-   npx bmad-method install
-   # Select: Test Architect (TEA)
-   ```
-
-### Issue: Old Commands Not Working
-
-**Symptom**: `/bmad:bmm:tea:test-design` returns "Command not found"
-
-**Solution**: Update to new namespace:
-
-```text
-# Old (won't work)
-/bmad:bmm:tea:test-design
-
-# New (correct)
-/bmad:tea:test-design
-
-# Codex skill mode
-$bmad-tea-testarch-test-design
-```
-
-### Issue: Configuration Variables Not Set
-
-**Symptom**: TEA asks for variables every time
-
-**Solution**: Ensure `_bmad/tea/module.yaml` exists and contains variable definitions.
-
-### Issue: Knowledge Base Fragments Not Loading
-
-**Symptom**: TEA workflows run but don't include knowledge base context
-
-**Solution**:
-
-1. Check tea-index.csv exists:
-   ```bash
-   ls -la _bmad/tea/testarch/tea-index.csv
-   ```
-2. Verify knowledge fragments:
-   ```bash
-   ls -la _bmad/tea/testarch/knowledge/
-   # Should show 35 .md files
-   ```
-
-### Issue: Workflows Producing Different Outputs
-
-**Symptom**: Test designs or reports look different than before
-
-**Solution**: This shouldn't happen - workflows are functionally identical. If you notice differences:
-
-1. Check you're using the same workflow (e.g., `test-design` not `test-review`)
-2. Verify knowledge base fragments loaded correctly
-3. Check variable configuration matches your previous setup
-
-For additional help, see [docs/reference/troubleshooting.md](/docs/reference/troubleshooting.md) or open an issue on GitHub.
-
-## Benefits of Standalone TEA
-
-### For End Users
-
-- ✅ **Optional Installation**: Only install TEA if you need test architecture guidance
-- ✅ **Lighter Weight**: Don't carry TEA's dependencies if you're not using it
-- ✅ **Clearer Purpose**: TEA focuses exclusively on test engineering
-- ✅ **Faster Updates**: TEA can release independently of BMM
-
-### For Contributors
-
-- ✅ **Focused Codebase**: Work on testing features without BMM complexity
-- ✅ **Independent Testing**: Test suite focused only on TEA functionality
-- ✅ **Easier Maintenance**: Changes to TEA don't affect BMM and vice versa
-- ✅ **Clearer Ownership**: Test engineering contributions go to TEA repo
-
-## Compatibility Matrix
-
-| BMAD Method Version | TEA Version | Compatible? | Notes                               |
-| ------------------- | ----------- | ----------- | ----------------------------------- |
-| v6.x (legacy)       | Embedded    | ✅          | Old BMM-embedded TEA                |
-| v7.0.0+             | 1.0.0+      | ✅          | Standalone TEA module               |
-| v7.0.0+             | Embedded    | ❌          | TEA removed from BMM in v7.0.0      |
-| v6.x (legacy)       | 1.0.0+      | ❌          | Standalone TEA requires BMM v7.0.0+ |
-
-## Migration Checklist
-
-Use this checklist to ensure a smooth migration:
-
-- [ ] Verify BMAD Method version is v7.0.0 or later
-- [ ] Install standalone TEA module via `npx bmad-method install`
-- [ ] Configure TEA variables (test_artifacts, Playwright Utils, MCP)
-- [ ] Update saved invocations for your tool (`/bmad:tea:*` for slash-command tools, or `$bmad-tea-*` skills for Codex)
-- [ ] Update documentation references to new commands
-- [ ] Update CI/CD scripts if they invoke TEA commands
-- [ ] Test each workflow you use (e.g., `test-design`, `automate`, `atdd`)
-- [ ] Verify knowledge base fragments load correctly
-- [ ] Confirm output formats match expectations
-- [ ] Update team documentation and onboarding guides
-
-## Getting Help
-
-If you encounter issues during migration:
-
-1. **Documentation**: Check [test-architect.bmad-method.org](https://test-architect.bmad-method.org)
-2. **Troubleshooting**: See [docs/reference/troubleshooting.md](/docs/reference/troubleshooting.md)
-3. **GitHub Issues**: Open an issue at [bmad-code-org/bmad-method-test-architecture-enterprise](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/issues)
-4. **Community**: Join discussions in GitHub Discussions
-
-## FAQ
-
-### Do I need to migrate immediately?
-
-**No.** If you're on BMAD Method v6.x with embedded TEA, you can continue using it. However, new features and updates will only be released for standalone TEA (v1.0.0+).
-
-### Can I use both BMM and TEA together?
-
-**Yes!** That's the recommended approach. Install both modules for integrated development and testing workflows.
-
-### Will my old test designs/reports still work?
-
-**Yes.** Output formats remain compatible. You can continue using test designs and reports generated by BMM-embedded TEA.
-
-### What if I don't want to use TEA?
-
-**That's fine!** TEA is now optional. Simply don't install it during BMAD Method setup.
-
-### Is standalone TEA compatible with Playwright Utils?
-
-**Yes.** Standalone TEA has the same Playwright Utils integration as BMM-embedded TEA. Enable it via the `tea_use_playwright_utils` variable during installation.
-
-### Where can I find the old BMM-embedded TEA?
-
-BMM-embedded TEA will remain available in BMAD Method v6.x releases for backwards compatibility. However, it won't receive new features or updates.
-
----
-
-**Ready to migrate?** Start with [Step 1: Check Current BMAD Version](#step-1-check-current-bmad-version)
-
-**Need help?** See [Troubleshooting](#troubleshooting) or [Getting Help](#getting-help)