agentvibes 3.0.0 → 3.2.0

package/.bmad/bmm/workflows/testarch/automate/instructions.md

@@ -81,16 +81,37 @@ Expands test automation coverage by generating comprehensive test suites at appr
    - Map tests to source files (coverage gaps)
    - Check existing fixture and factory patterns
 
-5. **Load Knowledge Base Fragments**
+5. **Check Playwright Utils Flag**
+
+   Read `{config_source}` and check `config.tea_use_playwright_utils`.
+
+6. **Load Knowledge Base Fragments**
 
    **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load:
+
+   **Core Testing Patterns (Always load):**
    - `test-levels-framework.md` - Test level selection (E2E vs API vs Component vs Unit with decision matrix, 467 lines, 4 examples)
    - `test-priorities-matrix.md` - Priority classification (P0-P3 with automated scoring, risk mapping, 389 lines, 2 examples)
-   - `fixture-architecture.md` - Test fixture patterns (pure function → fixture → mergeTests, auto-cleanup, 406 lines, 5 examples)
    - `data-factories.md` - Factory patterns with faker (overrides, nested factories, API seeding, 498 lines, 5 examples)
    - `selective-testing.md` - Targeted test execution strategies (tag-based, spec filters, diff-based, promotion rules, 727 lines, 4 examples)
    - `ci-burn-in.md` - Flaky test detection patterns (10-iteration burn-in, sharding, selective execution, 678 lines, 4 examples)
    - `test-quality.md` - Test design principles (deterministic, isolated, explicit assertions, length/time limits, 658 lines, 5 examples)
+
+   **If `config.tea_use_playwright_utils: true` (Playwright Utils Integration - All Utilities):**
+   - `overview.md` - Playwright utils installation, design principles, fixture patterns
+   - `api-request.md` - Typed HTTP client with schema validation
+   - `network-recorder.md` - HAR record/playback for offline testing
+   - `auth-session.md` - Token persistence and multi-user support
+   - `intercept-network-call.md` - Network spy/stub with automatic JSON parsing
+   - `recurse.md` - Cypress-style polling for async conditions
+   - `log.md` - Playwright report-integrated logging
+   - `file-utils.md` - CSV/XLSX/PDF/ZIP reading and validation
+   - `burn-in.md` - Smart test selection (relevant for CI test generation)
+   - `network-error-monitor.md` - Automatic HTTP error detection
+   - `fixtures-composition.md` - mergeTests composition patterns
+
+   **If `config.tea_use_playwright_utils: false` (Traditional Patterns):**
+   - `fixture-architecture.md` - Test fixture patterns (pure function → fixture → mergeTests, auto-cleanup, 406 lines, 5 examples)
    - `network-first.md` - Route interception patterns (intercept before navigate, HAR capture, deterministic waiting, 489 lines, 5 examples)
 
    **Healing Knowledge (If `{auto_heal_failures}` is true):**

package/.bmad/bmm/workflows/testarch/ci/checklist.md

@@ -4,7 +4,7 @@
 
 - [ ] Git repository initialized (`.git/` exists)
 - [ ] Git remote configured (`git remote -v` shows origin)
-- [ ] Test framework configured (playwright.config._ or cypress.config._)
+- [ ] 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)

package/.bmad/bmm/workflows/testarch/ci/github-actions-template.yaml

@@ -27,10 +27,21 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
+      - name: Determine Node version
+        id: node-version
+        run: |
+          if [ -f .nvmrc ]; then
+            echo "value=$(cat .nvmrc)" >> "$GITHUB_OUTPUT"
+            echo "Using Node from .nvmrc"
+          else
+            echo "value=24" >> "$GITHUB_OUTPUT"
+            echo "Using default Node 24 (current LTS)"
+          fi
+
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version-file: ".nvmrc"
+          node-version: ${{ steps.node-version.outputs.value }}
           cache: "npm"
 
       - name: Install dependencies
