workflows tasks and tools can be configured wether they are able to be run standalone from agents with ide commands

src/core/workflows/brainstorming/workflow.yaml

@@ -27,6 +27,8 @@ brain_techniques: "{installed_path}/brain-methods.csv"
 # Output configuration
 default_output_file: "{output_folder}/brainstorming-session-results-{{date}}.md"
 
+standalone: true
+
 web_bundle:
   name: "brainstorming"
   description: "Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions."

src/modules/bmb/workflows/audit-workflow/workflow.yaml

@@ -19,5 +19,7 @@ validation: "{installed_path}/checklist.md"
 # Output configuration
 default_output_file: "{output_folder}/audit-report-{{workflow_name}}-{{date}}.md"
 
+standalone: true
+
 # Web bundle configuration
 web_bundle: false # BMB workflows run locally in BMAD-METHOD project

src/modules/bmb/workflows/convert-legacy/workflow.yaml

@@ -29,4 +29,6 @@ sub_workflows:
   - create_workflow: "{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml"
   - create_module: "{project-root}/bmad/bmb/workflows/create-module/workflow.yaml"
 
+standalone: true
+
 web_bundle: false

src/modules/bmb/workflows/create-agent/workflow.yaml

@@ -34,6 +34,8 @@ standalone_output_file: "{custom_agent_location}/{{agent_filename}}.agent.yaml"
 # Optional user override file (auto-created by installer if missing)
 config_output_file: "{project-root}/bmad/_cfg/agents/{{target_module}}-{{agent_filename}}.customize.yaml"
 
+standalone: true
+
 web_bundle:
   name: "create-agent"
   description: "Interactive workflow to build BMAD Core compliant agents (simple, expert, or module types) with optional brainstorming for agent ideas, proper persona development, activation rules, and command structure"

src/modules/bmb/workflows/create-module/workflow.yaml

@@ -38,5 +38,7 @@ validation: "{installed_path}/checklist.md"
 # Save to custom_module_location/{{module_code}}
 installer_output_folder: "{custom_module_location}/{{module_code}}"
 
+standalone: true
+
 # Web bundle configuration
 web_bundle: false # BMB workflows run locally in BMAD-METHOD project

src/modules/bmb/workflows/create-workflow/workflow.yaml

@@ -36,5 +36,7 @@ workflow_template_path: "{installed_path}/workflow-template"
 module_output_folder: "{project-root}/bmad/{{target_module}}/workflows/{{workflow_name}}"
 standalone_output_folder: "{custom_workflow_location}/{{workflow_name}}"
 
+standalone: true
+
 # Web bundle configuration
 web_bundle: false # BMB workflows run locally in BMAD-METHOD project

src/modules/bmb/workflows/edit-workflow/workflow.yaml

@@ -23,5 +23,7 @@ template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 
+standalone: true
+
 # Web bundle configuration
 web_bundle: false # BMB workflows run locally in BMAD-METHOD project

src/modules/bmb/workflows/module-brief/workflow.yaml

@@ -25,5 +25,7 @@ validation: "{installed_path}/checklist.md"
 # Output configuration
 default_output_file: "{output_folder}/module-brief-{{module_code}}-{{date}}.md"
 
+standalone: true
+
 # Web bundle configuration
 web_bundle: false # BMB workflows run locally in BMAD-METHOD project

src/modules/bmb/workflows/redoc/workflow.yaml

@@ -28,5 +28,7 @@ validation: "{installed_path}/checklist.md"
 # Configuration
 autonomous: true # Runs without user checkpoints unless clarification needed
 
+standalone: true
+
 # Web bundle configuration
 web_bundle: false # BMB workflows run locally in BMAD-METHOD project

src/modules/bmm/tasks/daily-standup.xml

@@ -3,12 +3,12 @@
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
     <i>DO NOT skip steps or change the sequence</i>
     <i>HALT immediately when halt-conditions are met</i>
-    <i>Each andlt;actionandgt; within andlt;stepandgt; is a REQUIRED action to complete that step</i>
+    <i>Each action tag within a step tag is a REQUIRED action to complete that step</i>
     <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
   </llm>
   <flow>
     <step n="1" title="Project Context Discovery">
-      <action>Check for stories folder at {project-root}{output_folder}/stories/ directory</action>
+      <action>Check for stories folder at {project-root}{output_folder}/stories/</action>
       <action>Find current story by identifying highest numbered story file</action>
       <action>Read story status (In Progress, Ready for Review, etc.)</action>
       <action>Extract agent notes from Dev Agent Record, TEA Results, PO Notes sections</action>

