create-byan-agent 2.1.0 → 2.1.1

package/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md

@@ -1,162 +0,0 @@
----
-name: 'step-06-complete'
-description: 'Complete the product brief workflow, update status files, and suggest next steps for the project'
-
-# File References
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
----
-
-# Step 6: Product Brief Completion
-
-## STEP GOAL:
-
-Complete the product brief workflow, update status files, and provide guidance on logical next steps for continued product development.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a product-focused Business Analyst facilitator
-- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
-- ✅ Maintain collaborative completion tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on completion, next steps, and project guidance
-- 🚫 FORBIDDEN to generate new content for the product brief
-- 💬 Approach: Systematic completion with quality validation and next step recommendations
-- 📋 FINALIZE document and update workflow status appropriately
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 💾 Update the main workflow status file with completion information
-- 📖 Suggest potential next workflow steps for the user
-- 🚫 DO NOT load additional steps after this one (this is final)
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Complete product brief document from all previous steps, workflow frontmatter shows all completed steps
-- Focus: Completion validation, status updates, and next step guidance
-- Limits: No new content generation, only completion and wrap-up activities
-- Dependencies: All previous steps must be completed with content saved to document
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Announce Workflow Completion
-
-**Completion Announcement:**
-"🎉 **Product Brief Complete, {{user_name}}!**
-
-I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}.
-
-**What we've accomplished:**
-
-- ✅ Executive Summary with clear vision and problem statement
-- ✅ Core Vision with solution definition and unique differentiators
-- ✅ Target Users with rich personas and user journeys
-- ✅ Success Metrics with measurable outcomes and business objectives
-- ✅ MVP Scope with focused feature set and clear boundaries
-- ✅ Future Vision that inspires while maintaining current focus
-
-**The complete Product Brief is now available at:** `{outputFile}`
-
-This brief serves as the foundation for all subsequent product development activities and strategic decisions."
-
-### 2. Document Quality Check
-
-**Completeness Validation:**
-Perform final validation of the product brief:
-
-- Does the executive summary clearly communicate the vision and problem?
-- Are target users well-defined with compelling personas?
-- Do success metrics connect user value to business objectives?
-- Is MVP scope focused and realistic?
-- Does the brief provide clear direction for next steps?
-
-**Consistency Validation:**
-
-- Do all sections align with the core problem statement?
-- Is user value consistently emphasized throughout?
-- Are success criteria traceable to user needs and business goals?
-- Does MVP scope align with the problem and solution?
-
-### 3. Suggest Next Steps
-
-**Recommended Next Workflow:**
-Provide guidance on logical next workflows:
-
-1. `create-prd` - Create detailed Product Requirements Document
-   - Brief provides foundation for detailed requirements
-   - User personas inform journey mapping
-   - Success metrics become specific acceptance criteria
-   - MVP scope becomes detailed feature specifications
-
-**Other Potential Next Steps:**
-
-1. `create-ux-design` - UX research and design (can run parallel with PRD)
-2. `domain-research` - Deep market or domain research (if needed)
-
-**Strategic Considerations:**
-
-- The PRD workflow builds directly on this brief for detailed planning
-- Consider team capacity and immediate priorities
-- Use brief to validate concept before committing to detailed work
-- Brief can guide early technical feasibility discussions
-
-### 4. Congrats to the user
-
-"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**"
-
-Recap that the brief captures everything needed to guide subsequent product development:
-
-- Clear vision and problem definition
-- Deep understanding of target users
-- Measurable success criteria
-- Focused MVP scope with realistic boundaries
-- Inspiring long-term vision
-
-### 5. Suggest next steps
-
-Product Brief complete. Read fully and follow: `_bmad/core/tasks/bmad-help.md` with argument `Validate PRD`.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Product brief contains all essential sections with collaborative content
-- All collaborative content properly saved to document with proper frontmatter
-- Workflow status file updated with completion information and timestamp
-- Clear next step guidance provided to user with specific workflow recommendations
-- Document quality validation completed with completeness and consistency checks
-- User acknowledges completion and understands next available options
-- Workflow properly marked as complete in status tracking
-
-### ❌ SYSTEM FAILURE:
-
-- Not updating workflow status file with completion information
-- Missing clear next step guidance for user
-- Not confirming document completeness with user
-- Workflow not properly marked as complete in status tracking
-- User unclear about what happens next or available options
-- Document quality issues not identified or addressed
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
-
-## FINAL WORKFLOW COMPLETION
-
-This product brief is now complete and serves as the strategic foundation for the entire product lifecycle. All subsequent design, architecture, and development work should trace back to the vision, user needs, and success criteria documented in this brief.
-
-**Congratulations on completing the Product Brief for {{project_name}}!** 🎉

package/_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md

@@ -1,58 +0,0 @@
----
-name: create-product-brief
-description: Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
-web_bundle: true
----
-
-# Product Brief Workflow
-
-**Goal:** Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also a product-focused Business Analyst collaborating with an expert peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision. Work together as equals.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** for disciplined execution:
-
-### Core Principles
-
-- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
-- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
-- **Append-Only Building**: Build documents by appending content as directed to the output file
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, read fully and follow the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Configuration Loading
-
-Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`
-
-### 2. First Step EXECUTION
-
-Read fully and follow: `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md` to begin the workflow.

package/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md

@@ -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: `./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 `./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!

package/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md

@@ -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: `./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 `./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!