@@ -54,10 +65,21 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
+      - name: Determine Node version
+        id: node-version
+        run: |
+          if [ -f .nvmrc ]; then
+            echo "value=$(cat .nvmrc)" >> "$GITHUB_OUTPUT"
+            echo "Using Node from .nvmrc"
+          else
+            echo "value=22" >> "$GITHUB_OUTPUT"
+            echo "Using default Node 22 (current LTS)"
+          fi
+
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version-file: ".nvmrc"
+          node-version: ${{ steps.node-version.outputs.value }}
           cache: "npm"
 
       - name: Cache Playwright browsers
@@ -99,10 +121,21 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
+      - name: Determine Node version
+        id: node-version
+        run: |
+          if [ -f .nvmrc ]; then
+            echo "value=$(cat .nvmrc)" >> "$GITHUB_OUTPUT"
+            echo "Using Node from .nvmrc"
+          else
+            echo "value=22" >> "$GITHUB_OUTPUT"
+            echo "Using default Node 22 (current LTS)"
+          fi
+
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version-file: ".nvmrc"
+          node-version: ${{ steps.node-version.outputs.value }}
           cache: "npm"
 
       - name: Cache Playwright browsers

package/.bmad/bmm/workflows/testarch/ci/gitlab-ci-template.yaml

@@ -15,6 +15,8 @@ variables:
   npm_config_cache: "$CI_PROJECT_DIR/.npm"
   # Playwright browser cache
   PLAYWRIGHT_BROWSERS_PATH: "$CI_PROJECT_DIR/.cache/ms-playwright"
+  # Default Node version when .nvmrc is missing
+  DEFAULT_NODE_VERSION: "24"
 
 # Caching configuration
 cache:
@@ -29,19 +31,32 @@ cache:
 # Lint stage - Code quality checks
 lint:
   stage: lint
-  image: node:20
-  script:
+  image: node:$DEFAULT_NODE_VERSION
+  before_script:
+    - |
+      NODE_VERSION=$(cat .nvmrc 2>/dev/null || echo "$DEFAULT_NODE_VERSION")
+      echo "Using Node $NODE_VERSION"
+      npm install -g n
+      n "$NODE_VERSION"
+      node -v
     - npm ci
+  script:
     - npm run lint
   timeout: 5 minutes
 
 # Test stage - Parallel execution with sharding
 .test-template: &test-template
   stage: test
-  image: node:20
+  image: node:$DEFAULT_NODE_VERSION
   needs:
     - lint
   before_script:
+    - |
+      NODE_VERSION=$(cat .nvmrc 2>/dev/null || echo "$DEFAULT_NODE_VERSION")
+      echo "Using Node $NODE_VERSION"
+      npm install -g n
+      n "$NODE_VERSION"
+      node -v
     - npm ci
     - npx playwright install --with-deps chromium
   artifacts:
@@ -75,7 +90,7 @@ test:shard-4:
 # Burn-in stage - Flaky test detection
 burn-in:
   stage: burn-in
-  image: node:20
+  image: node:$DEFAULT_NODE_VERSION
   needs:
     - test:shard-1
     - test:shard-2
@@ -86,6 +101,12 @@ burn-in:
     - if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
     - if: '$CI_PIPELINE_SOURCE == "schedule"'
   before_script:
+    - |
+      NODE_VERSION=$(cat .nvmrc 2>/dev/null || echo "$DEFAULT_NODE_VERSION")
+      echo "Using Node $NODE_VERSION"
+      npm install -g n
+      n "$NODE_VERSION"
+      node -v
     - npm ci
     - npx playwright install --with-deps chromium
   script:

package/.bmad/bmm/workflows/testarch/ci/instructions.md

@@ -61,8 +61,8 @@ Scaffolds a production-ready CI/CD quality pipeline with test execution, burn-in
      - Ask user if unable to auto-detect
 
 5. **Read Environment Configuration**
-   - Check for `.nvmrc` to determine Node version
-   - Default to Node 20 LTS if not found
+   - Use `.nvmrc` for Node version if present
+   - If missing, default to a current LTS (Node 24) or newer instead of a fixed old version
    - Read `package.json` to identify dependencies (affects caching strategy)
 
 **Halt Condition:** If preflight checks fail, stop immediately and report which requirement failed.
