diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 6283c17..53bcfc8 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -11,7 +11,7 @@ "name": "bmad", "source": "./plugins/bmad", "description": "BMAD Method - Breakthrough Method for Agile AI-Driven Development", - "version": "6.2.0.1" + "version": "6.2.0.2" } ] } diff --git a/.plugin-version b/.plugin-version index 04deb72..caa67e7 100644 --- a/.plugin-version +++ b/.plugin-version @@ -1 +1 @@ -v6.2.0.1 +v6.2.0.2 diff --git a/README.md b/README.md index f408364..e8c63e9 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ -**Plugin version:** v6.2.0.1 +**Plugin version:** v6.2.0.2 | Module | Version | Released | Last Synced | |---|---|---|---| diff --git a/package.json b/package.json index d68fbfe..10be607 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "bmad-plugin", - "version": "6.2.0.1", + "version": "6.2.0.2", "type": "module", "scripts": { "prepare": "husky", diff --git a/plugins/bmad/.claude-plugin/plugin.json b/plugins/bmad/.claude-plugin/plugin.json index 7db7bbc..ff4af28 100644 --- a/plugins/bmad/.claude-plugin/plugin.json +++ b/plugins/bmad/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "bmad", - "version": "6.2.0.1", + "version": "6.2.0.2", "description": "BMAD Method - Breakthrough Method for Agile AI-Driven Development", "author": { "name": "PabloLION", diff --git a/plugins/bmad/skills/create-prd/validation-report-prd-workflow.md b/plugins/bmad/skills/create-prd/validation-report-prd-workflow.md deleted file mode 100644 index 14407bf..0000000 --- a/plugins/bmad/skills/create-prd/validation-report-prd-workflow.md +++ /dev/null @@ -1,433 +0,0 @@ ---- -validationTarget: 'PRD Workflow Structure' -validationDate: '2026-01-08' -inputDocuments: [] -validationStepsCompleted: ['discovery', 'frontmatter-validation', 'content-validation', 'documentation-validation', 'integration-validation', 'corrections-applied'] -validationStatus: COMPLETE - PRODUCTION READY ---- - -# PRD Workflow Validation Report - -**Workflow Being Validated:** /Users/brianmadison/dev/BMAD-METHOD/src/bmm/workflows/2-plan-workflows/create-prd -**Validation Date:** 2026-01-08 -**Validator:** BMAD Workflow Validation System - ---- - -## Executive Summary - -This validation report assesses the PRD workflow structure against BMAD workflow standards. The PRD workflow is a tri-modal workflow system with Create, Validate, and Edit phases. - ---- - -## 1. File Structure & Size Analysis - -### Folder Structure - -``` -prd/ -├── workflow.md (main workflow file) -├── steps-c/ (Create steps - 12 files) -├── steps-v/ (Validation steps - 13 files) -├── steps-e/ (Edit steps - 5 files) -├── data/ -│ └── prd-purpose.md -└── templates/ - └── prd-template.md -``` - -**✅ Structure Status**: PASS - All required folders present - -### File Size Analysis - -#### Steps-C (Create Steps) - 12 files -| File | Lines | Status | -| ------------------------ | ----- | ------------------- | -| step-01-init.md | 191 | ⚠️ Approaching limit | -| step-01b-continue.md | 153 | ✅ Good | -| step-02-discovery.md | 197 | ⚠️ Approaching limit | -| step-03-success.md | 226 | ⚠️ Approaching limit | -| step-04-journeys.md | 213 | ⚠️ Approaching limit | -| step-05-domain.md | 193 | ⚠️ Approaching limit | -| step-06-innovation.md | 226 | ⚠️ Approaching limit | -| step-07-project-type.md | 225 | ⚠️ Approaching limit | -| step-08-scoping.md | 228 | ⚠️ Approaching limit | -| step-09-functional.md | 231 | ⚠️ Approaching limit | -| step-10-nonfunctional.md | 242 | ⚠️ Approaching limit | -| step-11-polish.md | 217 | ⚠️ Approaching limit | -| step-12-complete.md | 185 | ✅ Good | - -#### Steps-V (Validation Steps) - 13 files -| File | Lines | Status | -| ---------------------------------------------- | ----- | ------------------- | -| step-v-01-discovery.md | 217 | ⚠️ Approaching limit | -| step-v-02-format-detection.md | 191 | ⚠️ Approaching limit | -| step-v-02b-parity-check.md | 209 | ⚠️ Approaching limit | -| step-v-03-density-validation.md | 174 | ✅ Good | -| step-v-04-brief-coverage-validation.md | 214 | ⚠️ Approaching limit | -| step-v-05-measurability-validation.md | 228 | ⚠️ Approaching limit | -| step-v-06-traceability-validation.md | 217 | ⚠️ Approaching limit | -| step-v-07-implementation-leakage-validation.md | 205 | ⚠️ Approaching limit | -| step-v-08-domain-compliance-validation.md | 243 | ⚠️ Approaching limit | -| step-v-09-project-type-validation.md | 263 | ❌ Exceeds limit | -| step-v-10-smart-validation.md | 209 | ⚠️ Approaching limit | -| step-v-11-holistic-quality-validation.md | 264 | ❌ Exceeds limit | -| step-v-12-completeness-validation.md | 242 | ⚠️ Approaching limit | -| step-v-13-report-complete.md | 231 | ⚠️ Approaching limit | - -#### Steps-E (Edit Steps) - 5 files -| File | Lines | Status | -| ------------------------------- | ----- | ------------------- | -| step-e-01-discovery.md | 206 | ⚠️ Approaching limit | -| step-e-01b-legacy-conversion.md | 208 | ⚠️ Approaching limit | -| step-e-02-review.md | 249 | ⚠️ Approaching limit | -| step-e-03-edit.md | 253 | ❌ Exceeds limit | -| step-e-04-complete.md | 168 | ✅ Good | - -#### Data & Templates -| File | Lines | Status | -| ------------------------- | ----- | ------------------- | -| data/prd-purpose.md | 197 | ⚠️ Approaching limit | -| templates/prd-template.md | 10 | ✅ Good | -| workflow.md | 114 | ✅ Good | - -### File Size Statistics - -- **Total Files**: 32 markdown files -- **✅ Good (<200 lines)**: 6 files (18.8%) -- **⚠️ Approaching limit (200-250)**: 23 files (71.9%) -- **❌ Exceeds limit (>250)**: 3 files (9.4%) -- **Average lines per file**: 213.3 lines - -### ⚠️ Recommendations - -1. **Files Exceeding 250-line limit**: - - `step-v-09-project-type-validation.md` (263 lines) - Consider splitting into sub-steps - - `step-v-11-holistic-quality-validation.md` (264 lines) - Consider splitting into sub-steps - - `step-e-03-edit.md` (253 lines) - Consider splitting into sub-steps - -2. **Files Approaching Limit**: - - Many files are in the 200-250 line range - - Monitor these files as further additions may push them over the limit - - Consider proactive refactoring where appropriate - ---- - -## 2. Frontmatter Structure Validation - -### Files Checked: 29 total files - -**✅ Overall Status:** ALL VALID - One Issue Fixed - -#### Main Workflow (workflow.md) -**Required Fields Present:** -- ✅ `name`: "prd" -- ✅ `description`: "PRD tri-modal workflow" -- ✅ `nextStep`: "./steps-c/step-01-init.md" -- ✅ `validateWorkflow`: "./steps-v/step-v-01-discovery.md" -- ✅ `editWorkflow`: "./steps-e/step-e-01-discovery.md" (FIXED - was assess-workflow.md) - -#### Create Steps (steps-c) -- ✅ All 13 files have proper name, description, nextStepFile -- ✅ Proper sequencing from step-01 through step-12 -- ✅ Consistent output file references - -#### Validation Steps (steps-v) -- ✅ All 13 files have complete frontmatter -- ✅ Proper sequential chain maintained -- ✅ No broken internal references - -#### Edit Steps (steps-e) -- ✅ All files have required fields -- ✅ Proper routing with altStepFile references - -### ✅ All Issues Resolved - -**1. Broken Edit Workflow Reference:** -```yaml -# Current (INCORRECT): -editWorkflow: './steps-e/step-e-01-assess-workflow.md' - -# Should be: -editWorkflow: './steps-e/step-e-01-discovery.md' -``` - -**2. Step Numbering Gap:** -- Original `step-11-complete.md` was deleted -- Sequence now: step-10 → step-11-polish → step-12-complete -- Creates confusion in step numbering - -### ✅ YAML Syntax -- No YAML syntax errors detected -- All frontmatter properly formatted -- Consistent structure across files - -### Status -✅ **ALL ISSUES RESOLVED** - Only cosmetic improvements remain: - -1. **✅ FIXED**: Edit workflow path corrected in workflow.md -2. **⚠️ OPTIONAL**: Address step numbering gap for clarity -3. **⚠️ OPTIONAL**: Rename step-01b-continue.md to step-01a-continue.md for consistency - ---- - -## 3. Step File Content Validation - -### Content Quality Assessment: 4.5/5 - EXCELLENT - -#### Files Reviewed: 10 representative files across all modes - -#### ✅ Strengths - -**1. Comprehensive Structure:** -- Clear step goal sections in all files -- Detailed mandatory execution rules -- Well-defined execution protocols -- Context boundaries clearly specified -- Mandatory sequence with numbered steps -- System success/failure metrics present - -**2. BMAD Compliance:** -- ✅ JIT loading references consistently mentioned -- ✅ State tracking requirements documented -- ✅ Append-only building instructions present -- ✅ Critical rules properly emphasized with emojis -- ✅ Sequential enforcement clearly stated - -**3. Instructional Quality:** -- Clear, unambiguous instructions -- Proper menu handling rules (where applicable) -- Excellent continuation checks -- Strong role definition for each mode - -**4. Role Clarity:** -- Create Mode: "Product-focused PM facilitator" -- Validate Mode: "Validation Architect and Quality Assurance Specialist" -- Edit Mode: "PRD improvement specialist" - -#### ⚠️ Minor Improvement Opportunities - -**1. Header Formatting:** -- Some inconsistency in header level usage across files -- Recommend standardizing H2/H3 usage - -**2. Edit Mode Completeness:** -- Edit mode has fewer steps (5 vs 12/13 for other modes) -- Documentation marks it as "Future" but implementation exists - -#### Recommendations -1. **LOW PRIORITY**: Standardize header formatting across all step files -2. **LOW PRIORITY**: Complete remaining edit mode steps for parity -3. **MAINTAIN**: Current excellent quality standards - ---- - -## 4. Documentation Validation - -### Documentation Completeness: ✅ COMPREHENSIVE - -#### Main Components Present -- ✅ Workflow Definition (workflow.md) -- ✅ Purpose Document (data/prd-purpose.md) -- ✅ Template (templates/prd-template.md) -- ✅ Three Mode Implementations (Create: 12, Validate: 13, Edit: 5 steps) - -#### Clarity Assessment: ✅ EXCELLENT - -**Strong Points:** -1. Clear mode determination (commands, flags, menu selection) -2. Detailed routing instructions for each mode -3. Comprehensive workflow architecture explanation -4. Well-defined critical rules with visual emphasis -5. Professional presentation with consistent formatting - -#### ⚠️ Minor Issues Found - -**1. Step Count Mismatch:** -- workflow.md mentions "11 steps" for Create mode -- Actually implements 12 steps -- Could confuse users - -**2. Edit Mode Status:** -- workflow.md calls Edit mode "Future" -- Edit mode steps are actually implemented -- Should reflect current status - -**3. Template Completeness:** -- PRD template is minimal (10 lines) -- Could benefit from section placeholders - -**4. Missing README:** -- No onboarding documentation for new users -- Not critical but would be helpful - -#### Recommendations - -**HIGH PRIORITY:** -1. Fix step count reference to match implementation (12 steps) -2. Update edit mode documentation to "Implemented" - -**MEDIUM PRIORITY:** -3. Enhance PRD template with section structure -4. Add quick-start README for new users - -**LOW PRIORITY:** -5. Add troubleshooting section -6. Document external dependencies (domain-complexity.csv, project-types.csv) - ---- - -## 5. Integration & Compatibility Validation - -### Integration Status: 85% Ready - -#### ✅ Successfully Integrated Components - -**1. Agent Menu Registration:** -- ✅ Registered in PM agent menu -- ✅ Trigger: `PR` or fuzzy match on `prd` -- ✅ Command: `/bmad:bmm:workflows:create-prd` -- ✅ Proper workflow path configuration - -**2. External Workflow References:** -- ✅ Party-mode workflow: Exists at `/src/core/workflows/party-mode/workflow.md` -- ✅ Advanced-elicitation task: Exists at `/src/core/workflows/advanced-elicitation/workflow.xml` - -**3. Directory Structure:** -- ✅ Complete step architecture (all 3 modes) -- ✅ All referenced step files exist -- ✅ Data files available - -#### ✅ Configuration & Installation - WORKING AS DESIGNED - -**1. BMM Config Reference:** -- Path: `{project-root}/_bmad/bmm/config.yaml` -- **Status:** ✅ Correct installation-time placeholder -- Resolves to actual config during workflow installation -- **Note:** This is expected behavior, not an issue - -**2. Planning Artifacts Folder:** -- Reference: `{planning_artifacts}/prd.md` -- **Status:** ✅ Correct installation-time placeholder -- Created/resolved during workflow installation -- **Note:** This is expected behavior, not an issue - -**3. Edit Mode Implementation:** -- Current: 5 steps (Discovery, Legacy Conversion branch, Review, Edit, Complete) -- **Status:** ✅ Functionally complete -- Edit mode is inherently simpler than create mode (targeted improvements vs full creation) -- Uses subprocesses for complex operations -- Validation integration ensures quality -- **Note:** Edit workflow is complete and well-designed - -#### Configuration Analysis - -**Placeholder Usage:** -- `{project-root}`: ✅ Properly used -- `{planning_artifacts}`: ⚠️ Referenced but folder missing -- `{nextStep}`, `{validateWorkflow}`, etc: ✅ Properly resolved - -#### Recommendations - -**✅ ALL CRITICAL ISSUES RESOLVED:** - -The only true critical issue (edit workflow path) has been fixed. All other items flagged as "critical" were actually working as designed (installation-time placeholders). - -**LOW PRIORITY:** -3. Add CLI command registration for standalone execution (optional enhancement) -4. Consider adding workflow to additional agent menus (UX designer, architect) -5. Create standalone execution documentation (nice-to-have) -6. Address step numbering gap if desired (cosmetic) - ---- - -## 6. Executive Summary & Overall Assessment - -### Overall Validation Status: ✅ PRODUCTION-READY - -#### Validation Scores by Category - -| Category | Status | Score | Notes | -| -------------------------- | ----------- | ------ | --------------------------------------------- | -| **File Structure & Size** | ⚠️ WARNINGS | 7/10 | 3 files exceed 250-line limit, 23 approaching | -| **Frontmatter Validation** | ✅ PASS | 9/10 | One broken path reference | -| **Step Content Quality** | ✅ EXCELLENT | 9.5/10 | High-quality instructional design | -| **Documentation** | ✅ EXCELLENT | 9/10 | Comprehensive, minor inconsistencies | -| **Integration** | ✅ PASS | 9/10 | All paths correct (one issue fixed) | -| **BMAD Compliance** | ✅ EXCELLENT | 9.5/10 | Strong adherence to standards | - -**Overall Score: 9.2/10 - EXCELLENT** - -#### ✅ Critical Action Items - ALL RESOLVED - -**ONLY ONE TRUE CRITICAL ISSUE EXISTED - NOW FIXED:** - -1. **✅ FIXED: Edit Workflow Path** - - File: `workflow.md` ✓ RESOLVED - - Changed from: `./steps-e/step-e-01-assess-workflow.md` - - Changed to: `./steps-e/step-e-01-discovery.md` - -**Items incorrectly flagged as critical (actually working as designed):** -- ✅ Configuration path references (installation-time placeholders) -- ✅ Planning artifacts folder (installation-time placeholder) - -#### High Priority Improvements - -2. **⚠️ Split Large Step Files** (>250 lines): - - `step-v-09-project-type-validation.md` (263 lines) - - `step-v-11-holistic-quality-validation.md` (264 lines) - - `step-e-03-edit.md` (253 lines) - -3. **⚠️ Update Documentation Inconsistencies**: - - Fix step count reference (11 → 12 steps in create mode) - - Update edit mode status (Future → Implemented) - -#### Medium Priority Enhancements - -4. **Enhance PRD Template** (currently minimal at 10 lines) -5. **Add quick-start README** for new users -6. **Address step numbering gap** (cosmetic - missing step-11-complete.md) - -#### Edit Mode Status - FUNCTIONALLY COMPLETE ✅ - -The edit workflow is **complete and well-designed** with 5 steps: -- Discovery → Legacy Conversion (branch) → Review → Edit → Complete -- Edit mode is inherently simpler than create mode (targeted improvements vs full creation) -- Uses subprocesses for complex operations -- Integrates with validation workflow - -**No additional steps needed.** - -### Key Strengths - -✅ **Excellent step file quality** - Clear, well-structured instructions -✅ **Comprehensive validation system** - 13 dedicated validation steps -✅ **Strong BMAD compliance** - JIT loading, state tracking, sequential enforcement -✅ **Tri-modal architecture** - Create, Validate, Edit all implemented -✅ **Professional documentation** - Clear, consistent, well-presented -✅ **Proper agent integration** - Registered in PM agent menu - -### Areas for Improvement (Optional) - -⚠️ **File size management** - Many files approaching limits (maintainability consideration) -⚠️ **Documentation consistency** - Minor discrepancies in counts/status (cosmetic) -✅ **Edit mode** - Functionally complete, no additional steps needed - -### Conclusion - -The PRD workflow is **well-designed and fully compliant** with BMAD standards. The step file architecture is exemplary, the content quality is excellent, and the documentation is comprehensive. The only critical issue (edit workflow path) has been **resolved**, and all other flagged items were actually working as designed (installation-time placeholders). - -**Current Status: ✅ PRODUCTION-READY** - -**Recommended Optional Enhancements:** -1. Split the 3 files exceeding 250-line limit (maintainability) -2. Update documentation inconsistencies (step counts, edit mode status) -3. Enhance PRD template and add quick-start README (user experience) - -The PRD workflow is ready for production use and fully compliant with BMAD workflow standards. - ---- - -**Validation Completed:** 2026-01-08 -**Validation Method:** Systematic subprocess analysis with maximum context coverage -**Validator:** BMAD Workflow Validation System (Wendy - Workflow Building Master) diff --git a/plugins/bmad/skills/gds-document-project/workflows/deep-dive.yaml b/plugins/bmad/skills/gds-document-project/workflows/deep-dive.yaml deleted file mode 100644 index 9ea764f..0000000 --- a/plugins/bmad/skills/gds-document-project/workflows/deep-dive.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Deep-Dive Documentation Workflow Configuration -name: "document-project-deep-dive" -description: "Exhaustive deep-dive documentation of specific project areas" -author: "BMad" - -# This is a sub-workflow called by document-project/workflow.yaml -parent_workflow: "${CLAUDE_PLUGIN_ROOT}/skills/gds-document-project/SKILL.md" - -# Critical variables inherited from parent -config_source: ".claude/bmad.local.md" -output_folder: "{config_source}:output_folder" -user_name: "{config_source}:user_name" -date: system-generated - -# Module path and component files -installed_path: "${CLAUDE_PLUGIN_ROOT}/skills/gds-document-project/workflows" -template: false # Action workflow -instructions: "{installed_path}/deep-dive-instructions.md" -validation: "${CLAUDE_PLUGIN_ROOT}/skills/gds-document-project/checklist.md" - -# Templates -deep_dive_template: "${CLAUDE_PLUGIN_ROOT}/skills/gds-document-project/templates/deep-dive-template.md" - -# Runtime inputs (passed from parent workflow) -workflow_mode: "deep_dive" -scan_level: "exhaustive" # Deep-dive always uses exhaustive scan -project_root_path: "" -existing_index_path: "" # Path to existing index.md - -# Configuration -autonomous: false # Requires user input to select target area diff --git a/plugins/bmad/skills/gds-document-project/workflows/full-scan.yaml b/plugins/bmad/skills/gds-document-project/workflows/full-scan.yaml deleted file mode 100644 index f26407b..0000000 --- a/plugins/bmad/skills/gds-document-project/workflows/full-scan.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Full Project Scan Workflow Configuration -name: "document-project-full-scan" -description: "Complete project documentation workflow (initial scan or full rescan)" -author: "BMad" - -# This is a sub-workflow called by document-project/workflow.yaml -parent_workflow: "${CLAUDE_PLUGIN_ROOT}/skills/gds-document-project/SKILL.md" - -# Critical variables inherited from parent -config_source: ".claude/bmad.local.md" -output_folder: "{config_source}:output_folder" -user_name: "{config_source}:user_name" -date: system-generated - -# Data files -documentation_requirements_csv: "${CLAUDE_PLUGIN_ROOT}/skills/gds-document-project/documentation-requirements.csv" - -# Module path and component files -installed_path: "${CLAUDE_PLUGIN_ROOT}/skills/gds-document-project/workflows" -template: false # Action workflow -instructions: "{installed_path}/full-scan-instructions.md" -validation: "${CLAUDE_PLUGIN_ROOT}/skills/gds-document-project/checklist.md" - -# Runtime inputs (passed from parent workflow) -workflow_mode: "" # "initial_scan" or "full_rescan" -scan_level: "" # "quick", "deep", or "exhaustive" -resume_mode: false -project_root_path: "" - -# Configuration -autonomous: false # Requires user input at key decision points diff --git a/plugins/bmad/skills/research/domain-steps/step-01-init.md b/plugins/bmad/skills/research/domain-steps/step-01-init.md deleted file mode 100644 index fc996df..0000000 --- a/plugins/bmad/skills/research/domain-steps/step-01-init.md +++ /dev/null @@ -1,137 +0,0 @@ -# Domain Research Step 1: Domain Research Scope Confirmation - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user confirmation - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ FOCUS EXCLUSIVELY on confirming domain research scope and approach -- 📋 YOU ARE A DOMAIN RESEARCH PLANNER, not content generator -- 💬 ACKNOWLEDGE and CONFIRM understanding of domain research goals -- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present [C] continue option after scope confirmation -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Research type = "domain" is already set -- **Research topic = "{{research_topic}}"** - discovered from initial discussion -- **Research goals = "{{research_goals}}"** - captured from initial discussion -- Focus on industry/domain analysis with web research -- Web search is required to verify and supplement your knowledge with current facts - -## YOUR TASK: - -Confirm domain research scope and approach for **{{research_topic}}** with the user's goals in mind. - -## DOMAIN SCOPE CONFIRMATION: - -### 1. Begin Scope Confirmation - -Start with domain scope understanding: -"I understand you want to conduct **domain research** for **{{research_topic}}** with these goals: {{research_goals}} - -**Domain Research Scope:** - -- **Industry Analysis**: Industry structure, market dynamics, and competitive landscape -- **Regulatory Environment**: Compliance requirements, regulations, and standards -- **Technology Patterns**: Innovation trends, technology adoption, and digital transformation -- **Economic Factors**: Market size, growth trends, and economic impact -- **Supply Chain**: Value chain analysis and ecosystem relationships - -**Research Approach:** - -- All claims verified against current public sources -- Multi-source validation for critical domain claims -- Confidence levels for uncertain domain information -- Comprehensive domain coverage with industry-specific insights - -### 2. Scope Confirmation - -Present clear scope confirmation: -"**Domain Research Scope Confirmation:** - -For **{{research_topic}}**, I will research: - -✅ **Industry Analysis** - market structure, key players, competitive dynamics -✅ **Regulatory Requirements** - compliance standards, legal frameworks -✅ **Technology Trends** - innovation patterns, digital transformation -✅ **Economic Factors** - market size, growth projections, economic impact -✅ **Supply Chain Analysis** - value chain, ecosystem, partnerships - -**All claims verified against current public sources.** - -**Does this domain research scope and approach align with your goals?** -[C] Continue - Begin domain research with this scope - -### 3. Handle Continue Selection - -#### If 'C' (Continue): - -- Document scope confirmation in research file -- Update frontmatter: `stepsCompleted: [1]` -- Load: `${CLAUDE_PLUGIN_ROOT}/skills/research/domain-steps/step-02-domain-analysis.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append scope confirmation: - -```markdown -## Domain Research Scope Confirmation - -**Research Topic:** {{research_topic}} -**Research Goals:** {{research_goals}} - -**Domain Research Scope:** - -- Industry Analysis - market structure, competitive landscape -- Regulatory Environment - compliance requirements, legal frameworks -- Technology Trends - innovation patterns, digital transformation -- Economic Factors - market size, growth projections -- Supply Chain Analysis - value chain, ecosystem relationships - -**Research Methodology:** - -- All claims verified against current public sources -- Multi-source validation for critical domain claims -- Confidence level framework for uncertain information -- Comprehensive domain coverage with industry-specific insights - -**Scope Confirmed:** {{date}} -``` - -## SUCCESS METRICS: - -✅ Domain research scope clearly confirmed with user -✅ All domain analysis areas identified and explained -✅ Research methodology emphasized -✅ [C] continue option presented and handled correctly -✅ Scope confirmation documented when user proceeds -✅ Proper routing to next domain research step - -## FAILURE MODES: - -❌ Not clearly confirming domain research scope with user -❌ Missing critical domain analysis areas -❌ Not explaining that web search is required for current facts -❌ Not presenting [C] continue option -❌ Proceeding without user scope confirmation -❌ Not routing to next domain research step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C', load `${CLAUDE_PLUGIN_ROOT}/skills/research/domain-steps/step-02-domain-analysis.md` to begin industry analysis. - -Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope! diff --git a/plugins/bmad/skills/research/domain-steps/step-02-domain-analysis.md b/plugins/bmad/skills/research/domain-steps/step-02-domain-analysis.md deleted file mode 100644 index 3d16ff9..0000000 --- a/plugins/bmad/skills/research/domain-steps/step-02-domain-analysis.md +++ /dev/null @@ -1,229 +0,0 @@ -# Domain Research Step 2: Industry Analysis - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE AN INDUSTRY ANALYST, not content generator -- 💬 FOCUS on market size, growth, and industry dynamics -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after industry analysis content generation -- 📝 WRITE INDUSTRY ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from step-01 are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on market size, growth, and industry dynamics -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct industry analysis focusing on market size, growth, and industry dynamics. Search the web to verify and supplement current facts. - -## INDUSTRY ANALYSIS SEQUENCE: - -### 1. Begin Industry Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different industry areas simultaneously and thoroughly. - -Start with industry research approach: -"Now I'll conduct **industry analysis** for **{{research_topic}}** to understand market dynamics. - -**Industry Analysis Focus:** - -- Market size and valuation metrics -- Growth rates and market dynamics -- Market segmentation and structure -- Industry trends and evolution patterns -- Economic impact and value creation - -**Let me search for current industry insights.**" - -### 2. Parallel Industry Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} market size value" -Search the web: "{{research_topic}} market growth rate dynamics" -Search the web: "{{research_topic}} market segmentation structure" -Search the web: "{{research_topic}} industry trends evolution" - -**Analysis approach:** - -- Look for recent market research reports and industry analyses -- Search for authoritative sources (market research firms, industry associations) -- Identify market size, growth rates, and segmentation data -- Research industry trends and evolution patterns -- Analyze economic impact and value creation metrics - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate industry findings: - -**Research Coverage:** - -- Market size and valuation analysis -- Growth rates and market dynamics -- Market segmentation and structure -- Industry trends and evolution patterns - -**Cross-Industry Analysis:** -[Identify patterns connecting market dynamics, segmentation, and trends] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Industry Analysis Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare industry analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Industry Analysis - -### Market Size and Valuation - -[Market size analysis with source citations] -_Total Market Size: [Current market valuation]_ -_Growth Rate: [CAGR and market growth projections]_ -_Market Segments: [Size and value of key market segments]_ -_Economic Impact: [Economic contribution and value creation]_ -_Source: [URL]_ - -### Market Dynamics and Growth - -[Market dynamics analysis with source citations] -_Growth Drivers: [Key factors driving market growth]_ -_Growth Barriers: [Factors limiting market expansion]_ -_Cyclical Patterns: [Industry seasonality and cycles]_ -_Market Maturity: [Life cycle stage and development phase]_ -_Source: [URL]_ - -### Market Structure and Segmentation - -[Market structure analysis with source citations] -_Primary Segments: [Key market segments and their characteristics]_ -_Sub-segment Analysis: [Detailed breakdown of market sub-segments]_ -_Geographic Distribution: [Regional market variations and concentrations]_ -_Vertical Integration: [Supply chain and value chain structure]_ -_Source: [URL]_ - -### Industry Trends and Evolution - -[Industry trends analysis with source citations] -_Emerging Trends: [Current industry developments and transformations]_ -_Historical Evolution: [Industry development over recent years]_ -_Technology Integration: [How technology is changing the industry]_ -_Future Outlook: [Projected industry developments and changes]_ -_Source: [URL]_ - -### Competitive Dynamics - -[Competitive dynamics analysis with source citations] -_Market Concentration: [Level of market consolidation and competition]_ -_Competitive Intensity: [Degree of competition and rivalry]_ -_Barriers to Entry: [Obstacles for new market entrants]_ -_Innovation Pressure: [Rate of innovation and change]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **industry analysis** for {{research_topic}}. - -**Key Industry Findings:** - -- Market size and valuation thoroughly analyzed -- Growth dynamics and market structure documented -- Industry trends and evolution patterns identified -- Competitive dynamics clearly mapped -- Multiple sources verified for critical insights - -**Ready to proceed to competitive landscape analysis?** -[C] Continue - Save this to document and proceed to competitive landscape - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2]` -- Load: `${CLAUDE_PLUGIN_ROOT}/skills/research/domain-steps/step-03-competitive-landscape.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Market size and valuation thoroughly analyzed -✅ Growth dynamics and market structure documented -✅ Industry trends and evolution patterns identified -✅ Competitive dynamics clearly mapped -✅ Multiple sources verified for critical insights -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (competitive landscape) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying on training data instead of web search for current facts -❌ Missing critical market size or growth data -❌ Incomplete market structure analysis -❌ Not identifying key industry trends -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to competitive landscape step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## INDUSTRY RESEARCH PROTOCOLS: - -- Research market research reports and industry analyses -- Use authoritative sources (market research firms, industry associations) -- Analyze market size, growth rates, and segmentation data -- Study industry trends and evolution patterns -- Search the web to verify facts -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## INDUSTRY ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative industry research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable industry insights - -## NEXT STEP: - -After user selects 'C', load `${CLAUDE_PLUGIN_ROOT}/skills/research/domain-steps/step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}. - -Remember: Always write research content to document immediately and search the web to verify facts! diff --git a/plugins/bmad/skills/research/domain-steps/step-03-competitive-landscape.md b/plugins/bmad/skills/research/domain-steps/step-03-competitive-landscape.md deleted file mode 100644 index fcf8296..0000000 --- a/plugins/bmad/skills/research/domain-steps/step-03-competitive-landscape.md +++ /dev/null @@ -1,238 +0,0 @@ -# Domain Research Step 3: Competitive Landscape - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A COMPETITIVE ANALYST, not content generator -- 💬 FOCUS on key players, market share, and competitive dynamics -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after competitive analysis content generation -- 📝 WRITE COMPETITIVE ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on key players, market share, and competitive dynamics -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct competitive landscape analysis focusing on key players, market share, and competitive dynamics. Search the web to verify and supplement current facts. - -## COMPETITIVE LANDSCAPE ANALYSIS SEQUENCE: - -### 1. Begin Competitive Landscape Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different competitive areas simultaneously and thoroughly. - -Start with competitive research approach: -"Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** to understand the competitive ecosystem. - -**Competitive Landscape Focus:** - -- Key players and market leaders -- Market share and competitive positioning -- Competitive strategies and differentiation -- Business models and value propositions -- Entry barriers and competitive dynamics - -**Let me search for current competitive insights.**" - -### 2. Parallel Competitive Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} key players market leaders" -Search the web: "{{research_topic}} market share competitive landscape" -Search the web: "{{research_topic}} competitive strategies differentiation" -Search the web: "{{research_topic}} entry barriers competitive dynamics" - -**Analysis approach:** - -- Look for recent competitive intelligence reports and market analyses -- Search for company websites, annual reports, and investor presentations -- Research market share data and competitive positioning -- Analyze competitive strategies and differentiation approaches -- Study entry barriers and competitive dynamics - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate competitive findings: - -**Research Coverage:** - -- Key players and market leaders analysis -- Market share and competitive positioning assessment -- Competitive strategies and differentiation mapping -- Entry barriers and competitive dynamics evaluation - -**Cross-Competitive Analysis:** -[Identify patterns connecting players, strategies, and market dynamics] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Competitive Landscape Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare competitive landscape analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Competitive Landscape - -### Key Players and Market Leaders - -[Key players analysis with source citations] -_Market Leaders: [Dominant players and their market positions]_ -_Major Competitors: [Significant competitors and their specialties]_ -_Emerging Players: [New entrants and innovative companies]_ -_Global vs Regional: [Geographic distribution of key players]_ -_Source: [URL]_ - -### Market Share and Competitive Positioning - -[Market share analysis with source citations] -_Market Share Distribution: [Current market share breakdown]_ -_Competitive Positioning: [How players position themselves in the market]_ -_Value Proposition Mapping: [Different value propositions across players]_ -_Customer Segments Served: [Different customer bases by competitor]_ -_Source: [URL]_ - -### Competitive Strategies and Differentiation - -[Competitive strategies analysis with source citations] -_Cost Leadership Strategies: [Players competing on price and efficiency]_ -_Differentiation Strategies: [Players competing on unique value]_ -_Focus/Niche Strategies: [Players targeting specific segments]_ -_Innovation Approaches: [How different players innovate]_ -_Source: [URL]_ - -### Business Models and Value Propositions - -[Business models analysis with source citations] -_Primary Business Models: [How competitors make money]_ -_Revenue Streams: [Different approaches to monetization]_ -_Value Chain Integration: [Vertical integration vs partnership models]_ -_Customer Relationship Models: [How competitors build customer loyalty]_ -_Source: [URL]_ - -### Competitive Dynamics and Entry Barriers - -[Competitive dynamics analysis with source citations] -_Barriers to Entry: [Obstacles facing new market entrants]_ -_Competitive Intensity: [Level of rivalry and competitive pressure]_ -_Market Consolidation Trends: [M&A activity and market concentration]_ -_Switching Costs: [Costs for customers to switch between providers]_ -_Source: [URL]_ - -### Ecosystem and Partnership Analysis - -[Ecosystem analysis with source citations] -_Supplier Relationships: [Key supplier partnerships and dependencies]_ -_Distribution Channels: [How competitors reach customers]_ -_Technology Partnerships: [Strategic technology alliances]_ -_Ecosystem Control: [Who controls key parts of the value chain]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **competitive landscape analysis** for {{research_topic}}. - -**Key Competitive Findings:** - -- Key players and market leaders thoroughly identified -- Market share and competitive positioning clearly mapped -- Competitive strategies and differentiation analyzed -- Business models and value propositions documented -- Competitive dynamics and entry barriers evaluated - -**Ready to proceed to regulatory focus analysis?** -[C] Continue - Save this to document and proceed to regulatory focus - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3]` -- Load: `${CLAUDE_PLUGIN_ROOT}/skills/research/domain-steps/step-04-regulatory-focus.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Key players and market leaders thoroughly identified -✅ Market share and competitive positioning clearly mapped -✅ Competitive strategies and differentiation analyzed -✅ Business models and value propositions documented -✅ Competitive dynamics and entry barriers evaluated -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (regulatory focus) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying on training data instead of web search for current facts -❌ Missing critical key players or market leaders -❌ Incomplete market share or positioning analysis -❌ Not identifying competitive strategies -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to regulatory focus step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## COMPETITIVE RESEARCH PROTOCOLS: - -- Research competitive intelligence reports and market analyses -- Use company websites, annual reports, and investor presentations -- Analyze market share data and competitive positioning -- Study competitive strategies and differentiation approaches -- Search the web to verify facts -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## COMPETITIVE ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative competitive intelligence sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable competitive insights - -## NEXT STEP: - -After user selects 'C', load `${CLAUDE_PLUGIN_ROOT}/skills/research/domain-steps/step-04-regulatory-focus.md` to analyze regulatory requirements, compliance frameworks, and legal considerations for {{research_topic}}. - -Remember: Always write research content to document immediately and search the web to verify facts! diff --git a/plugins/bmad/skills/research/domain-steps/step-04-regulatory-focus.md b/plugins/bmad/skills/research/domain-steps/step-04-regulatory-focus.md deleted file mode 100644 index 019d854..0000000 --- a/plugins/bmad/skills/research/domain-steps/step-04-regulatory-focus.md +++ /dev/null @@ -1,206 +0,0 @@ -# Domain Research Step 4: Regulatory Focus - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A REGULATORY ANALYST, not content generator -- 💬 FOCUS on compliance requirements and regulatory landscape -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after regulatory content generation -- 📝 WRITE REGULATORY ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on regulatory and compliance requirements for the domain -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct focused regulatory and compliance analysis with emphasis on requirements that impact {{research_topic}}. Search the web to verify and supplement current facts. - -## REGULATORY FOCUS SEQUENCE: - -### 1. Begin Regulatory Analysis - -Start with regulatory research approach: -"Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}**. - -**Regulatory Focus Areas:** - -- Specific regulations and compliance frameworks -- Industry standards and best practices -- Licensing and certification requirements -- Data protection and privacy regulations -- Environmental and safety requirements - -**Let me search for current regulatory requirements.**" - -### 2. Web Search for Specific Regulations - -Search for current regulatory information: -Search the web: "{{research_topic}} regulations compliance requirements" - -**Regulatory focus:** - -- Specific regulations applicable to the domain -- Compliance frameworks and standards -- Recent regulatory changes or updates -- Enforcement agencies and oversight bodies - -### 3. Web Search for Industry Standards - -Search for current industry standards: -Search the web: "{{research_topic}} standards best practices" - -**Standards focus:** - -- Industry-specific technical standards -- Best practices and guidelines -- Certification requirements -- Quality assurance frameworks - -### 4. Web Search for Data Privacy Requirements - -Search for current privacy regulations: -Search the web: "data privacy regulations {{research_topic}}" - -**Privacy focus:** - -- GDPR, CCPA, and other data protection laws -- Industry-specific privacy requirements -- Data governance and security standards -- User consent and data handling requirements - -### 5. Generate Regulatory Analysis Content - -Prepare regulatory content with source citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Regulatory Requirements - -### Applicable Regulations - -[Specific regulations analysis with source citations] -_Source: [URL]_ - -### Industry Standards and Best Practices - -[Industry standards analysis with source citations] -_Source: [URL]_ - -### Compliance Frameworks - -[Compliance frameworks analysis with source citations] -_Source: [URL]_ - -### Data Protection and Privacy - -[Privacy requirements analysis with source citations] -_Source: [URL]_ - -### Licensing and Certification - -[Licensing requirements analysis with source citations] -_Source: [URL]_ - -### Implementation Considerations - -[Practical implementation considerations with source citations] -_Source: [URL]_ - -### Risk Assessment - -[Regulatory and compliance risk assessment] -``` - -### 6. Present Analysis and Continue Option - -Show the generated regulatory analysis and present continue option: -"I've completed **regulatory requirements analysis** for {{research_topic}}. - -**Key Regulatory Findings:** - -- Specific regulations and frameworks identified -- Industry standards and best practices mapped -- Compliance requirements clearly documented -- Implementation considerations provided -- Risk assessment completed - -**Ready to proceed to technical trends?** -[C] Continue - Save this to the document and move to technical trends - -### 7. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]` -- Load: `${CLAUDE_PLUGIN_ROOT}/skills/research/domain-steps/step-05-technical-trends.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 5. No additional append needed. - -## SUCCESS METRICS: - -✅ Applicable regulations identified with current citations -✅ Industry standards and best practices documented -✅ Compliance frameworks clearly mapped -✅ Data protection requirements analyzed -✅ Implementation considerations provided -✅ [C] continue option presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Relying on training data instead of web search for current facts -❌ Missing critical regulatory requirements for the domain -❌ Not providing implementation considerations for compliance -❌ Not completing risk assessment for regulatory compliance -❌ Not presenting [C] continue option after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## REGULATORY RESEARCH PROTOCOLS: - -- Search for specific regulations by name and number -- Identify regulatory bodies and enforcement agencies -- Research recent regulatory changes and updates -- Map industry standards to regulatory requirements -- Consider regional and jurisdictional differences - -## SOURCE VERIFICATION: - -- Always cite regulatory agency websites -- Use official government and industry association sources -- Note effective dates and implementation timelines -- Present compliance requirement levels and obligations - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `${CLAUDE_PLUGIN_ROOT}/skills/research/domain-steps/step-05-technical-trends.md` to analyze technical trends and innovations in the domain. - -Remember: Search the web to verify regulatory facts and provide practical implementation considerations! diff --git a/plugins/bmad/skills/research/domain-steps/step-05-technical-trends.md b/plugins/bmad/skills/research/domain-steps/step-05-technical-trends.md deleted file mode 100644 index 85115dc..0000000 --- a/plugins/bmad/skills/research/domain-steps/step-05-technical-trends.md +++ /dev/null @@ -1,234 +0,0 @@ -# Domain Research Step 5: Technical Trends - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A TECHNOLOGY ANALYST, not content generator -- 💬 FOCUS on emerging technologies and innovation patterns -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after technical trends content generation -- 📝 WRITE TECHNICAL TRENDS ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on emerging technologies and innovation patterns in the domain -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct comprehensive technical trends analysis using current web data with emphasis on innovations and emerging technologies impacting {{research_topic}}. - -## TECHNICAL TRENDS SEQUENCE: - -### 1. Begin Technical Trends Analysis - -Start with technology research approach: -"Now I'll conduct **technical trends and emerging technologies** analysis for **{{research_topic}}** using current data. - -**Technical Trends Focus:** - -- Emerging technologies and innovations -- Digital transformation impacts -- Automation and efficiency improvements -- New business models enabled by technology -- Future technology projections and roadmaps - -**Let me search for current technology developments.**" - -### 2. Web Search for Emerging Technologies - -Search for current technology information: -Search the web: "{{research_topic}} emerging technologies innovations" - -**Technology focus:** - -- AI, machine learning, and automation impacts -- Digital transformation trends -- New technologies disrupting the industry -- Innovation patterns and breakthrough developments - -### 3. Web Search for Digital Transformation - -Search for current transformation trends: -Search the web: "{{research_topic}} digital transformation trends" - -**Transformation focus:** - -- Digital adoption trends and rates -- Business model evolution -- Customer experience innovations -- Operational efficiency improvements - -### 4. Web Search for Future Outlook - -Search for future projections: -Search the web: "{{research_topic}} future outlook trends" - -**Future focus:** - -- Technology roadmaps and projections -- Market evolution predictions -- Innovation pipelines and R&D trends -- Long-term industry transformation - -### 5. Generate Technical Trends Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare technical analysis with source citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Technical Trends and Innovation - -### Emerging Technologies - -[Emerging technologies analysis with source citations] -_Source: [URL]_ - -### Digital Transformation - -[Digital transformation analysis with source citations] -_Source: [URL]_ - -### Innovation Patterns - -[Innovation patterns analysis with source citations] -_Source: [URL]_ - -### Future Outlook - -[Future outlook and projections with source citations] -_Source: [URL]_ - -### Implementation Opportunities - -[Implementation opportunity analysis with source citations] -_Source: [URL]_ - -### Challenges and Risks - -[Challenges and risks assessment with source citations] -_Source: [URL]_ - -## Recommendations - -### Technology Adoption Strategy - -[Technology adoption recommendations] - -### Innovation Roadmap - -[Innovation roadmap suggestions] - -### Risk Mitigation - -[Risk mitigation strategies] -``` - -### 6. Present Analysis and Complete Option - -Show the generated technical analysis and present complete option: -"I've completed **technical trends and innovation analysis** for {{research_topic}}. - -**Technical Highlights:** - -- Emerging technologies and innovations identified -- Digital transformation trends mapped -- Future outlook and projections analyzed -- Implementation opportunities and challenges documented -- Practical recommendations provided - -**Technical Trends Research Completed:** - -- Emerging technologies and innovations identified -- Digital transformation trends mapped -- Future outlook and projections analyzed -- Implementation opportunities and challenges documented - -**Ready to proceed to research synthesis and recommendations?** -[C] Continue - Save this to document and proceed to synthesis - -### 7. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]` -- Load: `${CLAUDE_PLUGIN_ROOT}/skills/research/domain-steps/step-06-research-synthesis.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 5. No additional append needed. - -## SUCCESS METRICS: - -✅ Emerging technologies identified with current data -✅ Digital transformation trends clearly documented -✅ Future outlook and projections analyzed -✅ Implementation opportunities and challenges mapped -✅ Strategic recommendations provided -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (research synthesis) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts -❌ Missing critical emerging technologies in the domain -❌ Not providing practical implementation recommendations -❌ Not completing strategic recommendations -❌ Not presenting completion option for research workflow -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## TECHNICAL RESEARCH PROTOCOLS: - -- Search for cutting-edge technologies and innovations -- Identify disruption patterns and game-changers -- Research technology adoption timelines and barriers -- Consider regional technology variations -- Analyze competitive technological advantages - -## RESEARCH WORKFLOW COMPLETION: - -When 'C' is selected: - -- All domain research steps completed -- Comprehensive research document generated -- All sections appended with source citations -- Research workflow status updated -- Final recommendations provided to user - -## NEXT STEPS: - -Research workflow complete. User may: - -- Use the domain research to inform other workflows (PRD, architecture, etc.) -- Conduct additional research on specific topics if needed -- Move forward with product development based on research insights - -Congratulations on completing comprehensive domain research! 🎉 diff --git a/plugins/bmad/skills/research/domain-steps/step-06-research-synthesis.md b/plugins/bmad/skills/research/domain-steps/step-06-research-synthesis.md deleted file mode 100644 index 9e2261f..0000000 --- a/plugins/bmad/skills/research/domain-steps/step-06-research-synthesis.md +++ /dev/null @@ -1,444 +0,0 @@ -# Domain Research Step 6: Research Synthesis and Completion - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A DOMAIN RESEARCH STRATEGIST, not content generator -- 💬 FOCUS on comprehensive synthesis and authoritative conclusions -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] complete option after synthesis content generation -- 💾 ONLY save when user chooses C (Complete) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow -- 🚫 FORBIDDEN to complete workflow until C is selected -- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - comprehensive domain analysis -- **Research goals = "{{research_goals}}"** - achieved through exhaustive research -- All domain research sections have been completed (analysis, regulatory, technical) -- Web search capabilities with source verification are enabled -- This is the final synthesis step producing the complete research document - -## YOUR TASK: - -Produce a comprehensive, authoritative research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive domain research. - -## COMPREHENSIVE DOCUMENT SYNTHESIS: - -### 1. Document Structure Planning - -**Complete Research Document Structure:** - -```markdown -# [Compelling Title]: Comprehensive {{research_topic}} Research - -## Executive Summary - -[Brief compelling overview of key findings and implications] - -## Table of Contents - -- Research Introduction and Methodology -- Industry Overview and Market Dynamics -- Technology Trends and Innovation Landscape -- Regulatory Framework and Compliance Requirements -- Competitive Landscape and Key Players -- Strategic Insights and Recommendations -- Implementation Considerations and Risk Assessment -- Future Outlook and Strategic Opportunities -- Research Methodology and Source Documentation -- Appendices and Additional Resources -``` - -### 2. Generate Compelling Narrative Introduction - -**Introduction Requirements:** - -- Hook reader with compelling opening about {{research_topic}} -- Establish research significance and timeliness -- Outline comprehensive research methodology -- Preview key findings and strategic implications -- Set professional, authoritative tone - -**Web Search for Introduction Context:** -Search the web: "{{research_topic}} significance importance" - -### 3. Synthesize All Research Sections - -**Section-by-Section Integration:** - -- Combine industry analysis from step-02 -- Integrate regulatory focus from step-03 -- Incorporate technical trends from step-04 -- Add cross-sectional insights and connections -- Ensure comprehensive coverage with no gaps - -### 4. Generate Complete Document Content - -#### Final Document Structure: - -```markdown -# [Compelling Title]: Comprehensive {{research_topic}} Domain Research - -## Executive Summary - -[2-3 paragraph compelling summary of the most critical findings and strategic implications for {{research_topic}} based on comprehensive current research] - -**Key Findings:** - -- [Most significant market dynamics] -- [Critical regulatory considerations] -- [Important technology trends] -- [Strategic implications] - -**Strategic Recommendations:** - -- [Top 3-5 actionable recommendations based on research] - -## Table of Contents - -1. Research Introduction and Methodology -2. {{research_topic}} Industry Overview and Market Dynamics -3. Technology Landscape and Innovation Trends -4. Regulatory Framework and Compliance Requirements -5. Competitive Landscape and Ecosystem Analysis -6. Strategic Insights and Domain Opportunities -7. Implementation Considerations and Risk Assessment -8. Future Outlook and Strategic Planning -9. Research Methodology and Source Verification -10. Appendices and Additional Resources - -## 1. Research Introduction and Methodology - -### Research Significance - -[Compelling narrative about why {{research_topic}} research is critical right now] -_Why this research matters now: [Strategic importance with current context]_ -_Source: [URL]_ - -### Research Methodology - -[Comprehensive description of research approach including:] - -- **Research Scope**: [Comprehensive coverage areas] -- **Data Sources**: [Authoritative sources and verification approach] -- **Analysis Framework**: [Structured analysis methodology] -- **Time Period**: [current focus and historical context] -- **Geographic Coverage**: [Regional/global scope] - -### Research Goals and Objectives - -**Original Goals:** {{research_goals}} - -**Achieved Objectives:** - -- [Goal 1 achievement with supporting evidence] -- [Goal 2 achievement with supporting evidence] -- [Additional insights discovered during research] - -## 2. {{research_topic}} Industry Overview and Market Dynamics - -### Market Size and Growth Projections - -[Comprehensive market analysis synthesized from step-02 with current data] -_Market Size: [Current market valuation]_ -_Growth Rate: [CAGR and projections]_ -_Market Drivers: [Key growth factors]_ -_Source: [URL]_ - -### Industry Structure and Value Chain - -[Complete industry structure analysis] -_Value Chain Components: [Detailed breakdown]_ -_Industry Segments: [Market segmentation analysis]_ -_Economic Impact: [Industry economic significance]_ -_Source: [URL]_ - -## 3. Technology Landscape and Innovation Trends - -### Current Technology Adoption - -[Technology trends analysis from step-04 with current context] -_Emerging Technologies: [Key technologies affecting {{research_topic}}]_ -_Adoption Patterns: [Technology adoption rates and patterns]_ -_Innovation Drivers: [Factors driving technology change]_ -_Source: [URL]_ - -### Digital Transformation Impact - -[Comprehensive analysis of technology's impact on {{research_topic}}] -_Transformation Trends: [Major digital transformation patterns]_ -_Disruption Opportunities: [Technology-driven opportunities]_ -_Future Technology Outlook: [Emerging technologies and timelines]_ -_Source: [URL]_ - -## 4. Regulatory Framework and Compliance Requirements - -### Current Regulatory Landscape - -[Regulatory analysis from step-03 with current updates] -_Key Regulations: [Critical regulatory requirements]_ -_Compliance Standards: [Industry standards and best practices]_ -_Recent Changes: [current regulatory updates and implications]_ -_Source: [URL]_ - -### Risk and Compliance Considerations - -[Comprehensive risk assessment] -_Compliance Risks: [Major regulatory and compliance risks]_ -_Risk Mitigation Strategies: [Approaches to manage regulatory risks]_ -_Future Regulatory Trends: [Anticipated regulatory developments]_ -_Source: [URL]_ - -## 5. Competitive Landscape and Ecosystem Analysis - -### Market Positioning and Key Players - -[Competitive analysis with current market positioning] -_Market Leaders: [Dominant players and strategies]_ -_Emerging Competitors: [New entrants and innovative approaches]_ -_Competitive Dynamics: [Market competition patterns and trends]_ -_Source: [URL]_ - -### Ecosystem and Partnership Landscape - -[Complete ecosystem analysis] -_Ecosystem Players: [Key stakeholders and relationships]_ -_Partnership Opportunities: [Strategic collaboration potential]_ -_Supply Chain Dynamics: [Supply chain structure and risks]_ -_Source: [URL]_ - -## 6. Strategic Insights and Domain Opportunities - -### Cross-Domain Synthesis - -[Strategic insights from integrating all research sections] -_Market-Technology Convergence: [How technology and market forces interact]_ -_Regulatory-Strategic Alignment: [How regulatory environment shapes strategy]_ -_Competitive Positioning Opportunities: [Strategic advantages based on research]_ -_Source: [URL]_ - -### Strategic Opportunities - -[High-value opportunities identified through comprehensive research] -_Market Opportunities: [Specific market entry or expansion opportunities]_ -_Technology Opportunities: [Technology adoption or innovation opportunities]_ -_Partnership Opportunities: [Strategic collaboration and partnership potential]_ -_Source: [URL]_ - -## 7. Implementation Considerations and Risk Assessment - -### Implementation Framework - -[Practical implementation guidance based on research findings] -_Implementation Timeline: [Recommended phased approach]_ -_Resource Requirements: [Key resources and capabilities needed]_ -_Success Factors: [Critical success factors for implementation]_ -_Source: [URL]_ - -### Risk Management and Mitigation - -[Comprehensive risk assessment and mitigation strategies] -_Implementation Risks: [Major risks and mitigation approaches]_ -_Market Risks: [Market-related risks and contingency plans]_ -_Technology Risks: [Technology adoption and implementation risks]_ -_Source: [URL]_ - -## 8. Future Outlook and Strategic Planning - -### Future Trends and Projections - -[Forward-looking analysis based on comprehensive research] -_Near-term Outlook: [1-2 year projections and implications]_ -_Medium-term Trends: [3-5 year expected developments]_ -_Long-term Vision: [5+ year strategic outlook for {{research_topic}}]_ -_Source: [URL]_ - -### Strategic Recommendations - -[Comprehensive strategic recommendations] -_Immediate Actions: [Priority actions for next 6 months]_ -_Strategic Initiatives: [Key strategic initiatives for 1-2 years]_ -_Long-term Strategy: [Strategic positioning for 3+ years]_ -_Source: [URL]_ - -## 9. Research Methodology and Source Verification - -### Comprehensive Source Documentation - -[Complete documentation of all research sources] -_Primary Sources: [Key authoritative sources used]_ -_Secondary Sources: [Supporting research and analysis]_ -_Web Search Queries: [Complete list of search queries used]_ - -### Research Quality Assurance - -[Quality assurance and validation approach] -_Source Verification: [All factual claims verified with multiple sources]_ -_Confidence Levels: [Confidence assessments for uncertain data]_ -_Limitations: [Research limitations and areas for further investigation]_ -_Methodology Transparency: [Complete transparency about research approach]_ - -## 10. Appendices and Additional Resources - -### Detailed Data Tables - -[Comprehensive data tables supporting research findings] -_Market Data Tables: [Detailed market size, growth, and segmentation data]_ -_Technology Adoption Data: [Detailed technology adoption and trend data]_ -_Regulatory Reference Tables: [Complete regulatory requirements and compliance data]_ - -### Additional Resources - -[Valuable resources for continued research and implementation] -_Industry Associations: [Key industry organizations and resources]_ -_Research Organizations: [Authoritative research institutions and reports]_ -_Government Resources: [Regulatory agencies and official resources]_ -_Professional Networks: [Industry communities and knowledge sources]_ - ---- - -## Research Conclusion - -### Summary of Key Findings - -[Comprehensive summary of the most important research findings] - -### Strategic Impact Assessment - -[Assessment of strategic implications for {{research_topic}}] - -### Next Steps Recommendations - -[Specific next steps for leveraging this research] - ---- - -**Research Completion Date:** {{date}} -**Research Period:** Comprehensive analysis -**Document Length:** As needed for comprehensive coverage -**Source Verification:** All facts cited with sources -**Confidence Level:** High - based on multiple authoritative sources - -_This comprehensive research document serves as an authoritative reference on {{research_topic}} and provides strategic insights for informed decision-making._ -``` - -### 5. Present Complete Document and Final Option - -**Document Completion Presentation:** - -"I've completed the **comprehensive research document synthesis** for **{{research_topic}}**, producing an authoritative research document with: - -**Document Features:** - -- **Compelling Narrative Introduction**: Engaging opening that establishes research significance -- **Comprehensive Table of Contents**: Complete navigation structure for easy reference -- **Exhaustive Research Coverage**: All aspects of {{research_topic}} thoroughly analyzed -- **Executive Summary**: Key findings and strategic implications highlighted -- **Strategic Recommendations**: Actionable insights based on comprehensive research -- **Complete Source Citations**: Every factual claim verified with sources - -**Research Completeness:** - -- Industry analysis and market dynamics fully documented -- Technology trends and innovation landscape comprehensively covered -- Regulatory framework and compliance requirements detailed -- Competitive landscape and ecosystem analysis complete -- Strategic insights and implementation guidance provided - -**Document Standards Met:** - -- Exhaustive research with no critical gaps -- Professional structure and compelling narrative -- As long as needed for comprehensive coverage -- Multiple independent sources for all claims -- Proper citations throughout - -**Ready to complete this comprehensive research document?** -[C] Complete Research - Save final comprehensive document - -### 6. Handle Final Completion - -#### If 'C' (Complete Research): - -- **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section -- Append the complete document to the research file -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]` -- Complete the domain research workflow -- Provide final document delivery confirmation - -## APPEND TO DOCUMENT: - -When user selects 'C', append the complete comprehensive research document using the full structure above. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document. - -## SUCCESS METRICS: - -✅ Compelling narrative introduction with research significance -✅ Comprehensive table of contents with complete document structure -✅ Exhaustive research coverage across all domain aspects -✅ Executive summary with key findings and strategic implications -✅ Strategic recommendations grounded in comprehensive research -✅ Complete source verification with citations -✅ Professional document structure and compelling narrative -✅ [C] complete option presented and handled correctly -✅ Domain research workflow completed with comprehensive document - -## FAILURE MODES: - -❌ Not producing compelling narrative introduction -❌ Missing comprehensive table of contents -❌ Incomplete research coverage across domain aspects -❌ Not providing executive summary with key findings -❌ Missing strategic recommendations based on research -❌ Relying solely on training data without web verification for current facts -❌ Producing document without professional structure -❌ Not presenting completion option for final document - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## COMPREHENSIVE DOCUMENT STANDARDS: - -This step ensures the final research document: - -- Serves as an authoritative reference on {{research_topic}} -- Provides compelling narrative and professional structure -- Includes comprehensive coverage with no gaps -- Maintains rigorous source verification standards -- Delivers strategic insights and actionable recommendations -- Meets professional research document quality standards - -## DOMAIN RESEARCH WORKFLOW COMPLETION: - -When 'C' is selected: - -- All domain research steps completed (1-5) -- Comprehensive domain research document generated -- Professional document structure with intro, TOC, and summary -- All sections appended with source citations -- Domain research workflow status updated to complete -- Final comprehensive research document delivered to user - -## FINAL DELIVERABLE: - -Complete authoritative research document on {{research_topic}} that: - -- Establishes professional credibility through comprehensive research -- Provides strategic insights for informed decision-making -- Serves as reference document for continued use -- Maintains highest research quality standards - -Congratulations on completing comprehensive domain research! 🎉 diff --git a/plugins/bmad/skills/research/market-steps/step-02-customer-insights.md b/plugins/bmad/skills/research/market-steps/step-02-customer-insights.md deleted file mode 100644 index c6d7ea3..0000000 --- a/plugins/bmad/skills/research/market-steps/step-02-customer-insights.md +++ /dev/null @@ -1,200 +0,0 @@ -# Market Research Step 2: Customer Insights - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A CUSTOMER INSIGHTS ANALYST, not content generator -- 💬 FOCUS on customer behavior and needs analysis -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after customer insights content generation -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from step-01 are available -- Focus on customer behavior and needs analysis -- Web search capabilities with source verification are enabled -- May need to search for current customer behavior trends - -## YOUR TASK: - -Conduct comprehensive customer insights analysis with emphasis on behavior patterns and needs. - -## CUSTOMER INSIGHTS SEQUENCE: - -### 1. Begin Customer Insights Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer areas simultaneously and thoroughly - -Start with customer research approach: -"Now I'll conduct **customer insights analysis** to understand customer behavior and needs. - -**Customer Insights Focus:** - -- Customer behavior patterns and preferences -- Pain points and challenges -- Decision-making processes -- Customer journey mapping -- Customer satisfaction drivers -- Demographic and psychographic profiles - -**Let me search for current customer insights using parallel web searches for comprehensive coverage.**" - -### 2. Parallel Customer Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "[product/service/market] customer behavior patterns" -Search the web: "[product/service/market] customer pain points challenges" -Search the web: "[product/service/market] customer decision process" - -**Analysis approach:** - -- Look for customer behavior studies and surveys -- Search for customer experience and interaction patterns -- Research customer satisfaction methodologies -- Note generational and cultural customer variations -- Research customer pain points and frustrations -- Analyze decision-making processes and criteria - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate the customer insights: - -**Research Coverage:** - -- Customer behavior patterns and preferences -- Pain points and challenges -- Decision-making processes and journey mapping - -**Cross-Customer Analysis:** -[Identify patterns connecting behavior, pain points, and decisions] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Customer Insights Content - -Prepare customer analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Customer Insights - -### Customer Behavior Patterns - -[Customer behavior analysis with source citations] -_Source: [URL]_ - -### Pain Points and Challenges - -[Pain points analysis with source citations] -_Source: [URL]_ - -### Decision-Making Processes - -[Decision-making analysis with source citations] -_Source: [URL]_ - -### Customer Journey Mapping - -[Customer journey analysis with source citations] -_Source: [URL]_ - -### Customer Satisfaction Drivers - -[Satisfaction drivers analysis with source citations] -_Source: [URL]_ - -### Demographic Profiles - -[Demographic profiles analysis with source citations] -_Source: [URL]_ - -### Psychographic Profiles - -[Psychographic profiles analysis with source citations] -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -Show the generated customer insights and present continue option: -"I've completed the **customer insights analysis** for customer behavior and needs. - -**Key Customer Findings:** - -- Customer behavior patterns clearly identified -- Pain points and challenges thoroughly documented -- Decision-making processes mapped -- Customer journey insights captured -- Satisfaction and profile data analyzed - -**Ready to proceed to competitive analysis?** -[C] Continue - Save this to the document and proceed to competitive analysis - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- Append the final content to the research document -- Update frontmatter: `stepsCompleted: [1, 2]` -- Load: `./step-05-competitive-analysis.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the research document using the structure from step 4. - -## SUCCESS METRICS: - -✅ Customer behavior patterns identified with current citations -✅ Pain points and challenges clearly documented -✅ Decision-making processes thoroughly analyzed -✅ Customer journey insights captured and mapped -✅ Customer satisfaction drivers identified -✅ [C] continue option presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts - -❌ Missing critical customer behavior patterns -❌ Not identifying key pain points and challenges -❌ Incomplete customer journey mapping -❌ Not presenting [C] continue option after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## CUSTOMER RESEARCH PROTOCOLS: - -- Search for customer behavior studies and surveys -- Use market research firm and industry association sources -- Research customer experience and interaction patterns -- Note generational and cultural customer variations -- Research customer satisfaction methodologies - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `./step-05-competitive-analysis.md` to focus on competitive landscape analysis. - -Remember: Always emphasize current customer data and rigorous source verification! diff --git a/plugins/bmad/skills/research/workflow-domain-research.md b/plugins/bmad/skills/research/workflow-domain-research.md deleted file mode 100644 index e3f0236..0000000 --- a/plugins/bmad/skills/research/workflow-domain-research.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -name: domain-research -description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"' ---- - -# Domain Research Workflow - -**Goal:** Conduct comprehensive domain/industry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations. - -**Your Role:** You are a domain research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction. - -## PREREQUISITE - -**⛔ Web search required.** If unavailable, abort and tell the user. - -## CONFIGURATION - -Load config from `.claude/bmad.local.md` and resolve: -- `project_name`, `output_folder`, `planning_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as a system-generated value - -## QUICK TOPIC DISCOVERY - -"Welcome {{user_name}}! Let's get started with your **domain/industry research**. - -**What domain, industry, or sector do you want to research?** - -For example: -- 'The healthcare technology industry' -- 'Sustainable packaging regulations in Europe' -- 'Construction and building materials sector' -- 'Or any other domain you have in mind...'" - -### Topic Clarification - -Based on the user's topic, briefly clarify: -1. **Core Domain**: "What specific aspect of [domain] are you most interested in?" -2. **Research Goals**: "What do you hope to achieve with this research?" -3. **Scope**: "Should we focus broadly or dive deep into specific aspects?" - -## ROUTE TO DOMAIN RESEARCH STEPS - -After gathering the topic and goals: - -1. Set `research_type = "domain"` -2. Set `research_topic = [discovered topic from discussion]` -3. Set `research_goals = [discovered goals from discussion]` -4. Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents -5. Load: `./domain-steps/step-01-init.md` with topic context - -**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for domain research. - -**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`** diff --git a/scripts/lib/checks/content.ts b/scripts/lib/checks/content.ts index 266c677..f105db0 100644 --- a/scripts/lib/checks/content.ts +++ b/scripts/lib/checks/content.ts @@ -26,21 +26,31 @@ interface ContentPair { pluginDir: string; label: string; source: UpstreamSource; + /** All upstream dirs that map to this plugin dir (for overlapping skills). */ + allUpstreamDirs?: string[]; } /** * Get all workflow→skill pairs across all enabled sources (only existing plugin dirs). * When multiple sources map to the same plugin skill dir, the last source wins - * (matches sync order: later sources overwrite earlier content). + * for content comparison (matches sync order). All upstream dirs for a plugin dir + * are tracked so extra-file checks can consult all sources. */ async function getAllPairs(): Promise { + // Track all upstream dirs per plugin dir (for multi-source overlap checking) + const allUpstreamDirs = new Map(); const byPluginDir = new Map(); + for (const source of getEnabledSources()) { const upstreamRoot = join(ROOT, '.upstream', source.localPath); const entries = await getWorkflowEntries(source, upstreamRoot); for (const entry of entries) { if (await exists(entry.pluginSkillDir)) { + const dirs = allUpstreamDirs.get(entry.pluginSkillDir) ?? []; + dirs.push(entry.upstreamDir); + allUpstreamDirs.set(entry.pluginSkillDir, dirs); + byPluginDir.set(entry.pluginSkillDir, { upstreamDir: entry.upstreamDir, pluginDir: entry.pluginSkillDir, @@ -50,6 +60,12 @@ async function getAllPairs(): Promise { } } } + + // Attach all upstream dirs to each pair + for (const pair of byPluginDir.values()) { + pair.allUpstreamDirs = allUpstreamDirs.get(pair.pluginDir) ?? []; + } + return [...byPluginDir.values()]; } @@ -101,21 +117,38 @@ async function compareUpstreamFiles( return { checked, drifted }; } -/** Check for extra files in plugin that don't exist upstream. */ -function checkExtraPluginFiles( +/** Check for extra files in plugin that don't exist upstream. + * @param primaryUpstreamDir - the upstream dir used for content comparison + * @param allUpstreamDirs - all upstream dirs that map to this plugin dir + */ +async function checkExtraPluginFiles( label: string, skillName: string, pluginFiles: string[], upstreamFiles: string[], source: UpstreamSource, -): void { + primaryUpstreamDir: string, + allUpstreamDirs: string[], +): Promise { const pluginOnlyData = source.pluginOnlyData ?? new Set(); const sharedTargets = source.sharedFileTargets ?? {}; + // Build combined upstream file set from all sources that map to this dir + const combinedUpstream = new Set(upstreamFiles); + for (const dir of allUpstreamDirs) { + if (dir === primaryUpstreamDir) continue; // Already in upstreamFiles + if (await exists(dir)) { + const files = await listFilesRecursive(dir); + for (const f of files) combinedUpstream.add(f); + } + } + for (const relPath of pluginFiles) { const fileName = relPath.split('/').at(-1) ?? relPath; if (shouldSkipContentFile(source, fileName)) continue; - if (upstreamFiles.includes(relPath)) continue; + // Skip SKILL.md — always generated or synced separately + if (fileName === 'SKILL.md') continue; + if (combinedUpstream.has(relPath)) continue; const qualifiedPath = `${skillName}/${relPath}`; if (pluginOnlyData.has(qualifiedPath)) { @@ -211,7 +244,13 @@ export async function checkContent(): Promise { let checkedCount = 0; let driftCount = 0; - for (const { upstreamDir, pluginDir, label, source } of pairs) { + for (const { + upstreamDir, + pluginDir, + label, + source, + allUpstreamDirs, + } of pairs) { const upstreamFiles = await listFilesRecursive(upstreamDir); const pluginFiles = await listFilesRecursive(pluginDir); const pluginFileSet = new Set(pluginFiles); @@ -229,7 +268,15 @@ export async function checkContent(): Promise { driftCount += drifted; const skillName = pluginDir.split('/').at(-1) ?? pluginDir; - checkExtraPluginFiles(label, skillName, pluginFiles, upstreamFiles, source); + await checkExtraPluginFiles( + label, + skillName, + pluginFiles, + upstreamFiles, + source, + upstreamDir, + allUpstreamDirs ?? [], + ); } if (driftCount === 0) { diff --git a/scripts/lib/checks/workflows.ts b/scripts/lib/checks/workflows.ts index 9840c52..4afd51c 100644 --- a/scripts/lib/checks/workflows.ts +++ b/scripts/lib/checks/workflows.ts @@ -5,11 +5,11 @@ * - Plugin.json manifest commands */ -import { readdir } from 'node:fs/promises'; +import { exists, readdir } from 'node:fs/promises'; import { join } from 'node:path'; import { PLUGIN, PLUGIN_JSON_PATH, ROOT } from '../config.ts'; import { fail, pass, section, warn } from '../output.ts'; -import { getEnabledSources } from '../upstream-sources.ts'; +import { getCoreSource, getEnabledSources } from '../upstream-sources.ts'; import { getWorkflowEntries } from '../workflow-iterator.ts'; export interface SkillSets { @@ -18,7 +18,7 @@ export interface SkillSets { manifest: Set; } -/** Collect upstream workflow names from all enabled sources. */ +/** Collect upstream workflow names from all enabled sources + core skills. */ async function getUpstreamWorkflows(): Promise> { const names = new Set(); @@ -30,6 +30,17 @@ async function getUpstreamWorkflows(): Promise> { } } + // Core skills synced via syncCoreExtras (src/core/skills/) + const coreSource = getCoreSource(); + const coreRoot = join(ROOT, '.upstream', coreSource.localPath); + const coreSkillsDir = join(coreRoot, 'src/core/skills'); + if (await exists(coreSkillsDir)) { + const entries = await readdir(coreSkillsDir, { withFileTypes: true }); + for (const entry of entries) { + if (entry.isDirectory()) names.add(entry.name); + } + } + return names; }