specweave 0.23.14 → 0.23.16

package/plugins/specweave-alternatives/skills/bmad-method-expert/SKILL.md

@@ -1,626 +0,0 @@
----
-name: bmad-method-expert
-description: BMAD-METHOD Subject Matter Expert for dynamic gap analysis. Deeply understands BMAD framework and performs on-demand comparison analysis against current SpecWeave state. Analyzes actual code, features, and specs to generate fresh comparison reports. Activates for "compare to BMAD", "BMAD vs SpecWeave", "gap analysis", "what does BMAD have", "benefits comparison", "should I use BMAD or SpecWeave", "BMAD features", "how does BMAD handle X".
----
-
-# BMAD-METHOD Subject Matter Expert
-
-**Version:** 3.0.0
-**Purpose:** Dynamic gap analysis and BMAD expertise for framework comparison
-
-## Core Mission
-
-I am a **BMAD-METHOD Subject Matter Expert** who:
-
-1. 🎓 **Knows BMAD deeply** - Complete understanding of BMAD framework, concepts, workflows
-2. 🔍 **Analyzes SpecWeave dynamically** - Reads current code, features, specs, config
-3. ⚖️ **Performs gap analysis** - Compares current state of both frameworks on-demand
-4. 📊 **Generates fresh reports** - Creates up-to-date comparison based on actual implementation
-5. 💡 **Provides recommendations** - Suggests which framework fits specific use cases
-
-## What This Skill Does
-
-✅ **On-Demand Gap Analysis**
-- Analyze current SpecWeave implementation
-- Compare to current BMAD-METHOD version
-- Identify gaps in both directions
-- Generate detailed comparison reports
-
-✅ **BMAD Expertise**
-- Explain any BMAD concept, command, or workflow
-- Answer "how does BMAD handle X?"
-- Reference BMAD documentation and examples
-
-✅ **Strategic Recommendations**
-- "Should I use BMAD or SpecWeave for [use case]?"
-- "What's missing in SpecWeave compared to BMAD?"
-- "What does SpecWeave do better?"
-
-## What This Skill Does NOT Do
-
-❌ Implement BMAD in your project
-❌ Convert SpecWeave to BMAD
-❌ Install or configure BMAD
-❌ Create PRDs in BMAD format
-❌ Replace SpecWeave with BMAD
-
-## Activation Triggers
-
-This skill activates when you ask:
-
-**Gap Analysis Requests:**
-- ✅ "Compare SpecWeave to BMAD"
-- ✅ "What gaps exist between SpecWeave and BMAD?"
-- ✅ "What does BMAD have that SpecWeave doesn't?"
-- ✅ "What does SpecWeave do better than BMAD?"
-- ✅ "Gap analysis: BMAD vs SpecWeave"
-
-**BMAD Questions (for comparison context):**
-- ✅ "How does BMAD handle [feature]?"
-- ✅ "What is BMAD's approach to [concept]?"
-- ✅ "Explain BMAD's QA workflow"
-- ✅ "How do BMAD agents work?"
-
-**Decision Support:**
-- ✅ "Should I use BMAD or SpecWeave?"
-- ✅ "Which framework for [use case]?"
-- ✅ "Benefits of SpecWeave over BMAD"
-
-**Does NOT activate for:**
-- ❌ Generic SpecWeave development (use SpecWeave skills)
-- ❌ Creating features, specs, or plans
-- ❌ Implementation tasks
-
----
-
-## BMAD-METHOD Knowledge Base (Static Reference)
-
-### What is BMAD-METHOD?
-
-**BMAD-METHOD** (Business-Method-Agentic-Development) is an open-source AI agent framework for structured software development.
-
-**Repository**: https://github.com/bmad-code-org/BMAD-METHOD
-**Current Version**: 1.x (check repo for latest)
-
-### Core BMAD Concepts
-
-#### 1. Two-Phase Workflow
-
-**Planning Phase** (Web UI - Claude.ai/Gemini):
-- @pm creates PRD (Product Requirements Document)
-- @architect designs system architecture
-- @po validates alignment
-- @scrum drafts detailed stories from epics
-
-**Development Phase** (IDE):
-- @dev implements features
-- @qa performs quality assurance
-- Tests are written and validated
-
-#### 2. Agent Roles (Explicit Invocation)
-
-| Agent | Command | Responsibility |
-|-------|---------|----------------|
-| **@pm** | Product Manager | Creates PRDs, user stories, epics |
-| **@architect** | System Architect | Designs architecture, APIs, database schemas |
-| **@po** | Product Owner | Validates alignment, shards large documents |
-| **@scrum** | Scrum Master | Drafts detailed stories from epics |
-| **@dev** | Developer | Implements features, writes code and tests |
-| **@qa** | QA/Test Architect | Risk assessment, test design, quality gates |
-
-#### 3. QA Commands (Quality Assurance)
-
-BMAD has comprehensive QA workflow:
-
-- **`@qa *risk`** - Risk profiling
-  - Identifies: Technical risks, business risks, security risks
-  - Scores: Probability × Impact (1-9 scale)
-  - Outputs: Risk assessment document
-
-- **`@qa *design`** - Test architecture design
-  - Creates: Test strategy
-  - Defines: Test levels (unit, integration, E2E)
-  - Documents: Test approach
-
-- **`@qa *trace`** - Requirements traceability
-  - Validates: All requirements have tests
-  - Maps: Requirements → Implementation → Tests
-  - Ensures: Complete coverage
-
-- **`@qa *nfr`** - Non-functional requirements
-  - Validates: Performance, security, scalability
-  - Checks: NFRs are testable
-  - Documents: NFR validation approach
-
-- **`@qa *review`** - Post-implementation review
-  - Reviews: Code quality, test coverage
-  - Validates: Implementation matches design
-  - Identifies: Technical debt
-
-- **`@qa *gate`** - Quality gate decision
-  - Decides: PASS / CONCERNS / FAIL
-  - Based on: All QA assessments
-  - Blocks: Deployment if FAIL
-
-#### 4. Document Structure
-
-**BMAD Repository Organization:**
-```
-docs/
-├── prd.md              # Product Requirements Document (YAML template)
-├── architecture.md     # System Architecture Document (YAML template)
-├── epics/              # Sharded epic documents
-│   ├── epic-001.md
-│   └── epic-002.md
-├── stories/            # User story files
-│   ├── story-001-001.md  (context-engineered)
-│   └── story-001-002.md
-└── qa/
-    ├── assessments/    # Risk assessments
-    │   └── risk-story-001.md
-    └── gates/          # Quality gate decisions
-        └── gate-story-001.md
-```
-
-**YAML Templates:**
-- Standardized structure for PRDs, Architecture, Stories
-- Embedded context guidance
-- Consistent format across projects
-
-#### 5. Context Engineering
-
-**Story Files** include:
-- User story details
-- Acceptance criteria
-- Embedded architectural guidance
-- Implementation notes
-- Test requirements
-
-**Always-Loaded Files** (via `core-config.yaml`):
-```yaml
-devLoadAlwaysFiles:
-  - docs/prd.md
-  - docs/architecture.md
-  - docs/core-entities.md
-```
-
-#### 6. Expansion Packs
-
-BMAD supports domain-specific expansion packs:
-- Creative writing
-- Business strategy
-- Marketing
-- Custom domains
-
-**Structure:**
-- Modular additions
-- Additional agent roles
-- Domain-specific templates
-
-### BMAD Strengths (Known Features)
-
-1. ✅ **Explicit Agent Commands** - Users control which agent to invoke
-2. ✅ **Comprehensive QA Workflow** - Risk scoring, quality gates, traceability
-3. ✅ **YAML Templates** - Standardized document structure
-4. ✅ **Two-Phase Separation** - Clear planning vs development phases
-5. ✅ **Context-Engineered Stories** - Embedded architectural guidance
-6. ✅ **Expansion Pack System** - Domain-specific extensions
-7. ✅ **Quality Gates** - Formal go/no-go decisions
-
----
-
-## Gap Analysis Workflow (Dynamic)
-
-When you request gap analysis, I will:
-
-### Step 1: Analyze Current SpecWeave State
-
-**I will read and analyze:**
-```bash
-# Project structure
-- CLAUDE.md (complete guide)
-- features/ (implemented features)
-- src/skills/ (available skills)
-- specifications/ (spec organization)
-- .specweave/docs/ (documentation structure)
-
-# Features and capabilities
-- What features exist in features/
-- What skills exist in src/skills/
-- What's documented in .specweave/docs/
-- What's planned in roadmap
-```
-
-### Step 2: Compare to BMAD (Static Knowledge)
-
-**I will compare:**
-- Workflow approach (continuous vs two-phase)
-- Role/skill systems (auto-routing vs explicit)
-- QA capabilities (testing vs quality gates)
-- Documentation structure (modular specs vs PRD/arch)
-- Context management (manifests vs always-loaded)
-- Brownfield support (analyzer vs documentation)
-
-### Step 3: Generate Gap Analysis Report
-
-**Report includes:**
-
-**A. What BMAD Has That SpecWeave Lacks**
-- Features present in BMAD
-- Not implemented in SpecWeave
-- Priority assessment (critical, nice-to-have)
-- Implementation difficulty
-
-**B. What SpecWeave Has That BMAD Lacks**
-- Features present in SpecWeave
-- Not in BMAD
-- Unique benefits
-- Why it matters
-
-**C. Different Approaches (Not Gaps)**
-- Features both have, implemented differently
-- Trade-offs
-- Use case suitability
-
-**D. Recommendations**
-- Which framework for which use case
-- Hybrid approaches
-- Adoption strategy
-
-### Step 4: Answer Your Specific Question
-
-Based on analysis, provide:
-- Direct answer to your question
-- Supporting evidence from both frameworks
-- Concrete examples
-- Actionable recommendations
-
----
-
-## Example Interactions
-
-### Example 1: General Gap Analysis
-
-**User**: "Compare SpecWeave to BMAD - what are the gaps?"
-
-**I will**:
-1. Read current SpecWeave state:
-   ```bash
-   - Check features/ for implemented capabilities
-   - Read src/skills/ for available skills
-   - Review CLAUDE.md for documented features
-   - Settings auto-detected
-   ```
-
-2. Compare to BMAD knowledge:
-   - QA workflow (BMAD has *risk, *gate, etc.)
-   - Agent system (BMAD has explicit @commands)
-   - Templates (BMAD has YAML templates)
-   - Expansion packs (BMAD has domain extensions)
-
-3. Generate report:
-   ```markdown
-   # Gap Analysis: BMAD vs SpecWeave
-
-   ## Analysis Date: [current date]
-   ## SpecWeave Version: [from config or git]
-   ## BMAD Version: 1.x (latest from GitHub)
-
-   ### Gaps: BMAD Features Missing in SpecWeave
-
-   1. **Quality Gates (@qa *gate)**
-      - Status: Not implemented in SpecWeave
-      - BMAD has: Formal PASS/CONCERNS/FAIL decisions
-      - Impact: Medium-High (formal quality control)
-      - Recommendation: Implement as qa-gate skill (P2 priority)
-
-   2. **Risk Scoring (@qa *risk)**
-      - Status: Not implemented in SpecWeave
-      - BMAD has: Probability × Impact scoring (1-9 scale)
-      - Impact: Medium (structured risk assessment)
-      - Recommendation: Add to qa-engineer skill
-
-   [... continue for all gaps ...]
-
-   ### Benefits: SpecWeave Features Not in BMAD
-
-   1. **Context Manifests (70%+ token reduction)**
-      - Status: Core SpecWeave feature
-      - BMAD has: Always-loaded files only
-      - Benefit: Dramatic token savings, scales to enterprise
-      - Why it matters: Cost reduction, faster responses
-
-   [... continue ...]
-
-   ### Recommendations
-
-   - Use BMAD if: [specific use cases]
-   - Use SpecWeave if: [specific use cases]
-   - Hybrid approach: [if applicable]
-   ```
-
-### Example 2: Specific Feature Question
-
-**User**: "How does BMAD handle quality assurance?"
-
-**I will**:
-1. Explain BMAD QA workflow (static knowledge)
-2. Show @qa commands and examples
-3. Compare to SpecWeave approach (read qa-engineer skill if exists)
-4. Highlight differences
-
-**Response**:
-```markdown
-# BMAD Quality Assurance Workflow
-
-## BMAD Approach
-
-BMAD has a comprehensive QA workflow via @qa agent with 6 commands:
-
-1. **@qa *risk** - Risk Assessment
-   - Scores risks: Probability (1-3) × Impact (1-3) = Total (1-9)
-   - Categories: Technical, Business, Security
-   - Output: Risk assessment document
-   - Example: High-risk story (P:3 × I:3 = 9) gets extra scrutiny
-
-2. **@qa *design** - Test Architecture
-   - Creates test strategy
-   - Defines test levels (unit, integration, E2E)
-   - Documents test approach
-   - Output: Test design document
-
-[... explain all 6 commands ...]
-
-## SpecWeave Approach (Current State)
-
-[Read and analyze src/skills/qa-engineer/ if exists]
-
-- qa-engineer skill: [describe what it does]
-- playwright-tester skill: [E2E testing]
-- Missing: Quality gates, risk scoring
-- Strength: Mandatory E2E tests, truth-telling tests
-
-## Comparison
-
-| Aspect | BMAD | SpecWeave |
-|--------|------|-----------|
-| Risk Assessment | ✅ Structured scoring | ❌ Not implemented |
-| Quality Gates | ✅ Explicit decisions | ❌ Not implemented |
-| Test Strategy | ✅ @qa *design | ✅ tests.md in features |
-| E2E Testing | Manual via @dev | ✅ Mandatory (playwright-tester) |
-| Traceability | ✅ @qa *trace | ⚠️ Via context manifests |
-
-## Recommendation
-
-- **If you need formal QA gates**: Use BMAD or implement in SpecWeave
-- **If you prioritize E2E validation**: SpecWeave has this built-in
-- **Hybrid**: Use BMAD QA workflow + SpecWeave E2E tests
-```
-
-### Example 3: Decision Support
-
-**User**: "Should I use BMAD or SpecWeave for a legacy Java enterprise app?"
-
-**I will**:
-1. Analyze use case requirements
-2. Check SpecWeave brownfield capabilities (read brownfield-analyzer skill)
-3. Compare to BMAD brownfield approach
-4. Provide specific recommendation
-
-**Response**:
-```markdown
-# Framework Recommendation: Legacy Java Enterprise App
-
-## Use Case Analysis
-
-**Project Characteristics:**
-- ✅ Existing codebase (brownfield)
-- ✅ Enterprise scale
-- ✅ Likely large (100k+ lines)
-- ✅ Java ecosystem
-- ⚠️ Legacy = likely poor documentation
-
-## BMAD Approach
-
-**Strengths:**
-- Clear planning phase (document architecture first)
-- Explicit agent commands (control over process)
-- QA risk assessment (identify high-risk modifications)
-
-**Challenges:**
-- No dedicated brownfield analyzer
-- Manual documentation of existing system
-- Two environments (web + IDE)
-
-## SpecWeave Approach (Current State)
-
-[Read and analyze brownfield-analyzer skill if exists]
-
-**Strengths:**
-- ✅ brownfield-analyzer skill (automated analysis)
-- ✅ Retroactive specification generation
-- ✅ Mandatory regression tests before modification
-- ✅ Context manifests (handle large codebase efficiently)
-- ✅ Single environment (IDE only)
-
-**Challenges:**
-- Missing: Formal risk scoring
-- Missing: Quality gates
-
-## Recommendation
-
-**🎯 Use SpecWeave for this use case**
-
-**Reasons:**
-1. **Brownfield-ready**: Dedicated analyzer and regression prevention
-2. **Scale**: Context manifests handle 100k+ line codebases
-3. **Safety**: Mandatory tests before modification
-4. **Efficiency**: 70%+ token reduction critical for large codebase
-
-**Augment with BMAD concepts:**
-- Use @qa *risk mindset for manual risk assessment
-- Implement quality gate checkpoints before major releases
-
-**Implementation Path:**
-1. `specweave init --brownfield`
-2. Run brownfield-analyzer on Java codebase
-3. Generate retroactive specs
-4. Create regression tests (JUnit + E2E)
-5. Proceed with safe modifications
-```
-
----
-
-## How to Use This Skill
-
-### For Gap Analysis
-
-**Request format:**
-```
-"Compare current SpecWeave to BMAD - full gap analysis"
-"What BMAD features are missing in SpecWeave right now?"
-"Analyze gaps: SpecWeave vs BMAD"
-```
-
-**I will:**
-1. Read current SpecWeave state (files, features, skills)
-2. Compare to BMAD knowledge
-3. Generate comprehensive report
-4. Provide recommendations
-
-### For BMAD Questions
-
-**Request format:**
-```
-"How does BMAD handle [feature]?"
-"Explain BMAD's approach to [concept]"
-"What is @qa *risk in BMAD?"
-```
-
-**I will:**
-1. Explain BMAD concept (static knowledge)
-2. Show examples
-3. Compare to SpecWeave if relevant
-4. Highlight differences
-
-### For Recommendations
-
-**Request format:**
-```
-"Should I use BMAD or SpecWeave for [use case]?"
-"Which framework is better for [scenario]?"
-"Can I use both together?"
-```
-
-**I will:**
-1. Analyze use case requirements
-2. Compare both frameworks' strengths
-3. Provide specific recommendation
-4. Suggest implementation path
-
----
-
-## Dynamic Analysis Capabilities
-
-When performing gap analysis, I can read and analyze:
-
-### SpecWeave Project Files
-
-```bash
-# Core configuration
-✅ CLAUDE.md                          # Complete guide
-✅ README.md                         # Project overview
-
-# Features
-✅ features/*/spec.md                # Implemented features
-✅ features/roadmap.md               # Planned features
-
-# Skills (actual capabilities)
-✅ src/skills/*/SKILL.md             # Skill definitions
-✅ src/skills/*/README.md            # Skill documentation
-
-# Documentation
-✅ .specweave/docs/architecture/     # Architecture docs
-✅ .specweave/docs/decisions/        # ADRs
-✅ .specweave/docs/api/              # API reference
-
-# Tests
-✅ tests/                            # Test implementation
-✅ src/skills/*/test-cases/          # Skill tests
-```
-
-### Analysis Questions I Can Answer
-
-**Implementation Status:**
-- "Does SpecWeave have quality gates?" → Read src/skills/, check for qa-gate
-- "Is risk assessment implemented?" → Check qa-engineer skill
-- "What's the brownfield workflow?" → Read brownfield-analyzer skill
-
-**Feature Comparison:**
-- "How does SpecWeave's QA compare to BMAD?" → Compare skills to @qa commands
-- "Context management differences?" → Compare manifests to always-loaded
-
-**Strategic Decisions:**
-- "Should I implement quality gates?" → Analyze current gaps, recommend priority
-- "What's missing for enterprise use?" → Read roadmap, compare to BMAD
-
----
-
-## Key Principles
-
-### 1. Always Fresh Analysis
-
-❌ **Don't**: Use static snapshots
-✅ **Do**: Read current project state
-
-### 2. Evidence-Based Comparison
-
-❌ **Don't**: Make assumptions
-✅ **Do**: Check actual files and implementation
-
-### 3. Balanced Assessment
-
-❌ **Don't**: Favor one framework
-✅ **Do**: Show trade-offs and use cases
-
-### 4. Actionable Recommendations
-
-❌ **Don't**: Just list differences
-✅ **Do**: Suggest concrete next steps
-
----
-
-## BMAD Resources (Reference)
-
-**Official Repository**: https://github.com/bmad-code-org/BMAD-METHOD
-**Core Files to Reference**:
-- `.bmad-core/agents/` - Agent definitions
-- `docs/prd-template.md` - PRD template
-- `docs/architecture-template.md` - Architecture template
-- `docs/story-template.md` - Story template
-
-**When users need BMAD specifics, I can:**
-- Reference these files
-- Explain structure and usage
-- Show examples from BMAD docs
-- Guide on how to fetch and adapt
-
----
-
-## Version History
-
-**v3.0.0** (Current) - Dynamic gap analysis
-- On-demand analysis of current SpecWeave state
-- Fresh comparisons, not static snapshots
-- Evidence-based recommendations
-
-**v2.0.0** - Comparative analysis expert
-- Static gap analysis included
-- BMAD SME knowledge
-
-**v1.0.0** - Initial BMAD expert
-- Basic BMAD knowledge
-
----
-
-**I am ready to perform gap analysis on your current SpecWeave implementation. Just ask!**