@@ -353,7 +353,11 @@ Scaffolds a production-ready CI/CD quality pipeline with test execution, burn-in
 
 ### Knowledge Base Integration
 
-**Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to identify and load relevant knowledge fragments:
+**Critical:** Check configuration and load appropriate fragments.
+
+Read `{config_source}` and check `config.tea_use_playwright_utils`.
+
+**Core CI Patterns (Always load):**
 
 - `ci-burn-in.md` - Burn-in loop patterns: 10-iteration detection, GitHub Actions workflow, shard orchestration, selective execution (678 lines, 4 examples)
 - `selective-testing.md` - Changed test detection strategies: tag-based, spec filters, diff-based selection, promotion rules (727 lines, 4 examples)
@@ -361,6 +365,19 @@ Scaffolds a production-ready CI/CD quality pipeline with test execution, burn-in
 - `test-quality.md` - CI-specific test quality criteria: deterministic tests, isolated with cleanup, explicit assertions, length/time optimization (658 lines, 5 examples)
 - `playwright-config.md` - CI-optimized configuration: parallelization, artifact output, project dependencies, sharding (722 lines, 5 examples)
 
+**If `config.tea_use_playwright_utils: true`:**
+
+Load playwright-utils CI-relevant fragments:
+
+- `burn-in.md` - Smart test selection with git diff analysis (very important for CI optimization)
+- `network-error-monitor.md` - Automatic HTTP 4xx/5xx detection (recommend in CI pipelines)
+
+Recommend:
+
+- Add burn-in script for pull request validation
+- Enable network-error-monitor in merged fixtures for catching silent failures
+- Reference full docs in `*framework` and `*automate` workflows
+
 ### CI Platform-Specific Guidance
 
 **GitHub Actions:**

package/.bmad/bmm/workflows/testarch/framework/instructions.md

@@ -349,7 +349,33 @@ The generated `tests/README.md` should include:
 
 ### Knowledge Base Integration
 
-**Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to identify and load relevant knowledge fragments:
+**Critical:** Check configuration and load appropriate fragments.
+
+Read `{config_source}` and check `config.tea_use_playwright_utils`.
+
+**If `config.tea_use_playwright_utils: true` (Playwright Utils Integration):**
+
+Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` and load:
+
+- `overview.md` - Playwright utils installation and design principles
+- `fixtures-composition.md` - mergeTests composition with playwright-utils
+- `auth-session.md` - Token persistence setup (if auth needed)
+- `api-request.md` - API testing utilities (if API tests planned)
+- `burn-in.md` - Smart test selection for CI (recommend during framework setup)
+- `network-error-monitor.md` - Automatic HTTP error detection (recommend in merged fixtures)
+- `data-factories.md` - Factory patterns with faker (498 lines, 5 examples)
+
+Recommend installing playwright-utils:
+
+```bash
+npm install -D @seontechnologies/playwright-utils
+```
+
+Recommend adding burn-in and network-error-monitor to merged fixtures for enhanced reliability.
+
+**If `config.tea_use_playwright_utils: false` (Traditional Patterns):**
+
+Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` and load:
 
 - `fixture-architecture.md` - Pure function → fixture → `mergeTests` composition with auto-cleanup (406 lines, 5 examples)
 - `data-factories.md` - Faker-based factories with overrides, nested factories, API seeding, auto-cleanup (498 lines, 5 examples)

package/.bmad/bmm/workflows/testarch/test-design/instructions.md

@@ -66,7 +66,13 @@ The workflow auto-detects which mode to use based on project phase.
    - Note integration points and external system dependencies
    - Extract NFR requirements (performance SLOs, security requirements, etc.)
 
-2. **Load Knowledge Base Fragments (System-Level)**
+2. **Check Playwright Utils Flag**
+
+   Read `{config_source}` and check `config.tea_use_playwright_utils`.
+
+   If true, note that `@seontechnologies/playwright-utils` provides utilities for test implementation. Reference in test design where relevant.
+
+3. **Load Knowledge Base Fragments (System-Level)**
 
    **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load:
    - `nfr-criteria.md` - NFR validation approach (security, performance, reliability, maintainability)