src/modules/bmm/workflows/1-analysis/brainstorm-game/workflow.yaml

@@ -24,6 +24,8 @@ game_brain_methods: "{installed_path}/game-brain-methods.csv"
 # CORE brainstorming workflow to invoke
 core_brainstorming: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
 
+standalone: true
+
 web_bundle:
   name: "brainstorm-game"
   description: "Facilitate game brainstorming sessions by orchestrating the CIS brainstorming workflow with game-specific context, guidance, and additional game design techniques."

src/modules/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml

@@ -23,6 +23,8 @@ project_context: "{installed_path}/project-context.md"
 # CORE brainstorming workflow to invoke
 core_brainstorming: "{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
 
+standalone: true
+
 web_bundle:
   name: "brainstorm-project"
   description: "Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance."

src/modules/bmm/workflows/1-analysis/document-project/workflow.yaml

@@ -35,3 +35,7 @@ recommended_inputs:
 # Output configuration - Multiple files generated in output folder
 # Primary output: {output_folder}/index.md
 # Additional files generated by sub-workflows based on project structure
+
+standalone: true
+
+web_bundle: false # BMM workflows run locally in BMAD-METHOD project

src/modules/bmm/workflows/1-analysis/game-brief/workflow.yaml

@@ -29,8 +29,7 @@ validation: "{installed_path}/checklist.md"
 # Output configuration
 default_output_file: "{output_folder}/game-brief-{{game_name}}-{{date}}.md"
 
-# Workflow settings
-autonomous: false # This is an interactive workflow requiring user collaboration
+standalone: true
 
 web_bundle:
   name: "game-brief"

src/modules/bmm/workflows/1-analysis/product-brief/workflow.yaml

@@ -28,8 +28,7 @@ validation: "{installed_path}/checklist.md"
 # Output configuration
 default_output_file: "{output_folder}/product-brief-{{project_name}}-{{date}}.md"
 
-# Workflow settings
-autonomous: false # This is an interactive workflow requiring user collaboration
+standalone: true
 
 web_bundle:
   name: "product-brief"

src/modules/bmm/workflows/1-analysis/research/workflow.yaml

@@ -30,6 +30,8 @@ template_technical: "{installed_path}/template-technical.md"
 # Output configuration (dynamic based on research type selected in router)
 default_output_file: "{output_folder}/research-{{research_type}}-{{date}}.md"
 
+standalone: true
+
 web_bundle:
   name: "research"
   description: "Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis"

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml

@@ -39,17 +39,4 @@ default_output_file: "{output_folder}/ux-design-specification.md"
 color_themes_html: "{output_folder}/ux-color-themes.html"
 design_directions_html: "{output_folder}/ux-design-directions.html"
 
-# Workflow metadata
-version: "1.0.0"
-paradigm: "visual-collaboration-driven"
-execution_time: "45-120 minutes depending on project complexity and user engagement"
-features:
-  - "Design system discovery and selection"
-  - "Live HTML color theme visualization"
-  - "6-8 design direction mockup generation"
-  - "Adaptive facilitation by skill level"
-  - "Novel UX pattern design for unique concepts"
-  - "Progressive document building (saves after each step)"
-  - "Visual decision-making with actual mockups"
-  - "WebSearch for current design systems and trends"
-  - "Serves as input to follow-up workflows (wireframes, Figma, prototypes, architecture)"
+standalone: true

src/modules/bmm/workflows/2-plan-workflows/gdd/workflow.yaml

@@ -30,6 +30,8 @@ recommended_inputs:
   - narrative_design: "{output_folder}/narrative-design.md"
   - market_research: "{output_folder}/market-research.md"
 
+standalone: true
+
 web_bundle:
   name: "gdd"
   description: "Game Design Document workflow for all game project levels - from small prototypes to full AAA games. Generates comprehensive GDD with game mechanics, systems, progression, and implementation guidance."

src/modules/bmm/workflows/2-plan-workflows/narrative/workflow.yaml

@@ -26,6 +26,8 @@ recommended_inputs:
   - gdd: "{output_folder}/GDD.md"
   - product_brief: "{output_folder}/product-brief.md"
 
+standalone: true
+
 web_bundle:
   name: "narrative"
   description: "Narrative design workflow for story-driven games and applications. Creates comprehensive narrative documentation including story structure, character arcs, dialogue systems, and narrative implementation guidance."

