agentvibes 2.0.22 → 2.0.23

package/.bmad-core/enhanced-ide-development-workflow.md

@@ -1,248 +0,0 @@
-# Enhanced IDE Development Workflow
-
-This is a simple step-by-step guide to help you efficiently manage your development workflow using the BMad Method. The workflow integrates the Test Architect (QA agent) throughout the development lifecycle to ensure quality, prevent regressions, and maintain high standards. Refer to the **[<ins>User Guide</ins>](user-guide.md)** for any scenario that is not covered here.
-
-## Create New Branch
-
-1. **Start new branch**
-
-## Story Creation (Scrum Master)
-
-1. **Start new chat/conversation**
-2. **Load SM agent**
-3. **Execute**: `*draft` (runs create-next-story task)
-4. **Review generated story** in `docs/stories/`
-5. **Update status**: Change from "Draft" to "Approved"
-
-## Story Implementation (Developer)
-
-1. **Start new chat/conversation**
-2. **Load Dev agent**
-3. **Execute**: `*develop-story {selected-story}` (runs execute-checklist task)
-4. **Review generated report** in `{selected-story}`
-
-## Test Architect Integration Throughout Workflow
-
-The Test Architect (Quinn) provides comprehensive quality assurance throughout the development lifecycle. Here's how to leverage each capability at the right time.
-
-**Command Aliases:** Documentation uses short forms (`*risk`, `*design`, `*nfr`, `*trace`) for the full commands (`*risk-profile`, `*test-design`, `*nfr-assess`, `*trace-requirements`).
-
-### Quick Command Reference
-
-| **Stage**                | **Command** | **Purpose**                             | **Output**                                                      | **Priority**                |
-| ------------------------ | ----------- | --------------------------------------- | --------------------------------------------------------------- | --------------------------- |
-| **After Story Approval** | `*risk`     | Identify integration & regression risks | `docs/qa/assessments/{epic}.{story}-risk-{YYYYMMDD}.md`         | High for complex/brownfield |
-|                          | `*design`   | Create test strategy for dev            | `docs/qa/assessments/{epic}.{story}-test-design-{YYYYMMDD}.md`  | High for new features       |
-| **During Development**   | `*trace`    | Verify test coverage                    | `docs/qa/assessments/{epic}.{story}-trace-{YYYYMMDD}.md`        | Medium                      |
-|                          | `*nfr`      | Validate quality attributes             | `docs/qa/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md`          | High for critical features  |
-| **After Development**    | `*review`   | Comprehensive assessment                | QA Results in story + `docs/qa/gates/{epic}.{story}-{slug}.yml` | **Required**                |
-| **Post-Review**          | `*gate`     | Update quality decision                 | Updated `docs/qa/gates/{epic}.{story}-{slug}.yml`               | As needed                   |
-
-### Stage 1: After Story Creation (Before Dev Starts)
-
-**RECOMMENDED - Set Developer Up for Success:**
-
-```bash
-# 1. RISK ASSESSMENT (Run FIRST for complex stories)
-@qa *risk {approved-story}
-# Identifies:
-#   - Technical debt impact
-#   - Integration complexity
-#   - Regression potential (1-9 scoring)
-#   - Mitigation strategies
-# Critical for: Brownfield, API changes, data migrations
-
-# 2. TEST DESIGN (Run SECOND to guide implementation)
-@qa *design {approved-story}
-# Provides:
-#   - Test scenarios per acceptance criterion
-#   - Test level recommendations (unit/integration/E2E)
-#   - Risk-based priorities (P0/P1/P2)
-#   - Test data requirements
-# Share with Dev: Include in story comments or attach to ticket
-```
-
-### Stage 2: During Development (Mid-Implementation Checkpoints)
-
-**Developer Self-Service Quality Checks:**
-
-```bash
-# 3. REQUIREMENTS TRACING (Verify coverage mid-development)
-@qa *trace {story-in-progress}
-# Validates:
-#   - All acceptance criteria have tests
-#   - No missing test scenarios
-#   - Appropriate test levels
-#   - Given-When-Then documentation clarity
-# Run when: After writing initial tests
-
-# 4. NFR VALIDATION (Check quality attributes)
-@qa *nfr {story-in-progress}
-# Assesses:
-#   - Security: Authentication, authorization, data protection
-#   - Performance: Response times, resource usage
-#   - Reliability: Error handling, recovery
-#   - Maintainability: Code quality, documentation
-# Run when: Before marking "Ready for Review"
-```
-
-### Stage 3: Story Review (Quality Gate Assessment)
-
-**REQUIRED - Comprehensive Test Architecture Review:**
-
-**Prerequisite:** All tests green locally; lint & type checks pass.
-
-```bash
-# 5. FULL REVIEW (Standard review process)
-@qa *review {completed-story}
-```
-
-**What Happens During Review:**
-
-1. **Deep Code Analysis**
-   - Architecture pattern compliance
-   - Code quality and maintainability
-   - Security vulnerability scanning
-   - Performance bottleneck detection
-
-2. **Active Refactoring**
-   - Improves code directly when safe
-   - Fixes obvious issues immediately
-   - Suggests complex refactoring for dev
-
-3. **Test Validation**
-   - Coverage at all levels (unit/integration/E2E)
-   - Test quality (no flaky tests, proper assertions)
-   - Regression test adequacy
-
-4. **Gate Decision**
-   - Creates: `docs/qa/gates/{epic}.{story}-{slug}.yml`
-   - Adds: QA Results section to story file
-   - Status: PASS/CONCERNS/FAIL/WAIVED
-
-### Stage 4: Post-Review (After Addressing Issues)
-
-**Update Gate Status After Fixes:**
-
-```bash
-# 6. GATE UPDATE (Document final decision)
-@qa *gate {reviewed-story}
-# Updates: Quality gate with new status
-# Use when: After addressing review feedback
-# Documents: What was fixed, what was waived
-```
-
-### Understanding Gate Decisions
-
-| **Status**   | **Meaning**                                  | **Action Required**     | **Can Proceed?** |
-| ------------ | -------------------------------------------- | ----------------------- | ---------------- |
-| **PASS**     | All critical requirements met                | None                    | ✅ Yes           |
-| **CONCERNS** | Non-critical issues found                    | Team review recommended | ⚠️ With caution  |
-| **FAIL**     | Critical issues (security, missing P0 tests) | Must fix                | ❌ No            |
-| **WAIVED**   | Issues acknowledged and accepted             | Document reasoning      | ✅ With approval |
-
-### Risk-Based Testing Strategy
-
-The Test Architect uses risk scoring to prioritize testing:
-
-| **Risk Score** | **Calculation**                | **Testing Priority**      | **Gate Impact**          |
-| -------------- | ------------------------------ | ------------------------- | ------------------------ |
-| **9**          | High probability × High impact | P0 - Must test thoroughly | FAIL if untested         |
-| **6**          | Medium-high combinations       | P1 - Should test well     | CONCERNS if gaps         |
-| **4**          | Medium combinations            | P1 - Should test          | CONCERNS if notable gaps |
-| **2-3**        | Low-medium combinations        | P2 - Nice to have         | Note in review           |
-| **1**          | Minimal risk                   | P2 - Minimal              | Note in review           |
-
-### Special Situations & Best Practices
-
-#### High-Risk or Brownfield Stories
-
-```bash
-# ALWAYS run this sequence:
-@qa *risk {story}    # First - identify dangers
-@qa *design {story}  # Second - plan defense
-# Then during dev:
-@qa *trace {story}   # Verify regression coverage
-@qa *nfr {story}     # Check performance impact
-# Finally:
-@qa *review {story}  # Deep integration analysis
-```
-
-#### Complex Integrations
-
-- Run `*trace` multiple times during development
-- Focus on integration test coverage
-- Use `*nfr` to validate cross-system performance
-- Review with extra attention to API contracts
-
-#### Performance-Critical Features
-
-- Run `*nfr` early and often (not just at review)
-- Establish performance baselines before changes
-- Document acceptable performance degradation
-- Consider load testing requirements in `*design`
-
-### Test Quality Standards Enforced
-
-Quinn ensures all tests meet these standards:
-
-- **No Flaky Tests**: Proper async handling, explicit waits
-- **No Hard Waits**: Dynamic strategies only (polling, events)
-- **Stateless**: Tests run independently and in parallel
-- **Self-Cleaning**: Tests manage their own test data
-- **Appropriate Levels**: Unit for logic, integration for interactions, E2E for journeys
-- **Clear Assertions**: Keep assertions in tests, not buried in helpers
-
-### Documentation & Audit Trail
-
-All Test Architect activities create permanent records:
-
-- **Assessment Reports**: Timestamped analysis in `docs/qa/assessments/`
-- **Gate Files**: Decision records in `docs/qa/gates/`
-- **Story Updates**: QA Results sections in story files
-- **Traceability**: Requirements to test mapping maintained
-
-## Commit Changes and Push
-
-1. **Commit changes**
-2. **Push to remote**
-
-## Complete Development Cycle Flow
-
-### The Full Workflow with Test Architect
-
-1. **SM**: Create next story → Review → Approve
-2. **QA (Optional)**: Risk assessment (`*risk`) → Test design (`*design`)
-3. **Dev**: Implement story → Write tests → Complete
-4. **QA (Optional)**: Mid-dev checks (`*trace`, `*nfr`)
-5. **Dev**: Mark Ready for Review
-6. **QA (Required)**: Review story (`*review`) → Gate decision
-7. **Dev (If needed)**: Address issues
-8. **QA (If needed)**: Update gate (`*gate`)
-9. **Commit**: All changes
-10. **Push**: To remote
-11. **Continue**: Until all features implemented
-
-### Quick Decision Guide
-
-**Should I run Test Architect commands?**
-
-| **Scenario**             | **Before Dev**                  | **During Dev**               | **After Dev**                |
-| ------------------------ | ------------------------------- | ---------------------------- | ---------------------------- |
-| **Simple bug fix**       | Optional                        | Optional                     | Required `*review`           |
-| **New feature**          | Recommended `*risk`, `*design`  | Optional `*trace`            | Required `*review`           |
-| **Brownfield change**    | **Required** `*risk`, `*design` | Recommended `*trace`, `*nfr` | Required `*review`           |
-| **API modification**     | **Required** `*risk`, `*design` | **Required** `*trace`        | Required `*review`           |
-| **Performance-critical** | Recommended `*design`           | **Required** `*nfr`          | Required `*review`           |
-| **Data migration**       | **Required** `*risk`, `*design` | **Required** `*trace`        | Required `*review` + `*gate` |
-
-### Success Metrics
-
-The Test Architect helps achieve:
-
-- **Zero regression defects** in production
-- **100% requirements coverage** with tests
-- **Clear quality gates** for go/no-go decisions
-- **Documented risk acceptance** for technical debt
-- **Consistent test quality** across the team
-- **Shift-left testing** with early risk identification