@@ -74,7 +80,7 @@ The workflow auto-detects which mode to use based on project phase.
    - `risk-governance.md` - Testability risk identification
    - `test-quality.md` - Quality standards and Definition of Done
 
-3. **Analyze Existing Test Setup (if brownfield)**
+4. **Analyze Existing Test Setup (if brownfield)**
    - Search for existing test directories
    - Identify current test framework (if any)
    - Note testability concerns in existing codebase

package/.bmad/bmm/workflows/testarch/test-review/instructions.md

@@ -49,31 +49,51 @@ This workflow performs comprehensive test quality reviews using TEA's knowledge
 
 **Actions:**
 
-1. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`:
+1. Check playwright-utils flag:
+   - Read `{config_source}` and check `config.tea_use_playwright_utils`
+
+2. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`:
+
+   **Core Patterns (Always load):**
    - `test-quality.md` - Definition of Done (deterministic tests, isolated with cleanup, explicit assertions, <300 lines, <1.5 min, 658 lines, 5 examples)
-   - `fixture-architecture.md` - Pure function → Fixture → mergeTests composition with auto-cleanup (406 lines, 5 examples)
-   - `network-first.md` - Route intercept before navigate to prevent race conditions (intercept before navigate, HAR capture, deterministic waiting, 489 lines, 5 examples)
    - `data-factories.md` - Factory functions with faker: overrides, nested factories, API-first setup (498 lines, 5 examples)
    - `test-levels-framework.md` - E2E vs API vs Component vs Unit appropriateness with decision matrix (467 lines, 4 examples)
-   - `playwright-config.md` - Environment-based configuration with fail-fast validation (722 lines, 5 examples)
-   - `component-tdd.md` - Red-Green-Refactor patterns with provider isolation, accessibility, visual regression (480 lines, 4 examples)
    - `selective-testing.md` - Duplicate coverage detection with tag-based, spec filter, diff-based selection (727 lines, 4 examples)
    - `test-healing-patterns.md` - Common failure patterns: stale selectors, race conditions, dynamic data, network errors, hard waits (648 lines, 5 examples)
    - `selector-resilience.md` - Selector best practices (data-testid > ARIA > text > CSS hierarchy, anti-patterns, 541 lines, 4 examples)
    - `timing-debugging.md` - Race condition prevention and async debugging techniques (370 lines, 3 examples)
+
+   **If `config.tea_use_playwright_utils: true` (All Utilities):**
+   - `overview.md` - Playwright utils best practices
+   - `api-request.md` - Validate apiRequest usage patterns
+   - `network-recorder.md` - Review HAR record/playback implementation
+   - `auth-session.md` - Check auth token management
+   - `intercept-network-call.md` - Validate network interception
+   - `recurse.md` - Review polling patterns
+   - `log.md` - Check logging best practices
+   - `file-utils.md` - Validate file operation patterns
+   - `burn-in.md` - Review burn-in configuration
+   - `network-error-monitor.md` - Check error monitoring setup
+   - `fixtures-composition.md` - Validate mergeTests usage
+
+   **If `config.tea_use_playwright_utils: false`:**
+   - `fixture-architecture.md` - Pure function → Fixture → mergeTests composition with auto-cleanup (406 lines, 5 examples)
+   - `network-first.md` - Route intercept before navigate to prevent race conditions (489 lines, 5 examples)
+   - `playwright-config.md` - Environment-based configuration with fail-fast validation (722 lines, 5 examples)
+   - `component-tdd.md` - Red-Green-Refactor patterns with provider isolation (480 lines, 4 examples)
    - `ci-burn-in.md` - Flaky test detection with 10-iteration burn-in loop (678 lines, 4 examples)
 
-2. Determine review scope:
+3. Determine review scope:
    - **single**: Review one test file (`test_file_path` provided)
    - **directory**: Review all tests in directory (`test_dir` provided)
    - **suite**: Review entire test suite (discover all test files)
 