src/modules/bmm/workflows/2-plan-workflows/prd/workflow.yaml

@@ -33,6 +33,8 @@ recommended_inputs:
   - product_brief: "{output_folder}/product-brief.md"
   - market_research: "{output_folder}/market-research.md"
 
+standalone: true
+
 web_bundle:
   name: "prd"
   description: "Unified PRD workflow for project levels 2-4. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Level 0-1 use tech-spec workflow."

src/modules/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml

@@ -36,6 +36,8 @@ recommended_inputs:
   - bug_report: "Bug description or issue ticket"
   - feature_request: "Brief feature description"
 
+standalone: true
+
 web_bundle:
   name: "tech-spec-sm"
   description: "Technical specification workflow for Level 0-1 projects. Creates focused tech spec with story generation. Level 0: tech-spec + user story. Level 1: tech-spec + epic/stories."

src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml

@@ -50,3 +50,5 @@ features:
   - "Novel pattern design for unique concepts"
   - "Intelligent pattern identification - LLM figures out what patterns matter"
   - "Implementation patterns for agent consistency"
+
+standalone: true

src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml

@@ -34,3 +34,7 @@ recommended_inputs:
 
 # Validation criteria data
 validation_criteria: "{installed_path}/validation-criteria.yaml"
+
+standalone: true
+
+web_bundle: false

src/modules/bmm/workflows/4-implementation/correct-course/workflow.yaml

@@ -40,4 +40,6 @@ execution_modes:
   - incremental: "Recommended - Refine each edit with user collaboration"
   - batch: "Present all changes at once for review"
 
+standalone: true
+
 web_bundle: false

src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml

@@ -45,4 +45,6 @@ recommended_inputs:
   - prd: "PRD document"
   - architecture: "Architecture (optional)"
 
+standalone: true
+
 web_bundle: false

src/modules/bmm/workflows/4-implementation/dev-story/workflow.yaml

@@ -23,4 +23,6 @@ installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/dev-story"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 
+standalone: true
+
 web_bundle: false

src/modules/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml

@@ -29,4 +29,6 @@ validation: "{installed_path}/checklist.md"
 # Output configuration
 default_output_file: "{output_folder}/tech-spec-epic-{{epic_id}}.md"
 
+standalone: true
+
 web_bundle: false

src/modules/bmm/workflows/4-implementation/retrospective/workflow.yaml

@@ -40,4 +40,6 @@ validation_required:
   - technical_health: "Is codebase in stable, maintainable state?"
   - blocker_resolution: "Any unresolved blockers that will impact next epic?"
 
+standalone: true
+
 web_bundle: false

src/modules/bmm/workflows/4-implementation/review-story/workflow.yaml

@@ -51,4 +51,6 @@ recommended_inputs:
   - tech_spec: "Epic technical specification document (auto-discovered)"
   - story_context_file: "Story context file (.context.xml) (auto-discovered)"
 
+standalone: true
+
 web_bundle: false

src/modules/bmm/workflows/4-implementation/sprint-planning/workflow.yaml

@@ -36,4 +36,6 @@ variables:
 # Output configuration
 default_output_file: "{status_file}"
 
+standalone: true
+
 web_bundle: false

src/modules/bmm/workflows/4-implementation/story-context/workflow.yaml

@@ -27,4 +27,6 @@ variables:
 # Uses story_key from sprint-status.yaml (e.g., "1-2-user-authentication")
 default_output_file: "{story_dir}/{{story_key}}.context.xml"
 
+standalone: true
+
 web_bundle: false

src/modules/bmm/workflows/4-implementation/story-done/workflow.yaml

@@ -1,6 +1,6 @@
 # Story Done Workflow (DEV Agent)
 name: story-done
-description: "Marks a story as done (DoD complete) and moves it from IN PROGRESS → DONE in the status file. Advances the story queue. Simple status-update workflow with no searching required."
+description: "Marks a story as done (DoD complete) and moves it from its current status → DONE in the status file. Advances the story queue. Simple status-update workflow with no searching required."
 author: "BMad"
 
 # Critical variables from config
@@ -22,4 +22,6 @@ variables:
 # Output configuration - no output file, just status updates
 default_output_file: ""
 
+standalone: true
+
 web_bundle: false

src/modules/bmm/workflows/4-implementation/story-ready/workflow.yaml