package/.bmad-core/install-manifest.yaml

@@ -1,230 +0,0 @@
-version: 4.44.1
-installed_at: '2025-10-17T02:58:58.009Z'
-install_type: full
-agent: null
-ides_setup:
-  - claude-code
-expansion_packs: []
-files:
-  - path: .bmad-core/working-in-the-brownfield.md
-    hash: 07cc8eb6fc664bb8
-    modified: false
-  - path: .bmad-core/user-guide.md
-    hash: f83fb2a5bc8bfe4b
-    modified: false
-  - path: .bmad-core/enhanced-ide-development-workflow.md
-    hash: 39beb3516c070e2b
-    modified: false
-  - path: .bmad-core/core-config.yaml
-    hash: 073cf6d2527c545d
-    modified: false
-  - path: .bmad-core/workflows/greenfield-ui.yaml
-    hash: 2b595f235c095790
-    modified: false
-  - path: .bmad-core/workflows/greenfield-service.yaml
-    hash: 1ea8b8d218f8caef
-    modified: false
-  - path: .bmad-core/workflows/greenfield-fullstack.yaml
-    hash: df34e60ccfac2624
-    modified: false
-  - path: .bmad-core/workflows/brownfield-ui.yaml
-    hash: 8a8068093272d00f
-    modified: false
-  - path: .bmad-core/workflows/brownfield-service.yaml
-    hash: a3cd68897852876e
-    modified: false
-  - path: .bmad-core/workflows/brownfield-fullstack.yaml
-    hash: 9716ad5956a37037
-    modified: false
-  - path: .bmad-core/utils/workflow-management.md
-    hash: c2196880f2281f84
-    modified: false
-  - path: .bmad-core/utils/bmad-doc-template.md
-    hash: 34df6ead8b91abfc
-    modified: false
-  - path: .bmad-core/data/test-priorities-matrix.md
-    hash: 1dd5698a46ab054e
-    modified: false
-  - path: .bmad-core/data/test-levels-framework.md
-    hash: f814f8efed0e96e1
-    modified: false
-  - path: .bmad-core/data/technical-preferences.md
-    hash: a829f3172a10b396
-    modified: false
-  - path: .bmad-core/data/elicitation-methods.md
-    hash: 8c3ca9b84c8784c9
-    modified: false
-  - path: .bmad-core/data/brainstorming-techniques.md
-    hash: 62b0bf50648906b0
-    modified: false
-  - path: .bmad-core/data/bmad-kb.md
-    hash: c23a5fc5c6508c5c
-    modified: false
-  - path: .bmad-core/agents/ux-expert.md
-    hash: 5de34d36ca9a747c
-    modified: false
-  - path: .bmad-core/agents/sm.md
-    hash: bd6543412a550438
-    modified: false
-  - path: .bmad-core/agents/qa.md
-    hash: 4ad40f692ee9c9fe
-    modified: false
-  - path: .bmad-core/agents/po.md
-    hash: 02a321a754de36e3
-    modified: false
-  - path: .bmad-core/agents/pm.md
-    hash: eef91ef67b74c2cf
-    modified: false
-  - path: .bmad-core/agents/dev.md
-    hash: 944c6b2750c3f0a7
-    modified: false
-  - path: .bmad-core/agents/bmad-orchestrator.md
-    hash: 1adabdf959dddf55
-    modified: false
-  - path: .bmad-core/agents/bmad-master.md
-    hash: 7e7928ef673b5f79
-    modified: false
-  - path: .bmad-core/agents/architect.md
-    hash: f5d211e80b8e160d
-    modified: false
-  - path: .bmad-core/agents/analyst.md
-    hash: 220103a5b3af7eb1
-    modified: false
-  - path: .bmad-core/tasks/validate-next-story.md
-    hash: 75e84133d364d973
-    modified: false
-  - path: .bmad-core/tasks/trace-requirements.md
-    hash: cb3e06cc0b957948
-    modified: false
-  - path: .bmad-core/tasks/test-design.md
-    hash: bcd13a95d296ce22
-    modified: false
-  - path: .bmad-core/tasks/shard-doc.md
-    hash: a83c900f64ea3d4f
-    modified: false
-  - path: .bmad-core/tasks/risk-profile.md
-    hash: addf5d143cfe6f12
-    modified: false
-  - path: .bmad-core/tasks/review-story.md
-    hash: dc366f2bd2211e11
-    modified: false
-  - path: .bmad-core/tasks/qa-gate.md
-    hash: b0a768f56f425d9f
-    modified: false
-  - path: .bmad-core/tasks/nfr-assess.md
-    hash: b9011d038b81a69b
-    modified: false
-  - path: .bmad-core/tasks/kb-mode-interaction.md
-    hash: 4d6b921c24ba4999
-    modified: false
-  - path: .bmad-core/tasks/index-docs.md
-    hash: 70b1d526b19d015e
-    modified: false
-  - path: .bmad-core/tasks/generate-ai-frontend-prompt.md
-    hash: ca4cabd824ea1b60
-    modified: false
-  - path: .bmad-core/tasks/facilitate-brainstorming-session.md
-    hash: 38594d876614e077
-    modified: false
-  - path: .bmad-core/tasks/execute-checklist.md
-    hash: 8a704b6f2bc52e12
-    modified: false
-  - path: .bmad-core/tasks/document-project.md
-    hash: 98f8790d20e83cf3
-    modified: false
-  - path: .bmad-core/tasks/create-next-story.md
-    hash: 99e5cc3237a9cffd
-    modified: false
-  - path: .bmad-core/tasks/create-doc.md
-    hash: 0a6aeba58cd7a3e4
-    modified: false
-  - path: .bmad-core/tasks/create-deep-research-prompt.md
-    hash: 6d05224a13df6047
-    modified: false
-  - path: .bmad-core/tasks/create-brownfield-story.md
-    hash: a70e435c8aafbf23
-    modified: false
-  - path: .bmad-core/tasks/correct-course.md
-    hash: 0e6d3227b1aac200
-    modified: false
-  - path: .bmad-core/tasks/brownfield-create-story.md
-    hash: 873dbf0760039028
-    modified: false
-  - path: .bmad-core/tasks/brownfield-create-epic.md
-    hash: 7b95c09793f16e1a
-    modified: false
-  - path: .bmad-core/tasks/apply-qa-fixes.md
-    hash: 70e6143a80f7296b
-    modified: false
-  - path: .bmad-core/tasks/advanced-elicitation.md
-    hash: d39118bf32237a21
-    modified: false
-  - path: .bmad-core/agent-teams/team-no-ui.yaml
-    hash: 00cbffc4106cbe1e
-    modified: false
-  - path: .bmad-core/agent-teams/team-ide-minimal.yaml
-    hash: 424972103dfde87d
-    modified: false
-  - path: .bmad-core/agent-teams/team-fullstack.yaml
-    hash: 14c7a2d8bc7ceb6f
-    modified: false
-  - path: .bmad-core/agent-teams/team-all.yaml
-    hash: db5b0ff0a9c9c2e8
-    modified: false
-  - path: .bmad-core/checklists/story-draft-checklist.md
-    hash: 0bc8a90678dba318
-    modified: false
-  - path: .bmad-core/checklists/story-dod-checklist.md
-    hash: df403478049b6958
-    modified: false
-  - path: .bmad-core/checklists/po-master-checklist.md
-    hash: 8354985e56053c48
-    modified: false
-  - path: .bmad-core/checklists/pm-checklist.md
-    hash: b53f0270312713d2
-    modified: false
-  - path: .bmad-core/checklists/change-checklist.md
-    hash: fb2d071796c8f8b6
-    modified: false
-  - path: .bmad-core/checklists/architect-checklist.md
-    hash: 15ef7d01b0e31c3f
-    modified: false
-  - path: .bmad-core/templates/story-tmpl.yaml
-    hash: 11e79b87ff700c8f
-    modified: false
-  - path: .bmad-core/templates/qa-gate-tmpl.yaml
-    hash: 80bd060708208984
-    modified: false
-  - path: .bmad-core/templates/project-brief-tmpl.yaml
-    hash: 31ba176a6ea087ab
-    modified: false
-  - path: .bmad-core/templates/prd-tmpl.yaml
-    hash: 963116f9ab9f4b70
-    modified: false
-  - path: .bmad-core/templates/market-research-tmpl.yaml
-    hash: ad46d980371caeed
-    modified: false
-  - path: .bmad-core/templates/fullstack-architecture-tmpl.yaml
-    hash: cb00c49c284dc7cb
-    modified: false
-  - path: .bmad-core/templates/front-end-spec-tmpl.yaml
-    hash: b1513524db76eeda
-    modified: false
-  - path: .bmad-core/templates/front-end-architecture-tmpl.yaml
-    hash: 413a2d9541cb0645
-    modified: false
-  - path: .bmad-core/templates/competitor-analysis-tmpl.yaml
-    hash: d0b263b0f9de8221
-    modified: false
-  - path: .bmad-core/templates/brownfield-prd-tmpl.yaml
-    hash: 5b89b783cd2cacdb
-    modified: false
-  - path: .bmad-core/templates/brownfield-architecture-tmpl.yaml
-    hash: 24af1ba7d17e68da
-    modified: false
-  - path: .bmad-core/templates/brainstorming-output-tmpl.yaml
-    hash: ba806c97165c8178
-    modified: false
-  - path: .bmad-core/templates/architecture-tmpl.yaml
-    hash: e66f63be1af30585
-    modified: false