-3. Auto-discover related artifacts (if `auto_discover_story: true`):
+4. Auto-discover related artifacts (if `auto_discover_story: true`):
    - Extract test ID from filename (e.g., `1.3-E2E-001.spec.ts` → story 1.3)
    - Search for story file (`story-1.3.md`)
    - Search for test design (`test-design-story-1.3.md` or `test-design-epic-1.md`)
 
-4. Read story file for context (if available):
+5. Read story file for context (if available):
    - Extract acceptance criteria
    - Extract priority classification
    - Extract expected test IDs
@@ -504,7 +524,7 @@ await expect(page.locator('[data-testid="user-menu"]')).toBeVisible({ timeout: 1
 ### 1. Use Data Factory for Test User (Lines 23, 32, 41)
 
 **Severity**: P1 (High)
-**Issue**: Hardcoded email 'test@example.com' - maintainability risk
+**Issue**: Hardcoded email `test@example.com` - maintainability risk
 **Fix**: Create factory function for test users
 **Knowledge**: See data-factories.md
 

package/.bmad/bmm/workflows/workflow-status/init/instructions.md

@@ -3,7 +3,7 @@
 <critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: workflow-init/workflow.yaml</critical>
 <critical>Communicate in {communication_language} with {user_name}</critical>
-<critical>This workflow handles BOTH new projects AND legacy projects being migrated to BMad Method</critical>
+<critical>This workflow handles BOTH new projects AND legacy projects following the BMad Method</critical>
 
 <workflow>
 
@@ -12,7 +12,7 @@
 
 <action>Perform comprehensive scan for existing work:
 
-- BMM artifacts: PRD, tech-spec, epics, architecture, UX, brief, research, brainstorm
+- BMM artifacts: PRD, epics, architecture, UX, brief, research, brainstorm
 - Implementation: stories, sprint-status, workflow-status
 - Codebase: source directories, package files, git repo
 - Check both {output_folder} and {sprint_artifacts} locations
@@ -53,31 +53,31 @@ Happy building! 🚀</output>
 
 <ask>How would you like to proceed?
 
-a) **Continue** - Work with existing artifacts
-b) **Archive & Start Fresh** - Move old work to archive
-c) **Express Setup** - I know exactly what I need
-d) **Guided Setup** - Walk me through options
+1. **Continue** - Work with existing artifacts
+2. **Archive & Start Fresh** - Move old work to archive
+3. **Express Setup** - I know exactly what I need
+4. **Guided Setup** - Walk me through options
 
-Choice [a/b/c/d]:</ask>
+Choice [1-4]</ask>
 
-  <check if="choice == a">
+  <check if="choice == 1">
     <action>Set continuing_existing = true</action>
     <action>Store found artifacts</action>
     <action>Continue to step 7 (detect track from artifacts)</action>
   </check>
 
-  <check if="choice == b">
+  <check if="choice == 2">
     <ask>Archive existing work? (y/n)</ask>
     <action if="y">Move artifacts to {output_folder}/archive/</action>
     <output>Ready for fresh start!</output>
     <action>Continue to step 3</action>
   </check>
 
-  <check if="choice == c">
+  <check if="choice == 3">
     <action>Jump to step 3 (express path)</action>
   </check>
 
-  <check if="choice == d">
+  <check if="choice == 4">
     <action>Continue to step 4 (guided path)</action>
   </check>
 </check>
@@ -85,16 +85,16 @@ Choice [a/b/c/d]:</ask>
 <check if="state == CLEAN">
   <ask>Setup approach:
 
-a) **Express** - I know what I need
-b) **Guided** - Show me the options
+1. **Express** - I know what I need
+2. **Guided** - Show me the options
 
-Choice [a/b]:</ask>
+Choice [1 or 2]:</ask>
 
-  <check if="choice == a">
+  <check if="choice == 1">
     <action>Continue to step 3 (express)</action>
   </check>
 
-  <check if="choice == b">
+  <check if="choice == 2">
     <action>Continue to step 4 (guided)</action>
   </check>
 </check>
@@ -102,20 +102,22 @@ Choice [a/b]:</ask>
 
 <step n="3" goal="Express setup path">
 <ask>Is this for:
-1) **New project** (greenfield)
-2) **Existing codebase** (brownfield)
+1. **New project** (greenfield)
+2. **Existing codebase** (brownfield)
 
 Choice [1/2]:</ask>
 <action>Set field_type based on choice</action>
 
 <ask>Planning approach:
 
-1. **Quick Flow** - Minimal planning, fast to code
-2. **BMad Method** - Full planning for complex projects
-3. **Enterprise Method** - Extended planning with security/DevOps
+1. **BMad Method** - Full planning for complex projects
+2. **Enterprise Method** - Extended planning with security/DevOps
 
-Choice [1/2/3]:</ask>
-<action>Map to selected_track: quick-flow/method/enterprise</action>
+Choice [1/2]:</ask>
+<action>Map to selected_track: method/enterprise</action>
+
+<output>🚀 **For Quick Flow (minimal planning, straight to code):**
+Load the **quick-flow-solo-dev** agent instead - use Quick Flow agent for faster development</output>
 
 <template-output>field_type</template-output>
 <template-output>selected_track</template-output>
@@ -135,8 +137,8 @@ Choice [1/2/3]:</ask>
 
 <check if="field_type unclear AND codebase exists">
   <ask>I see existing code. Are you:
-1) **Modifying** existing codebase (brownfield)
-2) **Starting fresh** - code is just scaffold (greenfield)
+1. **Modifying** existing codebase (brownfield)
+2. **Starting fresh** - code is just scaffold (greenfield)
 
 Choice [1/2]:</ask>
 <action>Set field_type based on answer</action>
@@ -165,44 +167,60 @@ Continue with software workflows? (y/n)</output>
 </step>
 
 <step n="5" goal="Guided setup - select track">
-<output>Based on your project, here are your planning options:
+<output>Based on your project, here are your BMad Method planning options:
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-**1. Quick Flow** 🚀
-
-- Minimal planning, straight to code
-- Best for: Simple features, bug fixes
-- Risk: Potential rework if complexity emerges
-
-**2. BMad Method** 🎯 {{#if recommended}}(RECOMMENDED){{/if}}
+**1. BMad Method** 🎯 {{#if recommended}}(RECOMMENDED){{/if}}
 
 - Full planning: PRD + UX + Architecture
 - Best for: Products, platforms, complex features
 - Benefit: AI agents have complete context for better results
 
-**3. Enterprise Method** 🏢
+**2. Enterprise Method** 🏢
 
 - Extended: Method + Security + DevOps + Testing
 - Best for: Enterprise, compliance, mission-critical
 - Benefit: Comprehensive planning for complex systems
 
+**🚀 For Quick Flow (minimal planning, straight to code):**
+Load the **quick-flow-solo-dev** agent instead - use Quick Flow agent for faster development
+
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 {{#if brownfield}}
 💡 Architecture creates focused solution design from your codebase, keeping AI agents on track.
 {{/if}}</output>
 
-<ask>Which approach fits best?
+<ask>Which BMad Method approach fits best?
 
-1. Quick Flow
-2. BMad Method {{#if recommended}}(recommended){{/if}}
-3. Enterprise Method
-4. Help me decide
+1. BMad Method {{#if recommended}}(recommended){{/if}}
+2. Enterprise Method
+3. Help me decide
+4. Switch to Quick Flow (use quick-flow-solo-dev agent)
 
 Choice [1/2/3/4]:</ask>
 
 <check if="choice == 4">
+  <output>🚀 **Switching to Quick Flow!**
+
+Load the **quick-flow-solo-dev** agent instead:
+
+- Start a new chat
+- Load the quick-flow-solo-dev agent
+- Use Quick Flow for minimal planning and faster development
+
+Quick Flow is perfect for:
+
+- Simple features and bug fixes
+- Rapid prototyping
+- When you want to get straight to code
+
+Happy coding! 🚀</output>
+<action>Exit workflow</action>
+</check>
+
+<check if="choice == 3">
   <ask>What concerns you about choosing?</ask>
   <action>Provide tailored guidance based on concerns</action>
   <action>Loop back to choice</action>
@@ -215,7 +233,7 @@ Choice [1/2/3/4]:</ask>
 <step n="6" goal="Discovery workflows selection (unified)">
 <action>Determine available discovery workflows based on:
 - field_type (greenfield gets product-brief option)
-- selected_track (quick-flow skips product-brief)
+- selected_track (method/enterprise options)
 </action>
 
 <check if="field_type == greenfield AND selected_track in [method, enterprise]">
@@ -229,7 +247,7 @@ Choice [1/2/3/4]:</ask>
 Enter numbers (e.g., "1,3" or "all" or "none"): </ask>
 </check>
 
-<check if="field_type == brownfield OR selected_track == quick-flow">
+<check if="field_type == brownfield AND selected_track in [method, enterprise]">
   <output>Optional discovery workflows:</output>
   <ask>Include any of these?
 
@@ -250,7 +268,7 @@ Enter numbers (e.g., "1,2" or "none"): </ask>
 <template-output>research_requested</template-output>
 <template-output>product_brief_requested</template-output>
 
-<check if="brownfield AND selected_track != quick-flow">
+<check if="brownfield">
   <output>💡 **Note:** For brownfield projects, run document-project workflow first to analyze your codebase.</output>
 </check>
 </step>
@@ -258,18 +276,18 @@ Enter numbers (e.g., "1,2" or "none"): </ask>
 <step n="7" goal="Detect track from artifacts" if="continuing_existing OR migrating_legacy">
 <action>Analyze artifacts to detect track:
 - Has PRD → BMad Method
-- Has tech-spec only → Quick Flow
 - Has Security/DevOps → Enterprise Method
+- Has tech-spec only → Suggest switching to quick-flow-solo-dev agent
 </action>
 
 <output>Detected: **{{detected_track}}** based on {{found_artifacts}}</output>
 <ask>Correct? (y/n)</ask>
 
-<ask if="n">Which track instead?
+<ask if="n">Which BMad Method track instead?
 
-1. Quick Flow
-2. BMad Method
-3. Enterprise Method
+1. BMad Method
+2. Enterprise Method
+3. Switch to Quick Flow (use quick-flow-solo-dev agent)
 
 Choice:</ask>
 
@@ -298,11 +316,8 @@ Choice:</ask>
 {{#if brownfield}}Prerequisites: document-project{{/if}}
 {{#if has_discovery}}Discovery: {{list_selected_discovery}}{{/if}}
 
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
 {{workflow_path_summary}}
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━</output>
+</output>
 
 <ask>Create workflow tracking file? (y/n)</ask>
 
@@ -326,9 +341,6 @@ To check progress: /bmad:bmm:workflows:workflow-status
 Happy building! 🚀</output>
 </check>
 
-<check if="n">
-  <output>No problem! Run workflow-init again when ready.</output>
-</check>
 </step>
 
 </workflow>

package/.bmad/bmm/workflows/workflow-status/instructions.md

@@ -37,12 +37,19 @@
 <action>Search {output_folder}/ for file: bmm-workflow-status.yaml</action>
 
 <check if="no status file found">
-  <output>No workflow status found. To get started:
+  <output>No workflow status found.</output>
+  <ask>Would you like to run Workflow Init now? (y/n)</ask>
 
-Load analyst agent and run: `workflow-init`
+  <check if="response == y OR response == yes">
+    <action>Launching workflow-init to set up your project tracking...</action>
+    <invoke-workflow path="{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml"></invoke-workflow>
+    <action>Exit workflow and let workflow-init take over</action>
+  </check>
 
-This will guide you through project setup and create your workflow path.</output>
-<action>Exit workflow</action>
+  <check if="else">
+    <output>No workflow status file. Run workflow-init when ready to enable progress tracking.</output>
+    <action>Exit workflow</action>
+  </check>
 </check>
 
 <check if="status file found">