@@ -22,4 +22,6 @@ variables:
 # Output configuration - no output file, just status updates
 default_output_file: ""
 
+standalone: true
+
 web_bundle: false

src/modules/bmm/workflows/4-implementation/temp-testing-files/sample-sprint-status-file.yaml

@@ -1,93 +0,0 @@
-# generated: 2025-10-21
-# project: todo1
-# project_key: todo1
-# tracking_system: file-system
-# story_location: {project-root}/docs/stories
-
-# STATUS DEFINITIONS:
-# ==================
-# Epic Status:
-#   - backlog: Epic exists in epic file but not contexted
-#   - contexted: Epic tech context created (required before drafting stories)
-#
-# Story Status:
-#   - backlog: Story only exists in epic file
-#   - drafted: Story file created in stories folder
-#   - ready-for-dev: Draft approved and story context created
-#   - in-progress: Developer actively working on implementation
-#   - review: Under SM review (via review-story workflow)
-#   - done: Story completed
-#
-# Retrospective Status:
-#   - optional: Can be completed but not required
-#   - completed: Retrospective has been done
-#
-# WORKFLOW NOTES:
-# ===============
-# - Epics should be 'contexted' before stories can be 'drafted'
-# - Stories can be worked in parallel if team capacity allows
-# - SM typically drafts next story after previous one is 'done' to incorporate learnings
-# - Dev moves story to 'review', SM reviews, then Dev moves to 'done'
-
-generated: 2025-10-21
-project: todo1
-project_key: todo1
-tracking_system: file-system
-story_location: "{project-root}/docs/stories"
-
-development_status:
-  epic-1: backlog
-  1-1-project-foundation-development-environment: backlog
-  1-2-app-shell-navigation-framework: backlog
-  1-3-user-authentication-account-management: backlog
-  1-4-plant-data-model-species-database: backlog
-  1-5-add-plant-manual-species-selection: backlog
-  1-6-plant-photo-identification-integration: backlog
-  1-7-plant-naming-profile-creation: backlog
-  1-8-plant-collection-home-screen: backlog
-  1-9-plant-detail-view: backlog
-  1-10-cloud-photo-storage-display: backlog
-  epic-1-retrospective: optional
-
-  epic-2: backlog
-  2-1-personality-system-data-model: backlog
-  2-2-personality-prototype-testing: backlog
-  2-3-llm-integration-api-setup: backlog
-  2-4-chat-interface-ui: backlog
-  2-5-conversational-ai-system: backlog
-  2-6-graceful-degradation-library: backlog
-  2-7-response-caching-cost-optimization: backlog
-  2-8-personality-driven-care-reminders: backlog
-  2-9-push-notification-system: backlog
-  2-10-reminder-intelligence-adaptation: backlog
-  2-11-mood-system-visual-indicators: backlog
-  2-12-mood-calculation-logic-time-based: backlog
-  2-13-personality-introduction-onboarding: backlog
-  2-14-personality-tone-testing-calibration: backlog
-  2-15-emergency-tone-adjustment-system: backlog
-  2-16-api-reliability-monitoring-alerts: backlog
-  epic-2-retrospective: optional
-
-  epic-3: backlog
-  3-1-care-schedule-data-model: backlog
-  3-2-auto-generated-care-schedules: backlog
-  3-3-manual-care-logging: backlog
-  3-4-care-history-view: backlog
-  3-5-customizable-care-schedules: backlog
-  3-6-photo-timeline-tracking: backlog
-  3-7-health-status-visualization: backlog
-  3-8-enhanced-mood-calculation-care-data: backlog
-  epic-3-retrospective: optional
-
-  epic-4: backlog
-  4-1-shareable-content-card-design-system: backlog
-  4-2-share-plant-profile: backlog
-  4-3-share-conversation-snippets: backlog
-  4-4-share-growth-progress: backlog
-  4-5-share-care-achievements: backlog
-  4-6-freemium-tier-definition-enforcement: backlog
-  4-7-premium-upgrade-flow-paywall: backlog
-  4-8-payment-processing-subscription-management: backlog
-  4-9-premium-analytics-dashboard: backlog
-  4-10-trial-conversion-optimization: backlog
-  epic-4-retrospective: optional

src/modules/bmm/workflows/4-implementation/temp-testing-files/sample-workflow-status.md