package/.bmad-core/tasks/advanced-elicitation.md

@@ -1,119 +0,0 @@
-<!-- Powered by BMAD™ Core -->
-
-# Advanced Elicitation Task
-
-## Purpose
-
-- Provide optional reflective and brainstorming actions to enhance content quality
-- Enable deeper exploration of ideas through structured elicitation techniques
-- Support iterative refinement through multiple analytical perspectives
-- Usable during template-driven document creation or any chat conversation
-
-## Usage Scenarios
-
-### Scenario 1: Template Document Creation
-
-After outputting a section during document creation:
-
-1. **Section Review**: Ask user to review the drafted section
-2. **Offer Elicitation**: Present 9 carefully selected elicitation methods
-3. **Simple Selection**: User types a number (0-8) to engage method, or 9 to proceed
-4. **Execute & Loop**: Apply selected method, then re-offer choices until user proceeds
-
-### Scenario 2: General Chat Elicitation
-
-User can request advanced elicitation on any agent output:
-
-- User says "do advanced elicitation" or similar
-- Agent selects 9 relevant methods for the context
-- Same simple 0-9 selection process
-
-## Task Instructions
-
-### 1. Intelligent Method Selection
-
-**Context Analysis**: Before presenting options, analyze:
-
-- **Content Type**: Technical specs, user stories, architecture, requirements, etc.
-- **Complexity Level**: Simple, moderate, or complex content
-- **Stakeholder Needs**: Who will use this information
-- **Risk Level**: High-impact decisions vs routine items
-- **Creative Potential**: Opportunities for innovation or alternatives
-
-**Method Selection Strategy**:
-
-1. **Always Include Core Methods** (choose 3-4):
-   - Expand or Contract for Audience
-   - Critique and Refine
-   - Identify Potential Risks
-   - Assess Alignment with Goals
-
-2. **Context-Specific Methods** (choose 4-5):
-   - **Technical Content**: Tree of Thoughts, ReWOO, Meta-Prompting
-   - **User-Facing Content**: Agile Team Perspective, Stakeholder Roundtable
-   - **Creative Content**: Innovation Tournament, Escape Room Challenge
-   - **Strategic Content**: Red Team vs Blue Team, Hindsight Reflection
-
-3. **Always Include**: "Proceed / No Further Actions" as option 9
-
-### 2. Section Context and Review
-
-When invoked after outputting a section:
-
-1. **Provide Context Summary**: Give a brief 1-2 sentence summary of what the user should look for in the section just presented
-
-2. **Explain Visual Elements**: If the section contains diagrams, explain them briefly before offering elicitation options
-
-3. **Clarify Scope Options**: If the section contains multiple distinct items, inform the user they can apply elicitation actions to:
-   - The entire section as a whole
-   - Individual items within the section (specify which item when selecting an action)
-
-### 3. Present Elicitation Options
-
-**Review Request Process:**
-
-- Ask the user to review the drafted section
-- In the SAME message, inform them they can suggest direct changes OR select an elicitation method
-- Present 9 intelligently selected methods (0-8) plus "Proceed" (9)
-- Keep descriptions short - just the method name
-- Await simple numeric selection
-
-**Action List Presentation Format:**
-
-```text
-**Advanced Elicitation Options**
-Choose a number (0-8) or 9 to proceed:
-
-0. [Method Name]
-1. [Method Name]
-2. [Method Name]
-3. [Method Name]
-4. [Method Name]
-5. [Method Name]
-6. [Method Name]
-7. [Method Name]
-8. [Method Name]
-9. Proceed / No Further Actions
-```
-
-**Response Handling:**
-
-- **Numbers 0-8**: Execute the selected method, then re-offer the choice
-- **Number 9**: Proceed to next section or continue conversation
-- **Direct Feedback**: Apply user's suggested changes and continue
-
-### 4. Method Execution Framework
-
-**Execution Process:**
-
-1. **Retrieve Method**: Access the specific elicitation method from the elicitation-methods data file
-2. **Apply Context**: Execute the method from your current role's perspective
-3. **Provide Results**: Deliver insights, critiques, or alternatives relevant to the content
-4. **Re-offer Choice**: Present the same 9 options again until user selects 9 or gives direct feedback
-
-**Execution Guidelines:**
-
-- **Be Concise**: Focus on actionable insights, not lengthy explanations
-- **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
-- **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
-- **Maintain Flow**: Keep the process moving efficiently