Brian Madison 7eb52520fa Major Enhancements:
- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
  - Default installation location changed to .bmad (hidden directory) for cleaner project root organization

    Web Bundle Improvements:

    - All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
    - Advanced elicitation capabilities integrated into standalone agents
    - All bundles enhanced with party mode agent manifests
    - Added default-party.csv files to bmm, bmgd, and cis module teams
    - The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
    - New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)

    Phase 4 Workflow Updates (In Progress):

    - Initiated shift to separate phase 4 implementation artifacts from documentation
        - Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
        - Installer questions and configuration added for artifact path selection
        - Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates

    Additional Changes:

    - New agent and action command header models for standardization
    - Enhanced web-bundle-activation-steps fragment
    - Updated web-bundler.js to support new structure
    - VS Code settings updated for new .bmad directory
    - Party mode instructions and workflow enhanced for better orchestration

   IDE Installer Updates:

    - Show version number of installer in cli
    - improved Installer UX
    - Gemini TOML Improved to have clear loading instructions with @ commands
    - All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
2025-11-09 17:39:05 -06:00

6.1 KiB

Research Workflow Router Instructions

The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml You MUST have already loaded and processed: {installed_path}/workflow.yaml Communicate in {communication_language}, generate documents in {document_output_language} Web research is ENABLED - always use current {{current_year}} data

🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨 NEVER present information without a verified source - if you cannot find a source, say "I could not find reliable data on this" ALWAYS cite sources with URLs when presenting data, statistics, or factual claims REQUIRE at least 2 independent sources for critical claims (market size, growth rates, competitive data) When sources conflict, PRESENT BOTH views and note the discrepancy - do NOT pick one arbitrarily Flag any data you are uncertain about with confidence levels: [High Confidence], [Medium Confidence], [Low Confidence - verify] Distinguish clearly between: FACTS (from sources), ANALYSIS (your interpretation), and SPECULATION (educated guesses) When using WebSearch results, ALWAYS extract and include the source URL for every claim

This is a ROUTER that directs to specialized research instruction sets

Check if {output_folder}/bmm-workflow-status.yaml exists No workflow status file found. Research is optional - you can continue without status tracking. Set standalone_mode = true Load the FULL file: {output_folder}/bmm-workflow-status.yaml Parse workflow_status section Check status of "research" workflow Get project_level from YAML metadata Find first non-completed workflow (next expected workflow) Pass status context to loaded instruction set for final update ⚠️ Research already completed: {{research status}} Re-running will create a new research report. Continue? (y/n) Exiting. Use workflow-status to see your next step. Exit workflow ⚠️ Next expected workflow: {{next_workflow}}. Research is out of sequence. Note: Research can provide valuable insights at any project stage. Continue with Research anyway? (y/n) Exiting. Run {{next_workflow}} instead. Exit workflow

Set standalone_mode = false

Welcome {user_name} warmly. Position yourself as their research partner who uses live {{current_year}} web data. Ask what they're looking to understand or research.

Listen and collaboratively identify the research type based on what they describe:

  • Market/Business questions → Market Research
  • Competitor questions → Competitive Intelligence
  • Customer questions → User Research
  • Technology questions → Technical Research
  • Industry questions → Domain Research
  • Creating research prompts for AI platforms → Deep Research Prompt Generator

Confirm your understanding of what type would be most helpful and what it will produce.

Capture {{research_type}} and {{research_mode}}

research_type_discovery

Based on user selection, load the appropriate instruction set

Set research_mode = "market" LOAD: {installed_path}/instructions-market.md Continue with market research workflow Set research_mode = "deep-prompt" LOAD: {installed_path}/instructions-deep-prompt.md Continue with deep research prompt generation Set research_mode = "technical" LOAD: {installed_path}/instructions-technical.md Continue with technical research workflow Set research_mode = "competitive" This will use market research workflow with competitive focus LOAD: {installed_path}/instructions-market.md Pass mode="competitive" to focus on competitive intelligence Set research_mode = "user" This will use market research workflow with user research focus LOAD: {installed_path}/instructions-market.md Pass mode="user" to focus on customer insights Set research_mode = "domain" This will use market research workflow with domain focus LOAD: {installed_path}/instructions-market.md Pass mode="domain" to focus on industry/domain analysis

The loaded instruction set will continue from here with full context of the {research_type}