@@ -1,65 +0,0 @@
-# BMM Workflow Status
-
-## Project Configuration
-
-PROJECT_NAME: todo1
-PROJECT_TYPE: software
-PROJECT_LEVEL: 3
-FIELD_TYPE: greenfield
-START_DATE: 2025-10-18
-WORKFLOW_PATH: greenfield-level-3.yaml
-
-## Current State
-
-CURRENT_PHASE: 4-implementation
-CURRENT_WORKFLOW: tech-spec
-CURRENT_AGENT: architect
-PHASE_1_COMPLETE: true
-PHASE_2_COMPLETE: true
-PHASE_3_COMPLETE: true
-PHASE_4_COMPLETE: false
-
-## Next Action
-
-NEXT_ACTION: Create technical specification for Epic 1 (Foundation & Core Plant Management)
-NEXT_COMMAND: /bmad:bmm:agents:architect then run \*tech-spec for Epic 1
-NEXT_AGENT: architect
-
-## Story Backlog
-
-**Epic 1:** 10 stories - Foundation & Core Plant Management
-**Epic 2:** 16 stories - AI Personality System & Engagement Loop
-**Epic 3:** 8 stories - Care Scheduling, Photos & Growth Tracking
-**Epic 4:** 10 stories - Social Sharing & Premium Monetization
-
-**Total: 44 stories** (see epics.md for detailed breakdown)
-
-## Workflow Progress
-
-**Phase 1 - Analysis:**
-
-- ✅ Brainstorm Project (2025-10-18)
-- ⬜ Research (optional - skipped)
-- ✅ Product Brief (2025-10-18)
-
-**Phase 2 - Planning:**
-
-- ✅ PRD (2025-10-19) - 44 stories across 4 epics defined
-- ✅ UX Spec (2025-10-19) - Comprehensive design system, user flows, components
-
-**Phase 3 - Architecture (Required for Level 3):**
-
-- ✅ Architecture (2025-10-19)
-- ✅ Assess Project Ready (2025-10-19)
-
-**Phase 4 - Implementation:**
-
-- 🎯 Tech Spec for Epic 1 (next up)
-- Per Epic: Tech Spec (JIT) → Stories
-- Per Story: Create → Context → Validate → Ready → Develop → Review → Approved
-- Epic Retrospectives after each epic
-
----
-
-_Last Updated: 2025-10-19 (Phase 3 Complete - Starting Implementation Phase)_
-_Status Version: 6.0_

src/modules/bmm/workflows/workflow-status/init/workflow.yaml

@@ -23,3 +23,6 @@ path_files: "{project-root}/bmad/bmm/workflows/workflow-status/paths/"
 
 # Output configuration
 default_output_file: "{output_folder}/bmm-workflow-status.md"
+
+standalone: true
+web_bundle: false

src/modules/bmm/workflows/workflow-status/workflow.yaml

@@ -25,5 +25,6 @@ path_files: "{installed_path}/paths/"
 # Output configuration - reads existing status
 default_output_file: "{output_folder}/bmm-workflow-status.md"
 
-# This is now a lightweight router workflow
+standalone: true
+
 web_bundle: false

src/modules/cis/workflows/design-thinking/workflow.yaml

@@ -29,6 +29,8 @@ design_methods: "{installed_path}/design-methods.csv"
 # Output configuration
 default_output_file: "{output_folder}/design-thinking-{{date}}.md"
 
+standalone: true
+
 web_bundle:
   name: "design-thinking"
   description: "Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs."

src/modules/cis/workflows/innovation-strategy/workflow.yaml

@@ -29,6 +29,8 @@ innovation_frameworks: "{installed_path}/innovation-frameworks.csv"
 # Output configuration
 default_output_file: "{output_folder}/innovation-strategy-{{date}}.md"
 
+standalone: true
+
 web_bundle:
   name: "innovation-strategy"
   description: "Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities."

src/modules/cis/workflows/problem-solving/workflow.yaml

@@ -29,6 +29,8 @@ solving_methods: "{installed_path}/solving-methods.csv"
 # Output configuration
 default_output_file: "{output_folder}/problem-solution-{{date}}.md"
 
+standalone: true
+
 web_bundle:
   name: "problem-solving"
   description: "Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks."

src/modules/cis/workflows/storytelling/workflow.yaml

@@ -29,6 +29,8 @@ story_frameworks: "{installed_path}/story-types.csv"
 # Output configuration
 default_output_file: "{output_folder}/story-{{date}}.md"
 
+standalone: true
+
 web_bundle:
   name: "storytelling"
   description: "Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose."