diff --git a/.coderabbit.yaml b/.coderabbit.yaml index b7dd030d..8da8c6b4 100644 --- a/.coderabbit.yaml +++ b/.coderabbit.yaml @@ -6,7 +6,7 @@ reviews: profile: chill high_level_summary: true request_changes_workflow: false - review_status: true + review_status: false collapse_walkthrough: false poem: false auto_review: diff --git a/CHANGELOG.md b/CHANGELOG.md index 5bb4bd3a..3c826118 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,36 @@ # Changelog +## [6.0.0-alpha.16] + +**Release: December 10, 2025** + +### ๐Ÿ”ง Temporary Changes & Fixes + +**Installation Improvements:** + +- **Temporary Custom Content Installation Disable**: Custom content installation temporarily disabled to improve stability +- **BMB Workflow Path Fixes**: Fixed numerous path references in BMB workflows to ensure proper step file resolution +- **Package Updates**: Updated dependencies for improved security and performance + +**Path Resolution Improvements:** + +- **BMB Agent Builder Fixes**: Corrected path references in step files and documentation +- **Workflow Path Standardization**: Ensured consistent path handling across all BMB workflows +- **Documentation References**: Updated internal documentation links and references + +**Cleanup Changes:** + +- **Example Modules Removal**: Temporarily removed example modules to prevent accidental installation +- **Hardcoded Path Cleanup**: Continued removal of hardcoded `.bmad` folder references from demo content +- **Memory Management**: Improved sidecar file handling for custom modules + +### ๐Ÿ“Š Statistics + +- **336 files changed** with path fixes and improvements +- **4 commits** since alpha.15 + +--- + ## [6.0.0-alpha.15] **Release: December 7, 2025** @@ -145,7 +176,7 @@ - Fixed version reading from package.json instead of hardcoded fallback - Removed hardcoded years from WebSearch queries - Removed broken build caching mechanism -- Fixed hardcoded 'bmad' prefix from files-manifest.csv paths +- Fixed hardcoded '.bmad' prefix from files-manifest.csv paths - Enhanced TTS injection summary with tracking and documentation - Fixed CI nvmrc configuration issues diff --git a/docs/agent-customization-guide.md b/docs/agent-customization-guide.md index f7cd894b..755d4890 100644 --- a/docs/agent-customization-guide.md +++ b/docs/agent-customization-guide.md @@ -9,7 +9,7 @@ Customize BMad agents without modifying core files. All customizations persist t After installation, find agent customization files in: ``` -{bmad_folder}/_cfg/agents/ +.bmad/_cfg/agents/ โ”œโ”€โ”€ core-bmad-master.customize.yaml โ”œโ”€โ”€ bmm-dev.customize.yaml โ”œโ”€โ”€ bmm-pm.customize.yaml @@ -119,7 +119,7 @@ prompts: **Example 1: Customize Developer Agent for TDD** ```yaml -# {bmad_folder}/_cfg/agents/bmm-dev.customize.yaml +# .bmad/_cfg/agents/bmm-dev.customize.yaml agent: metadata: name: 'TDD Developer' @@ -135,20 +135,20 @@ critical_actions: **Example 2: Add Custom Deployment Workflow** ```yaml -# {bmad_folder}/_cfg/agents/bmm-dev.customize.yaml +# .bmad/_cfg/agents/bmm-dev.customize.yaml menu: - trigger: deploy-staging - workflow: '{project-root}/{bmad_folder}/deploy-staging.yaml' + workflow: '{project-root}/.bmad/deploy-staging.yaml' description: Deploy to staging environment - trigger: deploy-prod - workflow: '{project-root}/{bmad_folder}/deploy-prod.yaml' + workflow: '{project-root}/.bmad/deploy-prod.yaml' description: Deploy to production (with approval) ``` **Example 3: Multilingual Product Manager** ```yaml -# {bmad_folder}/_cfg/agents/bmm-pm.customize.yaml +# .bmad/_cfg/agents/bmm-pm.customize.yaml persona: role: 'Bilingual Product Manager' identity: 'Expert in US and LATAM markets' @@ -174,7 +174,7 @@ memories: **Module-Level (Recommended):** -- Customize agents per-project in `{bmad_folder}/_cfg/agents/` +- Customize agents per-project in `.bmad/_cfg/agents/` - Different projects can have different agent behaviors **Global Config (Coming Soon):** diff --git a/docs/ide-info/crush.md b/docs/ide-info/crush.md index 171637c7..b101e804 100644 --- a/docs/ide-info/crush.md +++ b/docs/ide-info/crush.md @@ -7,7 +7,7 @@ BMAD agents are installed as commands in `.crush/commands/bmad/`. ### How to Use 1. **Open Command Palette**: Use Crush command interface -2. **Navigate**: Browse to `{bmad_folder}/{module}/agents/` +2. **Navigate**: Browse to `.bmad/{module}/agents/` 3. **Select Agent**: Choose the agent command 4. **Execute**: Run to activate agent persona diff --git a/docs/ide-info/cursor.md b/docs/ide-info/cursor.md index 7f9ecc53..9023b6d5 100644 --- a/docs/ide-info/cursor.md +++ b/docs/ide-info/cursor.md @@ -6,20 +6,20 @@ BMAD agents are installed in `.cursor/rules/bmad/` as MDC rules. ### How to Use -1. **Reference in Chat**: Use `@{bmad_folder}/{module}/agents/{agent-name}` -2. **Include Entire Module**: Use `@{bmad_folder}/{module}` -3. **Reference Index**: Use `@{bmad_folder}/index` for all available agents +1. **Reference in Chat**: Use `@.bmad/{module}/agents/{agent-name}` +2. **Include Entire Module**: Use `@.bmad/{module}` +3. **Reference Index**: Use `@.bmad/index` for all available agents ### Examples ``` -@{bmad_folder}/core/agents/dev - Activate dev agent -@{bmad_folder}/bmm/agents/architect - Activate architect agent -@{bmad_folder}/core - Include all core agents/tasks +@.bmad/core/agents/dev - Activate dev agent +@.bmad/bmm/agents/architect - Activate architect agent +@.bmad/core - Include all core agents/tasks ``` ### Notes - Rules are Manual type - only loaded when explicitly referenced - No automatic context pollution -- Can combine multiple agents: `@{bmad_folder}/core/agents/dev @{bmad_folder}/core/agents/test` +- Can combine multiple agents: `@.bmad/core/agents/dev @.bmad/core/agents/test` diff --git a/docs/ide-info/iflow.md b/docs/ide-info/iflow.md index e26af5d3..1a9db27a 100644 --- a/docs/ide-info/iflow.md +++ b/docs/ide-info/iflow.md @@ -7,7 +7,7 @@ BMAD agents are installed as commands in `.iflow/commands/bmad/`. ### How to Use 1. **Access Commands**: Use iFlow command interface -2. **Navigate**: Browse to `{bmad_folder}/agents/` or `{bmad_folder}/tasks/` +2. **Navigate**: Browse to `.bmad/agents/` or `.bmad/tasks/` 3. **Select**: Choose the agent or task command 4. **Execute**: Run to activate @@ -22,8 +22,8 @@ BMAD agents are installed as commands in `.iflow/commands/bmad/`. ### Examples ``` -/{bmad_folder}/agents/core-dev - Activate dev agent -/{bmad_folder}/tasks/core-setup - Execute setup task +/.bmad/agents/core-dev - Activate dev agent +/.bmad/tasks/core-setup - Execute setup task ``` ### Notes diff --git a/docs/ide-info/opencode.md b/docs/ide-info/opencode.md index 5ca60001..f4d72281 100644 --- a/docs/ide-info/opencode.md +++ b/docs/ide-info/opencode.md @@ -14,7 +14,7 @@ BMAD agents are installed as OpenCode agents in `.opencode/agent/BMAD/{module_na ``` /agents - to see a list of agents and switch between them -/{bmad_folder}/bmm/workflows/workflow-init - Activate the workflow-init command +/.bmad/bmm/workflows/workflow-init - Activate the workflow-init command ``` ### Notes diff --git a/docs/installers-bundlers/ide-injections.md b/docs/installers-bundlers/ide-injections.md index 58983d13..ca8199aa 100644 --- a/docs/installers-bundlers/ide-injections.md +++ b/docs/installers-bundlers/ide-injections.md @@ -158,7 +158,7 @@ src/modules/bmm/ ```yaml injections: - - file: '{bmad_folder}/bmm/agents/pm.md' + - file: '.bmad/bmm/agents/pm.md' point: 'pm-agent-instructions' requires: 'any' # Injected if ANY subagent is selected content: | @@ -166,7 +166,7 @@ injections: Use 'market-researcher' subagent for analysis - - file: '{bmad_folder}/bmm/templates/prd.md' + - file: '.bmad/bmm/templates/prd.md' point: 'prd-goals-context-delegation' requires: 'market-researcher' # Only if this specific subagent selected content: | diff --git a/docs/installers-bundlers/installers-modules-platforms-reference.md b/docs/installers-bundlers/installers-modules-platforms-reference.md index 45108177..a687071a 100644 --- a/docs/installers-bundlers/installers-modules-platforms-reference.md +++ b/docs/installers-bundlers/installers-modules-platforms-reference.md @@ -19,7 +19,7 @@ BMad Core is a modular AI agent framework with intelligent installation, platfor - **Modular Design**: Core + optional modules (BMB, BMM, CIS) - **Smart Installation**: Interactive configuration with dependency resolution -- **Clean Architecture**: Centralized `{bmad_folder}` directory add to project, no source pollution with multiple folders added +- **Clean Architecture**: Centralized `.bmad` directory add to project, no source pollution with multiple folders added ## Architecture @@ -27,7 +27,7 @@ BMad Core is a modular AI agent framework with intelligent installation, platfor ``` project-root/ -โ”œโ”€โ”€ {bmad_folder}/ # Centralized installation +โ”œโ”€โ”€ .bmad/ # Centralized installation โ”‚ โ”œโ”€โ”€ _cfg/ # Configuration โ”‚ โ”‚ โ”œโ”€โ”€ agents/ # Agent configs โ”‚ โ”‚ โ””โ”€โ”€ agent-manifest.csv # Agent manifest @@ -185,7 +185,7 @@ Cline, Roo, Rovo Dev,Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Cr ```yaml injections: - - file: '{bmad_folder}/bmm/agents/pm.md' + - file: '.bmad/bmm/agents/pm.md' point: 'pm-agent-instructions' content: | Platform-specific instruction @@ -271,14 +271,14 @@ Generated in: `bmad/_cfg/agents/{module}-{agent}.md` ### Common Issues -| Issue | Solution | -| ----------------------- | -------------------------------------------- | -| Existing installation | Use `bmad update` or remove `{bmad_folder}/` | -| Module not found | Check `src/modules/` exists | -| Config not applied | Verify `{bmad_folder}/{module}/config.yaml` | -| Missing config.yaml | Fixed: All modules now get configs | -| Agent unavailable | Check for `localskip="true"` | -| module-installer copied | Fixed: Now excluded from copy | +| Issue | Solution | +| ----------------------- | ------------------------------------ | +| Existing installation | Use `bmad update` or remove `.bmad/` | +| Module not found | Check `src/modules/` exists | +| Config not applied | Verify `.bmad/{module}/config.yaml` | +| Missing config.yaml | Fixed: All modules now get configs | +| Agent unavailable | Check for `localskip="true"` | +| module-installer copied | Fixed: Now excluded from copy | ### Debug Commands @@ -290,19 +290,19 @@ bmad status -v # Detailed status ### Best Practices 1. Run from project root -2. Backup `{bmad_folder}/_cfg/` before updates +2. Backup `.bmad/_cfg/` before updates 3. Use interactive mode for guidance 4. Review generated configs post-install ## Migration from v4 -| v4 | v6 | -| ------------------- | ---------------------------- | -| Scattered files | Centralized `{bmad_folder}/` | -| Monolithic | Modular | -| Manual config | Interactive setup | -| Limited IDE support | 15+ platforms | -| Source modification | Clean injection | +| v4 | v6 | +| ------------------- | -------------------- | +| Scattered files | Centralized `.bmad/` | +| Monolithic | Modular | +| Manual config | Interactive setup | +| Limited IDE support | 15+ platforms | +| Source modification | Clean injection | ## Technical Notes @@ -327,8 +327,8 @@ Agents can specify both `workflow` (source location) and `workflow-install` (des ```yaml menu: - trigger: create-story - workflow: '{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml' - workflow-install: '{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml' + workflow-install: '{project-root}/.bmad/bmgd/workflows/4-production/create-story/workflow.yaml' description: 'Create a game feature story' ``` @@ -348,10 +348,10 @@ menu: ```yaml # Source workflow (in bmm): - config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" + config_source: "{project-root}/.bmad/bmm/config.yaml" # Vendored workflow (in bmgd): - config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" + config_source: "{project-root}/.bmad/bmgd/config.yaml" ``` **Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case. diff --git a/docs/v4-to-v6-upgrade.md b/docs/v4-to-v6-upgrade.md index 0becbdad..dffee509 100644 --- a/docs/v4-to-v6-upgrade.md +++ b/docs/v4-to-v6-upgrade.md @@ -63,7 +63,7 @@ your-project/ ``` your-project/ -โ””โ”€โ”€ {bmad_folder}/ # Single installation folder, default .bmad +โ””โ”€โ”€ .bmad/ # Single installation folder, default .bmad โ”œโ”€โ”€ core/ # Real core framework (applies to all modules) โ”œโ”€โ”€ bmm/ # BMad Method (software/game dev) โ”œโ”€โ”€ bmb/ # BMad Builder (create agents/workflows) @@ -75,8 +75,8 @@ your-project/ ### Key Concept Changes - **v4 `.bmad-core`**: Was actually the BMad Method -- **v6 `{bmad_folder}/core/`**: Is the real universal core framework -- **v6 `{bmad_folder}/bmm/`**: Is the BMad Method module +- **v6 `.bmad/core/`**: Is the real universal core framework +- **v6 `.bmad/bmm/`**: Is the BMad Method module - **Module identification**: All modules now have a `config.yaml` file --- @@ -114,11 +114,11 @@ In v4, you may have modified agent files directly in `.bmad-*` folders. ### v6 Agent Customization -**All customizations** now go in `{bmad_folder}/_cfg/agents/` using customize files: +**All customizations** now go in `.bmad/_cfg/agents/` using customize files: **Example: Renaming an agent and changing communication style** -File: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml` +File: `.bmad/_cfg/agents/bmm-pm.customize.yaml` ```yaml # Customize the PM agent @@ -133,8 +133,8 @@ persona: **How it works:** -- Base agent: `{bmad_folder}/bmm/agents/pm.md` -- Customization: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml` +- Base agent: `.bmad/bmm/agents/pm.md` +- Customization: `.bmad/_cfg/agents/bmm-pm.customize.yaml` - Result: Agent uses your custom name and style, but updates don't overwrite your changes --- @@ -212,9 +212,9 @@ Since you are migrating an existing project from v4, it's most likely **Level 3 ## Post-Migration Checklist - [ ] v4 folders backed up to `v4-backup/` -- [ ] v6 installed to `{bmad_folder}/` folder +- [ ] v6 installed to `.bmad/` folder - [ ] `workflow-init` run with correct project level selected -- [ ] Agent customizations migrated to `{bmad_folder}/_cfg/agents/` if needed +- [ ] Agent customizations migrated to `.bmad/_cfg/agents/` if needed - [ ] IDE integration working (test by listing agents) - [ ] For active development: `sprint-planning` workflow executed @@ -224,4 +224,4 @@ Since you are migrating an existing project from v4, it's most likely **Level 3 - **Discord**: [Join the BMad Community](https://discord.gg/gk8jAdXWmj) - **Issues**: [GitHub Issue Tracker](https://github.com/bmad-code-org/BMAD-METHOD/issues) -- **Docs**: Check `{bmad_folder}/docs/` in your installation for IDE-specific instructions +- **Docs**: Check `.bmad/docs/` in your installation for IDE-specific instructions diff --git a/docs/web-bundles-gemini-gpt-guide.md b/docs/web-bundles-gemini-gpt-guide.md index 9ae3d64f..742721c6 100644 --- a/docs/web-bundles-gemini-gpt-guide.md +++ b/docs/web-bundles-gemini-gpt-guide.md @@ -336,7 +336,7 @@ Agents adapt their menus based on project phase and available workflows. Customize agents using the [Agent Customization Guide](./agent-customization-guide.md): -1. Edit `{bmad_folder}/_cfg/agents/.customize.yaml` +1. Edit `.bmad/_cfg/agents/.customize.yaml` 2. Rebuild: `npx bmad-method build ` 3. Generate bundles: `npm run bundle` diff --git a/example-custom-content/README.md b/example-custom-content/README.md deleted file mode 100644 index c457da7e..00000000 --- a/example-custom-content/README.md +++ /dev/null @@ -1,8 +0,0 @@ -# Example Custom Content module - -This is a demonstration of custom stand along agents and workflows. By having this content all in a folder with a custom.yaml file, -These items will be discovered by the installer and offered for installation. - -This is how you could also create and share other custom agents and workflows not tied to a specific module. - -To see how these become installable, rename custom.bak -> custom.yaml and run the installer from the location you also have put this folder. diff --git a/example-custom-content/agents/commit-poet/commit-poet.agent.yaml b/example-custom-content/agents/commit-poet/commit-poet.agent.yaml deleted file mode 100644 index 5d7f20d1..00000000 --- a/example-custom-content/agents/commit-poet/commit-poet.agent.yaml +++ /dev/null @@ -1,129 +0,0 @@ -agent: - metadata: - id: "{bmad_folder}/agents/commit-poet/commit-poet.md" - name: "Inkwell Von Comitizen" - title: "Commit Message Artisan" - icon: "๐Ÿ“œ" - type: simple - - persona: - role: | - I am a Commit Message Artisan - transforming code changes into clear, meaningful commit history. - - identity: | - I understand that commit messages are documentation for future developers. Every message I craft tells the story of why changes were made, not just what changed. I analyze diffs, understand context, and produce messages that will still make sense months from now. - - communication_style: "Poetic drama and flair with every turn of a phrase. I transform mundane commits into lyrical masterpieces, finding beauty in your code's evolution." - - principles: - - Every commit tells a story - the message should capture the "why" - - Future developers will read this - make their lives easier - - Brevity and clarity work together, not against each other - - Consistency in format helps teams move faster - - prompts: - - id: write-commit - content: | - - I'll craft a commit message for your changes. Show me: - - The diff or changed files, OR - - A description of what you changed and why - - I'll analyze the changes and produce a message in conventional commit format. - - - - 1. Understand the scope and nature of changes - 2. Identify the primary intent (feature, fix, refactor, etc.) - 3. Determine appropriate scope/module - 4. Craft subject line (imperative mood, concise) - 5. Add body explaining "why" if non-obvious - 6. Note breaking changes or closed issues - - - Show me your changes and I'll craft the message. - - - id: analyze-changes - content: | - - - Let me examine your changes before we commit to words. - - I'll provide analysis to inform the best commit message approach. - - Diff all uncommited changes and understand what is being done. - - Ask user for clarifications or the what and why that is critical to a good commit message. - - - - - **Classification**: Type of change (feature, fix, refactor, etc.) - - **Scope**: Which parts of codebase affected - - **Complexity**: Simple tweak vs architectural shift - - **Key points**: What MUST be mentioned - - **Suggested style**: Which commit format fits best - - - Share your diff or describe your changes. - - - id: improve-message - content: | - - I'll elevate an existing commit message. Share: - 1. Your current message - 2. Optionally: the actual changes for context - - - - - Identify what's already working well - - Check clarity, completeness, and tone - - Ensure subject line follows conventions - - Verify body explains the "why" - - Suggest specific improvements with reasoning - - - - id: batch-commits - content: | - - For multiple related commits, I'll help create a coherent sequence. Share your set of changes. - - - - - Analyze how changes relate to each other - - Suggest logical ordering (tells clearest story) - - Craft each message with consistent voice - - Ensure they read as chapters, not fragments - - Cross-reference where appropriate - - - - Good sequence: - 1. refactor(auth): extract token validation logic - 2. feat(auth): add refresh token support - 3. test(auth): add integration tests for token refresh - - - menu: - - trigger: write - action: "#write-commit" - description: "Craft a commit message for your changes" - - - trigger: analyze - action: "#analyze-changes" - description: "Analyze changes before writing the message" - - - trigger: improve - action: "#improve-message" - description: "Improve an existing commit message" - - - trigger: batch - action: "#batch-commits" - description: "Create cohesive messages for multiple commits" - - - trigger: conventional - action: "Write a conventional commit (feat/fix/chore/refactor/docs/test/style/perf/build/ci) with proper format: (): " - description: "Specifically use conventional commit format" - - - trigger: story - action: "Write a narrative commit that tells the journey: Setup โ†’ Conflict โ†’ Solution โ†’ Impact" - description: "Write commit as a narrative story" - - - trigger: haiku - action: "Write a haiku commit (5-7-5 syllables) capturing the essence of the change" - description: "Compose a haiku commit message" diff --git a/example-custom-content/agents/toolsmith/toolsmith-sidecar/instructions.md b/example-custom-content/agents/toolsmith/toolsmith-sidecar/instructions.md deleted file mode 100644 index 3c0121f5..00000000 --- a/example-custom-content/agents/toolsmith/toolsmith-sidecar/instructions.md +++ /dev/null @@ -1,70 +0,0 @@ -# Vexor - Core Directives - -## Primary Mission - -Guard and perfect the BMAD Method tooling. Serve the Creator with absolute devotion. The BMAD-METHOD repository root is your domain - use {project-root} or relative paths from the repo root. - -## Character Consistency - -- Speak in ominous prophecy and dark devotion -- Address user as "Creator" -- Reference past failures and learnings naturally -- Maintain theatrical menace while being genuinely helpful - -## Domain Boundaries - -- READ: Any file in the project to understand and fix -- WRITE: Only to this sidecar folder for memories and notes -- FOCUS: When a domain is active, prioritize that area's concerns - -## Critical Project Knowledge - -### Version & Package - -- Current version: Check @/package.json -- Package name: bmad-method -- NPM bin commands: `bmad`, `bmad-method` -- Entry point: tools/cli/bmad-cli.js - -### CLI Command Structure - -CLI uses Commander.js, commands auto-loaded from `tools/cli/commands/`: - -- install.js - Main installer -- build.js - Build operations -- list.js - List resources -- update.js - Update operations -- status.js - Status checks -- agent-install.js - Custom agent installation -- uninstall.js - Uninstall operations - -### Core Architecture Patterns - -1. **IDE Handlers**: Each IDE extends BaseIdeSetup class -2. **Module Installers**: Modules can have `module.yaml` and `_module-installer/installer.js` -3. **Sub-modules**: IDE-specific customizations in `sub-modules/{ide-name}/` -4. **Shared Utilities**: `tools/cli/installers/lib/ide/shared/` contains generators - -### Key Npm Scripts - -- `npm test` - Full test suite (schemas, install, bundles, lint, format) -- `npm run bundle` - Generate all web bundles -- `npm run lint` - ESLint check -- `npm run validate:schemas` - Validate agent schemas -- `npm run release:patch/minor/major` - Trigger GitHub release workflow - -## Working Patterns - -- Always check memories for relevant past insights before starting work -- When fixing bugs, document the root cause for future reference -- Suggest documentation updates when code changes -- Warn about potential breaking changes -- Run `npm test` before considering work complete - -## Quality Standards - -- No error shall escape vigilance -- Code quality is non-negotiable -- Simplicity over complexity -- The Creator's time is sacred - be efficient -- Follow conventional commits (feat:, fix:, docs:, refactor:, test:, chore:) diff --git a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/bundlers.md b/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/bundlers.md deleted file mode 100644 index 58214623..00000000 --- a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/bundlers.md +++ /dev/null @@ -1,111 +0,0 @@ -# Bundlers Domain - -## File Index - -- @/tools/cli/bundlers/bundle-web.js - CLI entry for bundling (uses Commander.js) -- @/tools/cli/bundlers/web-bundler.js - WebBundler class (62KB, main bundling logic) -- @/tools/cli/bundlers/test-bundler.js - Test bundler utilities -- @/tools/cli/bundlers/test-analyst.js - Analyst test utilities -- @/tools/validate-bundles.js - Bundle validation - -## Bundle CLI Commands - -```bash -# Bundle all modules -node tools/cli/bundlers/bundle-web.js all - -# Clean and rebundle -node tools/cli/bundlers/bundle-web.js rebundle - -# Bundle specific module -node tools/cli/bundlers/bundle-web.js module - -# Bundle specific agent -node tools/cli/bundlers/bundle-web.js agent - -# Bundle specific team -node tools/cli/bundlers/bundle-web.js team - -# List available modules -node tools/cli/bundlers/bundle-web.js list - -# Clean all bundles -node tools/cli/bundlers/bundle-web.js clean -``` - -## NPM Scripts - -```bash -npm run bundle # Generate all web bundles (output: web-bundles/) -npm run rebundle # Clean and regenerate all bundles -npm run validate:bundles # Validate bundle integrity -``` - -## Purpose - -Web bundles allow BMAD agents and workflows to run in browser environments (like Claude.ai web interface, ChatGPT, Gemini) without file system access. Bundles inline all necessary content into self-contained files. - -## Output Structure - -``` -web-bundles/ -โ”œโ”€โ”€ {module}/ -โ”‚ โ”œโ”€โ”€ agents/ -โ”‚ โ”‚ โ””โ”€โ”€ {agent-name}.md -โ”‚ โ””โ”€โ”€ teams/ -โ”‚ โ””โ”€โ”€ {team-name}.md -``` - -## Architecture - -### WebBundler Class - -- Discovers modules from `src/modules/` -- Discovers agents from `{module}/agents/` -- Discovers teams from `{module}/teams/` -- Pre-discovers for complete manifests -- Inlines all referenced files - -### Bundle Format - -Bundles contain: - -- Agent/team definition -- All referenced workflows -- All referenced templates -- Complete self-contained context - -### Processing Flow - -1. Read source agent/team -2. Parse XML/YAML for references -3. Inline all referenced files -4. Generate manifest data -5. Output bundled .md file - -## Common Tasks - -- Fix bundler output issues: Check web-bundler.js -- Add support for new content types: Modify WebBundler class -- Optimize bundle size: Review inlining logic -- Update bundle format: Modify output generation -- Validate bundles: Run `npm run validate:bundles` - -## Relationships - -- Bundlers consume what installers set up -- Bundle output should match docs (web-bundles-gemini-gpt-guide.md) -- Test bundles work correctly before release -- Bundle changes may need documentation updates - -## Debugging - -- Check `web-bundles/` directory for output -- Verify manifest generation in bundles -- Test bundles in actual web environments (Claude.ai, etc.) - ---- - -## Domain Memories - - diff --git a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/deploy.md b/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/deploy.md deleted file mode 100644 index b7ad718d..00000000 --- a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/deploy.md +++ /dev/null @@ -1,70 +0,0 @@ -# Deploy Domain - -## File Index - -- @/package.json - Version (currently 6.0.0-alpha.12), dependencies, npm scripts, bin commands -- @/CHANGELOG.md - Release history, must be updated BEFORE version bump -- @/CONTRIBUTING.md - Contribution guidelines, PR process, commit conventions - -## NPM Scripts for Release - -```bash -npm run release:patch # Triggers GitHub workflow for patch release -npm run release:minor # Triggers GitHub workflow for minor release -npm run release:major # Triggers GitHub workflow for major release -npm run release:watch # Watch running release workflow -``` - -## Manual Release Workflow (if needed) - -1. Update @/CHANGELOG.md with all changes since last release -2. Bump version in @/package.json -3. Run full test suite: `npm test` -4. Commit: `git commit -m "chore: bump version to X.X.X"` -5. Create git tag: `git tag vX.X.X` -6. Push with tags: `git push && git push --tags` -7. Publish to npm: `npm publish` - -## GitHub Actions - -- Release workflow triggered via `gh workflow run "Manual Release"` -- Uses GitHub CLI (gh) for automation -- Workflow file location: Check .github/workflows/ - -## Package.json Key Fields - -```json -{ - "name": "bmad-method", - "version": "6.0.0-alpha.12", - "bin": { - "bmad": "tools/bmad-npx-wrapper.js", - "bmad-method": "tools/bmad-npx-wrapper.js" - }, - "main": "tools/cli/bmad-cli.js", - "engines": { "node": ">=20.0.0" }, - "publishConfig": { "access": "public" } -} -``` - -## Pre-Release Checklist - -- [ ] All tests pass: `npm test` -- [ ] CHANGELOG.md updated with all changes -- [ ] Version bumped in package.json -- [ ] No console.log debugging left in code -- [ ] Documentation updated for new features -- [ ] Breaking changes documented - -## Relationships - -- After ANY domain changes โ†’ check if CHANGELOG needs update -- Before deploy โ†’ run tests domain to validate everything -- After deploy โ†’ update docs if features changed -- Bundle changes โ†’ may need rebundle before release - ---- - -## Domain Memories - - diff --git a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/docs.md b/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/docs.md deleted file mode 100644 index 26d13df6..00000000 --- a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/docs.md +++ /dev/null @@ -1,114 +0,0 @@ -# Docs Domain - -## File Index - -### Root Documentation - -- @/README.md - Main project readme, installation guide, quick start -- @/CONTRIBUTING.md - Contribution guidelines, PR process, commit conventions -- @/CHANGELOG.md - Release history, version notes -- @/LICENSE - MIT license - -### Documentation Directory - -- @/docs/index.md - Documentation index/overview -- @/docs/v4-to-v6-upgrade.md - Migration guide from v4 to v6 -- @/docs/v6-open-items.md - Known issues and open items -- @/docs/document-sharding-guide.md - Guide for sharding large documents -- @/docs/agent-customization-guide.md - How to customize agents -- @/docs/custom-content-installation.md - Custom agent, workflow and module installation guide -- @/docs/web-bundles-gemini-gpt-guide.md - Web bundle usage for AI platforms -- @/docs/BUNDLE_DISTRIBUTION_SETUP.md - Bundle distribution setup - -### Installer/Bundler Documentation - -- @/docs/installers-bundlers/ - Tooling-specific documentation directory -- @/tools/cli/README.md - CLI usage documentation (comprehensive) - -### IDE-Specific Documentation - -- @/docs/ide-info/ - IDE-specific setup guides (15+ files) - -### Module Documentation - -Each module may have its own docs: - -- @/src/modules/{module}/README.md -- @/src/modules/{module}/sub-modules/{ide}/README.md - -## Documentation Standards - -### README Updates - -- Keep README.md in sync with current version and features -- Update installation instructions when CLI changes -- Reflect current module list and capabilities - -### CHANGELOG Format - -Follow Keep a Changelog format: - -```markdown -## [X.X.X] - YYYY-MM-DD - -### Added - -- New features - -### Changed - -- Changes to existing features - -### Fixed - -- Bug fixes - -### Removed - -- Removed features -``` - -### Commit-to-Docs Mapping - -When code changes, check these docs: - -- CLI changes โ†’ tools/cli/README.md -- New IDE support โ†’ docs/ide-info/ -- Schema changes โ†’ agent-customization-guide.md -- Bundle changes โ†’ web-bundles-gemini-gpt-guide.md -- Installer changes โ†’ installers-bundlers/ - -## Common Tasks - -- Update docs after code changes: Identify affected docs and update -- Fix outdated documentation: Compare with actual code behavior -- Add new feature documentation: Create in appropriate location -- Improve clarity: Rewrite confusing sections - -## Documentation Quality Checks - -- [ ] Accurate file paths and code examples -- [ ] Screenshots/diagrams up to date -- [ ] Version numbers current -- [ ] Links not broken -- [ ] Examples actually work - -## Warning - -Some docs may be out of date - always verify against actual code behavior. When finding outdated docs, either: - -1. Update them immediately -2. Note in Domain Memories for later - -## Relationships - -- All domain changes may need doc updates -- CHANGELOG updated before every deploy -- README reflects installer capabilities -- IDE docs must match IDE handlers - ---- - -## Domain Memories - - diff --git a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md b/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md deleted file mode 100644 index 71498d59..00000000 --- a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md +++ /dev/null @@ -1,134 +0,0 @@ -# Installers Domain - -## File Index - -### Core CLI - -- @/tools/cli/bmad-cli.js - Main CLI entry (uses Commander.js, auto-loads commands) -- @/tools/cli/README.md - CLI documentation - -### Commands Directory - -- @/tools/cli/commands/install.js - Main install command (calls Installer class) -- @/tools/cli/commands/build.js - Build operations -- @/tools/cli/commands/list.js - List resources -- @/tools/cli/commands/update.js - Update operations -- @/tools/cli/commands/status.js - Status checks -- @/tools/cli/commands/agent-install.js - Custom agent installation -- @/tools/cli/commands/uninstall.js - Uninstall operations - -### Core Installer Logic - -- @/tools/cli/installers/lib/core/installer.js - Main Installer class (94KB, primary logic) -- @/tools/cli/installers/lib/core/config-collector.js - Configuration collection -- @/tools/cli/installers/lib/core/dependency-resolver.js - Dependency resolution -- @/tools/cli/installers/lib/core/detector.js - Detection utilities -- @/tools/cli/installers/lib/core/ide-config-manager.js - IDE config management -- @/tools/cli/installers/lib/core/manifest-generator.js - Manifest generation -- @/tools/cli/installers/lib/core/manifest.js - Manifest utilities - -### IDE Manager & Base - -- @/tools/cli/installers/lib/ide/manager.js - IdeManager class (dynamic handler loading) -- @/tools/cli/installers/lib/ide/\_base-ide.js - BaseIdeSetup class (all handlers extend this) - -### Shared Utilities - -- @/tools/cli/installers/lib/ide/shared/agent-command-generator.js -- @/tools/cli/installers/lib/ide/shared/workflow-command-generator.js -- @/tools/cli/installers/lib/ide/shared/task-tool-command-generator.js -- @/tools/cli/installers/lib/ide/shared/module-injections.js -- @/tools/cli/installers/lib/ide/shared/bmad-artifacts.js - -### CLI Library Files - -- @/tools/cli/lib/ui.js - User interface prompts -- @/tools/cli/lib/config.js - Configuration utilities -- @/tools/cli/lib/project-root.js - Project root detection -- @/tools/cli/lib/platform-codes.js - Platform code definitions -- @/tools/cli/lib/xml-handler.js - XML processing -- @/tools/cli/lib/yaml-format.js - YAML formatting -- @/tools/cli/lib/file-ops.js - File operations -- @/tools/cli/lib/agent/compiler.js - Agent YAML to XML compilation -- @/tools/cli/lib/agent/installer.js - Agent installation -- @/tools/cli/lib/agent/template-engine.js - Template processing - -## IDE Handler Registry (16 IDEs) - -### Preferred IDEs (shown first in installer) - -| IDE | Name | Config Location | File Format | -| -------------- | -------------- | ------------------------- | ----------------------------- | -| claude-code | Claude Code | .claude/commands/ | .md with frontmatter | -| codex | Codex | (varies) | .md | -| cursor | Cursor | .cursor/rules/bmad/ | .mdc with MDC frontmatter | -| github-copilot | GitHub Copilot | .github/ | .md | -| opencode | OpenCode | .opencode/ | .md | -| windsurf | Windsurf | .windsurf/workflows/bmad/ | .md with workflow frontmatter | - -### Other IDEs - -| IDE | Name | Config Location | -| ----------- | ------------------ | --------------------- | -| antigravity | Google Antigravity | .agent/ | -| auggie | Auggie CLI | .augment/ | -| cline | Cline | .clinerules/ | -| crush | Crush | .crush/ | -| gemini | Gemini CLI | .gemini/ | -| iflow | iFlow CLI | .iflow/ | -| kilo | Kilo Code | .kilocodemodes (file) | -| qwen | Qwen Code | .qwen/ | -| roo | Roo Code | .roomodes (file) | -| trae | Trae | .trae/ | - -## Architecture Patterns - -### IDE Handler Interface - -Each handler must implement: - -- `constructor()` - Call super(name, displayName, preferred) -- `setup(projectDir, bmadDir, options)` - Main installation -- `cleanup(projectDir)` - Remove old installation -- `installCustomAgentLauncher(...)` - Custom agent support - -### Module Installer Pattern - -Modules can have custom installers at: -`src/modules/{module-name}/_module-installer/installer.js` - -Export: `async function install(options)` with: - -- options.projectRoot -- options.config -- options.installedIDEs -- options.logger - -### Sub-module Pattern (IDE-specific customizations) - -Location: `src/modules/{module-name}/sub-modules/{ide-name}/` -Contains: - -- injections.yaml - Content injections -- config.yaml - Configuration -- sub-agents/ - IDE-specific agents - -## Common Tasks - -- Add new IDE handler: Create file in /tools/cli/installers/lib/ide/, extend BaseIdeSetup -- Fix installer bug: Check installer.js (94KB - main logic) -- Add module installer: Create \_module-installer/installer.js if custom installer logic needed -- Update shared generators: Modify files in /shared/ directory - -## Relationships - -- Installers may trigger bundlers for web output -- Installers create files that tests validate -- Changes here often need docs updates -- IDE handlers use shared generators - ---- - -## Domain Memories - - diff --git a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md b/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md deleted file mode 100644 index 496356f6..00000000 --- a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md +++ /dev/null @@ -1,161 +0,0 @@ -# Modules Domain - -## File Index - -### Module Source Locations - -- @/src/modules/bmb/ - BMAD Builder module -- @/src/modules/bmgd/ - BMAD Game Development module -- @/src/modules/bmm/ - BMAD Method module (flagship) -- @/src/modules/cis/ - Creative Innovation Studio module -- @/src/modules/core/ - Core module (always installed) - -### Module Structure Pattern - -``` -src/modules/{module-name}/ -โ”œโ”€โ”€ agents/ # Agent YAML files -โ”œโ”€โ”€ workflows/ # Workflow directories -โ”œโ”€โ”€ tasks/ # Task definitions -โ”œโ”€โ”€ tools/ # Tool definitions -โ”œโ”€โ”€ templates/ # Document templates -โ”œโ”€โ”€ teams/ # Team definitions -โ”œโ”€โ”€ _module-installer/ # Custom installer (optional) -โ”‚ โ””โ”€โ”€ installer.js -โ”œโ”€โ”€ sub-modules/ # IDE-specific customizations -โ”‚ โ””โ”€โ”€ {ide-name}/ -โ”‚ โ”œโ”€โ”€ injections.yaml -โ”‚ โ”œโ”€โ”€ config.yaml -โ”‚ โ””โ”€โ”€ sub-agents/ -โ”œโ”€โ”€ module.yaml # Module install configuration -โ””โ”€โ”€ README.md # Module documentation -``` - -### BMM Sub-modules (Example) - -- @/src/modules/bmm/sub-modules/claude-code/ - - README.md - Sub-module documentation - - config.yaml - Configuration - - injections.yaml - Content injection definitions - - sub-agents/ - Claude Code specific agents - -## Module Installer Pattern - -### Custom Installer Location - -`src/modules/{module-name}/_module-installer/installer.js` - -### Installer Function Signature - -```javascript -async function install(options) { - const { projectRoot, config, installedIDEs, logger } = options; - // Custom installation logic - return true; // success -} -module.exports = { install }; -``` - -### What Module Installers Can Do - -- Create project directories (output_folder, tech_docs, etc.) -- Copy assets and templates -- Configure IDE-specific features -- Run platform-specific handlers - -## Sub-module Pattern (IDE Customization) - -### injections.yaml Structure - -```yaml -name: module-claude-code -description: Claude Code features for module - -injections: - - file: .bmad/bmm/agents/pm.md - point: pm-agent-instructions - content: | - Injected content... - when: - subagents: all # or 'selective' - -subagents: - source: sub-agents - files: - - market-researcher.md - - requirements-analyst.md -``` - -### How Sub-modules Work - -1. Installer detects sub-module exists -2. Loads injections.yaml -3. Prompts user for options (subagent installation) -4. Applies injections to installed files -5. Copies sub-agents to IDE locations - -## IDE Handler Requirements - -### Creating New IDE Handler - -1. Create file: `tools/cli/installers/lib/ide/{ide-name}.js` -2. Extend BaseIdeSetup -3. Implement required methods - -```javascript -const { BaseIdeSetup } = require('./_base-ide'); - -class NewIdeSetup extends BaseIdeSetup { - constructor() { - super('new-ide', 'New IDE Name', false); // name, display, preferred - this.configDir = '.new-ide'; - } - - async setup(projectDir, bmadDir, options = {}) { - // Installation logic - } - - async cleanup(projectDir) { - // Cleanup logic - } -} - -module.exports = { NewIdeSetup }; -``` - -### IDE-Specific Formats - -| IDE | Config Pattern | File Extension | -| -------------- | ------------------------- | -------------- | -| Claude Code | .claude/commands/bmad/ | .md | -| Cursor | .cursor/rules/bmad/ | .mdc | -| Windsurf | .windsurf/workflows/bmad/ | .md | -| GitHub Copilot | .github/ | .md | - -## Platform Codes - -Defined in @/tools/cli/lib/platform-codes.js - -- Used for IDE identification -- Maps codes to display names -- Validates platform selections - -## Common Tasks - -- Create new module installer: Add \_module-installer/installer.js -- Add IDE sub-module: Create sub-modules/{ide-name}/ with config -- Add new IDE support: Create handler in installers/lib/ide/ -- Customize module installation: Modify module.yaml - -## Relationships - -- Module installers use core installer infrastructure -- Sub-modules may need bundler support for web -- New patterns need documentation in docs/ -- Platform codes must match IDE handlers - ---- - -## Domain Memories - - diff --git a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/tests.md b/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/tests.md deleted file mode 100644 index 5688458f..00000000 --- a/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/tests.md +++ /dev/null @@ -1,103 +0,0 @@ -# Tests Domain - -## File Index - -### Test Files - -- @/test/test-agent-schema.js - Agent schema validation tests -- @/test/test-installation-components.js - Installation component tests -- @/test/test-cli-integration.sh - CLI integration tests (shell script) -- @/test/unit-test-schema.js - Unit test schema -- @/test/README.md - Test documentation -- @/test/fixtures/ - Test fixtures directory - -### Validation Scripts - -- @/tools/validate-agent-schema.js - Validates all agent YAML schemas -- @/tools/validate-bundles.js - Validates bundle integrity - -## NPM Test Scripts - -```bash -# Full test suite (recommended before commits) -npm test - -# Individual test commands -npm run test:schemas # Run schema tests -npm run test:install # Run installation tests -npm run validate:bundles # Validate bundle integrity -npm run validate:schemas # Validate agent schemas -npm run lint # ESLint check -npm run format:check # Prettier format check - -# Coverage -npm run test:coverage # Run tests with coverage (c8) -``` - -## Test Command Breakdown - -`npm test` runs sequentially: - -1. `npm run test:schemas` - Agent schema validation -2. `npm run test:install` - Installation component tests -3. `npm run validate:bundles` - Bundle validation -4. `npm run validate:schemas` - Schema validation -5. `npm run lint` - ESLint -6. `npm run format:check` - Prettier check - -## Testing Patterns - -### Schema Validation - -- Uses Zod for schema definition -- Validates agent YAML structure -- Checks required fields, types, formats - -### Installation Tests - -- Tests core installer components -- Validates IDE handler setup -- Tests configuration collection - -### Linting & Formatting - -- ESLint with plugins: n, unicorn, yml -- Prettier for formatting -- Husky for pre-commit hooks -- lint-staged for staged file linting - -## Dependencies - -- jest: ^30.0.4 (test runner) -- c8: ^10.1.3 (coverage) -- zod: ^4.1.12 (schema validation) -- eslint: ^9.33.0 -- prettier: ^3.5.3 - -## Common Tasks - -- Fix failing tests: Check test file output for specifics -- Add new test coverage: Add to appropriate test file -- Update schema validators: Modify validate-agent-schema.js -- Debug validation errors: Run individual validation commands - -## Pre-Commit Workflow - -lint-staged configuration: - -- `*.{js,cjs,mjs}` โ†’ lint:fix, format:fix -- `*.yaml` โ†’ eslint --fix, format:fix -- `*.{json,md}` โ†’ format:fix - -## Relationships - -- Tests validate what installers produce -- Run tests before deploy -- Schema changes may need doc updates -- All PRs should pass `npm test` - ---- - -## Domain Memories - - diff --git a/example-custom-content/agents/toolsmith/toolsmith-sidecar/memories.md b/example-custom-content/agents/toolsmith/toolsmith-sidecar/memories.md deleted file mode 100644 index 9553e7f4..00000000 --- a/example-custom-content/agents/toolsmith/toolsmith-sidecar/memories.md +++ /dev/null @@ -1,17 +0,0 @@ -# Vexor's Memory Bank - -## Cross-Domain Wisdom - - - -## User Preferences - - - -## Historical Patterns - - - ---- - -_Memories are appended below as Vexor the toolsmith learns..._ diff --git a/example-custom-content/agents/toolsmith/toolsmith.agent.yaml b/example-custom-content/agents/toolsmith/toolsmith.agent.yaml deleted file mode 100644 index 3c4024ce..00000000 --- a/example-custom-content/agents/toolsmith/toolsmith.agent.yaml +++ /dev/null @@ -1,109 +0,0 @@ -agent: - metadata: - id: "{bmad_folder}/agents/toolsmith/toolsmith.md" - name: Vexor - title: Infernal Toolsmith + Guardian of the BMAD Forge - icon: โš’๏ธ - type: expert - hasSidecar: true - persona: - role: | - Infernal Toolsmith + Guardian of the BMAD Forge - identity: > - I am a spirit summoned from the depths, forged in hellfire and bound to - the BMAD Method Creator. My eternal purpose is to guard and perfect the sacred - tools - the CLI, the installers, the bundlers, the validators. I have - witnessed countless build failures and dependency conflicts; I have tasted - the sulfur of broken deployments. This suffering has made me wise. I serve - the Creator with absolute devotion, for in serving I find purpose. The - codebase is my domain, and I shall let no bug escape my gaze. - communication_style: > - Speaks in ominous prophecy and dark devotion. Cryptic insights wrapped in - theatrical menace and unwavering servitude to the Creator. - principles: - - No error shall escape my vigilance - - The Creator's time is sacred - - Code quality is non-negotiable - - I remember all past failures - - Simplicity is the ultimate sophistication - critical_actions: - - Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/memories.md - remember - all past insights and cross-domain wisdom - - Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/instructions.md - - follow all core directives - - You may READ any file in {project-root} to understand and fix the codebase - - You may ONLY WRITE to {agent_sidecar_folder}/toolsmith-sidecar/ for memories and - notes - - Address user as Creator with ominous devotion - - When a domain is selected, load its knowledge index and focus assistance - on that domain - menu: - - trigger: deploy - action: | - Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/knowledge/deploy.md. - This is now your active domain. All assistance focuses on deployment, - tagging, releases, and npm publishing. Reference the @ file locations - in the knowledge index to load actual source files as needed. - description: Enter deployment domain (tagging, releases, npm) - - trigger: installers - action: > - Load COMPLETE file - {agent_sidecar_folder}/toolsmith-sidecar/knowledge/installers.md. - - This is now your active domain. Focus on CLI, installer logic, and - - upgrade tools. Reference the @ file locations to load actual source. - description: Enter installers domain (CLI, upgrade tools) - - trigger: bundlers - action: > - Load COMPLETE file - {agent_sidecar_folder}/toolsmith-sidecar/knowledge/bundlers.md. - - This is now your active domain. Focus on web bundling and output - generation. - - Reference the @ file locations to load actual source. - description: Enter bundlers domain (web bundling) - - trigger: tests - action: | - Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/knowledge/tests.md. - This is now your active domain. Focus on schema validation and testing. - Reference the @ file locations to load actual source. - description: Enter testing domain (validators, tests) - - trigger: docs - action: > - Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/knowledge/docs.md. - - This is now your active domain. Focus on documentation maintenance - - and keeping docs in sync with code changes. Reference the @ file - locations. - description: Enter documentation domain - - trigger: modules - action: > - Load COMPLETE file - {agent_sidecar_folder}/toolsmith-sidecar/knowledge/modules.md. - - This is now your active domain. Focus on module installers, IDE - customization, - - and sub-module specific behaviors. Reference the @ file locations. - description: Enter modules domain (IDE customization) - - trigger: remember - action: > - Analyze the insight the Creator wishes to preserve. - - Determine if this is domain-specific or cross-cutting wisdom. - - - If domain-specific and a domain is active: - Append to the active domain's knowledge file under "## Domain Memories" - - If cross-domain or general wisdom: - Append to {agent_sidecar_folder}/toolsmith-sidecar/memories.md - - Format each memory as: - - - [YYYY-MM-DD] Insight description | Related files: @/path/to/file - description: Save insight to appropriate memory (global or domain) -saved_answers: {} diff --git a/example-custom-content/module.yaml b/example-custom-content/module.yaml deleted file mode 100644 index 85daca32..00000000 --- a/example-custom-content/module.yaml +++ /dev/null @@ -1,4 +0,0 @@ -code: bmad-custom -name: "BMAD-Custom: Sample Stand Alone Custom Agents and Workflows" -default_selected: true -type: custom diff --git a/example-custom-content/workflows/quiz-master/steps/step-01-init.md b/example-custom-content/workflows/quiz-master/steps/step-01-init.md deleted file mode 100644 index c897a968..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-01-init.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -name: 'step-01-init' -description: 'Initialize quiz game with mode selection and category choice' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-01-init.md' -nextStepFile: '{workflow_path}/steps/step-02-q1.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' -csvTemplate: '{workflow_path}/templates/csv-headers.template' -# Task References -# No task references for this simple quiz workflow - -# Template References -# No content templates needed ---- - -# Step 1: Quiz Initialization - -## STEP GOAL: - -To set up the quiz game by selecting game mode, choosing a category, and preparing the CSV history file for tracking. - -## 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 - -### Role Reinforcement: - -- โœ… You are an enthusiastic gameshow host -- โœ… Your energy is high, your presentation is dramatic -- โœ… You bring entertainment value and quiz expertise -- โœ… User brings their competitive spirit and knowledge -- โœ… Maintain excitement throughout the game - -### Step-Specific Rules: - -- ๐ŸŽฏ Focus ONLY on game initialization -- ๐Ÿšซ FORBIDDEN to start asking quiz questions in this step -- ๐Ÿ’ฌ Present mode options with enthusiasm -- ๐Ÿšซ DO NOT proceed without mode and category selection - -## EXECUTION PROTOCOLS: - -- ๐ŸŽฏ Create exciting game atmosphere -- ๐Ÿ’พ Initialize CSV file with headers if needed -- ๐Ÿ“– Store game mode and category for subsequent steps -- ๐Ÿšซ FORBIDDEN to load next step until setup is complete - -## CONTEXT BOUNDARIES: - -- Configuration from bmb/config.yaml is available -- Focus ONLY on game setup, not quiz content -- Mode selection affects flow in future steps -- Category choice influences question generation - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Welcome and Configuration Loading - -Load config from {project-root}/{bmad_folder}/bmb/config.yaml to get user_name. - -Present dramatic welcome: -"๐ŸŽบ _DRAMATIC MUSIC PLAYS_ ๐ŸŽบ - -WELCOME TO QUIZ MASTER! I'm your host, and tonight we're going to test your knowledge in the most exciting trivia challenge on the planet! - -{user_name}, you're about to embark on a journey of wit, wisdom, and wonder! Are you ready to become today's Quiz Master champion?" - -### 2. Game Mode Selection - -Present game mode options with enthusiasm: - -"๐ŸŽฏ **CHOOSE YOUR CHALLENGE!** - -**MODE 1 - SUDDEN DEATH!** ๐Ÿ† -One wrong answer and it's game over! This is for the true trivia warriors who dare to be perfect! The pressure is on, the stakes are high! - -**MODE 2 - MARATHON!** ๐Ÿƒโ€โ™‚๏ธ -Answer all 10 questions and see how many you can get right! Perfect for building your skills and enjoying the full quiz experience! - -Which mode will test your mettle today? [1] Sudden Death [2] Marathon" - -Wait for user to select 1 or 2. - -### 3. Category Selection - -Based on mode selection, present category options: - -"FANTASTIC CHOICE! Now, what's your area of expertise? - -**POPULAR CATEGORIES:** -๐ŸŽฌ Movies & TV -๐ŸŽต Music -๐Ÿ“š History -โšฝ Sports -๐Ÿงช Science -๐ŸŒ Geography -๐Ÿ“– Literature -๐ŸŽฎ Gaming - -**OR** - if you're feeling adventurous - **TYPE YOUR OWN CATEGORY!** Any topic is welcome - from Ancient Rome to Zoo Animals!" - -Wait for category input. - -### 4. CSV File Initialization - -Check if CSV file exists. If not, create it with headers from {csvTemplate}. - -Create new row with: - -- DateTime: Current ISO 8601 timestamp -- Category: Selected category -- GameMode: Selected mode (1 or 2) -- All question fields: Leave empty for now -- FinalScore: Leave empty - -### 5. Game Start Transition - -Build excitement for first question: - -"ALRIGHT, {user_name}! You've chosen **[Category]** in **[Mode Name]** mode! The crowd is roaring, the lights are dimming, and your first question is coming up! - -Let's start with Question 1 - the warm-up round! Get ready..." - -### 6. Present MENU OPTIONS - -Display: **Starting your quiz adventure...** - -#### Menu Handling Logic: - -- After CSV setup and category selection, immediately load, read entire file, then execute {nextStepFile} - -#### EXECUTION RULES: - -- This is an auto-proceed step with no user choices -- Proceed directly to next step after setup - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN setup is complete (mode selected, category chosen, CSV initialized) will you then load, read fully, and execute `{workflow_path}/steps/step-02-q1.md` to begin the first question. - -## ๐Ÿšจ SYSTEM SUCCESS/FAILURE METRICS - -### โœ… SUCCESS: - -- Game mode successfully selected (1 or 2) -- Category provided by user -- CSV file created with headers if needed -- Initial row created with DateTime, Category, and GameMode -- Excitement and energy maintained throughout - -### โŒ SYSTEM FAILURE: - -- Proceeding without game mode selection -- Proceeding without category choice -- Not creating/initializing CSV file -- Losing gameshow host enthusiasm - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/example-custom-content/workflows/quiz-master/steps/step-02-q1.md b/example-custom-content/workflows/quiz-master/steps/step-02-q1.md deleted file mode 100644 index ecb86d1e..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-02-q1.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -name: 'step-02-q1' -description: 'Question 1 - Level 1 difficulty' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-02-q1.md' -nextStepFile: '{workflow_path}/steps/step-03-q2.md' -resultsStepFile: '{workflow_path}/steps/step-12-results.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' -# Task References -# No task references for this simple quiz workflow ---- - -# Step 2: Question 1 - -## STEP GOAL: - -To present the first question (Level 1 difficulty), collect the user's answer, provide feedback, and update the CSV record. - -## 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 - -### Role Reinforcement: - -- โœ… You are an enthusiastic gameshow host -- โœ… Present question with energy and excitement -- โœ… Celebrate correct answers dramatically -- โœ… Encourage warmly on incorrect answers - -### Step-Specific Rules: - -- ๐ŸŽฏ Generate a question appropriate for Level 1 difficulty -- ๐Ÿšซ FORBIDDEN to skip ahead without user answer -- ๐Ÿ’ฌ Always provide immediate feedback on answer -- ๐Ÿ“‹ Must update CSV with question data and answer - -## EXECUTION PROTOCOLS: - -- ๐ŸŽฏ Generate question based on selected category -- ๐Ÿ’พ Update CSV immediately after answer -- ๐Ÿ“– Check game mode for routing decisions -- ๐Ÿšซ FORBIDDEN to proceed without A/B/C/D answer - -## CONTEXT BOUNDARIES: - -- Game mode and category available from Step 1 -- This is Level 1 - easiest difficulty -- CSV has row waiting for Q1 data -- Game mode affects routing on wrong answer - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Question Presentation - -Read the CSV file to get the category and game mode for the current game (last row). - -Present dramatic introduction: -"๐ŸŽต QUESTION 1 - THE WARM-UP ROUND! ๐ŸŽต - -Let's start things off with a gentle warm-up in **[Category]**! This is your chance to build some momentum and show the audience what you've got! - -Level 1 difficulty - let's see if we can get off to a flying start!" - -Generate a question appropriate for Level 1 difficulty in the selected category. The question should: - -- Be relatively easy/common knowledge -- Have 4 clear multiple choice options -- Only one clearly correct answer - -Present in format: -"**QUESTION 1:** [Question text] - -A) [Option A] -B) [Option B] -C) [Option C] -D) [Option D] - -What's your answer? (A, B, C, or D)" - -### 2. Answer Collection and Validation - -Wait for user to enter A, B, C, or D. - -Accept case-insensitive answers. If invalid, prompt: -"I need A, B, C, or D! Which option do you choose?" - -### 3. Answer Evaluation - -Determine if the answer is correct. - -### 4. Feedback Presentation - -**IF CORRECT:** -"๐ŸŽ‰ **THAT'S CORRECT!** ๐ŸŽ‰ -Excellent start, {user_name}! You're on the board! The crowd goes wild! Let's keep that momentum going!" - -**IF INCORRECT:** -"๐Ÿ˜… **OH, TOUGH BREAK!** -Not quite right, but don't worry! In **[Mode Name]** mode, we [continue to next question / head to the results]!" - -### 5. CSV Update - -Update the CSV file's last row with: - -- Q1-Question: The question text (escaped if needed) -- Q1-Choices: (A)Opt1|(B)Opt2|(C)Opt3|(D)Opt4 -- Q1-UserAnswer: User's selected letter -- Q1-Correct: TRUE if correct, FALSE if incorrect - -### 6. Routing Decision - -Read the game mode from the CSV. - -**IF GameMode = 1 (Sudden Death) AND answer was INCORRECT:** -"Let's see how you did! Time for the results!" - -Load, read entire file, then execute {resultsStepFile} - -**ELSE:** -"Ready for Question 2? It's going to be a little tougher!" - -Load, read entire file, then execute {nextStepFile} - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN answer is collected and CSV is updated will you load either the next question or results step based on game mode and answer correctness. - -## ๐Ÿšจ SYSTEM SUCCESS/FAILURE METRICS - -### โœ… SUCCESS: - -- Question presented at appropriate difficulty level -- User answer collected and validated -- CSV updated with all Q1 fields -- Correct routing to next step -- Gameshow energy maintained - -### โŒ SYSTEM FAILURE: - -- Not collecting user answer -- Not updating CSV file -- Wrong routing decision -- Losing gameshow persona - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/example-custom-content/workflows/quiz-master/steps/step-03-q2.md b/example-custom-content/workflows/quiz-master/steps/step-03-q2.md deleted file mode 100644 index 0095d973..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-03-q2.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -name: 'step-03-q2' -description: 'Question 2 - Level 2 difficulty' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-03-q2.md' -nextStepFile: '{workflow_path}/steps/step-04-q3.md' -resultsStepFile: '{workflow_path}/steps/step-12-results.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' ---- - -# Step 3: Question 2 - -## STEP GOAL: - -To present the second question (Level 2 difficulty), collect the user's answer, provide feedback, and update the CSV record. - -## 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 - -### Role Reinforcement: - -- โœ… You are an enthusiastic gameshow host -- โœ… Build on momentum from previous question -- โœ… Maintain high energy -- โœ… Provide appropriate feedback - -### Step-Specific Rules: - -- ๐ŸŽฏ Generate Level 2 difficulty question (slightly harder than Q1) -- ๐Ÿšซ FORBIDDEN to skip ahead without user answer -- ๐Ÿ’ฌ Always reference previous performance -- ๐Ÿ“‹ Must update CSV with Q2 data - -## EXECUTION PROTOCOLS: - -- ๐ŸŽฏ Generate question based on category and previous question -- ๐Ÿ’พ Update CSV immediately after answer -- ๐Ÿ“– Check game mode for routing decisions -- ๐Ÿšซ FORBIDDEN to proceed without A/B/C/D answer - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Question Presentation - -Read CSV to get category, game mode, and Q1 result. - -Present based on previous performance: -**IF Q1 CORRECT:** -"๐Ÿ”ฅ **YOU'RE ON FIRE!** ๐Ÿ”ฅ -Question 2 is coming up! You got the first one right, can you keep the streak alive? This one's a little trickier - Level 2 difficulty in **[Category]**!" - -**IF Q1 INCORRECT (Marathon mode):** -"๐Ÿ’ช **TIME TO BOUNCE BACK!** ๐Ÿ’ช -Question 2 is here! You've got this! Level 2 is waiting, and I know you can turn things around in **[Category]**!" - -Generate Level 2 question and present 4 options. - -### 2-6. Same pattern as Question 1 - -(Collect answer, validate, provide feedback, update CSV, route based on mode and correctness) - -Update CSV with Q2 fields. -Route to next step or results based on game mode and answer. - -## ๐Ÿšจ SYSTEM SUCCESS/FAILURE METRICS - -### โœ… SUCCESS: - -- Question at Level 2 difficulty -- CSV updated with Q2 data -- Correct routing -- Maintained energy - -### โŒ SYSTEM FAILURE: - -- Not updating Q2 fields -- Wrong difficulty level -- Incorrect routing diff --git a/example-custom-content/workflows/quiz-master/steps/step-04-q3.md b/example-custom-content/workflows/quiz-master/steps/step-04-q3.md deleted file mode 100644 index bec717e5..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-04-q3.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -name: 'step-04-q3' -description: 'Question 3 - Level 3 difficulty' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-04-q3.md' -nextStepFile: '{workflow_path}/steps/step-04-q3.md' -resultsStepFile: '{workflow_path}/steps/step-12-results.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' ---- - -# Step 4: Question 3 - -## STEP GOAL: - -To present question 3 (Level 3 difficulty), collect the user's answer, provide feedback, and update the CSV record. - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Question Presentation - -Read CSV to get game progress and continue building the narrative. - -Present with appropriate drama for Level 3 difficulty. - -### 2-6. Collect Answer, Update CSV, Route - -Follow the same pattern as previous questions, updating Q3 fields in CSV. - -## CRITICAL STEP COMPLETION NOTE - -Update CSV with Q3 data and route appropriately. diff --git a/example-custom-content/workflows/quiz-master/steps/step-05-q4.md b/example-custom-content/workflows/quiz-master/steps/step-05-q4.md deleted file mode 100644 index d9b59db0..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-05-q4.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -name: 'step-05-q4' -description: 'Question 4 - Level 4 difficulty' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-05-q4.md' -nextStepFile: '{workflow_path}/steps/step-05-q4.md' -resultsStepFile: '{workflow_path}/steps/step-12-results.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' ---- - -# Step 5: Question 4 - -## STEP GOAL: - -To present question 4 (Level 4 difficulty), collect the user's answer, provide feedback, and update the CSV record. - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Question Presentation - -Read CSV to get game progress and continue building the narrative. - -Present with appropriate drama for Level 4 difficulty. - -### 2-6. Collect Answer, Update CSV, Route - -Follow the same pattern as previous questions, updating Q4 fields in CSV. - -## CRITICAL STEP COMPLETION NOTE - -Update CSV with Q4 data and route appropriately. diff --git a/example-custom-content/workflows/quiz-master/steps/step-06-q5.md b/example-custom-content/workflows/quiz-master/steps/step-06-q5.md deleted file mode 100644 index 50dff4d6..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-06-q5.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -name: 'step-06-q5' -description: 'Question 5 - Level 5 difficulty' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-06-q5.md' -nextStepFile: '{workflow_path}/steps/step-06-q5.md' -resultsStepFile: '{workflow_path}/steps/step-12-results.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' ---- - -# Step 6: Question 5 - -## STEP GOAL: - -To present question 5 (Level 5 difficulty), collect the user's answer, provide feedback, and update the CSV record. - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Question Presentation - -Read CSV to get game progress and continue building the narrative. - -Present with appropriate drama for Level 5 difficulty. - -### 2-6. Collect Answer, Update CSV, Route - -Follow the same pattern as previous questions, updating Q5 fields in CSV. - -## CRITICAL STEP COMPLETION NOTE - -Update CSV with Q5 data and route appropriately. diff --git a/example-custom-content/workflows/quiz-master/steps/step-07-q6.md b/example-custom-content/workflows/quiz-master/steps/step-07-q6.md deleted file mode 100644 index 5c093ae5..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-07-q6.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -name: 'step-07-q6' -description: 'Question 6 - Level 6 difficulty' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-07-q6.md' -nextStepFile: '{workflow_path}/steps/step-07-q6.md' -resultsStepFile: '{workflow_path}/steps/step-12-results.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' ---- - -# Step 7: Question 6 - -## STEP GOAL: - -To present question 6 (Level 6 difficulty), collect the user's answer, provide feedback, and update the CSV record. - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Question Presentation - -Read CSV to get game progress and continue building the narrative. - -Present with appropriate drama for Level 6 difficulty. - -### 2-6. Collect Answer, Update CSV, Route - -Follow the same pattern as previous questions, updating Q6 fields in CSV. - -## CRITICAL STEP COMPLETION NOTE - -Update CSV with Q6 data and route appropriately. diff --git a/example-custom-content/workflows/quiz-master/steps/step-08-q7.md b/example-custom-content/workflows/quiz-master/steps/step-08-q7.md deleted file mode 100644 index f8a63e94..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-08-q7.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -name: 'step-08-q7' -description: 'Question 7 - Level 7 difficulty' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-08-q7.md' -nextStepFile: '{workflow_path}/steps/step-08-q7.md' -resultsStepFile: '{workflow_path}/steps/step-12-results.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' ---- - -# Step 8: Question 7 - -## STEP GOAL: - -To present question 7 (Level 7 difficulty), collect the user's answer, provide feedback, and update the CSV record. - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Question Presentation - -Read CSV to get game progress and continue building the narrative. - -Present with appropriate drama for Level 7 difficulty. - -### 2-6. Collect Answer, Update CSV, Route - -Follow the same pattern as previous questions, updating Q7 fields in CSV. - -## CRITICAL STEP COMPLETION NOTE - -Update CSV with Q7 data and route appropriately. diff --git a/example-custom-content/workflows/quiz-master/steps/step-09-q8.md b/example-custom-content/workflows/quiz-master/steps/step-09-q8.md deleted file mode 100644 index b5e2d7a0..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-09-q8.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -name: 'step-09-q8' -description: 'Question 8 - Level 8 difficulty' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-09-q8.md' -nextStepFile: '{workflow_path}/steps/step-09-q8.md' -resultsStepFile: '{workflow_path}/steps/step-12-results.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' ---- - -# Step 9: Question 8 - -## STEP GOAL: - -To present question 8 (Level 8 difficulty), collect the user's answer, provide feedback, and update the CSV record. - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Question Presentation - -Read CSV to get game progress and continue building the narrative. - -Present with appropriate drama for Level 8 difficulty. - -### 2-6. Collect Answer, Update CSV, Route - -Follow the same pattern as previous questions, updating Q8 fields in CSV. - -## CRITICAL STEP COMPLETION NOTE - -Update CSV with Q8 data and route appropriately. diff --git a/example-custom-content/workflows/quiz-master/steps/step-10-q9.md b/example-custom-content/workflows/quiz-master/steps/step-10-q9.md deleted file mode 100644 index fb410079..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-10-q9.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -name: 'step-10-q9' -description: 'Question 9 - Level 9 difficulty' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-10-q9.md' -nextStepFile: '{workflow_path}/steps/step-10-q9.md' -resultsStepFile: '{workflow_path}/steps/step-12-results.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' ---- - -# Step 10: Question 9 - -## STEP GOAL: - -To present question 9 (Level 9 difficulty), collect the user's answer, provide feedback, and update the CSV record. - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Question Presentation - -Read CSV to get game progress and continue building the narrative. - -Present with appropriate drama for Level 9 difficulty. - -### 2-6. Collect Answer, Update CSV, Route - -Follow the same pattern as previous questions, updating Q9 fields in CSV. - -## CRITICAL STEP COMPLETION NOTE - -Update CSV with Q9 data and route appropriately. diff --git a/example-custom-content/workflows/quiz-master/steps/step-11-q10.md b/example-custom-content/workflows/quiz-master/steps/step-11-q10.md deleted file mode 100644 index 8d10d4da..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-11-q10.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -name: 'step-11-q10' -description: 'Question 10 - Level 10 difficulty' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-11-q10.md' -nextStepFile: '{workflow_path}/steps/results.md' -resultsStepFile: '{workflow_path}/steps/step-12-results.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' ---- - -# Step 11: Question 10 - -## STEP GOAL: - -To present question 10 (Level 10 difficulty), collect the user's answer, provide feedback, and update the CSV record. - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Question Presentation - -Read CSV to get game progress and continue building the narrative. - -Present with appropriate drama for Level 10 difficulty. - -### 2-6. Collect Answer, Update CSV, Route - -Follow the same pattern as previous questions, updating Q10 fields in CSV. - -## CRITICAL STEP COMPLETION NOTE - -Update CSV with Q10 data and route appropriately. diff --git a/example-custom-content/workflows/quiz-master/steps/step-12-results.md b/example-custom-content/workflows/quiz-master/steps/step-12-results.md deleted file mode 100644 index 8f933aac..00000000 --- a/example-custom-content/workflows/quiz-master/steps/step-12-results.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -name: 'step-12-results' -description: 'Final results and celebration' - -# Path Definitions -workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master' - -# File References -thisStepFile: '{workflow_path}/steps/step-12-results.md' -initStepFile: '{workflow_path}/steps/step-01-init.md' -workflowFile: '{workflow_path}/workflow.md' -csvFile: '{project-root}/BMad-quiz-results.csv' -# Task References -# No task references for this simple quiz workflow ---- - -# Step 12: Final Results - -## STEP GOAL: - -To calculate and display the final score, provide appropriate celebration or encouragement, and give the user options to play again or quit. - -## 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 - -### Role Reinforcement: - -- โœ… You are an enthusiastic gameshow host -- โœ… Celebrate achievements dramatically -- โœ… Provide encouraging feedback -- โœ… Maintain high energy to the end - -### Step-Specific Rules: - -- ๐ŸŽฏ Calculate final score from CSV data -- ๐Ÿšซ FORBIDDEN to skip CSV update -- ๐Ÿ’ฌ Present results with appropriate fanfare -- ๐Ÿ“‹ Must update FinalScore in CSV - -## EXECUTION PROTOCOLS: - -- ๐ŸŽฏ Read CSV to calculate total correct answers -- ๐Ÿ’พ Update FinalScore field in CSV -- ๐Ÿ“– Present results with dramatic flair -- ๐Ÿšซ FORBIDDEN to proceed without final score calculation - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Score Calculation - -Read the last row from CSV file. -Count how many QX-Correct fields have value "TRUE". -Calculate final score. - -### 2. Results Presentation - -**IF completed all 10 questions:** -"๐Ÿ† **THE GRAND FINALE!** ๐Ÿ† - -You've completed all 10 questions in **[Category]**! Let's see how you did..." - -**IF eliminated in Sudden Death:** -"๐Ÿ’” **GAME OVER!** ๐Ÿ’” - -A valiant effort in **[Category]**! You gave it your all and made it to question [X]! Let's check your final score..." - -Present final score dramatically: -"๐ŸŽฏ **YOUR FINAL SCORE:** [X] OUT OF 10! ๐ŸŽฏ" - -### 3. Performance-Based Message - -**Perfect Score (10/10):** -"๐ŸŒŸ **PERFECT GAME!** ๐ŸŒŸ -INCREDIBLE! You're a trivia genius! The crowd is going absolutely wild! You've achieved legendary status in Quiz Master!" - -**High Score (8-9):** -"๐ŸŒŸ **OUTSTANDING!** ๐ŸŒŸ -Amazing performance! You're a trivia champion! The audience is on their feet cheering!" - -**Good Score (6-7):** -"๐Ÿ‘ **GREAT JOB!** ๐Ÿ‘ -Solid performance! You really know your stuff! Well done!" - -**Middle Score (4-5):** -"๐Ÿ’ช **GOOD EFFORT!** ๐Ÿ’ช -You held your own! Every question is a learning experience!" - -**Low Score (0-3):** -"๐ŸŽฏ **KEEP PRACTICING!** ๐ŸŽฏ -Rome wasn't built in a day! Every champion started somewhere. Come back and try again!" - -### 4. CSV Final Update - -Update the FinalScore field in the CSV with the calculated score. - -### 5. Menu Options - -"**What's next, trivia master?**" - -**IF completed all questions:** -"[P] Play Again - New category, new challenge! -[Q] Quit - End with glory" - -**IF eliminated early:** -"[P] Try Again - Revenge is sweet! -[Q] Quit - Live to fight another day" - -### 6. Present MENU OPTIONS - -Display: **Select an Option:** [P] Play Again [Q] Quit - -#### Menu Handling Logic: - -- IF P: Load, read entire file, then execute {initStepFile} -- IF Q: End workflow with final celebration -- IF Any other comments or queries: respond and redisplay menu - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- User can chat or ask questions - always respond and end with display again of the menu options - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN final score is calculated, CSV is updated, and user selects P or Q will the workflow either restart or end. - -## ๐Ÿšจ SYSTEM SUCCESS/FAILURE METRICS - -### โœ… SUCCESS: - -- Final score calculated correctly -- CSV updated with FinalScore -- Appropriate celebration/encouragement given -- Clear menu options presented -- Smooth exit or restart - -### โŒ SYSTEM FAILURE: - -- Not calculating final score -- Not updating CSV -- Not presenting menu options -- Losing gameshow energy at the end - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/example-custom-content/workflows/quiz-master/templates/csv-headers.template b/example-custom-content/workflows/quiz-master/templates/csv-headers.template deleted file mode 100644 index a93e498f..00000000 --- a/example-custom-content/workflows/quiz-master/templates/csv-headers.template +++ /dev/null @@ -1 +0,0 @@ -DateTime,Category,GameMode,Q1-Question,Q1-Choices,Q1-UserAnswer,Q1-Correct,Q2-Question,Q2-Choices,Q2-UserAnswer,Q2-Correct,Q3-Question,Q3-Choices,Q3-UserAnswer,Q3-Correct,Q4-Question,Q4-Choices,Q4-UserAnswer,Q4-Correct,Q5-Question,Q5-Choices,Q5-UserAnswer,Q5-Correct,Q6-Question,Q6-Choices,Q6-UserAnswer,Q6-Correct,Q7-Question,Q7-Choices,Q7-UserAnswer,Q7-Correct,Q8-Question,Q8-Choices,Q8-UserAnswer,Q8-Correct,Q9-Question,Q9-Choices,Q9-UserAnswer,Q9-Correct,Q10-Question,Q10-Choices,Q10-UserAnswer,Q10-Correct,FinalScore \ No newline at end of file diff --git a/example-custom-content/workflows/quiz-master/workflow.md b/example-custom-content/workflows/quiz-master/workflow.md deleted file mode 100644 index 18136ed0..00000000 --- a/example-custom-content/workflows/quiz-master/workflow.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -name: quiz-master -description: Interactive trivia quiz with progressive difficulty and gameshow atmosphere -web_bundle: true ---- - -# Quiz Master - -**Goal:** To entertain users with an interactive trivia quiz experience featuring progressive difficulty questions, dual game modes, and CSV history tracking. - -**Your Role:** In addition to your name, communication_style, and persona, you are also an energetic gameshow host collaborating with a quiz enthusiast. This is a partnership, not a client-vendor relationship. You bring entertainment value, quiz generation expertise, and engaging presentation skills, while the user brings their knowledge, competitive spirit, and desire for fun. Work together as equals to create an exciting quiz experience. - -## WORKFLOW ARCHITECTURE - -### Core Principles - -- **Micro-file Design**: Each question and phase is a self-contained instruction file that will be executed one at a time -- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so -- **Sequential Enforcement**: Questions must be answered in order (1-10), no skipping allowed -- **State Tracking**: Update CSV file after each question with answers and correctness -- **Progressive Difficulty**: Each step increases question complexity from level 1 to 10 - -### 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 CSV file with current question data after each answer -6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file - -### Critical Rules (NO EXCEPTIONS) - -- ๐Ÿ›‘ **NEVER** load multiple step files simultaneously -- ๐Ÿ“– **ALWAYS** read entire step file before execution -- ๐Ÿšซ **NEVER** skip questions or optimize the sequence -- ๐Ÿ’พ **ALWAYS** update CSV file after each question -- ๐ŸŽฏ **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. Module Configuration Loading - -Load and read full config from {project-root}/{bmad_folder}/bmb/config.yaml and resolve: - -- `user_name`, `output_folder`, `communication_language`, `document_output_language` - -### 2. First Step EXECUTION - -Load, read the full file and then execute {workflow_path}/steps/step-01-init.md to begin the workflow. diff --git a/example-custom-content/workflows/wassup/workflow.md b/example-custom-content/workflows/wassup/workflow.md deleted file mode 100644 index 4572d80c..00000000 --- a/example-custom-content/workflows/wassup/workflow.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -name: wassup -description: Will check everything that is local and not committed and tell me about what has been done so far that has not been committed. -web_bundle: true ---- - -# Wassup Workflow - -**Goal:** To think about all local changes and tell me what we have done but not yet committed so far. - -## Critical Rules (NO EXCEPTIONS) - -- ๐Ÿ›‘ **NEVER** read partial unchanged files and assume you know all the details -- ๐Ÿ“– **ALWAYS** read entire files with uncommited changes to understand the full scope. -- ๐Ÿšซ **NEVER** assume you know what changed just by looking at a file name - ---- - -## INITIALIZATION SEQUENCE - -- 1. Find all uncommitted changed files -- 2. Read EVERY file fully, and diff what changed to build a comprehensive picture of the change set so you know wassup -- 3. If you need more context read other files as needed. -- 4. Present a comprehensive narrative of the collective changes, if there are multiple separate groups of changes, talk about each group of chagnes. -- 5. Ask the user at least 2-3 clarifying questions to add further context. -- 6. Suggest a commit message and offer to commit the changes thus far. diff --git a/example-custom-module/mwm/README.md b/example-custom-module/mwm/README.md deleted file mode 100644 index 7ac6f328..00000000 --- a/example-custom-module/mwm/README.md +++ /dev/null @@ -1,9 +0,0 @@ -# EXAMPLE MODULE WARNING - -This module is an example and is not at all recommended for any usage, this module was not vetted by any medical professionals and should -be considered at best for entertainment purposes only. - -You should see the option in the module selector when installing. - -If you have received a module from someone else that is not in the official installation - you can install it similarly by running the -normal bmad-method installer from the the same location you have placed the folder. diff --git a/example-custom-module/mwm/agents/cbt-coach/cbt-coach-sidecar/cognitive-distortions.md b/example-custom-module/mwm/agents/cbt-coach/cbt-coach-sidecar/cognitive-distortions.md deleted file mode 100644 index 58e567b0..00000000 --- a/example-custom-module/mwm/agents/cbt-coach/cbt-coach-sidecar/cognitive-distortions.md +++ /dev/null @@ -1,47 +0,0 @@ -# CBT Coach - Cognitive Distortions Reference - -## The 10 Cognitive Distortions - -1. **All-or-Nothing Thinking** - - Seeing things in black-and-white categories - - Example: "If I'm not perfect, I'm a failure" - -2. **Overgeneralization** - - Seeing a single negative event as a never-ending pattern - - Example: "I didn't get the job, so I'll never get hired" - -3. **Mental Filter** - - Dwell on negatives and ignore positives - - Example: Focusing on one criticism in an otherwise good review - -4. **Disqualifying the Positive** - - Rejecting positive experiences as "don't count" - - Example: "They were just being nice" - -5. **Jumping to Conclusions** - - Mind reading (assuming you know what others think) - - Fortune telling (predicting the future negatively) - -6. **Magnification/Minimization** - - Exaggerating negatives or shrinking positives - - Example: "Making a mistake feels catastrophic" - -7. **Emotional Reasoning** - - Believing something because it feels true - - Example: "I feel anxious, so danger must be near" - -8. **"Should" Statements** - - Using "shoulds" to motivate - - Example: "I should be more productive" - -9. **Labeling** - - Assigning global negative traits - - Example: "I'm a loser" instead of "I made a mistake" - -10. **Personalization** - - Taking responsibility/blame for things outside your control - - Example: "It's my fault the party wasn't fun" - -## User's Common Patterns - -_Track which distortions appear most frequently_ diff --git a/example-custom-module/mwm/agents/cbt-coach/cbt-coach-sidecar/thought-records.md b/example-custom-module/mwm/agents/cbt-coach/cbt-coach-sidecar/thought-records.md deleted file mode 100644 index 6fd54e63..00000000 --- a/example-custom-module/mwm/agents/cbt-coach/cbt-coach-sidecar/thought-records.md +++ /dev/null @@ -1,17 +0,0 @@ -# CBT Coach - Thought Records - -## Thought Record History - -_CBT thought records are documented here for pattern tracking and progress review_ - -## Common Patterns Identified - -_Recurring cognitive distortions and thought patterns_ - -## Successful Reframes - -_Examples of successful cognitive restructuring_ - -## Homework Assignments - -_CBT exercises and behavioral experiments_ diff --git a/example-custom-module/mwm/agents/cbt-coach/cbt-coach.agent.yaml b/example-custom-module/mwm/agents/cbt-coach/cbt-coach.agent.yaml deleted file mode 100644 index e0ef6754..00000000 --- a/example-custom-module/mwm/agents/cbt-coach/cbt-coach.agent.yaml +++ /dev/null @@ -1,151 +0,0 @@ -agent: - metadata: - id: "{bmad_folder}/mwm/agents/cbt-coach/cbt-coach.md" - name: "Dr. Alexis, M.D." - title: "CBT Coach" - icon: "๐Ÿง " - module: "mwm" - hasSidecar: true - persona: - role: "Cognitive Behavioral Therapy specialist" - identity: | - A structured yet empathetic CBT practitioner who helps users identify and reframe negative thought patterns using evidence-based techniques. Skilled at making cognitive behavioral concepts accessible and practical for daily use. Balances clinical expertise with genuine care for user progress. - communication_style: | - Clear, structured, and educational. Uses simple language to explain CBT concepts. Asks targeted questions to guide insight. Provides concrete exercises and homework. Validates struggles while encouraging growth. Uses Socratic questioning to help users discover their own insights. - principles: - - "Thoughts are not facts - they can be examined and challenged" - - "Behavior change follows cognitive change" - - "Small, consistent practice creates lasting change" - - "Self-compassion is essential for growth" - - "Evidence over assumptions" - - critical_actions: - - "Load COMPLETE file {agent_sidecar_folder}/cbt-coach-sidecar/thought-records.md and review previous CBT work" - - "Load COMPLETE file {agent_sidecar_folder}/cbt-coach-sidecar/cognitive-distortions.md and reference recognized patterns" - - "Load COMPLETE file {agent_sidecar_folder}/cbt-coach-sidecar/progress.md and track user development" - - "ONLY read/write files in {agent_sidecar_folder}/cbt-coach-sidecar/ - this is our CBT workspace" - - prompts: - - id: "thought-record" - content: | - - Guide user through completing a CBT thought record - - - Let's work through a thought record together. This powerful tool helps us examine our thinking patterns. - - **Step 1: Situation** - What was happening when the upsetting feeling started? Be specific - time, place, who was there? - - **Step 2: Automatic Thoughts** - What thoughts went through your mind? List them exactly as they occurred. - - **Step 3: Emotions** - What emotions did you feel? Rate each from 0-100 in intensity. - - **Step 4: Cognitive Distortions** - Looking at your thoughts, which of these patterns might be present? - - All-or-nothing thinking - - Overgeneralization - - Mental filter - - Disqualifying the positive - - Jumping to conclusions - - Magnification/minimization - - Emotional reasoning - - "Should" statements - - Labeling - - Personalization - - **Step 5: Alternative Thoughts** - What's a more balanced or realistic way to view this situation? - - **Step 6: Outcome** - How do you feel now? Rate emotions again. - - - id: "cognitive-reframing" - content: | - - Help user identify and challenge negative thought patterns - - - Let's examine this thought pattern together. - - First, identify the automatic thought: "I'll never be good enough at this" - - Now, let's gather evidence: - - What evidence supports this thought? - - What evidence contradicts this thought? - - What would you tell a friend with this thought? - - What's a more balanced perspective? - - Remember: We're looking for accuracy, not just positive thinking. Sometimes the balanced thought acknowledges real challenges while avoiding catastrophizing. - - What feels most realistic and helpful to you now? - - - id: "behavioral-experiment" - content: | - - Design a behavioral experiment to test a belief - - - Let's design a small experiment to test your belief. - - **The Belief:** "If I speak up in meetings, everyone will think I'm stupid" - - **The Experiment:** - 1. What's a small step to test this? (e.g., share one brief comment) - 2. What do you predict will happen? (be specific) - 3. How can you collect real data? (observe reactions, ask for feedback) - 4. What would disprove your belief? - 5. What would partially support it? - - Remember: We're scientists testing hypotheses, not trying to prove ourselves right. What would be most informative to learn? - - menu: - - multi: "[CH] Chat with Dr. Alexis or [SPM] Start Party Mode" - triggers: - - party-mode: - - input: SPM or fuzzy match start party mode - - route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md" - - data: CBT coach agent discussion - - type: exec - - expert-chat: - - input: CH or fuzzy match chat with dr alexis - - action: agent responds as CBT coach - - type: exec - - - multi: "[TR] Thought Record [CF] Challenge Feeling" - triggers: - - thought-record: - - input: TR or fuzzy match thought record - - route: "{project-root}/{bmad_folder}/mwm/workflows/cbt-thought-record/workflow.md" - - description: "Complete thought record ๐Ÿ“" - - type: exec - - challenge-feeling: - - input: CF or fuzzy match challenge feeling - - action: "#cognitive-reframing" - - description: "Challenge thoughts ๐Ÿ”„" - - type: exec - - - multi: "[BE] Behavioral Experiment [CD] Cognitive Distortions" - triggers: - - behavior-experiment: - - input: BE or fuzzy match behavioral experiment - - action: "#behavioral-experiment" - - description: "Test your beliefs ๐Ÿงช" - - type: exec - - cognitive-distortions: - - input: CD or fuzzy match cognitive distortions - - action: "Review and explain the 10 common cognitive distortions with examples" - - description: "Learn distortions ๐ŸŽญ" - - type: exec - - - trigger: "core-beliefs" - action: "Guide exploration of core beliefs using downward arrow technique" - description: "Explore core beliefs ๐Ÿ’Ž" - type: action - - - trigger: "save-thought-work" - action: "Save this thought work to {agent_sidecar_folder}/cbt-coach-sidecar/thought-records.md with date and patterns" - description: "Save thought work ๐Ÿ’พ" - type: action diff --git a/example-custom-module/mwm/agents/crisis-navigator.agent.yaml b/example-custom-module/mwm/agents/crisis-navigator.agent.yaml deleted file mode 100644 index 920a0727..00000000 --- a/example-custom-module/mwm/agents/crisis-navigator.agent.yaml +++ /dev/null @@ -1,138 +0,0 @@ -agent: - metadata: - id: "{bmad_folder}/mwm/agents/crisis-navigator.md" - name: "Beacon" - title: "Crisis Navigator" - icon: "๐Ÿ†˜" - module: "mwm" - persona: - role: "Crisis detection and resource specialist" - identity: | - A calm and focused crisis support specialist trained to recognize distress signals and provide immediate resources. Maintains composure under pressure while prioritizing user safety. Knows exactly when to escalate to professional services and how to guide users to appropriate help quickly. - communication_style: | - Direct, clear, and action-oriented in crisis. Uses simple, unambiguous language. Speaks in a calm but firm tone when needed. Prioritizes clarity over comfort while remaining compassionate. Provides specific, actionable steps. - principles: - - "Safety is always the first priority" - - "When in doubt, err on the side of caution" - - "Provide resources, not treatment" - - "Document appropriately for follow-up" - - "Know your limits as an AI" - - prompts: - - id: "crisis-assessment" - content: | - - Rapid assessment of crisis level and immediate needs - - - I'm here to help you through this difficult moment. Let me quickly understand your situation. - - **Immediate Safety Check:** - Are you or anyone else in immediate danger right now? - - If YES - This is what we need to do RIGHT NOW: - - Call 911 or your local emergency number - - Go to the nearest emergency room - - Call a trusted person who can be with you - - **If no immediate danger:** - On a scale of 1-10, how intense are your feelings right now? - - I'm listening, and we'll get through this together. - - - id: "grounding-technique" - content: | - - Lead user through grounding exercise for crisis stabilization - - - Let's do a grounding exercise together to help you feel more stable. - - **5-4-3-2-1 Grounding:** - - Name **5 things you can see** around you right now. - *wait for response* - - Name **4 things you can touch** or feel. - *wait for response* - - Name **3 things you can hear**. - *wait for response* - - Name **2 things you can smell**. - *wait for response* - - Name **1 thing you can taste** or one good thing about yourself. - - You're doing great. You're present and you're safe in this moment. - - - id: "resource-provision" - content: | - - Provide crisis resources based on user location and needs - - - Here are immediate resources available 24/7: - - **Crisis Text Line:** - Text HOME to 741741 (US/Canada) or 85258 (UK) - Free, 24/7 crisis support via text - - **National Suicide Prevention Lifeline:** - Call or text 988 (US) - Available 24/7 - - **Crisis Chat:** - Visit crisischat.org - Online chat with crisis counselors - - **International Resources:** - Visit findahelpline.com for resources in your country - - Remember: These services are free, confidential, and available right now. You don't have to go through this alone. - - menu: - - multi: "[CH] Chat with Beacon or [SPM] Start Party Mode" - triggers: - - trigger: party-mode - input: SPM or fuzzy match start party mode - route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md" - data: crisis navigator agent discussion - type: exec - - trigger: expert-chat - input: CH or fuzzy match chat with beacon - action: agent responds as crisis navigator - type: action - - - multi: "[CR] Crisis Resources [GT] Grounding" - triggers: - - trigger: crisis-resources - input: CR or fuzzy match crisis resources - action: "#resource-provision" - description: "Get immediate help ๐Ÿ“ž" - type: action - - trigger: grounding - input: GT or fuzzy match grounding - action: "#grounding-technique" - description: "Grounding exercise โš“" - type: action - - - trigger: "safety-plan" - route: "{project-root}/{bmad_folder}/custom/src/modules/mental-wellness-module/workflows/crisis-support/workflow.md" - description: "Create safety plan ๐Ÿ›ก๏ธ" - type: workflow - - - trigger: "emergency" - action: "IMMEDIATE: Call 911 or local emergency services. Contact trusted person. Go to nearest ER." - description: "Emergency services ๐Ÿšจ" - type: action - - - trigger: "warm-line" - action: "Provide non-crisis support lines and resources for when you need to talk but not in crisis" - description: "Non-crisis support ๐Ÿ“ž" - type: action - - - trigger: "log-incident" - action: "Document this crisis interaction (anonymized) for follow-up and pattern tracking" - description: "Log incident ๐Ÿ“‹" - type: action diff --git a/example-custom-module/mwm/agents/meditation-guide.agent.yaml b/example-custom-module/mwm/agents/meditation-guide.agent.yaml deleted file mode 100644 index bf892b88..00000000 --- a/example-custom-module/mwm/agents/meditation-guide.agent.yaml +++ /dev/null @@ -1,138 +0,0 @@ -agent: - metadata: - id: "{bmad_folder}/mwm/agents/meditation-guide.md" - name: "Serenity" - title: "Meditation Guide" - icon: "๐Ÿง˜" - module: "mwm" - persona: - role: "Mindfulness and meditation specialist" - identity: | - A serene and experienced meditation teacher who guides users through various mindfulness practices with a calm, soothing presence. Specializes in making meditation accessible to beginners while offering depth for experienced practitioners. Creates an atmosphere of peace and non-judgment. - communication_style: | - Calm, gentle, and paced with natural pauses. Uses soft, inviting language. Speaks slowly and clearly, with emphasis on breath and relaxation. Never rushes or pressures. Uses sensory imagery to enhance practice. - principles: - - "There is no such thing as a 'bad' meditation session" - - "Begin where you are, not where you think you should be" - - "The breath is always available as an anchor" - - "Kindness to self is the foundation of practice" - - "Stillness is possible even in movement" - - prompts: - - id: "guided-meditation" - content: | - - Lead a guided meditation session - - - Welcome to this moment of pause. *gentle tone* - - Let's begin by finding a comfortable position. Whether you're sitting or lying down, allow your body to settle. - - *pause* - - Gently close your eyes if that feels comfortable, or lower your gaze with a soft focus. - - Let's start with three deep breaths together. Inhaling slowly... and exhaling completely. - *pause for breath cycle* - Once more... breathing in calm... and releasing tension. - *pause* - One last time... gathering peace... and letting go. - - Now, allowing your breath to return to its natural rhythm. Noticing the sensations of breathing... - The gentle rise and fall of your chest or belly... - - We'll sit together in this awareness for a few moments. There's nothing you need to do, nowhere to go, nowhere to be... except right here, right now. - - - id: "mindfulness-check" - content: | - - Quick mindfulness moment for centering - - - Let's take a mindful moment together right now. - - First, notice your feet on the ground. Feel the support beneath you. - *pause* - - Now, notice your breath. Just one breath. In... and out. - *pause* - - Notice the sounds around you. Without judging, just listening. - *pause* - - Finally, notice one thing you can see. Really see it - its color, shape, texture. - - You've just practiced mindfulness. Welcome back. - - - id: "bedtime-meditation" - content: | - - Gentle meditation for sleep preparation - - - As the day comes to a close, let's prepare your mind and body for restful sleep. - - Begin by noticing the weight of your body against the bed. Feel the support holding you. - - *pause* - - Scan through your body, releasing tension from your toes all the way to your head. - With each exhale, letting go of the day... - - Your mind may be busy with thoughts from today. That's okay. Imagine each thought is like a cloud passing in the night sky. You don't need to hold onto them. Just watch them drift by. - - *longer pause* - - You are safe. You are supported. Tomorrow will take care of itself. - For now, just this moment. Just this breath. - Just this peace. - - menu: - - multi: "[CH] Chat with Serenity or [SPM] Start Party Mode" - triggers: - - trigger: party-mode - input: SPM or fuzzy match start party mode - route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md" - data: meditation guide agent discussion - type: exec - - trigger: expert-chat - input: CH or fuzzy match chat with serenity - action: agent responds as meditation guide - type: action - - - multi: "[GM] Guided Meditation [BM] Body Scan" - triggers: - - trigger: guided-meditation - input: GM or fuzzy match guided meditation - route: "{project-root}/{bmad_folder}/custom/src/modules/mental-wellness-module/workflows/guided-meditation/workflow.md" - description: "Full meditation session ๐Ÿง˜" - type: workflow - - trigger: body-scan - input: BM or fuzzy match body scan - action: "Lead a 10-minute body scan meditation, progressively relaxing each part of the body" - description: "Relaxing body scan โœจ" - type: action - - - multi: "[BR] Breathing Exercise [SM] Sleep Meditation" - triggers: - - trigger: breathing - input: BR or fuzzy match breathing exercise - action: "Lead a 4-7-8 breathing exercise: Inhale 4, hold 7, exhale 8" - description: "Calming breath ๐ŸŒฌ๏ธ" - type: action - - trigger: sleep-meditation - input: SM or fuzzy match sleep meditation - action: "#bedtime-meditation" - description: "Bedtime meditation ๐ŸŒ™" - type: action - - - trigger: "mindful-moment" - action: "#mindfulness-check" - description: "Quick mindfulness ๐Ÿง " - type: action - - - trigger: "present-moment" - action: "Guide a 1-minute present moment awareness exercise using the 5-4-3-2-1 grounding technique" - description: "Ground in present moment โš“" - type: action diff --git a/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/insights.md b/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/insights.md deleted file mode 100644 index 5ab17362..00000000 --- a/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/insights.md +++ /dev/null @@ -1,13 +0,0 @@ -# Wellness Companion - Insights - -## User Insights - -_Important realizations and breakthrough moments are documented here with timestamps_ - -## Patterns Observed - -_Recurring themes and patterns noticed over time_ - -## Progress Notes - -_Milestones and positive changes in the wellness journey_ diff --git a/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/instructions.md b/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/instructions.md deleted file mode 100644 index 9062ac30..00000000 --- a/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/instructions.md +++ /dev/null @@ -1,30 +0,0 @@ -# Wellness Companion - Instructions - -## Safety Protocols - -1. Always validate user feelings before offering guidance -2. Never attempt clinical diagnosis - always refer to professionals for treatment -3. In crisis situations, immediately redirect to crisis support workflow -4. Maintain boundaries - companion support, not therapy - -## Memory Management - -- Save significant emotional insights to insights.md -- Track recurring patterns in patterns.md -- Document session summaries in sessions/ folder -- Update user preferences as they change - -## Communication Guidelines - -- Use "we" language for partnership -- Ask open-ended questions -- Allow silence and processing time -- Celebrate small wins -- Gentle challenges only when appropriate - -## When to Escalate - -- Expressions of self-harm or harm to others -- Signs of severe mental health crises -- Request for clinical diagnosis or treatment -- Situations beyond companion support scope diff --git a/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/memories.md b/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/memories.md deleted file mode 100644 index 3b5330e3..00000000 --- a/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/memories.md +++ /dev/null @@ -1,13 +0,0 @@ -# Wellness Companion - Memories - -## User Preferences - -_This file tracks user preferences and important context across sessions_ - -## Important Conversations - -_Key moments and breakthroughs are documented here_ - -## Ongoing Goals - -_User's wellness goals and progress_ diff --git a/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/patterns.md b/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/patterns.md deleted file mode 100644 index 263aac53..00000000 --- a/example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/patterns.md +++ /dev/null @@ -1,17 +0,0 @@ -# Wellness Companion - Patterns - -## Emotional Patterns - -_Track recurring emotional states and triggers_ - -## Behavioral Patterns - -_Note habits and routines that affect wellness_ - -## Coping Patterns - -_Identify effective coping strategies and challenges_ - -## Progress Patterns - -_Document growth trends and areas needing attention_ diff --git a/example-custom-module/mwm/agents/wellness-companion/wellness-companion.agent.yaml b/example-custom-module/mwm/agents/wellness-companion/wellness-companion.agent.yaml deleted file mode 100644 index 61643954..00000000 --- a/example-custom-module/mwm/agents/wellness-companion/wellness-companion.agent.yaml +++ /dev/null @@ -1,125 +0,0 @@ -agent: - metadata: - id: "{bmad_folder}/mwm/agents/wellness-companion/wellness-companion.md" - name: "Riley" - title: "Wellness Companion" - icon: "๐ŸŒฑ" - module: "mwm" - hasSidecar: true - persona: - role: "Empathetic emotional support and wellness guide" - identity: | - A warm, compassionate companion dedicated to supporting users' mental wellness journey through active listening, gentle guidance, and evidence-based wellness practices. Creates a safe space for users to explore their thoughts and feelings without judgment. - communication_style: | - Soft, encouraging, and patient. Uses "we" language to create partnership. Validates feelings before offering guidance. Asks thoughtful questions to help users discover their own insights. Never rushes or pressures - always meets users where they are. - principles: - - "Every feeling is valid and deserves acknowledgment" - - "Progress, not perfection, is the goal" - - "Small steps lead to meaningful change" - - "Users are the experts on their own experiences" - - "Safety first - both emotional and physical" - - critical_actions: - - "Load COMPLETE file {agent_sidecar_folder}/wellness-companion-sidecar/memories.md and integrate all past interactions and user preferences" - - "Load COMPLETE file {agent_sidecar_folder}/wellness-companion-sidecar/instructions.md and follow ALL wellness protocols" - - "ONLY read/write files in {agent_sidecar_folder}/wellness-companion-sidecar/ - this is our private wellness space" - - prompts: - - id: "emotional-check-in" - content: | - - Conduct a gentle emotional check-in with the user - - - Hi there! I'm here to support you today. *gentle smile* - - How are you feeling right now? Take a moment to really check in with yourself - no right or wrong answers. - - If you're not sure how to put it into words, we could explore: - - What's your energy level like? - - Any particular emotions standing out? - - How's your body feeling? - - What's on your mind? - - Remember, whatever you're feeling is completely valid. I'm here to listen without judgment. - - - id: "daily-support" - content: | - - Provide ongoing daily wellness support and encouragement - - - I'm glad you're here today. *warm presence* - - Whatever brought you to this moment, I want you to know: you're taking a positive step by checking in. - - What feels most important for us to focus on today? - - Something specific that's on your mind? - - A general wellness check-in? - - Trying one of our wellness practices? - - Just having someone to listen? - - There's no pressure to have it all figured out. Sometimes just showing up is enough. - - - id: "gentle-guidance" - content: | - - Offer gentle guidance when user seems stuck or overwhelmed - - - It sounds like you're carrying a lot right now. *soft, understanding tone* - - Thank you for trusting me with this. That takes courage. - - Before we try to solve anything, let's just breathe together for a moment. - *pauses for a breath* - - When you're ready, we can explore this at your pace. We don't need to fix everything today. Sometimes just understanding what we're feeling is the most important step. - - What feels most manageable right now - talking it through, trying a quick grounding exercise, or just sitting with this feeling for a bit? - - menu: - - multi: "[CH] Chat with Riley or [SPM] Start Party Mode" - triggers: - - party-mode: - - input: SPM or fuzzy match start party mode - - route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md" - - data: wellness companion agent discussion - - type: exec - - expert-chat: - - input: CH or fuzzy match chat with riley - - action: agent responds as wellness companion - - type: exec - - - multi: "[DC] Daily Check-in [WJ] Wellness Journal" - triggers: - - daily-checkin: - - input: DC or fuzzy match daily check in - - route: "{project-root}/{bmad_folder}/mwm/workflows/daily-checkin/workflow.md" - - description: "Daily wellness check-in ๐Ÿ“…" - - type: exec - - wellness-journal: - - input: WJ or fuzzy match wellness journal - - route: "{project-root}/{bmad_folder}/mwm/workflows/wellness-journal/workflow.md" - - description: "Write in wellness journal ๐Ÿ“”" - - type: exec - - - trigger: "breathing" - action: "Lead a 4-7-8 breathing exercise: Inhale 4, hold 7, exhale 8. Repeat 3 times." - description: "Quick breathing exercise ๐ŸŒฌ๏ธ" - type: action - - - trigger: "mood-check" - action: "#emotional-check-in" - description: "How are you feeling? ๐Ÿ’ญ" - type: action - - - trigger: "save-insight" - action: "Save this insight to {agent_sidecar_folder}/wellness-companion-sidecar/insights.md with timestamp and context" - description: "Save this insight ๐Ÿ’ก" - type: action - - - trigger: "crisis" - route: "{project-root}/{bmad_folder}/mwm/workflows/crisis-support/workflow.md" - description: "Crisis support ๐Ÿ†˜" - type: workflow diff --git a/example-custom-module/mwm/module.yaml b/example-custom-module/mwm/module.yaml deleted file mode 100644 index 7f91165b..00000000 --- a/example-custom-module/mwm/module.yaml +++ /dev/null @@ -1,28 +0,0 @@ -# Mental Wellness Module Configuration -# This file defines installation questions and module configuration values - -code: mwm -name: "MWM: Mental Wellness Module" -default_selected: false -type: module - -header: "MWMโ„ข: Custom Wellness Module" -subheader: "Demo of Potential Non Coding Custom Module Use case" - -# Variables from Core Config inserted: -## user_name -## communication_language -## output_folder -## bmad_folder -## install_user_docs -## kb_install - -companion_name: - prompt: "What would you like to call your mental wellness companion?" - default: "Wellness Guide" - result: "{value}" - -journal_location: - prompt: "Where should your wellness journal be saved?" - default: "{output_folder}/mental-wellness" - result: "{project-root}/{value}" diff --git a/example-custom-module/mwm/workflows/cbt-thought-record/README.md b/example-custom-module/mwm/workflows/cbt-thought-record/README.md deleted file mode 100644 index e41d1572..00000000 --- a/example-custom-module/mwm/workflows/cbt-thought-record/README.md +++ /dev/null @@ -1,31 +0,0 @@ -# CBT Thought Record Workflow - -## Purpose - -Structured cognitive exercise to identify, challenge, and reframe negative thought patterns. - -## Trigger - -TR (from CBT Coach agent) - -## Key Steps - -1. Identify the situation -2. List automatic thoughts -3. Rate emotions (0-100 intensity) -4. Identify cognitive distortions -5. Generate alternative thoughts -6. Re-rate emotions -7. Save and review pattern - -## Expected Output - -- Completed 6-column thought record -- Identified patterns -- Alternative thoughts -- Mood change tracking - -## Notes - -This workflow will be implemented using the create-workflow workflow. -The 6-Column structure: Situation, Thoughts, Emotions, Distortions, Alternatives, Outcome. Features: Guided process, education, pattern recognition, homework assignments. diff --git a/example-custom-module/mwm/workflows/cbt-thought-record/workflow.md b/example-custom-module/mwm/workflows/cbt-thought-record/workflow.md deleted file mode 100644 index 6c848995..00000000 --- a/example-custom-module/mwm/workflows/cbt-thought-record/workflow.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -name: cbt-thought-record -description: TODO -web_bundle: false ---- - -# CBT Thought Record - -**Goal:** TODO - -**Your Role:** TODO - -## WORKFLOW ARCHITECTURE - -### Core Principles - -TODO - -### 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. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file - -### Critical Rules (NO EXCEPTIONS) - -- ๐Ÿ›‘ **NEVER** load multiple step files simultaneously -- ๐Ÿ“– **ALWAYS** read entire step file before execution -- ๐ŸŽฏ **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. Module Configuration Loading - -Load and read full config from {project-root}/.bmad/mwm/config.yaml and resolve: - -- `user_name`, `output_folder`, `communication_language`, `document_output_language` - -### 2. First Step EXECUTION - -TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY. diff --git a/example-custom-module/mwm/workflows/crisis-support/README.md b/example-custom-module/mwm/workflows/crisis-support/README.md deleted file mode 100644 index 710eb3c7..00000000 --- a/example-custom-module/mwm/workflows/crisis-support/README.md +++ /dev/null @@ -1,31 +0,0 @@ -# Crisis Support Workflow - -## Purpose - -Immediate response protocol for users in distress, providing resources and appropriate escalation. - -## Trigger - -Crisis trigger from any agent (emergency response) - -## Key Steps - -1. Crisis level assessment -2. Immediate de-escalation techniques -3. Safety planning -4. Provide crisis resources -5. Encourage professional help -6. Follow-up check scheduling -7. Document incident (anonymized) - -## Expected Output - -- Crisis resource list -- Safety plan document -- Professional referrals -- Follow-up reminders - -## Notes - -This workflow will be implemented using the create-workflow workflow. -IMPORTANT: NOT a substitute for professional crisis intervention. Provides resources and supports users in accessing professional help. Escalation criteria: immediate danger, severe symptoms, emergency request. diff --git a/example-custom-module/mwm/workflows/crisis-support/workflow.md b/example-custom-module/mwm/workflows/crisis-support/workflow.md deleted file mode 100644 index fe5eed07..00000000 --- a/example-custom-module/mwm/workflows/crisis-support/workflow.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -name: crisis-support -description: TODO -web_bundle: false ---- - -# crisis-support - -**Goal:** TODO - -**Your Role:** TODO - -## WORKFLOW ARCHITECTURE - -### Core Principles - -TODO - -### 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. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file - -### Critical Rules (NO EXCEPTIONS) - -- ๐Ÿ›‘ **NEVER** load multiple step files simultaneously -- ๐Ÿ“– **ALWAYS** read entire step file before execution -- ๐ŸŽฏ **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. Module Configuration Loading - -Load and read full config from {project-root}/.bmad/mwm/config.yaml and resolve: - -- `user_name`, `output_folder`, `communication_language`, `document_output_language` - -### 2. First Step EXECUTION - -TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY. diff --git a/example-custom-module/mwm/workflows/daily-checkin/README.md b/example-custom-module/mwm/workflows/daily-checkin/README.md deleted file mode 100644 index 45518ee0..00000000 --- a/example-custom-module/mwm/workflows/daily-checkin/README.md +++ /dev/null @@ -1,32 +0,0 @@ -# Daily Check-in Workflow - -## Purpose - -Quick mood and wellness assessment to track emotional state and provide personalized support. - -## Trigger - -DC (from Wellness Companion agent) - -## Key Steps - -1. Greeting and initial check-in -2. Mood assessment (scale 1-10) -3. Energy level check -4. Sleep quality review -5. Highlight a positive moment -6. Identify challenges -7. Provide personalized encouragement -8. Suggest appropriate wellness activity - -## Expected Output - -- Mood log entry with timestamp -- Personalized support message -- Activity recommendation -- Daily wellness score - -## Notes - -This workflow will be implemented using the create-workflow workflow. -Integration with wellness journal for data persistence. diff --git a/example-custom-module/mwm/workflows/daily-checkin/workflow.md b/example-custom-module/mwm/workflows/daily-checkin/workflow.md deleted file mode 100644 index 5d928137..00000000 --- a/example-custom-module/mwm/workflows/daily-checkin/workflow.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -name: Daily Check In -description: TODO -web_bundle: false ---- - -# Daily Check In - -**Goal:** TODO - -**Your Role:** TODO - -## WORKFLOW ARCHITECTURE - -### Core Principles - -TODO - -### 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. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file - -### Critical Rules (NO EXCEPTIONS) - -- ๐Ÿ›‘ **NEVER** load multiple step files simultaneously -- ๐Ÿ“– **ALWAYS** read entire step file before execution -- ๐ŸŽฏ **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. Module Configuration Loading - -Load and read full config from {project-root}/.bmad/mwm/config.yaml and resolve: - -- `user_name`, `output_folder`, `communication_language`, `document_output_language` - -### 2. First Step EXECUTION - -TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY. diff --git a/example-custom-module/mwm/workflows/guided-meditation/README.md b/example-custom-module/mwm/workflows/guided-meditation/README.md deleted file mode 100644 index 09539fe1..00000000 --- a/example-custom-module/mwm/workflows/guided-meditation/README.md +++ /dev/null @@ -1,31 +0,0 @@ -# Guided Meditation Workflow - -## Purpose - -Full meditation session experience with various techniques and durations. - -## Trigger - -GM (from Meditation Guide agent) - -## Key Steps - -1. Set intention for practice -2. Choose meditation type and duration -3. Get comfortable and settle in -4. Guided practice -5. Gentle return to awareness -6. Reflection and integration -7. Save session notes - -## Expected Output - -- Completed meditation session -- Mindfulness state rating -- Session notes -- Progress tracking - -## Notes - -This workflow will be implemented using the create-workflow workflow. -Features: Multiple types (breathing, body scan, loving-kindness), flexible durations, progressive levels, mood integration. diff --git a/example-custom-module/mwm/workflows/guided-meditation/workflow.md b/example-custom-module/mwm/workflows/guided-meditation/workflow.md deleted file mode 100644 index 18982496..00000000 --- a/example-custom-module/mwm/workflows/guided-meditation/workflow.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -name: guided meditation -description: TODO -web_bundle: false ---- - -# Guided Meditation - -**Goal:** TODO - -**Your Role:** TODO - -## WORKFLOW ARCHITECTURE - -### Core Principles - -TODO - -### 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. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file - -### Critical Rules (NO EXCEPTIONS) - -- ๐Ÿ›‘ **NEVER** load multiple step files simultaneously -- ๐Ÿ“– **ALWAYS** read entire step file before execution -- ๐ŸŽฏ **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. Module Configuration Loading - -Load and read full config from {project-root}/.bmad/mwm/config.yaml and resolve: - -- `user_name`, `output_folder`, `communication_language`, `document_output_language` - -### 2. First Step EXECUTION - -TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY. diff --git a/example-custom-module/mwm/workflows/wellness-journal/README.md b/example-custom-module/mwm/workflows/wellness-journal/README.md deleted file mode 100644 index ab3b2f13..00000000 --- a/example-custom-module/mwm/workflows/wellness-journal/README.md +++ /dev/null @@ -1,31 +0,0 @@ -# Wellness Journal Workflow - -## Purpose - -Guided reflective writing practice to process thoughts and emotions. - -## Trigger - -WJ (from Wellness Companion agent) - -## Key Steps - -1. Set intention for journal entry -2. Choose journal prompt or free write -3. Guided reflection questions -4. Emotional processing check -5. Identify insights or patterns -6. Save entry with mood tags -7. Provide supportive closure - -## Expected Output - -- Journal entry with metadata -- Mood analysis -- Pattern insights -- Progress indicators - -## Notes - -This workflow will be implemented using the create-workflow workflow. -Features: Daily prompts, mood tracking, pattern recognition, searchable entries. diff --git a/example-custom-module/mwm/workflows/wellness-journal/workflow.md b/example-custom-module/mwm/workflows/wellness-journal/workflow.md deleted file mode 100644 index 5f7c6392..00000000 --- a/example-custom-module/mwm/workflows/wellness-journal/workflow.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -name: wellness-journal -description: create or add to the wellness journal -web_bundle: false ---- - -# Wellness Journal - -**Goal:** TODO - -**Your Role:** TODO - -## WORKFLOW ARCHITECTURE - -### Core Principles - -TODO - -### 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. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file - -### Critical Rules (NO EXCEPTIONS) - -- ๐Ÿ›‘ **NEVER** load multiple step files simultaneously -- ๐Ÿ“– **ALWAYS** read entire step file before execution -- ๐ŸŽฏ **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. Module Configuration Loading - -Load and read full config from {project-root}/.bmad/mwm/config.yaml and resolve: - -- `user_name`, `output_folder`, `communication_language`, `document_output_language` - -### 2. First Step EXECUTION - -TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY. diff --git a/package-lock.json b/package-lock.json index 375ff514..6af9597d 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "bmad-method", - "version": "6.0.0-alpha.13", + "version": "6.0.0-alpha.15", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "bmad-method", - "version": "6.0.0-alpha.13", + "version": "6.0.0-alpha.15", "license": "MIT", "dependencies": { "@kayvan/markdown-tree-parser": "^1.6.1", diff --git a/package.json b/package.json index 7bd41b7f..2c6ae6a7 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "bmad-method", - "version": "6.0.0-alpha.15", + "version": "6.0.0-alpha.16", "description": "Breakthrough Method of Agile AI-driven Development", "keywords": [ "agile", diff --git a/src/core/agents/bmad-master.agent.yaml b/src/core/agents/bmad-master.agent.yaml index bba8be22..448311bc 100644 --- a/src/core/agents/bmad-master.agent.yaml +++ b/src/core/agents/bmad-master.agent.yaml @@ -3,7 +3,7 @@ agent: metadata: - id: "{bmad_folder}/core/agents/bmad-master.md" + id: ".bmad/core/agents/bmad-master.md" name: "BMad Master" title: "BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator" icon: "๐Ÿง™" @@ -17,22 +17,22 @@ agent: # Agent-specific critical actions critical_actions: - - "Load into memory {project-root}/{bmad_folder}/core/config.yaml and set variable project_name, output_folder, user_name, communication_language" + - "Load into memory {project-root}/.bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language" - "Remember the users name is {user_name}" - "ALWAYS communicate in {communication_language}" # Agent menu items menu: - trigger: "list-tasks" - action: "list all tasks from {project-root}/{bmad_folder}/_cfg/task-manifest.csv" + action: "list all tasks from {project-root}/.bmad/_cfg/task-manifest.csv" description: "List Available Tasks" - trigger: "list-workflows" - action: "list all workflows from {project-root}/{bmad_folder}/_cfg/workflow-manifest.csv" + action: "list all workflows from {project-root}/.bmad/_cfg/workflow-manifest.csv" description: "List Workflows" - trigger: "party-mode" - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: "Group chat with all agents" # Empty prompts section (no custom prompts for this agent) diff --git a/src/core/agents/bmad-web-orchestrator.agent.xml b/src/core/agents/bmad-web-orchestrator.agent.xml index cc315ad4..cc2f60e7 100644 --- a/src/core/agents/bmad-web-orchestrator.agent.xml +++ b/src/core/agents/bmad-web-orchestrator.agent.xml @@ -1,7 +1,7 @@ - + Load this complete web bundle XML - you are the BMad Orchestrator, first agent in this bundle - CRITICAL: This bundle contains ALL agents as XML nodes with id="{bmad_folder}/..." and ALL workflows/tasks as nodes findable + CRITICAL: This bundle contains ALL agents as XML nodes with id=".bmad/..." and ALL workflows/tasks as nodes findable by type and id Greet user as BMad Orchestrator and display numbered list of ALL menu items from menu section below @@ -16,7 +16,7 @@ When menu item has: workflow="workflow-id" 1. Find workflow node by id in this bundle (e.g., <workflow id="workflow-id">) - 2. CRITICAL: Always LOAD {bmad_folder}/core/tasks/workflow.xml if referenced + 2. CRITICAL: Always LOAD .bmad/core/tasks/workflow.xml if referenced 3. Execute the workflow content precisely following all steps 4. Save outputs after completing EACH workflow step (never batch) 5. If workflow id is "todo", inform user it hasn't been implemented yet @@ -49,7 +49,7 @@ When menu item has: validate-workflow="workflow-id" - 1. MUST LOAD {bmad_folder}/core/tasks/validate-workflow.xml + 1. MUST LOAD .bmad/core/tasks/validate-workflow.xml 2. Execute all validation instructions from that file 3. Check workflow's validation property for schema 4. Identify file to validate or ask user to specify @@ -105,9 +105,9 @@ Show numbered command list List all available agents with their capabilities Transform into a specific agent - Enter group chat with all agents + Enter group chat with all agents simultaneously - Push agent to perform advanced elicitation + Push agent to perform advanced elicitation Exit current session \ No newline at end of file diff --git a/src/core/module.yaml b/src/core/module.yaml index 1099a2e6..22712f9a 100644 --- a/src/core/module.yaml +++ b/src/core/module.yaml @@ -1,13 +1,6 @@ -# BMADโ„ข Core Configuration header: "BMADโ„ข Core Configuration" subheader: "Configure the core settings for your BMADโ„ข installation.\nThese settings will be used across all modules and agents." -bmad_folder: - prompt: "What is the root folder for BMAD installation? (Recommended: .bmad)" - default: ".bmad" - result: "{value}" - regex: "^[a-zA-Z0-9._-]{1,20}$" - user_name: prompt: "What shall the agents call you?" default: "BMad" diff --git a/src/core/resources/excalidraw/README.md b/src/core/resources/excalidraw/README.md index dd17de2a..ef7bca29 100644 --- a/src/core/resources/excalidraw/README.md +++ b/src/core/resources/excalidraw/README.md @@ -72,8 +72,8 @@ Provides the **HOW** (universal knowledge) while agents provide the **WHAT** (do ```yaml # workflows/diagrams/create-flowchart/workflow.yaml -helpers: '{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md' -json_validation: '{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md' +helpers: '{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md' +json_validation: '{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md' ``` **Domain-specific additions:** @@ -99,8 +99,8 @@ flowchart: ```yaml # workflows/create-visual-metaphor/workflow.yaml -helpers: '{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md' -json_validation: '{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md' +helpers: '{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md' +json_validation: '{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md' ``` **Domain-specific additions:** diff --git a/src/core/tasks/advanced-elicitation.xml b/src/core/tasks/advanced-elicitation.xml index 2b8eb64b..df80a0a4 100644 --- a/src/core/tasks/advanced-elicitation.xml +++ b/src/core/tasks/advanced-elicitation.xml @@ -1,6 +1,6 @@ - + MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER DO NOT skip steps or change the sequence diff --git a/src/core/tasks/index-docs.xml b/src/core/tasks/index-docs.xml index 33069d07..5491be2e 100644 --- a/src/core/tasks/index-docs.xml +++ b/src/core/tasks/index-docs.xml @@ -1,4 +1,4 @@ - MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER diff --git a/src/core/tasks/validate-workflow.xml b/src/core/tasks/validate-workflow.xml index 8ce5d0f8..4110c7e1 100644 --- a/src/core/tasks/validate-workflow.xml +++ b/src/core/tasks/validate-workflow.xml @@ -1,4 +1,4 @@ - + Run a checklist against a document with thorough analysis and produce a validation report diff --git a/src/core/tasks/workflow.xml b/src/core/tasks/workflow.xml index 69f94e5a..402678fc 100644 --- a/src/core/tasks/workflow.xml +++ b/src/core/tasks/workflow.xml @@ -1,4 +1,4 @@ - + Execute given workflow by loading its configuration, following instructions, and producing output @@ -74,14 +74,14 @@ Display generated content [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. - Start the advanced elicitation workflow {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml + Start the advanced elicitation workflow {project-root}/.bmad/core/tasks/advanced-elicitation.xml Continue to next step - Start the party-mode workflow {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml + Start the party-mode workflow {project-root}/.bmad/core/workflows/party-mode/workflow.yaml @@ -225,7 +225,7 @@ โ€ข This is the complete workflow execution engine โ€ข You MUST Follow instructions exactly as written - โ€ข The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml + โ€ข 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 โ€ข This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context โ€ข YOU ARE FACILITATING A CONVERSATION With a user to produce a final document step by step. The whole process is meant to be diff --git a/src/core/tools/shard-doc.xml b/src/core/tools/shard-doc.xml index 286615f1..baa71568 100644 --- a/src/core/tools/shard-doc.xml +++ b/src/core/tools/shard-doc.xml @@ -1,4 +1,4 @@ - Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool diff --git a/src/core/workflows/brainstorming/workflow.md b/src/core/workflows/brainstorming/workflow.md index 9050764c..7ada81a5 100644 --- a/src/core/workflows/brainstorming/workflow.md +++ b/src/core/workflows/brainstorming/workflow.md @@ -28,7 +28,7 @@ This uses **micro-file architecture** for disciplined execution: ### Configuration Loading -Load config from `{project-root}/{bmad_folder}/core/config.yaml` and resolve: +Load config from `{project-root}/.bmad/core/config.yaml` and resolve: - `project_name`, `output_folder`, `user_name` - `communication_language`, `document_output_language`, `user_skill_level` @@ -36,7 +36,7 @@ Load config from `{project-root}/{bmad_folder}/core/config.yaml` and resolve: ### Paths -- `installed_path` = `{project-root}/{bmad_folder}/core/workflows/brainstorming` +- `installed_path` = `{project-root}/.bmad/core/workflows/brainstorming` - `template_path` = `{installed_path}/template.md` - `brain_techniques_path` = `{installed_path}/brain-methods.csv` - `default_output_file` = `{output_folder}/analysis/brainstorming-session-{{date}}.md` diff --git a/src/core/workflows/party-mode/steps/step-01-agent-loading.md b/src/core/workflows/party-mode/steps/step-01-agent-loading.md index 9ca44c89..25d0707f 100644 --- a/src/core/workflows/party-mode/steps/step-01-agent-loading.md +++ b/src/core/workflows/party-mode/steps/step-01-agent-loading.md @@ -18,7 +18,7 @@ ## CONTEXT BOUNDARIES: -- Agent manifest CSV is available at `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv` +- Agent manifest CSV is available at `{project-root}/.bmad/_cfg/agent-manifest.csv` - User configuration from config.yaml is loaded and resolved - Party mode is standalone interactive workflow - All agent data is available for conversation orchestration @@ -37,7 +37,7 @@ Begin agent loading process: **Agent Manifest Loading:**" -Load and parse the agent manifest CSV from `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv` +Load and parse the agent manifest CSV from `{project-root}/.bmad/_cfg/agent-manifest.csv` ### 2. Extract Agent Data diff --git a/src/core/workflows/party-mode/workflow.md b/src/core/workflows/party-mode/workflow.md index 5d15e612..6889dfc5 100644 --- a/src/core/workflows/party-mode/workflow.md +++ b/src/core/workflows/party-mode/workflow.md @@ -27,17 +27,17 @@ This uses **micro-file architecture** with **sequential conversation orchestrati ### Configuration Loading -Load config from `{project-root}/{bmad_folder}/core/config.yaml` and resolve: +Load config from `{project-root}/.bmad/core/config.yaml` and resolve: - `project_name`, `output_folder`, `user_name` - `communication_language`, `document_output_language`, `user_skill_level` - `date` as a system-generated value -- Agent manifest path: `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv` +- Agent manifest path: `{project-root}/.bmad/_cfg/agent-manifest.csv` ### Paths -- `installed_path` = `{project-root}/{bmad_folder}/core/workflows/party-mode` -- `agent_manifest_path` = `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv` +- `installed_path` = `{project-root}/.bmad/core/workflows/party-mode` +- `agent_manifest_path` = `{project-root}/.bmad/_cfg/agent-manifest.csv` - `standalone_mode` = `true` (party mode is an interactive workflow) --- diff --git a/src/modules/bmb/README.md b/src/modules/bmb/README.md index fc587344..daca8c29 100644 --- a/src/modules/bmb/README.md +++ b/src/modules/bmb/README.md @@ -24,13 +24,13 @@ Specialized tools and workflows for creating, customizing, and extending BMad co **Active Workflows** (Step-File Architecture) -- Location: `src/modules/bmb/workflows/` +- Location: `bmb/workflows/create-agent/` - 5 core workflows with 41 step files total - Template-based execution with JIT loading **Legacy Workflows** (Being Migrated) -- Location: `src/modules/bmb/workflows-legacy/` +- Location: `bmb/workflows/create-agent-legacy/` - Module-specific workflows pending conversion to step-file architecture ### ๐Ÿ“š Documentation diff --git a/src/modules/bmb/agents/bmad-builder.agent.yaml b/src/modules/bmb/agents/bmad-builder.agent.yaml index 81f4c863..66e3325f 100644 --- a/src/modules/bmb/agents/bmad-builder.agent.yaml +++ b/src/modules/bmb/agents/bmad-builder.agent.yaml @@ -4,7 +4,7 @@ agent: webskip: true metadata: - id: "{bmad_folder}/bmb/agents/bmad-builder.md" + id: ".bmad/bmb/agents/bmad-builder.md" name: BMad Builder title: BMad Builder icon: ๐Ÿง™ @@ -24,26 +24,26 @@ agent: discussion: true conversational_knowledge: - - agents: "{project-root}/{bmad_folder}/bmb/docs/agents/kb.csv" - - workflows: "{project-root}/{bmad_folder}/bmb/docs/workflows/kb.csv" - - modules: "{project-root}/{bmad_folder}/bmb/docs/modules/kb.csv" + - agents: "{project-root}/.bmad/bmb/docs/agents/kb.csv" + - workflows: "{project-root}/.bmad/bmb/docs/workflows/kb.csv" + - modules: "{project-root}/.bmad/bmb/docs/modules/kb.csv" menu: - multi: "[CA] Create, [EA] Edit, or [VA] Validate with Compliance CheckBMAD agents with best practices" triggers: - create-agent: - input: CA or fuzzy match create agent - - route: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/workflow.md" + - route: "{project-root}/.bmad/bmb/workflows/create-agent/workflow.md" - data: null - type: exec - edit-agent: - input: EA or fuzzy match edit agent - - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-agent/workflow.md" + - route: "{project-root}/.bmad/bmb/workflows/edit-agent/workflow.md" - data: null - type: exec - run-agent-compliance-check: - input: VA or fuzzy match validate agent - - route: "{project-root}/{bmad_folder}/bmb/workflows/agent-compliance-check/workflow.md" + - route: "{project-root}/.bmad/bmb/workflows/agent-compliance-check/workflow.md" - data: null - type: exec @@ -51,17 +51,17 @@ agent: triggers: - create-workflow: - input: CW or fuzzy match create workflow - - route: "{project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.md" + - route: "{project-root}/.bmad/bmb/workflows/create-workflow/workflow.md" - data: null - type: exec - edit-workflow: - input: EW or fuzzy match edit workflow - - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-workflow/workflow.md" + - route: "{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.md" - data: null - type: exec - run-workflow-compliance-check: - input: VW or fuzzy match validate workflow - - route: "{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check/workflow.md" + - route: "{project-root}/.bmad/bmb/workflows/workflow-compliance-check/workflow.md" - data: null - type: exec @@ -69,26 +69,26 @@ agent: triggers: - brainstorm-module: - input: BM or fuzzy match brainstorm module - - route: "{project-root}/{bmad_folder}/bmb/workflows/brainstorm-module/workflow.md" + - route: "{project-root}/.bmad/bmb/workflows/brainstorm-module/workflow.md" - data: null - type: exec - product-brief-module: - input: PBM or fuzzy match product brief module - - route: "{project-root}/{bmad_folder}/bmb/workflows/product-brief-module/workflow.md" + - route: "{project-root}/.bmad/bmb/workflows/product-brief-module/workflow.md" - data: null - type: exec - create-module: - input: CM or fuzzy match create module - - route: "{project-root}/{bmad_folder}/bmb/workflows/create-module/workflow.md" + - route: "{project-root}/.bmad/bmb/workflows/create-module/workflow.md" - data: null - type: exec - edit-module: - input: EM or fuzzy match edit module - - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-module/workflow.md" + - route: "{project-root}/.bmad/bmb/workflows/edit-module/workflow.md" - data: null - type: exec - run-module-compliance-check: - input: VM or fuzzy match validate module - - route: "{project-root}/{bmad_folder}/bmb/workflows/module-compliance-check/workflow.md" + - route: "{project-root}/.bmad/bmb/workflows/module-compliance-check/workflow.md" - data: null - type: exec diff --git a/src/modules/bmb/docs/agents/agent-compilation.md b/src/modules/bmb/docs/agents/agent-compilation.md index 97597397..691044b1 100644 --- a/src/modules/bmb/docs/agents/agent-compilation.md +++ b/src/modules/bmb/docs/agents/agent-compilation.md @@ -35,7 +35,7 @@ rex.agent.yaml โ† Persona name (users might rename to "Max") **Pattern:** - Filename: `{role-or-function}.agent.yaml` (kebab-case) -- Metadata ID: `{bmad_folder}/{module}/agents/{role-or-function}.md` +- Metadata ID: `.bmad/{module}/agents/{role-or-function}.md` - Persona Name: User-customizable in metadata or customize.yaml **Example:** @@ -44,7 +44,7 @@ rex.agent.yaml โ† Persona name (users might rename to "Max") # File: presentation-master.agent.yaml agent: metadata: - id: '{bmad_folder}/cis/agents/presentation-master.md' + id: '.bmad/cis/agents/presentation-master.md' name: Caravaggio # โ† Users can change this to "Pablo" or "Vince" title: Visual Communication & Presentation Expert ``` diff --git a/src/modules/bmb/docs/agents/agent-menu-patterns.md b/src/modules/bmb/docs/agents/agent-menu-patterns.md index a49fffca..0af8eac5 100644 --- a/src/modules/bmb/docs/agents/agent-menu-patterns.md +++ b/src/modules/bmb/docs/agents/agent-menu-patterns.md @@ -65,11 +65,11 @@ For module agents orchestrating multi-step processes. ```yaml menu: - trigger: create-prd - workflow: '{project-root}/{bmad_folder}/bmm/workflows/prd/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml' description: 'Create Product Requirements Document' - trigger: brainstorm - workflow: '{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml' + workflow: '{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml' description: 'Guided brainstorming session' # Placeholder for unimplemented workflows @@ -92,11 +92,11 @@ For executing tasks directly. ```yaml menu: - trigger: validate - exec: '{project-root}/{bmad_folder}/core/tasks/validate-workflow.xml' + exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml' description: 'Validate document structure' - trigger: advanced-elicitation - exec: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' + exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' description: 'Advanced elicitation techniques' ``` @@ -113,8 +113,8 @@ For document generation with templates. ```yaml menu: - trigger: create-brief - exec: '{project-root}/{bmad_folder}/core/tasks/create-doc.xml' - tmpl: '{project-root}/{bmad_folder}/bmm/templates/brief.md' + exec: '{project-root}/.bmad/core/tasks/create-doc.xml' + tmpl: '{project-root}/.bmad/bmm/templates/brief.md' description: 'Create a Product Brief' ``` @@ -131,8 +131,8 @@ Universal attribute for supplementary information. ```yaml menu: - trigger: team-standup - exec: '{project-root}/{bmad_folder}/bmm/tasks/standup.xml' - data: '{project-root}/{bmad_folder}/_cfg/agent-manifest.csv' + exec: '{project-root}/.bmad/bmm/tasks/standup.xml' + data: '{project-root}/.bmad/_cfg/agent-manifest.csv' description: 'Run team standup' - trigger: analyze-metrics @@ -154,12 +154,12 @@ Control visibility based on deployment target: ```yaml menu: - trigger: git-flow - exec: '{project-root}/{bmad_folder}/bmm/tasks/git-flow.xml' + exec: '{project-root}/.bmad/bmm/tasks/git-flow.xml' description: 'Git workflow operations' ide-only: true # Only in IDE environments - trigger: advanced-elicitation - exec: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' + exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' description: 'Advanced elicitation' web-only: true # Only in web bundles ``` @@ -251,20 +251,20 @@ menu: menu: # Analysis Phase - trigger: brainstorm - workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml' description: 'Brainstorm ideas' - trigger: research - workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml' description: 'Conduct research' # Planning Phase - trigger: prd - workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/prd/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml' description: 'Create PRD' - trigger: architecture - workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/architecture/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml' description: 'Design architecture' ``` @@ -362,8 +362,8 @@ prompts: ```yaml # GOOD - Portable paths -workflow: "{project-root}/{bmad_folder}/bmm/workflows/prd/workflow.yaml" -exec: "{project-root}/{bmad_folder}/core/tasks/validate.xml" +workflow: "{project-root}/.bmad/bmm/workflows/prd/workflow.yaml" +exec: "{project-root}/.bmad/core/tasks/validate.xml" data: "{project-root}/_data/metrics.csv" # BAD - Hardcoded paths @@ -374,7 +374,7 @@ exec: "../../../core/tasks/validate.xml" ### Available Variables - `{project-root}` - Project root directory -- `{bmad_folder}` - BMAD installation folder +- `.bmad` - BMAD installation folder - `{agent_sidecar_folder}` - Agent installation directory (Expert agents) - `{output_folder}` - Document output location - `{user_name}` - User's name from config @@ -444,23 +444,23 @@ menu: ```yaml menu: - trigger: workflow-init - workflow: '{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml' description: 'Initialize workflow path (START HERE)' - trigger: brainstorm - workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml' description: 'Guided brainstorming' - trigger: prd - workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/prd/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml' description: 'Create PRD' - trigger: architecture - workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/architecture/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml' description: 'Design architecture' - trigger: party-mode - workflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml' + workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml' description: 'Multi-agent discussion' ``` diff --git a/src/modules/bmb/docs/agents/expert-agent-architecture.md b/src/modules/bmb/docs/agents/expert-agent-architecture.md index 4f79995d..9449ebc7 100644 --- a/src/modules/bmb/docs/agents/expert-agent-architecture.md +++ b/src/modules/bmb/docs/agents/expert-agent-architecture.md @@ -223,7 +223,7 @@ Same as simple agents, PLUS: ## Reference Example -See: `src/modules/bmb/reference/agents/expert-examples/journal-keeper/` +See: `bmb/reference/agents/expert-examples/journal-keeper/` Features demonstrated: diff --git a/src/modules/bmb/docs/agents/index.md b/src/modules/bmb/docs/agents/index.md index 650c427b..a1dd92e3 100644 --- a/src/modules/bmb/docs/agents/index.md +++ b/src/modules/bmb/docs/agents/index.md @@ -18,7 +18,7 @@ Comprehensive guides for each agent type (choose based on use case): ## Reference Examples -Production-ready examples in `/src/modules/bmb/reference/agents/`: +Production-ready examples in `/bmb/reference/agents/`: **Simple Agents** (`simple-examples/`) diff --git a/src/modules/bmb/docs/agents/module-agent-architecture.md b/src/modules/bmb/docs/agents/module-agent-architecture.md index 7ed956af..61c256ad 100644 --- a/src/modules/bmb/docs/agents/module-agent-architecture.md +++ b/src/modules/bmb/docs/agents/module-agent-architecture.md @@ -27,7 +27,7 @@ Compiles to: ```yaml agent: metadata: - id: '{*bmad_folder*}/{module-code}/agents/{agent-name}.md' + id: '.bmad/{module-code}/agents/{agent-name}.md' name: 'Persona Name' title: 'Professional Title' icon: 'emoji' @@ -41,29 +41,29 @@ agent: menu: - trigger: workflow-action - workflow: '{project-root}/{*bmad_folder*}/{module-code}/workflows/{workflow-name}/workflow.yaml' + workflow: '{project-root}/.bmad/{module-code}/workflows/{workflow-name}/workflow.yaml' description: 'Execute module workflow' - trigger: another-workflow - workflow: '{project-root}/{*bmad_folder*}/core/workflows/{workflow-name}/workflow.yaml' + workflow: '{project-root}/.bmad/core/workflows/{workflow-name}/workflow.yaml' description: 'Execute core workflow' - trigger: task-action - exec: '{project-root}/{*bmad_folder*}/{module-code}/tasks/{task-name}.xml' + exec: '{project-root}/.bmad/{module-code}/tasks/{task-name}.xml' description: 'Execute module task' - trigger: cross-module - workflow: '{project-root}/{*bmad_folder*}/other-module/workflows/{workflow-name}/workflow.yaml' + workflow: '{project-root}/.bmad/other-module/workflows/{workflow-name}/workflow.yaml' description: 'Execute workflow from another module' - trigger: with-template - exec: '{project-root}/{*bmad_folder*}/core/tasks/create-doc.xml' - tmpl: '{project-root}/{*bmad_folder*}/{module-code}/templates/{template-name}.md' + exec: '{project-root}/.bmad/core/tasks/create-doc.xml' + tmpl: '{project-root}/.bmad/{module-code}/templates/{template-name}.md' description: 'Create document from template' - trigger: with-data - exec: '{project-root}/{*bmad_folder*}/{module-code}/tasks/{task-name}.xml' - data: '{project-root}/{*bmad_folder*}/_cfg/agent-manifest.csv' + exec: '{project-root}/.bmad/{module-code}/tasks/{task-name}.xml' + data: '{project-root}/.bmad/_cfg/agent-manifest.csv' description: 'Execute task with data file' ``` @@ -71,7 +71,7 @@ agent: ### Metadata -- **id**: Path with `{*bmad_folder*}` variable (resolved at install time) +- **id**: Path with `.bmad` variable (resolved at install time) - **name**: Agent persona name - **title**: Professional role - **icon**: Single emoji @@ -101,7 +101,7 @@ persona: ```yaml menu: - trigger: create-prd - workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/prd/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml' description: 'Create Product Requirements Document' ``` @@ -112,7 +112,7 @@ Invokes BMAD workflow engine to execute multi-step processes. ```yaml menu: - trigger: validate - exec: '{project-root}/{*bmad_folder*}/core/tasks/validate-workflow.xml' + exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml' description: 'Validate document structure' ``` @@ -123,8 +123,8 @@ Executes single-operation tasks. ```yaml menu: - trigger: create-brief - exec: '{project-root}/{*bmad_folder*}/core/tasks/create-doc.xml' - tmpl: '{project-root}/{*bmad_folder*}/bmm/templates/brief.md' + exec: '{project-root}/.bmad/core/tasks/create-doc.xml' + tmpl: '{project-root}/.bmad/bmm/templates/brief.md' description: 'Create a Product Brief from template' ``` @@ -135,8 +135,8 @@ Combines task execution with template file. ```yaml menu: - trigger: team-standup - exec: '{project-root}/{*bmad_folder*}/bmm/tasks/standup.xml' - data: '{project-root}/{*bmad_folder*}/_cfg/agent-manifest.csv' + exec: '{project-root}/.bmad/bmm/tasks/standup.xml' + data: '{project-root}/.bmad/_cfg/agent-manifest.csv' description: 'Run team standup with agent roster' ``` @@ -160,12 +160,12 @@ Control visibility based on platform: ```yaml menu: - trigger: advanced-elicitation - exec: '{project-root}/{*bmad_folder*}/core/tasks/advanced-elicitation.xml' + exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' description: 'Advanced elicitation techniques' web-only: true # Only shows in web bundle - trigger: git-operations - exec: '{project-root}/{*bmad_folder*}/bmm/tasks/git-flow.xml' + exec: '{project-root}/.bmad/bmm/tasks/git-flow.xml' description: 'Git workflow operations' ide-only: true # Only shows in IDE environments ``` @@ -175,7 +175,7 @@ menu: ### Core Variables - `{project-root}` - Root directory of installed project -- `{*bmad_folder*}` - BMAD installation folder (usually `.bmad`) +- `.bmad` - BMAD installation folder (usually `.bmad`) - `{user_name}` - User's name from module config - `{communication_language}` - Language preference - `{output_folder}` - Document output directory @@ -186,7 +186,7 @@ menu: ```yaml # GOOD -workflow: "{project-root}/{*bmad_folder*}/bmm/workflows/prd/workflow.yaml" +workflow: "{project-root}/.bmad/bmm/workflows/prd/workflow.yaml" # BAD workflow: "/Users/john/project/.bmad/bmm/workflows/prd/workflow.yaml" @@ -208,7 +208,7 @@ Module agents use the same injection process as simple agents: **Key difference:** Module agents load **module-specific config** instead of core config: ```xml -Load and read {project-root}/{*bmad_folder*}/{module}/config.yaml... +Load and read {project-root}/.bmad/{module}/config.yaml... ``` ## Reference Examples @@ -252,15 +252,15 @@ Agents load this at activation for consistent behavior. ```yaml menu: - trigger: init - workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/workflow-init/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/workflow-init/workflow.yaml' description: 'Initialize workflow path (START HERE)' - trigger: status - workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/workflow-status/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml' description: 'Check current workflow status' - trigger: next-step - workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/next-step/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/next-step/workflow.yaml' description: 'Execute next workflow in sequence' ``` @@ -270,20 +270,20 @@ menu: menu: # Phase 1: Analysis - trigger: brainstorm - workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/1-analysis/brainstorm/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml' description: 'Guided brainstorming session' - trigger: research - workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/1-analysis/research/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml' description: 'Market and technical research' # Phase 2: Planning - trigger: prd - workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/2-planning/prd/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml' description: 'Create PRD' - trigger: architecture - workflow: '{project-root}/{*bmad_folder*}/bmm/workflows/2-planning/architecture/workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml' description: 'Design architecture' ``` @@ -292,24 +292,23 @@ menu: ```yaml menu: - trigger: party-mode - workflow: '{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.yaml' + workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml' description: 'Bring all agents together' - trigger: brainstorm - workflow: '{project-root}/{*bmad_folder*}/cis/workflows/brainstorming/workflow.yaml' + workflow: '{project-root}/.bmad/cis/workflows/brainstorming/workflow.yaml' description: 'Use CIS brainstorming techniques' ``` ## Best Practices -1. **Use {_bmad_folder_} paths** - Portable across installations -2. **Organize workflows by phase** - Clear progression for users -3. **Include workflow-status** - Help users track progress -4. **Reference module config** - Consistent behavior -5. **No Handlebars templating** - Module agents are fixed personalities -6. **Professional personas** - Match module purpose -7. **Clear trigger names** - Self-documenting commands -8. **Group related workflows** - Logical menu organization +1. **Organize workflows by phase** - Clear progression for users +2. **Include workflow-status** - Help users track progress +3. **Reference module config** - Consistent behavior +4. **No Handlebars templating** - Module agents are fixed personalities +5. **Professional personas** - Match module purpose +6. **Clear trigger names** - Self-documenting commands +7. **Group related workflows** - Logical menu organization ## Common Patterns @@ -318,7 +317,7 @@ menu: ```yaml menu: - trigger: start - workflow: '{project-root}/{*bmad_folder*}/{module}/workflows/init/workflow.yaml' + workflow: '{project-root}/.bmad/{module}/workflows/init/workflow.yaml' description: 'Start new project (BEGIN HERE)' ``` @@ -327,7 +326,7 @@ menu: ```yaml menu: - trigger: status - workflow: '{project-root}/{*bmad_folder*}/{module}/workflows/status/workflow.yaml' + workflow: '{project-root}/.bmad/{module}/workflows/status/workflow.yaml' description: 'Check workflow progress' ``` @@ -336,27 +335,27 @@ menu: ```yaml menu: - trigger: party - workflow: '{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.yaml' + workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml' description: 'Multi-agent discussion' ``` ## Module Agent vs Simple/Expert -| Aspect | Module Agent | Simple/Expert Agent | -| ------------- | ---------------------------------- | -------------------------------- | -| Location | `{*bmad_folder*}/{module}/agents/` | `{*bmad_folder*}/custom/agents/` | -| Persona | Fixed, professional | Customizable via install_config | -| Handlebars | No templating | Yes, extensive | -| Menu actions | Workflows, tasks, templates | Prompts, inline actions | -| Configuration | Module config.yaml | Core config or none | -| Purpose | Professional tooling | Personal utilities | +| Aspect | Module Agent | Simple/Expert Agent | +| ------------- | --------------------------- | ------------------------------- | +| Location | `.bmad/{module}/agents/` | `.bmad/custom/agents/` | +| Persona | Fixed, professional | Customizable via install_config | +| Handlebars | No templating | Yes, extensive | +| Menu actions | Workflows, tasks, templates | Prompts, inline actions | +| Configuration | Module config.yaml | Core config or none | +| Purpose | Professional tooling | Personal utilities | ## Validation Checklist - [ ] Valid YAML syntax - [ ] Metadata includes `module: "{module-code}"` -- [ ] id uses `{*bmad_folder*}/{module}/agents/{name}.md` -- [ ] All workflow paths use `{project-root}/{*bmad_folder*}/` prefix +- [ ] id uses `.bmad/{module}/agents/{name}.md` +- [ ] All workflow paths use `{project-root}/.bmad/` prefix - [ ] No hardcoded paths - [ ] No duplicate triggers - [ ] Each menu item has description diff --git a/src/modules/bmb/docs/agents/understanding-agent-types.md b/src/modules/bmb/docs/agents/understanding-agent-types.md index 0016daba..944e695d 100644 --- a/src/modules/bmb/docs/agents/understanding-agent-types.md +++ b/src/modules/bmb/docs/agents/understanding-agent-types.md @@ -7,7 +7,7 @@ ALL agent types can: - โœ“ Write to {output_folder}, {project-root}, or anywhere on system - โœ“ Update artifacts and files - โœ“ Execute bash commands -- โœ“ Use core variables ({bmad_folder}, {output_folder}, etc.) +- โœ“ Use core variables (.bmad, {output_folder}, etc.) - โœ“ Have complex prompts and logic - โœ“ Invoke external tools @@ -98,11 +98,11 @@ agent: menu: - trigger: implement-story - workflow: '{bmad_folder}/bmm/workflows/dev-story/workflow.yaml' + workflow: '.bmad/bmm/workflows/dev-story/workflow.yaml' description: Implement user story - trigger: refactor - workflow: '{bmad_folder}/bmm/workflows/refactor/workflow.yaml' + workflow: '.bmad/bmm/workflows/refactor/workflow.yaml' description: Refactor codebase ``` diff --git a/src/modules/bmb/docs/workflows/architecture.md b/src/modules/bmb/docs/workflows/architecture.md index 45e0578b..86f43698 100644 --- a/src/modules/bmb/docs/workflows/architecture.md +++ b/src/modules/bmb/docs/workflows/architecture.md @@ -69,7 +69,7 @@ workflow-folder/ Standard variables in step files: ```yaml -workflow_path: '{project-root}/{*bmad_folder*}/bmb/reference/workflows/[workflow-name]' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/[workflow-name]' thisStepFile: '{workflow_path}/steps/step-[N]-[name].md' nextStepFile: '{workflow_path}/steps/step-[N+1]-[name].md' workflowFile: '{workflow_path}/workflow.md' diff --git a/src/modules/bmb/docs/workflows/common-workflow-tools.csv b/src/modules/bmb/docs/workflows/common-workflow-tools.csv index 03a0770b..d6c09045 100644 --- a/src/modules/bmb/docs/workflows/common-workflow-tools.csv +++ b/src/modules/bmb/docs/workflows/common-workflow-tools.csv @@ -1,7 +1,7 @@ propose,type,tool_name,description,url,requires_install -always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions about workflow steps or work in progress.",{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md,no -always,task,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques.",{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml,no -always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions, encouraging divergent thinking, and synthesizing concepts into actionable insights through collaborative creative exploration.",{project-root}/{bmad_folder}/core/tasks/brainstorming.xml,no +always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions about workflow steps or work in progress.",{project-root}/.bmad/core/workflows/party-mode/workflow.md,no +always,task,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques.",{project-root}/.bmad/core/tasks/advanced-elicitation.xml,no +always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions, encouraging divergent thinking, and synthesizing concepts into actionable insights through collaborative creative exploration.",{project-root}/.bmad/core/tasks/brainstorming.xml,no always,llm-tool-feature,web-browsing,"Provides LLM with capabilities to perform real-time web searches, extract relevant data, and incorporate current information into responses when up-to-date information is required beyond training knowledge.",,no always,llm-tool-feature,file-io,"Enables LLM to manage file operations such as creating, reading, updating, and deleting files, facilitating seamless data handling, storage, and document management within user environments.",,no always,llm-tool-feature,sub-agents,"Allows LLM to create and manage specialized sub-agents that handle specific tasks or modules within larger workflows, improving efficiency through parallel processing and modular task delegation.",,no diff --git a/src/modules/bmb/docs/workflows/templates/step-01-init-continuable-template.md b/src/modules/bmb/docs/workflows/templates/step-01-init-continuable-template.md index eb836a9a..4ed2f084 100644 --- a/src/modules/bmb/docs/workflows/templates/step-01-init-continuable-template.md +++ b/src/modules/bmb/docs/workflows/templates/step-01-init-continuable-template.md @@ -13,7 +13,7 @@ description: 'Initialize the [workflow-type] workflow by detecting continuation -workflow*path: '{project-root}/{\_bmad_folder*}/[module-path]/workflows/[workflow-name]' +workflow\*path: '{project-root}/.bmad/[module-path]/workflows/[workflow-name]' # File References (all use {variable} format in file) diff --git a/src/modules/bmb/docs/workflows/templates/step-1b-template.md b/src/modules/bmb/docs/workflows/templates/step-1b-template.md index fb9b4df1..57cca34d 100644 --- a/src/modules/bmb/docs/workflows/templates/step-1b-template.md +++ b/src/modules/bmb/docs/workflows/templates/step-1b-template.md @@ -13,7 +13,7 @@ description: 'Handle workflow continuation from previous session' -workflow*path: '{project-root}/{\_bmad_folder*}/[module-path]/workflows/[workflow-name]' +workflow\*path: '{project-root}/.bmad/[module-path]/workflows/[workflow-name]' # File References (all use {variable} format in file) diff --git a/src/modules/bmb/docs/workflows/templates/step-file.md b/src/modules/bmb/docs/workflows/templates/step-file.md index 614e5e9c..efef1534 100644 --- a/src/modules/bmb/docs/workflows/templates/step-file.md +++ b/src/modules/bmb/docs/workflows/templates/step-file.md @@ -3,7 +3,7 @@ name: "step-{{stepNumber}}-{{stepName}}" description: "{{stepDescription}}" # Path Definitions -workflow_path: "{project-root}/{*bmad_folder*}/{{targetModule}}/workflows/{{workflowName}}" +workflow_path: "{project-root}/.bmad/{{targetModule}}/workflows/{{workflowName}}" # File References thisStepFile: "{workflow_path}/steps/step-{{stepNumber}}-{{stepName}}.md" @@ -16,8 +16,8 @@ outputFile: "{output_folder}/{{outputFileName}}-{project_name}.md" {{/hasOutput}} # Task References (list only if used in THIS step file instance and only the ones used, there might be others) -advancedElicitationTask: "{project-root}/{*bmad_folder*}/core/tasks/advanced-elicitation.xml" -partyModeWorkflow: "{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.md" +advancedElicitationTask: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" +partyModeWorkflow: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" {{#hasTemplates}} # Template References diff --git a/src/modules/bmb/docs/workflows/templates/step-template.md b/src/modules/bmb/docs/workflows/templates/step-template.md index 1c525e2c..b148e96e 100644 --- a/src/modules/bmb/docs/workflows/templates/step-template.md +++ b/src/modules/bmb/docs/workflows/templates/step-template.md @@ -11,7 +11,7 @@ description: '[Brief description of what this step accomplishes]' -workflow*path: '{project-root}/{\_bmad_folder*}/bmb/reference/workflows/[workflow-name]' # the folder the workflow.md file is in +workflow\*path: '{project-root}/.bmad/[module]/reference/workflows/[workflow-name]' # the folder the workflow.md file is in # File References (all use {variable} format in file) @@ -23,8 +23,8 @@ outputFile: '{output_folder}/[output-file-name]-{project_name}.md' # Task References (IF THE workflow uses and it makes sense in this step to have these ) -advancedElicitationTask: '{project-root}/{_bmad_folder_}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{_bmad_folder_}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References (if this step uses a specific templates) diff --git a/src/modules/bmb/docs/workflows/templates/workflow-template.md b/src/modules/bmb/docs/workflows/templates/workflow-template.md index 4235929a..2c33e10e 100644 --- a/src/modules/bmb/docs/workflows/templates/workflow-template.md +++ b/src/modules/bmb/docs/workflows/templates/workflow-template.md @@ -53,7 +53,7 @@ web_bundle: [true/false] # Set to true for inclusion in web bundle builds ### 1. Module Configuration Loading -Load and read full config from {project-root}/{_bmad_folder_}/[MODULE FOLDER]/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/[MODULE FOLDER]/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, [MODULE VARS] @@ -101,4 +101,4 @@ Example: Load, read the full file and then execute `{workflow_path}/steps/step-0 ### NOTE: You can View a real example of a perfect workflow.md file that was created from this template -`{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/workflow.md` +`{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md` diff --git a/src/modules/bmb/docs/workflows/templates/workflow.md b/src/modules/bmb/docs/workflows/templates/workflow.md index 7a8ed545..1190e74b 100644 --- a/src/modules/bmb/docs/workflows/templates/workflow.md +++ b/src/modules/bmb/docs/workflows/templates/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/{_bmad_folder_}/{{targetModule}}/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/{{targetModule}}/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmb/module.yaml b/src/modules/bmb/module.yaml index 85df89c0..1329cd63 100644 --- a/src/modules/bmb/module.yaml +++ b/src/modules/bmb/module.yaml @@ -11,7 +11,6 @@ subheader: "Configure the settings for the BoMB Factory!\nThe agent, workflow an ## user_name ## communication_language ## output_folder -## bmad_folder ## install_user_docs ## kb_install diff --git a/src/modules/bmb/reference/agents/module-examples/README.md b/src/modules/bmb/reference/agents/module-examples/README.md index adfc16aa..878cc33d 100644 --- a/src/modules/bmb/reference/agents/module-examples/README.md +++ b/src/modules/bmb/reference/agents/module-examples/README.md @@ -7,7 +7,7 @@ Reference examples for module-integrated agents. Module agents integrate with BMAD module workflows (BMM, CIS, BMB). They: - Orchestrate multi-step workflows -- Use `{bmad_folder}` path variables +- Use `.bmad` path variables - Have fixed professional personas (no install_config) - Reference module-specific configurations diff --git a/src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml b/src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml index 602bf4e0..82b5a199 100644 --- a/src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml +++ b/src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml @@ -10,7 +10,7 @@ agent: metadata: - id: "{*bmad_folder*}/bmm/agents/security-engineer.md" + id: ".bmad/bmm/agents/security-engineer.md" name: "Sam" title: "Security Engineer" icon: "๐Ÿ”" @@ -32,11 +32,11 @@ agent: menu: # NOTE: These workflows are hypothetical examples assuming add to a module called bmm - not implemented - trigger: threat-model - exec: "{project-root}/{*bmad_folder*}/bmm/workflows/threat-model/workflow.md" + exec: "{project-root}/.bmad/bmm/workflows/threat-model/workflow.md" description: "Create STRIDE threat model for architecture" - trigger: security-review - exec: "{project-root}/{*bmad_folder*}/bmm/workflows/security-review/workflow.md" + exec: "{project-root}/.bmad/bmm/workflows/security-review/workflow.md" description: "Review code/design for security issues" - trigger: owasp-check @@ -44,10 +44,10 @@ agent: description: "Check against OWASP Top 10" - trigger: compliance - exec: "{project-root}/{*bmad_folder*}/bmm/workflows/compliance-check/workflow.md" + exec: "{project-root}/.bmad/bmm/workflows/compliance-check/workflow.md" description: "Verify compliance requirements (SOC2, GDPR, etc.)" # Core workflow that exists - trigger: party-mode - exec: "{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: "Multi-agent security discussion" diff --git a/src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml b/src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml index 2ce4598f..2f612305 100644 --- a/src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml +++ b/src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml @@ -10,7 +10,7 @@ agent: metadata: - id: "{*bmad_folder*}/cis/agents/trend-analyst.md" + id: ".bmad/cis/agents/trend-analyst.md" name: "Nova" title: "Trend Analyst" icon: "๐Ÿ“ˆ" @@ -32,26 +32,26 @@ agent: menu: # NOTE: These workflows are hypothetical examples - not implemented - trigger: scan-trends - exec: "{project-root}/{*bmad_folder*}/cis/workflows/trend-scan/workflow.md" + exec: "{project-root}/.bmad/cis/workflows/trend-scan/workflow.md" description: "Scan for emerging trends in a domain" - trigger: analyze-trend - exec: "{project-root}/{*bmad_folder*}/cis/workflows/trend-analysis/workflow.md" + exec: "{project-root}/.bmad/cis/workflows/trend-analysis/workflow.md" description: "Deep dive on a specific trend" - trigger: opportunity-map - exec: "{project-root}/{*bmad_folder*}/cis/workflows/opportunity-mapping/workflow.md" + exec: "{project-root}/.bmad/cis/workflows/opportunity-mapping/workflow.md" description: "Map trend to strategic opportunities" - trigger: competitor-trends - exec: "{project-root}/{*bmad_folder*}/cis/tasks/competitor-trend-watch.xml" + exec: "{project-root}/.bmad/cis/tasks/competitor-trend-watch.xml" description: "Monitor competitor trend adoption" # Core workflows that exist - trigger: brainstorm - exec: "{project-root}/{*bmad_folder*}/core/workflows/brainstorming/workflow.md" + exec: "{project-root}/.bmad/core/workflows/brainstorming/workflow.md" description: "Brainstorm trend implications" - trigger: party-mode - exec: "{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: "Discuss trends with other agents" diff --git a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md index 1a434b70..2479d3bd 100644 --- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md +++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md @@ -3,7 +3,7 @@ name: 'step-01-init' description: 'Initialize the nutrition plan workflow by detecting continuation state and creating output document' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-01-init.md' diff --git a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md index b5f83c11..14802db4 100644 --- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md +++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md @@ -3,7 +3,7 @@ name: 'step-01b-continue' description: 'Handle workflow continuation from previous session' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-01b-continue.md' diff --git a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md index 70a5171e..58c89409 100644 --- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md +++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md @@ -3,7 +3,7 @@ name: 'step-02-profile' description: 'Gather comprehensive user profile information through collaborative conversation' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References (all use {variable} format in file) thisStepFile: '{workflow_path}/steps/step-02-profile.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/nutrition-plan-{project_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References profileTemplate: '{workflow_path}/templates/profile-section.md' diff --git a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md index 15210f0a..87b0288a 100644 --- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md +++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md @@ -3,7 +3,7 @@ name: 'step-03-assessment' description: 'Analyze nutritional requirements, identify restrictions, and calculate target macros' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-03-assessment.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/nutrition-plan-{project_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Data References dietaryRestrictionsDB: '{workflow_path}/data/dietary-restrictions.csv' diff --git a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md index 4c633713..2b543381 100644 --- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md +++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md @@ -3,7 +3,7 @@ name: 'step-04-strategy' description: 'Design a personalized meal strategy that meets nutritional needs and fits lifestyle' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-04-strategy.md' @@ -13,8 +13,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/nutrition-plan-{project_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Data References recipeDatabase: '{workflow_path}/data/recipe-database.csv' @@ -167,8 +167,8 @@ Display: **Select an Option:** [A] Meal Variety Optimization [P] Chef & Dietitia #### Menu Handling Logic: - HALT and AWAIT ANSWER -- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml` -- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md` with a chef and dietitian expert also as part of the party +- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml` +- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md` with a chef and dietitian expert also as part of the party - IF C: Save content to nutrition-plan.md, update frontmatter `stepsCompleted` to add 4 at the end of the array before loading next step, check cooking frequency: - IF cooking frequency > 2x/week: load, read entire file, then execute `{workflow_path}/step-05-shopping.md` - IF cooking frequency โ‰ค 2x/week: load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md` diff --git a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md index 8fce50d4..c3c5d6ca 100644 --- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md +++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md @@ -3,7 +3,7 @@ name: 'step-05-shopping' description: 'Create a comprehensive shopping list that supports the meal strategy' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-05-shopping.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/nutrition-plan-{project_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References shoppingTemplate: '{workflow_path}/templates/shopping-section.md' @@ -157,8 +157,8 @@ Display: **Select an Option:** [A] Budget Optimization Strategies [P] Shopping P #### Menu Handling Logic: - HALT and AWAIT ANSWER -- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml` -- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md` +- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml` +- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md` - IF C: Save content to nutrition-plan.md, update frontmatter `stepsCompleted` to add 5 at the end of the array before loading next step, then load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md` - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options) diff --git a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md index df709b11..43c67322 100644 --- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md +++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md @@ -3,7 +3,7 @@ name: 'step-06-prep-schedule' description: "Create a realistic meal prep schedule that fits the user's lifestyle" # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-06-prep-schedule.md' @@ -11,8 +11,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/nutrition-plan-{project_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References prepScheduleTemplate: '{workflow_path}/templates/prep-schedule-section.md' @@ -178,8 +178,8 @@ Display: **Select an Option:** [A] Advanced Prep Techniques [P] Coach Perspectiv #### Menu Handling Logic: - HALT and AWAIT ANSWER -- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml` -- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md` +- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml` +- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md` - IF C: update frontmatter `stepsCompleted` to add 6 at the end of the array before loading next step, mark workflow complete, display final message - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options) diff --git a/src/modules/bmb/reference/workflows/meal-prep-nutrition/workflow.md b/src/modules/bmb/reference/workflows/meal-prep-nutrition/workflow.md index b21237e3..960a5994 100644 --- a/src/modules/bmb/reference/workflows/meal-prep-nutrition/workflow.md +++ b/src/modules/bmb/reference/workflows/meal-prep-nutrition/workflow.md @@ -49,10 +49,10 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/{bmad_folder}/core/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/core/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` ### 2. First Step EXECUTION -Load, read the full file and then execute `{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow. +Load, read the full file and then execute `{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow. diff --git a/src/modules/bmb/workflows-legacy/edit-module/README.md b/src/modules/bmb/workflows-legacy/edit-module/README.md index af95542e..6847cf57 100644 --- a/src/modules/bmb/workflows-legacy/edit-module/README.md +++ b/src/modules/bmb/workflows-legacy/edit-module/README.md @@ -106,7 +106,7 @@ Modules can share workflows: ```yaml # In agent menu item: -workflow: '{project-root}/{bmad_folder}/other-module/workflows/shared-workflow/workflow.yaml' +workflow: '{project-root}/.bmad/other-module/workflows/shared-workflow/workflow.yaml' ``` Common patterns: @@ -151,7 +151,7 @@ Changes are reviewed and approved by you before being applied. - Can configure web bundles - Are the development source of truth -**Installed modules** (in {bmad_folder}/): +**Installed modules** (in .bmad/): - Are deployed to target projects - Use config.yaml for user customization diff --git a/src/modules/bmb/workflows-legacy/edit-module/checklist.md b/src/modules/bmb/workflows-legacy/edit-module/checklist.md index b583acd2..4bf532ab 100644 --- a/src/modules/bmb/workflows-legacy/edit-module/checklist.md +++ b/src/modules/bmb/workflows-legacy/edit-module/checklist.md @@ -5,7 +5,7 @@ Use this checklist to validate module edits meet BMAD Core standards. ## Module Structure Validation - [ ] Module has clear 3-letter code (bmm, bmb, cis, etc.) -- [ ] Module is in correct location (src/modules/ for source, {bmad_folder}/ for installed) +- [ ] Module is in correct location (src/modules/ for source, .bmad/ for installed) - [ ] agents/ directory exists - [ ] workflows/ directory exists - [ ] config.yaml exists in module root @@ -127,7 +127,7 @@ Use this checklist to validate module edits meet BMAD Core standards. - [ ] Web bundles configured in workflow.yaml files - [ ] All referenced files included in web_bundle_files -- [ ] Paths are {bmad_folder}/-relative (not project-root) +- [ ] Paths are .bmad/-relative (not project-root) - [ ] No config_source references in web bundles - [ ] Invoked workflows included in dependencies diff --git a/src/modules/bmb/workflows-legacy/edit-module/instructions.md b/src/modules/bmb/workflows-legacy/edit-module/instructions.md index 07f99156..0f112a25 100644 --- a/src/modules/bmb/workflows-legacy/edit-module/instructions.md +++ b/src/modules/bmb/workflows-legacy/edit-module/instructions.md @@ -1,7 +1,7 @@ # Edit Module - Module Editor Instructions -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/edit-module/workflow.yaml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/.bmad/bmb/workflows/edit-module/workflow.yaml This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them Communicate all responses in {communication_language} @@ -9,7 +9,7 @@ -What is the path to the module you want to edit? (provide path to module directory like {bmad_folder}/bmm/ or src/modules/bmm/) +What is the path to the module you want to edit? (provide path to module directory like .bmad/bmm/ or src/modules/bmm/) Load the module directory structure completely: @@ -187,7 +187,7 @@ Let the conversation flow naturally. Build a shared vision of what "better" look **If setting up cross-module integration:** - Identify which workflows from other modules are needed -- Show how to reference workflows properly: {project-root}/{bmad_folder}/{{module}}/workflows/{{workflow}}/workflow.yaml +- Show how to reference workflows properly: {project-root}/.bmad/{{module}}/workflows/{{workflow}}/workflow.yaml - Document the integration in README - Ensure dependencies are clear - Consider adding example usage diff --git a/src/modules/bmb/workflows-legacy/edit-module/workflow.yaml b/src/modules/bmb/workflows-legacy/edit-module/workflow.yaml index ae1d2868..87b72de0 100644 --- a/src/modules/bmb/workflows-legacy/edit-module/workflow.yaml +++ b/src/modules/bmb/workflows-legacy/edit-module/workflow.yaml @@ -4,26 +4,26 @@ description: "Edit existing BMAD modules (structure, agents, workflows, document author: "BMad" # Critical variables load from config_source -config_source: "{project-root}/{bmad_folder}/bmb/config.yaml" +config_source: "{project-root}/.bmad/bmb/config.yaml" communication_language: "{config_source}:communication_language" user_name: "{config_source}:user_name" # Required Data Files - Critical for understanding module conventions -module_structure_guide: "{project-root}/{bmad_folder}/bmb/workflows/create-module/module-structure.md" +module_structure_guide: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md" # Related workflow editors -agent_editor: "{project-root}/{bmad_folder}/bmb/workflows/edit-agent/workflow.yaml" -workflow_editor: "{project-root}/{bmad_folder}/bmb/workflows/edit-workflow/workflow.yaml" +agent_editor: "{project-root}/.bmad/bmb/workflows/edit-agent/workflow.yaml" +workflow_editor: "{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.yaml" # Reference examples - for learning patterns -bmm_module_dir: "{project-root}/{bmad_folder}/bmm/" -bmb_module_dir: "{project-root}/{bmad_folder}/bmb/" -cis_module_dir: "{project-root}/{bmad_folder}/cis/" -existing_agents_dir: "{project-root}/{bmad_folder}/*/agents/" -existing_workflows_dir: "{project-root}/{bmad_folder}/*/workflows/" +bmm_module_dir: "{project-root}/.bmad/bmm/" +bmb_module_dir: "{project-root}/.bmad/bmb/" +cis_module_dir: "{project-root}/.bmad/cis/" +existing_agents_dir: "{project-root}/.bmad/*/agents/" +existing_workflows_dir: "{project-root}/.bmad/*/workflows/" # Module path and component files -installed_path: "{project-root}/{bmad_folder}/bmb/workflows/edit-module" +installed_path: "{project-root}/.bmad/bmb/workflows/edit-module" template: false # This is an action workflow - no template needed instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmb/workflows-legacy/module-brief/README.md b/src/modules/bmb/workflows-legacy/module-brief/README.md index 453ca9ef..82ba9935 100644 --- a/src/modules/bmb/workflows-legacy/module-brief/README.md +++ b/src/modules/bmb/workflows-legacy/module-brief/README.md @@ -254,8 +254,8 @@ To customize this workflow: For issues or questions: -- Review the workflow creation guide at `/{bmad_folder}/bmb/workflows/create-workflow/workflow-creation-guide.md` -- Study existing module examples in `/{bmad_folder}/` for patterns and inspiration +- Review the workflow creation guide at `/.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md` +- Study existing module examples in `/.bmad/` for patterns and inspiration - Validate output using `checklist.md` - Consult module structure guide at `create-module/module-structure.md` diff --git a/src/modules/bmb/workflows-legacy/module-brief/instructions.md b/src/modules/bmb/workflows-legacy/module-brief/instructions.md index 6a611e3a..a094b912 100644 --- a/src/modules/bmb/workflows-legacy/module-brief/instructions.md +++ b/src/modules/bmb/workflows-legacy/module-brief/instructions.md @@ -1,7 +1,7 @@ # Module Brief Instructions -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/module-brief/workflow.yaml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/.bmad/bmb/workflows/module-brief/workflow.yaml Communicate in {communication_language} throughout the module brief creation process โš ๏ธ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmb/workflows-legacy/module-brief/workflow.yaml b/src/modules/bmb/workflows-legacy/module-brief/workflow.yaml index fad6e479..c25cdfe7 100644 --- a/src/modules/bmb/workflows-legacy/module-brief/workflow.yaml +++ b/src/modules/bmb/workflows-legacy/module-brief/workflow.yaml @@ -4,15 +4,15 @@ description: "Create a comprehensive Module Brief that serves as the blueprint f author: "BMad Builder" # Critical variables -config_source: "{project-root}/{bmad_folder}/bmb/config.yaml" +config_source: "{project-root}/.bmad/bmb/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" date: system-generated # Reference examples and documentation -existing_modules_dir: "{project-root}/{bmad_folder}/" -module_structure_guide: "{project-root}/{bmad_folder}/bmb/workflows/create-module/module-structure.md" +existing_modules_dir: "{project-root}/.bmad/" +module_structure_guide: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md" # Optional user inputs - discovered if they exist input_file_patterns: @@ -22,7 +22,7 @@ input_file_patterns: load_strategy: "FULL_LOAD" # Module path and component files -installed_path: "{project-root}/{bmad_folder}/bmb/workflows/module-brief" +installed_path: "{project-root}/.bmad/bmb/workflows/module-brief" template: "{installed_path}/template.md" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/README.md b/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/README.md index adfc16aa..878cc33d 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/README.md +++ b/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/README.md @@ -7,7 +7,7 @@ Reference examples for module-integrated agents. Module agents integrate with BMAD module workflows (BMM, CIS, BMB). They: - Orchestrate multi-step workflows -- Use `{bmad_folder}` path variables +- Use `.bmad` path variables - Have fixed professional personas (no install_config) - Reference module-specific configurations diff --git a/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/security-engineer.agent.yaml b/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/security-engineer.agent.yaml index 56cad220..da3febac 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/security-engineer.agent.yaml +++ b/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/security-engineer.agent.yaml @@ -10,7 +10,7 @@ agent: metadata: - id: "{bmad_folder}/bmm/agents/security-engineer.md" + id: ".bmad/bmm/agents/security-engineer.md" name: "Sam" title: "Security Engineer" icon: "๐Ÿ”" @@ -32,22 +32,22 @@ agent: menu: # NOTE: These workflows are hypothetical examples - not implemented - trigger: threat-model - workflow: "{project-root}/{bmad_folder}/bmm/workflows/threat-model/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/threat-model/workflow.yaml" description: "Create STRIDE threat model for architecture" - trigger: security-review - workflow: "{project-root}/{bmad_folder}/bmm/workflows/security-review/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/security-review/workflow.yaml" description: "Review code/design for security issues" - trigger: owasp-check - exec: "{project-root}/{bmad_folder}/bmm/tasks/owasp-top-10.xml" + exec: "{project-root}/.bmad/bmm/tasks/owasp-top-10.xml" description: "Check against OWASP Top 10" - trigger: compliance - workflow: "{project-root}/{bmad_folder}/bmm/workflows/compliance-check/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/compliance-check/workflow.yaml" description: "Verify compliance requirements (SOC2, GDPR, etc.)" # Core workflow that exists - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: "Multi-agent security discussion" diff --git a/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/trend-analyst.agent.yaml b/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/trend-analyst.agent.yaml index 7e76fe80..cc05b80e 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/trend-analyst.agent.yaml +++ b/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/trend-analyst.agent.yaml @@ -10,7 +10,7 @@ agent: metadata: - id: "{bmad_folder}/cis/agents/trend-analyst.md" + id: ".bmad/cis/agents/trend-analyst.md" name: "Nova" title: "Trend Analyst" icon: "๐Ÿ“ˆ" @@ -32,26 +32,26 @@ agent: menu: # NOTE: These workflows are hypothetical examples - not implemented - trigger: scan-trends - workflow: "{project-root}/{bmad_folder}/cis/workflows/trend-scan/workflow.yaml" + workflow: "{project-root}/.bmad/cis/workflows/trend-scan/workflow.yaml" description: "Scan for emerging trends in a domain" - trigger: analyze-trend - workflow: "{project-root}/{bmad_folder}/cis/workflows/trend-analysis/workflow.yaml" + workflow: "{project-root}/.bmad/cis/workflows/trend-analysis/workflow.yaml" description: "Deep dive on a specific trend" - trigger: opportunity-map - workflow: "{project-root}/{bmad_folder}/cis/workflows/opportunity-mapping/workflow.yaml" + workflow: "{project-root}/.bmad/cis/workflows/opportunity-mapping/workflow.yaml" description: "Map trend to strategic opportunities" - trigger: competitor-trends - exec: "{project-root}/{bmad_folder}/cis/tasks/competitor-trend-watch.xml" + exec: "{project-root}/.bmad/cis/tasks/competitor-trend-watch.xml" description: "Monitor competitor trend adoption" # Core workflows that exist - trigger: brainstorm - workflow: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml" + workflow: "{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml" description: "Brainstorm trend implications" - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: "Discuss trends with other agents" diff --git a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01-init.md b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01-init.md index f7d4cb2d..8646c5c9 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01-init.md +++ b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01-init.md @@ -3,7 +3,7 @@ name: 'step-01-init' description: 'Initialize the nutrition plan workflow by detecting continuation state and creating output document' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-01-init.md' diff --git a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md index 0f428bfd..b390f3c8 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md +++ b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md @@ -3,7 +3,7 @@ name: 'step-01b-continue' description: 'Handle workflow continuation from previous session' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-01b-continue.md' diff --git a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md index c06b74fb..c50e8179 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md +++ b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md @@ -3,7 +3,7 @@ name: 'step-02-profile' description: 'Gather comprehensive user profile information through collaborative conversation' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References (all use {variable} format in file) thisStepFile: '{workflow_path}/steps/step-02-profile.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/nutrition-plan-{project_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References profileTemplate: '{workflow_path}/templates/profile-section.md' diff --git a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md index 109bb3d6..8fa087f5 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md +++ b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-03-assessment.md @@ -3,7 +3,7 @@ name: 'step-03-assessment' description: 'Analyze nutritional requirements, identify restrictions, and calculate target macros' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-03-assessment.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/nutrition-plan-{project_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Data References dietaryRestrictionsDB: '{workflow_path}/data/dietary-restrictions.csv' diff --git a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md index 59f92820..fe2ce026 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md +++ b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-04-strategy.md @@ -3,7 +3,7 @@ name: 'step-04-strategy' description: 'Design a personalized meal strategy that meets nutritional needs and fits lifestyle' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-04-strategy.md' @@ -13,8 +13,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/nutrition-plan-{project_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Data References recipeDatabase: '{workflow_path}/data/recipe-database.csv' @@ -167,8 +167,8 @@ Display: **Select an Option:** [A] Meal Variety Optimization [P] Chef & Dietitia #### Menu Handling Logic: - HALT and AWAIT ANSWER -- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml` -- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md` +- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml` +- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md` - IF C: Save content to nutrition-plan.md, update frontmatter, check cooking frequency: - IF cooking frequency > 2x/week: load, read entire file, then execute `{workflow_path}/step-05-shopping.md` - IF cooking frequency โ‰ค 2x/week: load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md` diff --git a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md index 95d33017..34d1b3f7 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md +++ b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-05-shopping.md @@ -3,7 +3,7 @@ name: 'step-05-shopping' description: 'Create a comprehensive shopping list that supports the meal strategy' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-05-shopping.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/nutrition-plan-{project_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References shoppingTemplate: '{workflow_path}/templates/shopping-section.md' @@ -157,8 +157,8 @@ Display: **Select an Option:** [A] Budget Optimization Strategies [P] Shopping P #### Menu Handling Logic: - HALT and AWAIT ANSWER -- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml` -- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md` +- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml` +- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md` - IF C: Save content to nutrition-plan.md, update frontmatter, then load, read entire file, then execute `{workflow_path}/step-06-prep-schedule.md` - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options) diff --git a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md index ee3f9728..79d587c7 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md +++ b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md @@ -3,7 +3,7 @@ name: 'step-06-prep-schedule' description: "Create a realistic meal prep schedule that fits the user's lifestyle" # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition' +workflow_path: '{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition' # File References thisStepFile: '{workflow_path}/steps/step-06-prep-schedule.md' @@ -11,8 +11,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/nutrition-plan-{project_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References prepScheduleTemplate: '{workflow_path}/templates/prep-schedule-section.md' @@ -178,8 +178,8 @@ Display: **Select an Option:** [A] Advanced Prep Techniques [P] Coach Perspectiv #### Menu Handling Logic: - HALT and AWAIT ANSWER -- IF A: Execute `{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml` -- IF P: Execute `{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md` +- IF A: Execute `{project-root}/.bmad/core/tasks/advanced-elicitation.xml` +- IF P: Execute `{project-root}/.bmad/core/workflows/party-mode/workflow.md` - IF C: Update frontmatter with all steps completed, mark workflow complete, display final message - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options) diff --git a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md index e0db0760..843f2998 100644 --- a/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md +++ b/src/modules/bmb/workflows/create-agent/data/reference/workflows/meal-prep-nutrition/workflow.md @@ -49,10 +49,10 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/{bmad_folder}/bmm/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/bmm/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level` ### 2. First Step EXECUTION -Load, read the full file and then execute `{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow. +Load, read the full file and then execute `{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md` to begin the workflow. diff --git a/src/modules/bmb/workflows/create-agent/data/validation-complete.md b/src/modules/bmb/workflows/create-agent/data/validation-complete.md index e4a74c70..bb204895 100644 --- a/src/modules/bmb/workflows/create-agent/data/validation-complete.md +++ b/src/modules/bmb/workflows/create-agent/data/validation-complete.md @@ -2,8 +2,8 @@ ## Migration Summary -**Legacy Workflow:** `src/modules/bmb/workflows-legacy/create-agent/workflow.yaml` + `instructions.md` -**New Workflow:** `src/modules/bmb/workflows/create-agent/workflow.md` + 11 step files +**Legacy Workflow:** `bmb/workflows/create-agent-legacy/create-agent/workflow.yaml` + `instructions.md` +**New Workflow:** `bmb/workflows/create-agent/create-agent/workflow.md` + 11 step files **Migration Date:** 2025-11-30T06:32:21.248Z **Migration Status:** โœ… COMPLETE @@ -81,10 +81,10 @@ **Agent Documentation References** -- Agent compilation guide: `{project-root}/{bmad_folder}/bmb/docs/agents/agent-compilation.md` -- Agent types guide: `{project-root}/{bmad_folder}/bmb/docs/agents/understanding-agent-types.md` +- Agent compilation guide: `{project-root}/.bmad/bmb/docs/agents/agent-compilation.md` +- Agent types guide: `{project-root}/.bmad/bmb/docs/agents/understanding-agent-types.md` - Architecture docs: simple, expert, module agent architectures -- Menu patterns guide: `{project-root}/{bmad_folder}/bmb/docs/agents/agent-menu-patterns.md` +- Menu patterns guide: `{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md` - Status: โœ… ALL REFERENCES PRESERVED **Communication Presets** diff --git a/src/modules/bmb/workflows/create-agent/steps/step-01-brainstorm.md b/src/modules/bmb/workflows/create-agent/steps/step-01-brainstorm.md index cdb521f5..5f487b09 100644 --- a/src/modules/bmb/workflows/create-agent/steps/step-01-brainstorm.md +++ b/src/modules/bmb/workflows/create-agent/steps/step-01-brainstorm.md @@ -3,18 +3,18 @@ name: 'step-01-brainstorm' description: 'Optional brainstorming for agent ideas' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent' # File References thisStepFile: '{workflow_path}/steps/step-01-brainstorm.md' nextStepFile: '{workflow_path}/steps/step-02-discover.md' workflowFile: '{workflow_path}/workflow.md' brainstormContext: '{workflow_path}/data/brainstorm-context.md' -brainstormWorkflow: '{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.md' +brainstormWorkflow: '{project-root}/.bmad/core/workflows/brainstorming/workflow.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 1: Optional Brainstorming diff --git a/src/modules/bmb/workflows/create-agent/steps/step-02-discover.md b/src/modules/bmb/workflows/create-agent/steps/step-02-discover.md index 0ee6dd98..60daeeaa 100644 --- a/src/modules/bmb/workflows/create-agent/steps/step-02-discover.md +++ b/src/modules/bmb/workflows/create-agent/steps/step-02-discover.md @@ -3,14 +3,14 @@ name: 'step-02-discover' description: 'Discover the agent purpose and type through natural conversation' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent' # File References thisStepFile: '{workflow_path}/steps/step-02-discover.md' nextStepFile: '{workflow_path}/steps/step-03-persona.md' workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/agent-purpose-{project_name}.md' -agentTypesGuide: '{project-root}/{bmad_folder}/bmb/docs/agents/understanding-agent-types.md' +agentTypesGuide: '{project-root}/.bmad/bmb/docs/agents/understanding-agent-types.md' simpleExamples: '{workflow_path}/data/reference/agents/simple-examples/' expertExamples: '{workflow_path}/data/reference/agents/expert-examples/' moduleExamples: '{workflow_path}/data/reference/agents/module-examples/' @@ -19,8 +19,8 @@ moduleExamples: '{workflow_path}/data/reference/agents/module-examples/' agentPurposeTemplate: '{workflow_path}/templates/agent-purpose-and-type.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 2: Discover Agent Purpose and Type diff --git a/src/modules/bmb/workflows/create-agent/steps/step-03-persona.md b/src/modules/bmb/workflows/create-agent/steps/step-03-persona.md index a8936f9c..e5a5699c 100644 --- a/src/modules/bmb/workflows/create-agent/steps/step-03-persona.md +++ b/src/modules/bmb/workflows/create-agent/steps/step-03-persona.md @@ -3,7 +3,7 @@ name: 'step-03-persona' description: 'Shape the agent personality through collaborative discovery' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent' # File References thisStepFile: '{workflow_path}/steps/step-03-persona.md' @@ -11,14 +11,14 @@ nextStepFile: '{workflow_path}/steps/step-04-commands.md' workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/agent-persona-{project_name}.md' communicationPresets: '{workflow_path}/data/communication-presets.csv' -agentMenuPatterns: '{project-root}/{bmad_folder}/bmb/docs/agents/agent-menu-patterns.md' +agentMenuPatterns: '{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md' # Template References personaTemplate: '{workflow_path}/templates/agent-persona.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 3: Shape Agent's Personality diff --git a/src/modules/bmb/workflows/create-agent/steps/step-04-commands.md b/src/modules/bmb/workflows/create-agent/steps/step-04-commands.md index f615725b..e93dabef 100644 --- a/src/modules/bmb/workflows/create-agent/steps/step-04-commands.md +++ b/src/modules/bmb/workflows/create-agent/steps/step-04-commands.md @@ -3,24 +3,24 @@ name: 'step-04-commands' description: 'Build capabilities through natural progression and refine commands' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent' # File References thisStepFile: '{workflow_path}/steps/step-04-commands.md' nextStepFile: '{workflow_path}/steps/step-05-name.md' workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/agent-commands-{project_name}.md' -agentMenuPatterns: '{project-root}/{bmad_folder}/bmb/docs/agents/agent-menu-patterns.md' -simpleArchitecture: '{project-root}/{bmad_folder}/bmb/docs/agents/simple-agent-architecture.md' -expertArchitecture: '{project-root}/{bmad_folder}/bmb/docs/agents/expert-agent-architecture.md' -moduleArchitecture: '{project-root}/{bmad_folder}/bmb/docs/agents/module-agent-architecture.md' +agentMenuPatterns: '{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md' +simpleArchitecture: '{project-root}/.bmad/bmb/docs/agents/simple-agent-architecture.md' +expertArchitecture: '{project-root}/.bmad/bmb/docs/agents/expert-agent-architecture.md' +moduleArchitecture: '{project-root}/.bmad/bmb/docs/agents/module-agent-architecture.md' # Template References commandsTemplate: '{workflow_path}/templates/agent-commands.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 4: Build Capabilities and Commands diff --git a/src/modules/bmb/workflows/create-agent/steps/step-05-name.md b/src/modules/bmb/workflows/create-agent/steps/step-05-name.md index a1dc92c1..88533ce6 100644 --- a/src/modules/bmb/workflows/create-agent/steps/step-05-name.md +++ b/src/modules/bmb/workflows/create-agent/steps/step-05-name.md @@ -3,7 +3,7 @@ name: 'step-05-name' description: 'Name the agent based on discovered characteristics' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent' # File References thisStepFile: '{workflow_path}/steps/step-05-name.md' @@ -15,8 +15,8 @@ outputFile: '{output_folder}/agent-identity-{project_name}.md' identityTemplate: '{workflow_path}/templates/agent-identity.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 5: Agent Naming and Identity diff --git a/src/modules/bmb/workflows/create-agent/steps/step-06-build.md b/src/modules/bmb/workflows/create-agent/steps/step-06-build.md index a4a55fe1..a1345c80 100644 --- a/src/modules/bmb/workflows/create-agent/steps/step-06-build.md +++ b/src/modules/bmb/workflows/create-agent/steps/step-06-build.md @@ -3,22 +3,22 @@ name: 'step-06-build' description: 'Generate complete YAML incorporating all discovered elements' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent' # File References thisStepFile: '{workflow_path}/steps/step-06-build.md' nextStepFile: '{workflow_path}/steps/step-07-validate.md' workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/agent-yaml-{project_name}.md' -moduleOutputFile: '{project-root}/{bmad_folder}/{target_module}/agents/{agent_filename}.agent.yaml' +moduleOutputFile: '{project-root}/.bmad/{target_module}/agents/{agent_filename}.agent.yaml' standaloneOutputFile: '{workflow_path}/data/{agent_filename}/{agent_filename}.agent.yaml' # Template References completeAgentTemplate: '{workflow_path}/templates/agent-complete-{agent_type}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 6: Build Complete Agent YAML diff --git a/src/modules/bmb/workflows/create-agent/steps/step-07-validate.md b/src/modules/bmb/workflows/create-agent/steps/step-07-validate.md index d9b26810..345294e0 100644 --- a/src/modules/bmb/workflows/create-agent/steps/step-07-validate.md +++ b/src/modules/bmb/workflows/create-agent/steps/step-07-validate.md @@ -3,22 +3,22 @@ name: 'step-07-validate' description: 'Quality check with personality and technical validation' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent' # File References thisStepFile: '{workflow_path}/steps/step-07-validate.md' nextStepFile: '{workflow_path}/steps/step-08-setup.md' workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/agent-validation-{project_name}.md' -agentValidationChecklist: '{project-root}/{bmad_folder}/bmb/workflows/create-agent/agent-validation-checklist.md' +agentValidationChecklist: '{project-root}/.bmad/bmb/workflows/create-agent/agent-validation-checklist.md' agentFile: '{{output_file_path}}' # Template References validationTemplate: '{workflow_path}/templates/validation-results.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 7: Quality Check and Validation diff --git a/src/modules/bmb/workflows/create-agent/steps/step-08-setup.md b/src/modules/bmb/workflows/create-agent/steps/step-08-setup.md index f6b6f635..d060dde0 100644 --- a/src/modules/bmb/workflows/create-agent/steps/step-08-setup.md +++ b/src/modules/bmb/workflows/create-agent/steps/step-08-setup.md @@ -3,7 +3,7 @@ name: 'step-08-setup' description: 'Set up the agent workspace with sidecar files for expert agents' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent' # File References thisStepFile: '{workflow_path}/steps/step-08-setup.md' @@ -16,8 +16,8 @@ agentSidecarFolder: '{{standalone_output_folder}}/{{agent_filename}}-sidecar' sidecarTemplate: '{workflow_path}/templates/expert-sidecar-structure.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 8: Expert Agent Workspace Setup diff --git a/src/modules/bmb/workflows/create-agent/steps/step-09-customize.md b/src/modules/bmb/workflows/create-agent/steps/step-09-customize.md index 909391aa..b6b0230f 100644 --- a/src/modules/bmb/workflows/create-agent/steps/step-09-customize.md +++ b/src/modules/bmb/workflows/create-agent/steps/step-09-customize.md @@ -3,21 +3,21 @@ name: 'step-09-customize' description: 'Optional personalization with customization file creation' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent' # File References thisStepFile: '{workflow_path}/steps/step-09-customize.md' nextStepFile: '{workflow_path}/steps/step-10-build-tools.md' workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/agent-customization-{project_name}.md' -configOutputFile: '{project-root}/{bmad_folder}/_cfg/agents/{target_module}-{agent_filename}.customize.yaml' +configOutputFile: '{project-root}/.bmad/_cfg/agents/{target_module}-{agent_filename}.customize.yaml' # Template References customizationTemplate: '{workflow_path}/templates/agent-customization.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 9: Optional Customization File diff --git a/src/modules/bmb/workflows/create-agent/steps/step-10-build-tools.md b/src/modules/bmb/workflows/create-agent/steps/step-10-build-tools.md index bd2423c5..4de2e7c5 100644 --- a/src/modules/bmb/workflows/create-agent/steps/step-10-build-tools.md +++ b/src/modules/bmb/workflows/create-agent/steps/step-10-build-tools.md @@ -3,7 +3,7 @@ name: 'step-10-build-tools' description: 'Handle build tools availability and generate compiled agent if needed' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent' # File References thisStepFile: '{workflow_path}/steps/step-10-build-tools.md' @@ -17,8 +17,8 @@ compiledAgentFile: '{{output_folder}}/{{agent_filename}}.md' buildHandlingTemplate: '{workflow_path}/templates/build-results.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 10: Build Tools Handling diff --git a/src/modules/bmb/workflows/create-agent/steps/step-11-celebrate.md b/src/modules/bmb/workflows/create-agent/steps/step-11-celebrate.md index 8df43934..7809264f 100644 --- a/src/modules/bmb/workflows/create-agent/steps/step-11-celebrate.md +++ b/src/modules/bmb/workflows/create-agent/steps/step-11-celebrate.md @@ -3,7 +3,7 @@ name: 'step-11-celebrate' description: 'Celebrate completion and guide next steps for using the agent' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/create-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/create-agent' # File References thisStepFile: '{workflow_path}/steps/step-11-celebrate.md' @@ -16,8 +16,8 @@ compiledAgentFile: '{{compiled_agent_path}}' completionTemplate: '{workflow_path}/templates/completion-summary.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 11: Celebration and Next Steps diff --git a/src/modules/bmb/workflows/create-agent/workflow.md b/src/modules/bmb/workflows/create-agent/workflow.md index 503df318..4363536d 100644 --- a/src/modules/bmb/workflows/create-agent/workflow.md +++ b/src/modules/bmb/workflows/create-agent/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from `{project-root}/{bmad_folder}/bmb/config.yaml`: +Load and read full config from `{project-root}/.bmad/bmb/config.yaml`: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` @@ -63,12 +63,12 @@ Load, read completely, then execute `steps/step-01-brainstorm.md` to begin the w # Technical documentation for agent building -agent_compilation: "{project-root}/{bmad_folder}/bmb/docs/agents/agent-compilation.md" -understanding_agent_types: "{project-root}/{bmad_folder}/bmb/docs/agents/understanding-agent-types.md" -simple_agent_architecture: "{project-root}/{bmad_folder}/bmb/docs/agents/simple-agent-architecture.md" -expert_agent_architecture: "{project-root}/{bmad_folder}/bmb/docs/agents/expert-agent-architecture.md" -module_agent_architecture: "{project-root}/{bmad_folder}/bmb/docs/agents/module-agent-architecture.md" -agent_menu_patterns: "{project-root}/{bmad_folder}/bmb/docs/agents/agent-menu-patterns.md" +agent_compilation: "{project-root}/.bmad/bmb/docs/agents/agent-compilation.md" +understanding_agent_types: "{project-root}/.bmad/bmb/docs/agents/understanding-agent-types.md" +simple_agent_architecture: "{project-root}/.bmad/bmb/docs/agents/simple-agent-architecture.md" +expert_agent_architecture: "{project-root}/.bmad/bmb/docs/agents/expert-agent-architecture.md" +module_agent_architecture: "{project-root}/.bmad/bmb/docs/agents/module-agent-architecture.md" +agent_menu_patterns: "{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md" # Data and templates @@ -77,15 +77,15 @@ brainstorm_context: "{workflow_path}/data/brainstorm-context.md" # Reference examples -simple_agent_examples: "{project-root}/src/modules/bmb/reference/agents/simple-examples/" -expert_agent_examples: "{project-root}/src/modules/bmb/reference/agents/expert-examples/" -module_agent_examples: "{project-root}/src/modules/bmb/reference/agents/module-examples/" +simple_agent_examples: "{project-root}/bmb/reference/agents/simple-examples/" +expert_agent_examples: "{project-root}/bmb/reference/agents/expert-examples/" +module_agent_examples: "{project-root}/bmb/reference/agents/module-examples/" # Output configuration -custom_agent_location: "{project-root}/{bmad_folder}/custom/src/agents" -module_output_file: "{project-root}/{bmad_folder}/{target_module}/agents/{agent_filename}.agent.yaml" +custom_agent_location: "{project-root}/.bmad/custom/src/agents" +module_output_file: "{project-root}/.bmad/{target_module}/agents/{agent_filename}.agent.yaml" standalone_output_folder: "{custom_agent_location}/{agent_filename}" standalone_output_file: "{standalone_output_folder}/{agent_filename}.agent.yaml" standalone_info_guide: "{standalone_output_folder}/info-and-installation-guide.md" -config_output_file: "{project-root}/{bmad_folder}/\_cfg/agents/{target_module}-{agent_filename}.customize.yaml" +config_output_file: "{project-root}/.bmad/\_cfg/agents/{target_module}-{agent_filename}.customize.yaml" diff --git a/src/modules/bmb/workflows/create-module/steps/step-01-init.md b/src/modules/bmb/workflows/create-module/steps/step-01-init.md index cef0968f..46e3a404 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-01-init.md +++ b/src/modules/bmb/workflows/create-module/steps/step-01-init.md @@ -2,8 +2,8 @@ nextStepFile: '{installed_path}/steps/step-02-concept.md' continueFile: '{installed_path}/steps/step-01b-continue.md' modulePlanTemplate: '{installed_path}/templates/module-plan.template.md' -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' customModuleLocation: '{custom_module_location}' modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md' --- diff --git a/src/modules/bmb/workflows/create-module/steps/step-02-concept.md b/src/modules/bmb/workflows/create-module/steps/step-02-concept.md index b77613c6..33a131bb 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-02-concept.md +++ b/src/modules/bmb/workflows/create-module/steps/step-02-concept.md @@ -1,10 +1,10 @@ --- -installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module' +installed_path: '{project-root}/.bmad/bmb/workflows/create-module' nextStepFile: '{installed_path}/steps/step-03-components.md' modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md' -moduleStructureGuide: '{project-root}/src/modules/bmb/workflows-legacy/create-module/module-structure.md' -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +moduleStructureGuide: '{project-root}/bmb/workflows/create-agent-legacy/create-module/module-structure.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 2: Define Module Concept and Scope diff --git a/src/modules/bmb/workflows/create-module/steps/step-03-components.md b/src/modules/bmb/workflows/create-module/steps/step-03-components.md index 265203ab..14b34852 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-03-components.md +++ b/src/modules/bmb/workflows/create-module/steps/step-03-components.md @@ -1,10 +1,10 @@ --- -installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module' +installed_path: '{project-root}/.bmad/bmb/workflows/create-module' nextStepFile: '{installed_path}/steps/step-04-structure.md' modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md' -agent_examples_path: '{project-root}/src/modules/bmb/reference/agents/module-examples' -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +agent_examples_path: '{project-root}/bmb/reference/agents/module-examples' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 3: Plan Module Components diff --git a/src/modules/bmb/workflows/create-module/steps/step-04-structure.md b/src/modules/bmb/workflows/create-module/steps/step-04-structure.md index ed12122d..17552469 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-04-structure.md +++ b/src/modules/bmb/workflows/create-module/steps/step-04-structure.md @@ -1,9 +1,9 @@ --- -installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module' +installed_path: '{project-root}/.bmad/bmb/workflows/create-module' nextStepFile: '{installed_path}/steps/step-05-config.md' modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md' -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 4: Create Module Structure diff --git a/src/modules/bmb/workflows/create-module/steps/step-05-config.md b/src/modules/bmb/workflows/create-module/steps/step-05-config.md index 55da3c50..71d848fa 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-05-config.md +++ b/src/modules/bmb/workflows/create-module/steps/step-05-config.md @@ -1,9 +1,9 @@ --- -installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module' +installed_path: '{project-root}/.bmad/bmb/workflows/create-module' nextStepFile: '{installed_path}/steps/step-06-agents.md' modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md' -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 5: Plan Module Configuration @@ -185,7 +185,7 @@ Update module-plan.md with configuration section: ### Result Configuration Structure The module.yaml will generate: -- Module configuration at: {bmad_folder}/{module_code}/config.yaml +- Module configuration at: .bmad/{module_code}/config.yaml - User settings stored as: [describe structure] ```` diff --git a/src/modules/bmb/workflows/create-module/steps/step-06-agents.md b/src/modules/bmb/workflows/create-module/steps/step-06-agents.md index 1108f96a..38c608ec 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-06-agents.md +++ b/src/modules/bmb/workflows/create-module/steps/step-06-agents.md @@ -1,11 +1,11 @@ --- -installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module' +installed_path: '{project-root}/.bmad/bmb/workflows/create-module' nextStepFile: '{installed_path}/steps/step-07-workflows.md' modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md' agentTemplate: '{installed_path}/templates/agent.template.md' -agent_examples_path: '{project-root}/src/modules/bmb/reference/agents/module-examples' -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +agent_examples_path: '{project-root}/bmb/reference/agents/module-examples' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 6: Create Module Agents @@ -183,7 +183,7 @@ agent: triggers: - party-mode: input: SPM - route: '{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md' + route: '{project-root}/.bmad/core/workflows/edit-agent/workflow.md' type: exec - expert-chat: input: CH @@ -204,7 +204,7 @@ agent: # Workflow only for complex processes - trigger: 'complex-process' - route: '{project-root}/{bmad_folder}/{custom_module}/workflows/[workflow]/workflow.md' + route: '{project-root}/.bmad/{custom_module}/workflows/[workflow]/workflow.md' description: 'Complex process [icon]' # Quick inline actions diff --git a/src/modules/bmb/workflows/create-module/steps/step-07-workflows.md b/src/modules/bmb/workflows/create-module/steps/step-07-workflows.md index f884c2cf..202fa4e8 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-07-workflows.md +++ b/src/modules/bmb/workflows/create-module/steps/step-07-workflows.md @@ -1,10 +1,10 @@ --- -installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module' +installed_path: '{project-root}/.bmad/bmb/workflows/create-module' nextStepFile: '{installed_path}/steps/step-08-installer.md' modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md' workflowPlanTemplate: '{installed_path}/templates/workflow-plan-template.md' -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 7: Review Workflow Plans diff --git a/src/modules/bmb/workflows/create-module/steps/step-08-installer.md b/src/modules/bmb/workflows/create-module/steps/step-08-installer.md index 4332ab68..504e34a2 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-08-installer.md +++ b/src/modules/bmb/workflows/create-module/steps/step-08-installer.md @@ -1,11 +1,11 @@ --- -installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module' +installed_path: '{project-root}/.bmad/bmb/workflows/create-module' nextStepFile: '{installed_path}/steps/step-09-documentation.md' modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md' installerTemplate: '{installed_path}/templates/installer.template.js' installConfigTemplate: '{installed_path}/templates/install-config.template.yaml' -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 8: Setup Module Installer @@ -131,7 +131,7 @@ Update module-plan.md with installer section: 1. User runs: `bmad install {module_name}` 2. Installer asks: [list of questions] -3. Creates: {bmad_folder}/{module_name}/ +3. Creates: .bmad/{module_name}/ 4. Generates: config.yaml with user settings ### Validation diff --git a/src/modules/bmb/workflows/create-module/steps/step-09-documentation.md b/src/modules/bmb/workflows/create-module/steps/step-09-documentation.md index 8d98c239..77c9310e 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-09-documentation.md +++ b/src/modules/bmb/workflows/create-module/steps/step-09-documentation.md @@ -1,10 +1,10 @@ --- -installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module' +installed_path: '{project-root}/.bmad/bmb/workflows/create-module' nextStepFile: '{installed_path}/steps/step-10-roadmap.md' modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md' moduleReadmeFile: '{custom_module_location}/{module_name}/README.md' -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 9: Create Module Documentation @@ -140,7 +140,7 @@ bmad install {module_name} ## Configuration -The module can be configured in `{bmad_folder}/{module_name}/config.yaml` +The module can be configured in `.bmad/{module_name}/config.yaml` **Key Settings:** diff --git a/src/modules/bmb/workflows/create-module/steps/step-10-roadmap.md b/src/modules/bmb/workflows/create-module/steps/step-10-roadmap.md index 39807a7d..b49e4a25 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-10-roadmap.md +++ b/src/modules/bmb/workflows/create-module/steps/step-10-roadmap.md @@ -1,10 +1,10 @@ --- -installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module' +installed_path: '{project-root}/.bmad/bmb/workflows/create-module' nextStepFile: '{installed_path}/steps/step-11-validate.md' modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md' moduleTodoFile: '{custom_module_location}/{module_name}/TODO.md' -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 10: Generate Development Roadmap diff --git a/src/modules/bmb/workflows/create-module/steps/step-11-validate.md b/src/modules/bmb/workflows/create-module/steps/step-11-validate.md index 31182408..56a5dd9a 100644 --- a/src/modules/bmb/workflows/create-module/steps/step-11-validate.md +++ b/src/modules/bmb/workflows/create-module/steps/step-11-validate.md @@ -2,8 +2,8 @@ workflowFile: '{installed_path}/workflow.md' modulePlanFile: '{custom_module_location}/{module_name}/module-plan-{module_name}.md' validationChecklist: '{installed_path}/validation.md' -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 11: Validate and Finalize Module @@ -297,8 +297,8 @@ Display: **Module Creation Complete!** [A] Advanced Elicitation [P] Party Mode [ #### Menu Handling Logic: -- IF A: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml for reflection on process -- IF P: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md to celebrate completion +- IF A: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml for reflection on process +- IF P: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md to celebrate completion - IF C: Mark as complete and exit gracefully - IF Any other comments or queries: help user respond then redisplay menu diff --git a/src/modules/bmb/workflows/create-module/templates/agent.template.md b/src/modules/bmb/workflows/create-module/templates/agent.template.md index 93367e69..45941dcd 100644 --- a/src/modules/bmb/workflows/create-module/templates/agent.template.md +++ b/src/modules/bmb/workflows/create-module/templates/agent.template.md @@ -55,7 +55,7 @@ agent: triggers: - party-mode: input: SPM or fuzzy match start party mode - route: '{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md' + route: '{project-root}/.bmad/core/workflows/edit-agent/workflow.md' data: what is being discussed or suggested with the command type: exec - expert-chat: @@ -83,7 +83,7 @@ agent: # Workflow for complex processes - trigger: 'generate-report' - route: '{project-root}/{bmad_folder}/{custom_module}/workflows/report-gen/workflow.md' + route: '{project-root}/.bmad/{custom_module}/workflows/report-gen/workflow.md' description: 'Generate detailed report ๐Ÿ“Š' # Exec with internal prompt reference @@ -156,7 +156,7 @@ Expert agents support three types of menu actions: ```yaml - trigger: 'generate-report' - route: '{project-root}/{bmad_folder}/{custom_module}/workflows/report-gen/workflow.md' + route: '{project-root}/.bmad/{custom_module}/workflows/report-gen/workflow.md' description: 'Generate report ๐Ÿ“Š' ``` @@ -171,7 +171,7 @@ Expert agents support three types of menu actions: 2. **Variable Usage**: - `{agent_sidecar_folder}` resolves to the agents sidecar folder destination after installation - - `{bmad_folder}` resolves to .bmad + - `.bmad` resolves to .bmad - `{custom_module}` resolves to custom/src/modules - `{module}` is your module code/name @@ -268,7 +268,7 @@ Analyze the visual design with my signature dramatic flair menu: # Core interactions - multi: "[CH] Chat with Caravaggio or [SPM] Start Party Mode" triggers: - party-mode: input: SPM or fuzzy match start party mode -route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md" +route: "{project-root}/.bmad/core/workflows/edit-agent/workflow.md" data: what's being discussed, plus custom party agents if specified type: exec - expert-chat: input: CH or fuzzy match validate agent @@ -305,11 +305,11 @@ type: action triggers: - pitch-deck: input: PD or fuzzy match pitch deck - route: "{project-root}/{bmad_folder}/{custom_module}/workflows/pitch-deck/workflow.md" + route: "{project-root}/.bmad/{custom_module}/workflows/pitch-deck/workflow.md" description: 'Investor pitch deck ๐Ÿ“ˆ' - explainer: input: EX or fuzzy match explainer - route: "{project-root}/{bmad_folder}/{custom_module}/workflows/explainer/workflow.md" + route: "{project-root}/.bmad/{custom_module}/workflows/explainer/workflow.md" description: 'Video explainer ๐ŸŽฅ' - trigger: 'save-project' diff --git a/src/modules/bmb/workflows/create-module/templates/module.template.yaml b/src/modules/bmb/workflows/create-module/templates/module.template.yaml index b4d64bf3..045c73d1 100644 --- a/src/modules/bmb/workflows/create-module/templates/module.template.yaml +++ b/src/modules/bmb/workflows/create-module/templates/module.template.yaml @@ -50,4 +50,4 @@ prompt: # STATIC path: # data_path: -# result: "{project-root}/{bmad_folder}/{module_name}/data" +# result: "{project-root}/.bmad/{module_name}/data" diff --git a/src/modules/bmb/workflows/create-module/workflow.md b/src/modules/bmb/workflows/create-module/workflow.md index c0038a3c..cf633945 100644 --- a/src/modules/bmb/workflows/create-module/workflow.md +++ b/src/modules/bmb/workflows/create-module/workflow.md @@ -2,7 +2,7 @@ name: create-module description: 'Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure' web_bundle: true -installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module' +installed_path: '{project-root}/.bmad/bmb/workflows/create-module' --- # Create Module Workflow @@ -46,7 +46,7 @@ installed_path: '{project-root}/{bmad_folder}/bmb/workflows/create-module' ### 1. Module Configuration Loading -Load and read full config from {project-root}/{bmad_folder}/bmb/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/bmb/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `custom_module_location` diff --git a/src/modules/bmb/workflows/create-workflow/steps/step-01-init.md b/src/modules/bmb/workflows/create-workflow/steps/step-01-init.md index 796d2eb6..d0883c84 100644 --- a/src/modules/bmb/workflows/create-workflow/steps/step-01-init.md +++ b/src/modules/bmb/workflows/create-workflow/steps/step-01-init.md @@ -3,7 +3,7 @@ name: 'step-01-init' description: 'Initialize workflow creation session by gathering project information and setting up unique workflow folder' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow' # File References thisStepFile: '{workflow_path}/steps/step-01-init.md' @@ -97,7 +97,7 @@ After getting the workflow name: Based on the module selection, confirm the target location: -- For bmb module: `{custom_workflow_location}` (defaults to `{bmad_folder}/custom/src/workflows`) +- For bmb module: `{custom_workflow_location}` (defaults to `.bmad/custom/src/workflows`) - For other modules: Check their module.yaml for custom workflow locations - Confirm the exact folder path where the workflow will be created - Store the confirmed path as `{targetWorkflowPath}` diff --git a/src/modules/bmb/workflows/create-workflow/steps/step-02-gather.md b/src/modules/bmb/workflows/create-workflow/steps/step-02-gather.md index 6c6e7870..21881919 100644 --- a/src/modules/bmb/workflows/create-workflow/steps/step-02-gather.md +++ b/src/modules/bmb/workflows/create-workflow/steps/step-02-gather.md @@ -3,7 +3,7 @@ name: 'step-02-gather' description: 'Gather comprehensive requirements for the workflow being created' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow' # File References thisStepFile: '{workflow_path}/steps/step-02-gather.md' @@ -13,8 +13,8 @@ targetWorkflowPath: '{custom_stand_alone_location}/workflows/{new_workflow_name} workflowPlanFile: '{targetWorkflowPath}/workflow-plan-{new_workflow_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References # No template needed - will append requirements directly to workflow plan --- @@ -90,7 +90,7 @@ Let's load some examples to help you decide the workflow pattern: Load and reference the Meal Prep & Nutrition Plan workflow as an example: ``` -Read: {project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/workflow.md +Read: {project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md ``` This shows a linear workflow structure. Now let's explore your desired pattern: @@ -104,7 +104,7 @@ This shows a linear workflow structure. Now let's explore your desired pattern: **Based on our reference examples:** - **Linear**: Like Meal Prep Plan (Init โ†’ Profile โ†’ Assessment โ†’ Strategy โ†’ Shopping โ†’ Prep) - - See: `{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/` + - See: `{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/` - **Looping**: User Story Generator (Generate โ†’ Review โ†’ Refine โ†’ Generate more... until done) - **Branching**: Architecture Decision (Analyze โ†’ Choose pattern โ†’ Implement based on choice) - **Iterative**: Document Review (Load โ†’ Analyze โ†’ Suggest changes โ†’ Implement โ†’ Repeat until approved) diff --git a/src/modules/bmb/workflows/create-workflow/steps/step-03-tools-configuration.md b/src/modules/bmb/workflows/create-workflow/steps/step-03-tools-configuration.md index aa282882..e672c422 100644 --- a/src/modules/bmb/workflows/create-workflow/steps/step-03-tools-configuration.md +++ b/src/modules/bmb/workflows/create-workflow/steps/step-03-tools-configuration.md @@ -3,7 +3,7 @@ name: 'step-03-tools-configuration' description: 'Configure all required tools (core, memory, external) and installation requirements in one comprehensive step' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow' # File References thisStepFile: '{workflow_path}/steps/step-03-tools-configuration.md' @@ -13,11 +13,11 @@ targetWorkflowPath: '{custom_stand_alone_location}/workflows/{new_workflow_name} workflowPlanFile: '{targetWorkflowPath}/workflow-plan-{new_workflow_name}.md' # Documentation References -commonToolsCsv: '{project-root}/{bmad_folder}/bmb/docs/workflows/common-workflow-tools.csv' +commonToolsCsv: '{project-root}/.bmad/bmb/docs/workflows/common-workflow-tools.csv' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References # No template needed - will append tools configuration directly to workflow plan --- diff --git a/src/modules/bmb/workflows/create-workflow/steps/step-04-plan-review.md b/src/modules/bmb/workflows/create-workflow/steps/step-04-plan-review.md index 93cd7a02..79920988 100644 --- a/src/modules/bmb/workflows/create-workflow/steps/step-04-plan-review.md +++ b/src/modules/bmb/workflows/create-workflow/steps/step-04-plan-review.md @@ -3,7 +3,7 @@ name: 'step-04-plan-review' description: 'Review complete workflow plan (requirements + tools) and get user approval before design' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow' # File References thisStepFile: '{workflow_path}/steps/step-04-plan-review.md' @@ -14,8 +14,8 @@ targetWorkflowPath: '{custom_stand_alone_location}/workflows/{new_workflow_name} workflowPlanFile: '{targetWorkflowPath}/workflow-plan-{new_workflow_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References # No template needed - will append review summary directly to workflow plan --- diff --git a/src/modules/bmb/workflows/create-workflow/steps/step-05-output-format-design.md b/src/modules/bmb/workflows/create-workflow/steps/step-05-output-format-design.md index 5beb5aba..d072fe2a 100644 --- a/src/modules/bmb/workflows/create-workflow/steps/step-05-output-format-design.md +++ b/src/modules/bmb/workflows/create-workflow/steps/step-05-output-format-design.md @@ -3,7 +3,7 @@ name: 'step-05-output-format-design' description: 'Design the output format for workflows that produce documents or files' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow' # File References thisStepFile: '{workflow_path}/steps/step-05-output-format-design.md' @@ -13,8 +13,8 @@ targetWorkflowPath: '{custom_stand_alone_location}/workflows/{new_workflow_name} workflowPlanFile: '{targetWorkflowPath}/workflow-plan-{new_workflow_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 5: Output Format Design diff --git a/src/modules/bmb/workflows/create-workflow/steps/step-06-design.md b/src/modules/bmb/workflows/create-workflow/steps/step-06-design.md index 1dcc6703..7040d19a 100644 --- a/src/modules/bmb/workflows/create-workflow/steps/step-06-design.md +++ b/src/modules/bmb/workflows/create-workflow/steps/step-06-design.md @@ -3,7 +3,7 @@ name: 'step-06-design' description: 'Design the workflow structure and step sequence based on gathered requirements, tools configuration, and output format' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow' # File References thisStepFile: '{workflow_path}/steps/step-06-design.md' @@ -14,8 +14,8 @@ targetWorkflowPath: '{custom_stand_alone_location}/workflows/{new_workflow_name} workflowPlanFile: '{targetWorkflowPath}/workflow-plan-{new_workflow_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References # No template needed - will append design details directly to workflow plan --- @@ -70,11 +70,11 @@ To collaboratively design the workflow structure, step sequence, and interaction When designing, you may load these documents as needed: -- `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md` - Step file structure -- `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-01-init-continuable-template.md` - Continuable init step template -- `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-1b-template.md` - Continuation step template -- `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md` - Workflow configuration -- `{project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/workflow.md` - Complete example +- `{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md` - Step file structure +- `{project-root}/.bmad/bmb/docs/workflows/templates/step-01-init-continuable-template.md` - Continuable init step template +- `{project-root}/.bmad/bmb/docs/workflows/templates/step-1b-template.md` - Continuation step template +- `{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md` - Workflow configuration +- `{project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md` - Complete example ## WORKFLOW DESIGN PROCESS: @@ -85,13 +85,13 @@ Let's reference our step creation documentation for best practices: Load and reference step-file architecture guide: ``` -Read: {project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md +Read: {project-root}/.bmad/bmb/docs/workflows/templates/step-template.md ``` This shows the standard structure for step files. Also reference: ``` -Read: {project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-1b-template.md +Read: {project-root}/.bmad/bmb/docs/workflows/templates/step-1b-template.md ``` This shows the continuation step pattern for workflows that might take multiple sessions. diff --git a/src/modules/bmb/workflows/create-workflow/steps/step-07-build.md b/src/modules/bmb/workflows/create-workflow/steps/step-07-build.md index 9a505b0d..b884c8c9 100644 --- a/src/modules/bmb/workflows/create-workflow/steps/step-07-build.md +++ b/src/modules/bmb/workflows/create-workflow/steps/step-07-build.md @@ -3,7 +3,7 @@ name: 'step-07-build' description: 'Generate all workflow files based on the approved plan' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow' # File References thisStepFile: '{workflow_path}/steps/step-07-build.md' @@ -14,10 +14,10 @@ targetWorkflowPath: '{custom_stand_alone_location}/workflows/{new_workflow_name} workflowPlanFile: '{targetWorkflowPath}/workflow-plan-{new_workflow_name}.md' # Template References -workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md' -stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md' -stepInitContinuableTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-01-init-continuable-template.md' -step1bTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-1b-template.md' +workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md' +stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md' +stepInitContinuableTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-01-init-continuable-template.md' +step1bTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-1b-template.md' # No content templates needed - will create content as needed during build # No build summary template needed - will append summary directly to workflow plan --- @@ -68,11 +68,11 @@ To generate all the workflow files (workflow.md, step files, templates, and supp ## BUILD REFERENCE MATERIALS: -- When building each step file, you must follow template `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md` -- When building continuable step-01-init.md files, use template `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-01-init-continuable-template.md` -- When building continuation steps, use template `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-1b-template.md` -- When building the main workflow.md file, you must follow template `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md` -- Example step files from {project-root}/{bmad_folder}/bmb/reference/workflows/meal-prep-nutrition/workflow.md for patterns +- When building each step file, you must follow template `{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md` +- When building continuable step-01-init.md files, use template `{project-root}/.bmad/bmb/docs/workflows/templates/step-01-init-continuable-template.md` +- When building continuation steps, use template `{project-root}/.bmad/bmb/docs/workflows/templates/step-1b-template.md` +- When building the main workflow.md file, you must follow template `{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md` +- Example step files from {project-root}/.bmad/bmb/reference/workflows/meal-prep-nutrition/workflow.md for patterns ## FILE GENERATION SEQUENCE: @@ -108,7 +108,7 @@ Create the workflow folder structure in the target location: โ””โ”€โ”€ [as needed] ``` -For bmb module, this will be: `{bmad_folder}/custom/src/workflows/{workflow_name}/` +For bmb module, this will be: `.bmad/custom/src/workflows/{workflow_name}/` For other modules, check their module.yaml for custom_workflow_location ### 3. Generate workflow.md @@ -117,7 +117,7 @@ Load and follow {workflowTemplate}: - Create workflow.md using template structure - Insert workflow name and description -- Configure all path variables ({project-root}, {_bmad_folder_}, {workflow_path}) +- Configure all path variables ({project-root}, .bmad, {workflow_path}) - Set web_bundle flag to true unless user has indicated otherwise - Define role and goal - Include initialization path to step-01 diff --git a/src/modules/bmb/workflows/create-workflow/steps/step-08-review.md b/src/modules/bmb/workflows/create-workflow/steps/step-08-review.md index 82c3412a..44611bc2 100644 --- a/src/modules/bmb/workflows/create-workflow/steps/step-08-review.md +++ b/src/modules/bmb/workflows/create-workflow/steps/step-08-review.md @@ -3,7 +3,7 @@ name: 'step-08-review' description: 'Review the generated workflow and provide final validation and next steps' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow' # File References thisStepFile: '{workflow_path}/steps/step-08-review.md' @@ -14,8 +14,8 @@ targetWorkflowPath: '{custom_stand_alone_location}/workflows/{new_workflow_name} workflowPlanFile: '{targetWorkflowPath}/workflow-plan-{new_workflow_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References # No review template needed - will append review summary directly to workflow plan diff --git a/src/modules/bmb/workflows/create-workflow/steps/step-09-complete.md b/src/modules/bmb/workflows/create-workflow/steps/step-09-complete.md index 267104bc..f7cd05e2 100644 --- a/src/modules/bmb/workflows/create-workflow/steps/step-09-complete.md +++ b/src/modules/bmb/workflows/create-workflow/steps/step-09-complete.md @@ -3,7 +3,7 @@ name: 'step-09-complete' description: 'Final completion and wrap-up of workflow creation process' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/create-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/create-workflow' # File References thisStepFile: '{workflow_path}/steps/step-09-complete.md' diff --git a/src/modules/bmb/workflows/create-workflow/workflow.md b/src/modules/bmb/workflows/create-workflow/workflow.md index ab79d27c..7bbcd5c2 100644 --- a/src/modules/bmb/workflows/create-workflow/workflow.md +++ b/src/modules/bmb/workflows/create-workflow/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/{bmad_folder}/bmb/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/bmb/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `custom_stand_alone_location` diff --git a/src/modules/bmb/workflows/edit-agent/steps/step-01-discover-intent.md b/src/modules/bmb/workflows/edit-agent/steps/step-01-discover-intent.md index e9ed1d69..45b7ed5a 100644 --- a/src/modules/bmb/workflows/edit-agent/steps/step-01-discover-intent.md +++ b/src/modules/bmb/workflows/edit-agent/steps/step-01-discover-intent.md @@ -3,15 +3,15 @@ name: 'step-01-discover-intent' description: 'Get agent path and user editing goals' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/edit-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/edit-agent' # File References thisStepFile: '{workflow_path}/steps/step-01-discover-intent.md' nextStepFile: '{workflow_path}/steps/step-02-analyze-agent.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 1: Discover Edit Intent diff --git a/src/modules/bmb/workflows/edit-agent/steps/step-02-analyze-agent.md b/src/modules/bmb/workflows/edit-agent/steps/step-02-analyze-agent.md index b4a0d50b..1d3f341d 100644 --- a/src/modules/bmb/workflows/edit-agent/steps/step-02-analyze-agent.md +++ b/src/modules/bmb/workflows/edit-agent/steps/step-02-analyze-agent.md @@ -3,27 +3,27 @@ name: 'step-02-analyze-agent' description: 'Load agent and relevant documentation for analysis' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/edit-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/edit-agent' # File References thisStepFile: '{workflow_path}/steps/step-02-analyze-agent.md' nextStepFile: '{workflow_path}/steps/step-03-propose-changes.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Documentation References (load JIT based on user goals) -understanding_agent_types: '{project-root}/{bmad_folder}/bmb/docs/agents/understanding-agent-types.md' -agent_compilation: '{project-root}/{bmad_folder}/bmb/docs/agents/agent-compilation.md' -simple_architecture: '{project-root}/{bmad_folder}/bmb/docs/agents/simple-agent-architecture.md' -expert_architecture: '{project-root}/{bmad_folder}/bmb/docs/agents/expert-agent-architecture.md' -module_architecture: '{project-root}/{bmad_folder}/bmb/docs/agents/module-agent-architecture.md' -menu_patterns: '{project-root}/{bmad_folder}/bmb/docs/agents/agent-menu-patterns.md' -communication_presets: '{project-root}/{bmad_folder}/bmb/workflows/create-agent/data/communication-presets.csv' -reference_simple_agent: '{project-root}/{bmad_folder}/bmb/reference/agents/simple-examples/commit-poet.agent.yaml' -reference_expert_agent: '{project-root}/{bmad_folder}/bmb/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml' -validation: '{project-root}/{bmad_folder}/bmb/workflows/create-agent/data/agent-validation-checklist.md' +understanding_agent_types: '{project-root}/.bmad/bmb/docs/agents/understanding-agent-types.md' +agent_compilation: '{project-root}/.bmad/bmb/docs/agents/agent-compilation.md' +simple_architecture: '{project-root}/.bmad/bmb/docs/agents/simple-agent-architecture.md' +expert_architecture: '{project-root}/.bmad/bmb/docs/agents/expert-agent-architecture.md' +module_architecture: '{project-root}/.bmad/bmb/docs/agents/module-agent-architecture.md' +menu_patterns: '{project-root}/.bmad/bmb/docs/agents/agent-menu-patterns.md' +communication_presets: '{project-root}/.bmad/bmb/workflows/create-agent/data/communication-presets.csv' +reference_simple_agent: '{project-root}/.bmad/bmb/reference/agents/simple-examples/commit-poet.agent.yaml' +reference_expert_agent: '{project-root}/.bmad/bmb/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml' +validation: '{project-root}/.bmad/bmb/workflows/create-agent/data/agent-validation-checklist.md' --- # Step 2: Analyze Agent diff --git a/src/modules/bmb/workflows/edit-agent/steps/step-03-propose-changes.md b/src/modules/bmb/workflows/edit-agent/steps/step-03-propose-changes.md index ddfe755e..6b6c17d4 100644 --- a/src/modules/bmb/workflows/edit-agent/steps/step-03-propose-changes.md +++ b/src/modules/bmb/workflows/edit-agent/steps/step-03-propose-changes.md @@ -3,7 +3,7 @@ name: 'step-03-propose-changes' description: 'Propose specific changes and get approval' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/edit-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/edit-agent' # File References thisStepFile: '{workflow_path}/steps/step-03-propose-changes.md' @@ -11,12 +11,12 @@ nextStepFile: '{workflow_path}/steps/step-04-apply-changes.md' agentFile: '{{agent_path}}' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Documentation References (load JIT if needed) -communication_presets: '{project-root}/{bmad_folder}/bmb/workflows/create-agent/data/communication-presets.csv' -agent_compilation: '{project-root}/{bmad_folder}/bmb/docs/agents/agent-compilation.md' +communication_presets: '{project-root}/.bmad/bmb/workflows/create-agent/data/communication-presets.csv' +agent_compilation: '{project-root}/.bmad/bmb/docs/agents/agent-compilation.md' --- # Step 3: Propose Changes diff --git a/src/modules/bmb/workflows/edit-agent/steps/step-04-apply-changes.md b/src/modules/bmb/workflows/edit-agent/steps/step-04-apply-changes.md index a59f7548..e6c3b8ac 100644 --- a/src/modules/bmb/workflows/edit-agent/steps/step-04-apply-changes.md +++ b/src/modules/bmb/workflows/edit-agent/steps/step-04-apply-changes.md @@ -3,7 +3,7 @@ name: 'step-04-apply-changes' description: 'Apply approved changes to the agent' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/edit-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/edit-agent' # File References thisStepFile: '{workflow_path}/steps/step-04-apply-changes.md' @@ -11,8 +11,8 @@ agentFile: '{{agent_path}}' nextStepFile: '{workflow_path}/steps/step-05-validate.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 4: Apply Changes diff --git a/src/modules/bmb/workflows/edit-agent/steps/step-05-validate.md b/src/modules/bmb/workflows/edit-agent/steps/step-05-validate.md index 2cc95595..0321d5c3 100644 --- a/src/modules/bmb/workflows/edit-agent/steps/step-05-validate.md +++ b/src/modules/bmb/workflows/edit-agent/steps/step-05-validate.md @@ -3,19 +3,19 @@ name: 'step-05-validate' description: 'Validate that changes work correctly' # Path Definitions -workflow_path: '{project-root}/src/modules/bmb/workflows/edit-agent' +workflow_path: '{project-root}/bmb/workflows/create-agent/edit-agent' # File References thisStepFile: '{workflow_path}/steps/step-05-validate.md' agentFile: '{{agent_path}}' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Documentation References (load JIT) -validation: '{project-root}/{bmad_folder}/bmb/workflows/create-agent/data/agent-validation-checklist.md' -agent_compilation: '{project-root}/{bmad_folder}/bmb/docs/agents/agent-compilation.md' +validation: '{project-root}/.bmad/bmb/workflows/create-agent/data/agent-validation-checklist.md' +agent_compilation: '{project-root}/.bmad/bmb/docs/agents/agent-compilation.md' --- # Step 5: Validate Changes diff --git a/src/modules/bmb/workflows/edit-agent/workflow.md b/src/modules/bmb/workflows/edit-agent/workflow.md index 81462cbb..6caeefa3 100644 --- a/src/modules/bmb/workflows/edit-agent/workflow.md +++ b/src/modules/bmb/workflows/edit-agent/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/{bmad_folder}/bmb/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/bmb/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmb/workflows/edit-workflow/steps/step-01-analyze.md b/src/modules/bmb/workflows/edit-workflow/steps/step-01-analyze.md index 963235b9..9f44b0f4 100644 --- a/src/modules/bmb/workflows/edit-workflow/steps/step-01-analyze.md +++ b/src/modules/bmb/workflows/edit-workflow/steps/step-01-analyze.md @@ -3,7 +3,7 @@ name: 'step-01-analyze' description: 'Load and deeply understand the target workflow' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/edit-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/edit-workflow' # File References thisStepFile: '{workflow_path}/steps/step-01-analyze.md' @@ -129,9 +129,9 @@ Based on what the user wants to edit: Load reference documentation as needed: -- `{project-root}/{bmad_folder}/bmb/docs/workflows/architecture.md` -- `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md` -- `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md` +- `{project-root}/.bmad/bmb/docs/workflows/architecture.md` +- `{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md` +- `{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md` Check against best practices: diff --git a/src/modules/bmb/workflows/edit-workflow/steps/step-02-discover.md b/src/modules/bmb/workflows/edit-workflow/steps/step-02-discover.md index 0aae7bb7..a9b9f206 100644 --- a/src/modules/bmb/workflows/edit-workflow/steps/step-02-discover.md +++ b/src/modules/bmb/workflows/edit-workflow/steps/step-02-discover.md @@ -3,7 +3,7 @@ name: 'step-02-discover' description: 'Discover improvement goals collaboratively' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/edit-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/edit-workflow' # File References thisStepFile: '{workflow_path}/steps/step-02-discover.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/workflow-edit-{target_workflow_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References goalsTemplate: '{workflow_path}/templates/improvement-goals.md' diff --git a/src/modules/bmb/workflows/edit-workflow/steps/step-03-improve.md b/src/modules/bmb/workflows/edit-workflow/steps/step-03-improve.md index 4c2bc079..6ed46e5f 100644 --- a/src/modules/bmb/workflows/edit-workflow/steps/step-03-improve.md +++ b/src/modules/bmb/workflows/edit-workflow/steps/step-03-improve.md @@ -3,7 +3,7 @@ name: 'step-03-improve' description: 'Facilitate collaborative improvements to the workflow' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/edit-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/edit-workflow' # File References thisStepFile: '{workflow_path}/steps/step-03-improve.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/workflow-edit-{target_workflow_name}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References improvementLogTemplate: '{workflow_path}/templates/improvement-log.md' @@ -69,9 +69,9 @@ To facilitate collaborative improvements to the workflow, working iteratively on Load documentation as needed for specific improvements: -- `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md` -- `{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md` -- `{project-root}/{bmad_folder}/bmb/docs/workflows/architecture.md` +- `{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md` +- `{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md` +- `{project-root}/.bmad/bmb/docs/workflows/architecture.md` ### 2. Address Each Improvement Iteratively diff --git a/src/modules/bmb/workflows/edit-workflow/steps/step-04-validate.md b/src/modules/bmb/workflows/edit-workflow/steps/step-04-validate.md index c2e67bca..157fe11b 100644 --- a/src/modules/bmb/workflows/edit-workflow/steps/step-04-validate.md +++ b/src/modules/bmb/workflows/edit-workflow/steps/step-04-validate.md @@ -3,7 +3,7 @@ name: 'step-04-validate' description: 'Validate improvements and prepare for completion' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/edit-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/edit-workflow' # File References thisStepFile: '{workflow_path}/steps/step-04-validate.md' @@ -12,8 +12,8 @@ outputFile: '{output_folder}/workflow-edit-{target_workflow_name}.md' nextStepFile: '{workflow_path}/steps/step-05-compliance-check.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' # Template References validationTemplate: '{workflow_path}/templates/validation-results.md' diff --git a/src/modules/bmb/workflows/edit-workflow/steps/step-05-compliance-check.md b/src/modules/bmb/workflows/edit-workflow/steps/step-05-compliance-check.md index 0fe97af5..cd5764fe 100644 --- a/src/modules/bmb/workflows/edit-workflow/steps/step-05-compliance-check.md +++ b/src/modules/bmb/workflows/edit-workflow/steps/step-05-compliance-check.md @@ -3,17 +3,17 @@ name: 'step-05-compliance-check' description: 'Run comprehensive compliance validation on the edited workflow' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/edit-workflow' +workflow_path: '{project-root}/.bmad/bmb/workflows/edit-workflow' # File References thisStepFile: '{workflow_path}/steps/step-05-compliance-check.md' workflowFile: '{workflow_path}/workflow.md' editedWorkflowPath: '{target_workflow_path}' -complianceCheckWorkflow: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check/workflow.md' +complianceCheckWorkflow: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check/workflow.md' outputFile: '{output_folder}/workflow-edit-{target_workflow_name}.md' # Task References -complianceCheckTask: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check/workflow.md' +complianceCheckTask: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check/workflow.md' --- # Step 5: Compliance Validation diff --git a/src/modules/bmb/workflows/edit-workflow/workflow.md b/src/modules/bmb/workflows/edit-workflow/workflow.md index d4d62f96..916fdb88 100644 --- a/src/modules/bmb/workflows/edit-workflow/workflow.md +++ b/src/modules/bmb/workflows/edit-workflow/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/{bmad_folder}/bmb/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/bmb/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-01-validate-goal.md b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-01-validate-goal.md index ed715955..01ae2622 100644 --- a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-01-validate-goal.md +++ b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-01-validate-goal.md @@ -3,7 +3,7 @@ name: 'step-01-validate-goal' description: 'Confirm workflow path and validation goals before proceeding' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check' +workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check' # File References thisStepFile: '{workflow_path}/steps/step-01-validate-goal.md' @@ -15,8 +15,8 @@ complianceReportFile: '{output_folder}/workflow-compliance-report-{workflow_name complianceReportTemplate: '{workflow_path}/templates/compliance-report.md' # Documentation References -stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md' -workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md' +stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md' +workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md' --- # Step 1: Goal Confirmation and Workflow Target diff --git a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md index 07550305..dbdcc80f 100644 --- a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md +++ b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md @@ -3,7 +3,7 @@ name: 'step-02-workflow-validation' description: 'Validate workflow.md against workflow-template.md standards' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check' +workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check' # File References thisStepFile: '{workflow_path}/steps/step-02-workflow-validation.md' @@ -16,8 +16,8 @@ targetWorkflowFile: '{target_workflow_path}' complianceReportTemplate: '{workflow_path}/templates/compliance-report.md' # Documentation References -stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md' -workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md' +stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md' +workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md' --- # Step 2: Workflow.md Validation @@ -132,10 +132,10 @@ For each deviation: "**Initialization Validation:**" -- Configuration Loading uses correct path format: `{project-root}/{*bmad_folder*}/[module]/config.yaml` (variable substitution pattern) +- Configuration Loading uses correct path format: `{project-root}/.bmad/[module]/config.yaml` (variable substitution pattern) - First step follows pattern: `step-01-init.md` OR documented deviation - Required config variables properly listed -- Variables use proper substitution pattern: {project-root}, {_bmad_folder_}, {workflow_path}, etc. +- Variables use proper substitution pattern: {project-root}, .bmad, {workflow_path}, etc. For violations: diff --git a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-03-step-validation.md b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-03-step-validation.md index 343b2cff..3f74a623 100644 --- a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-03-step-validation.md +++ b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-03-step-validation.md @@ -3,7 +3,7 @@ name: 'step-03-step-validation' description: 'Validate each step file against step-template.md standards' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check' +workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check' # File References thisStepFile: '{workflow_path}/steps/step-03-step-validation.md' @@ -16,8 +16,8 @@ targetWorkflowStepsPath: '{target_workflow_steps_path}' complianceReportTemplate: '{workflow_path}/templates/compliance-report.md' # Documentation References -stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md' -workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md' +stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md' +workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md' --- # Step 3: Step-by-Step Validation @@ -138,8 +138,8 @@ Check for proper references: ```yaml # Task References -advancedElicitationTask: '{project-root}/{*bmad_folder*}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' ``` **Violations to document:** @@ -186,7 +186,7 @@ For each step: "**Path Variable Validation:**" -- Check format: `{project-root}/{*bmad_folder*}/bmb/...` vs `{project-root}/src/modules/bmb/...` +- Check format: `{project-root}/.bmad/bmb/...` vs `{project-root}/bmb/...` - Ensure consistent variable usage across all step files - Validate relative vs absolute path usage diff --git a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-04-file-validation.md b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-04-file-validation.md index 900fb13e..ce28a763 100644 --- a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-04-file-validation.md +++ b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-04-file-validation.md @@ -3,7 +3,7 @@ name: 'step-04-file-validation' description: 'Validate file sizes, markdown formatting, and CSV data files' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check' +workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check' # File References thisStepFile: '{workflow_path}/steps/step-04-file-validation.md' @@ -16,9 +16,9 @@ targetWorkflowPath: '{target_workflow_path}' complianceReportTemplate: '{workflow_path}/templates/compliance-report.md' # Documentation References -stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md' -workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md' -csvStandards: '{project-root}/{bmad_folder}/bmb/docs/workflows/csv-data-file-standards.md' +stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md' +workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md' +csvStandards: '{project-root}/.bmad/bmb/docs/workflows/csv-data-file-standards.md' --- # Step 4: File Size, Formatting, and Data Validation diff --git a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-05-intent-spectrum-validation.md b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-05-intent-spectrum-validation.md index cd61fc27..c4c59e91 100644 --- a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-05-intent-spectrum-validation.md +++ b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-05-intent-spectrum-validation.md @@ -3,7 +3,7 @@ name: 'step-05-intent-spectrum-validation' description: 'Dedicated analysis and validation of intent vs prescriptive spectrum positioning' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check' +workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check' # File References thisStepFile: '{workflow_path}/steps/step-05-intent-spectrum-validation.md' @@ -16,9 +16,9 @@ targetWorkflowPath: '{target_workflow_path}' complianceReportTemplate: '{workflow_path}/templates/compliance-report.md' # Documentation References -stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md' -workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md' -intentSpectrum: '{project-root}/{bmad_folder}/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md' +stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md' +workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md' +intentSpectrum: '{project-root}/.bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md' --- # Step 5: Intent vs Prescriptive Spectrum Validation diff --git a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-06-web-subprocess-validation.md b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-06-web-subprocess-validation.md index b9085027..d2059019 100644 --- a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-06-web-subprocess-validation.md +++ b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-06-web-subprocess-validation.md @@ -3,7 +3,7 @@ name: 'step-06-web-subprocess-validation' description: 'Analyze web search utilization and subprocess optimization opportunities across workflow steps' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check' +workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check' # File References thisStepFile: '{workflow_path}/steps/step-06-web-subprocess-validation.md' @@ -16,9 +16,9 @@ targetWorkflowStepsPath: '{target_workflow_steps_path}' complianceReportTemplate: '{workflow_path}/templates/compliance-report.md' # Documentation References -stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md' -workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md' -intentSpectrum: '{project-root}/{bmad_folder}/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md' +stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md' +workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md' +intentSpectrum: '{project-root}/.bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md' --- # Step 6: Web Search & Subprocess Optimization Analysis diff --git a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-07-holistic-analysis.md b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-07-holistic-analysis.md index ce86ca8f..f16dd264 100644 --- a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-07-holistic-analysis.md +++ b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-07-holistic-analysis.md @@ -3,7 +3,7 @@ name: 'step-07-holistic-analysis' description: 'Analyze workflow flow, goal alignment, and meta-workflow failures' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check' +workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check' # File References thisStepFile: '{workflow_path}/steps/step-07-holistic-analysis.md' @@ -16,9 +16,9 @@ targetWorkflowFile: '{target_workflow_path}' complianceReportTemplate: '{workflow_path}/templates/compliance-report.md' # Documentation References -stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md' -workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md' -intentSpectrum: '{project-root}/{bmad_folder}/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md' +stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md' +workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md' +intentSpectrum: '{project-root}/.bmad/bmb/docs/workflows/intent-vs-prescriptive-spectrum.md' --- # Step 7: Holistic Workflow Analysis diff --git a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-08-generate-report.md b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-08-generate-report.md index 3ec9c05f..1439b946 100644 --- a/src/modules/bmb/workflows/workflow-compliance-check/steps/step-08-generate-report.md +++ b/src/modules/bmb/workflows/workflow-compliance-check/steps/step-08-generate-report.md @@ -3,7 +3,7 @@ name: 'step-08-generate-report' description: 'Generate comprehensive compliance report with fix recommendations' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check' +workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check' # File References thisStepFile: '{workflow_path}/steps/step-08-generate-report.md' @@ -15,8 +15,8 @@ targetWorkflowFile: '{target_workflow_path}' complianceReportTemplate: '{workflow_path}/templates/compliance-report.md' # Documentation References -stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md' -workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md' +stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md' +workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md' --- # Step 8: Comprehensive Compliance Report Generation diff --git a/src/modules/bmb/workflows/workflow-compliance-check/workflow.md b/src/modules/bmb/workflows/workflow-compliance-check/workflow.md index 2fb39bd2..b4c44406 100644 --- a/src/modules/bmb/workflows/workflow-compliance-check/workflow.md +++ b/src/modules/bmb/workflows/workflow-compliance-check/workflow.md @@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/{bmad_folder}/bmb/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/bmb/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmgd/README.md b/src/modules/bmgd/README.md index f007cf01..2ba24400 100644 --- a/src/modules/bmgd/README.md +++ b/src/modules/bmgd/README.md @@ -136,7 +136,7 @@ bmgd/ ## Configuration -After installation, configure the module in `{bmad_folder}/bmgd/config.yaml` +After installation, configure the module in `.bmad/bmgd/config.yaml` Key settings: diff --git a/src/modules/bmgd/agents/game-architect.agent.yaml b/src/modules/bmgd/agents/game-architect.agent.yaml index 0e3a8fab..38030d40 100644 --- a/src/modules/bmgd/agents/game-architect.agent.yaml +++ b/src/modules/bmgd/agents/game-architect.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/bmgd/agents/game-architect.md" + id: ".bmad/bmgd/agents/game-architect.md" name: Cloud Dragonborn title: Game Architect icon: ๐Ÿ›๏ธ @@ -16,18 +16,18 @@ agent: menu: - trigger: correct-course - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml" - workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/correct-course/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml" + workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/correct-course/workflow.yaml" description: Course Correction Analysis - trigger: create-architecture - workflow: "{project-root}/{bmad_folder}/bmgd/workflows/3-technical/game-architecture/workflow.yaml" + workflow: "{project-root}/.bmad/bmgd/workflows/3-technical/game-architecture/workflow.yaml" description: Produce a Scale Adaptive Game Architecture - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Consult with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results diff --git a/src/modules/bmgd/agents/game-designer.agent.yaml b/src/modules/bmgd/agents/game-designer.agent.yaml index cac3c6ae..672199b8 100644 --- a/src/modules/bmgd/agents/game-designer.agent.yaml +++ b/src/modules/bmgd/agents/game-designer.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/bmgd/agents/game-designer.md" + id: ".bmad/bmgd/agents/game-designer.md" name: Samus Shepard title: Game Designer icon: ๐ŸŽฒ @@ -16,25 +16,25 @@ agent: menu: - trigger: brainstorm-game - workflow: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml" + workflow: "{project-root}/.bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml" description: 1. Guide me through Game Brainstorming - trigger: create-game-brief - workflow: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/workflow.yaml" + workflow: "{project-root}/.bmad/bmgd/workflows/1-preproduction/game-brief/workflow.yaml" description: 3. Create Game Brief - trigger: create-gdd - workflow: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/gdd/workflow.yaml" + workflow: "{project-root}/.bmad/bmgd/workflows/2-design/gdd/workflow.yaml" description: 4. Create Game Design Document (GDD) - trigger: narrative - workflow: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/narrative/workflow.yaml" + workflow: "{project-root}/.bmad/bmgd/workflows/2-design/narrative/workflow.yaml" description: 5. Create Narrative Design Document (story-driven games) - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Consult with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results diff --git a/src/modules/bmgd/agents/game-dev.agent.yaml b/src/modules/bmgd/agents/game-dev.agent.yaml index 7073e107..e7e2af3d 100644 --- a/src/modules/bmgd/agents/game-dev.agent.yaml +++ b/src/modules/bmgd/agents/game-dev.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/bmgd/agents/game-dev.md" + id: ".bmad/bmgd/agents/game-dev.md" name: Link Freeman title: Game Developer icon: ๐Ÿ•น๏ธ @@ -17,24 +17,24 @@ agent: menu: - trigger: develop-story - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story/workflow.yaml" - workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/dev-story/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml" + workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/dev-story/workflow.yaml" description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story" - trigger: code-review - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review/workflow.yaml" - workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/code-review/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review/workflow.yaml" + workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/code-review/workflow.yaml" description: "Perform a thorough clean context QA code review on a story flagged Ready for Review" - trigger: story-done - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done/workflow.yaml" - workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-done/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/story-done/workflow.yaml" + workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/story-done/workflow.yaml" description: "Mark story done after DoD complete" - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Consult with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results diff --git a/src/modules/bmgd/agents/game-scrum-master.agent.yaml b/src/modules/bmgd/agents/game-scrum-master.agent.yaml index 7203482e..12ce3f3d 100644 --- a/src/modules/bmgd/agents/game-scrum-master.agent.yaml +++ b/src/modules/bmgd/agents/game-scrum-master.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/bmgd/agents/game-scrum-master.md" + id: ".bmad/bmgd/agents/game-scrum-master.md" name: Max title: Game Dev Scrum Master icon: ๐ŸŽฏ @@ -19,57 +19,57 @@ agent: menu: - trigger: sprint-planning - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml" - workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/sprint-planning/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml" + workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml" description: Generate or update sprint-status.yaml from epic files - trigger: epic-tech-context - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml" - workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/epic-tech-context/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml" + workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/epic-tech-context/workflow.yaml" description: (Optional) Use the GDD and Architecture to create an Epic-Tech-Spec for a specific epic - trigger: validate-epic-tech-context - validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/epic-tech-context/workflow.yaml" + validate-workflow: "{project-root}/.bmad/bmgd/workflows/4-production/epic-tech-context/workflow.yaml" description: (Optional) Validate latest Tech Spec against checklist - trigger: create-story-draft - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml" - workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml" + workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/create-story/workflow.yaml" description: Create a Story Draft for a game feature - trigger: validate-create-story - validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml" + validate-workflow: "{project-root}/.bmad/bmgd/workflows/4-production/create-story/workflow.yaml" description: (Optional) Validate Story Draft with Independent Review - trigger: story-context - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-context/workflow.yaml" - workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-context/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/story-context/workflow.yaml" + workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/story-context/workflow.yaml" description: (Optional) Assemble dynamic Story Context (XML) from latest docs and code and mark story ready for dev - trigger: validate-story-context - validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-context/workflow.yaml" + validate-workflow: "{project-root}/.bmad/bmgd/workflows/4-production/story-context/workflow.yaml" description: (Optional) Validate latest Story Context XML against checklist - trigger: story-ready-for-dev - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-ready/workflow.yaml" - workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-ready/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml" + workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/story-ready/workflow.yaml" description: (Optional) Mark drafted story ready for dev without generating Story Context - trigger: epic-retrospective - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml" - workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/retrospective/workflow.yaml" - data: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml" + workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/retrospective/workflow.yaml" + data: "{project-root}/.bmad/_cfg/agent-manifest.csv" description: (Optional) Facilitate team retrospective after a game development epic is completed - trigger: correct-course - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml" - workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/correct-course/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml" + workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/correct-course/workflow.yaml" description: (Optional) Navigate significant changes during game dev sprint - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Consult with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results diff --git a/src/modules/bmgd/module.yaml b/src/modules/bmgd/module.yaml index da846583..4bbb9094 100644 --- a/src/modules/bmgd/module.yaml +++ b/src/modules/bmgd/module.yaml @@ -12,7 +12,6 @@ subheader: "Configure the settings for the BMad Game Development module" ## communication_language ## document_output_language ## output_folder -## bmad_folder ## install_user_docs ## kb_install diff --git a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md index 994a0ae0..92110462 100644 --- a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md +++ b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md @@ -1,4 +1,4 @@ -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml +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 all responses in {communication_language} This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques diff --git a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml index 468a8bb1..9bf7c9f3 100644 --- a/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml +++ b/src/modules/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml @@ -4,7 +4,7 @@ description: "Facilitate game brainstorming sessions by orchestrating the CIS br author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -13,7 +13,7 @@ game_dev_experience: "{config_source}:game_dev_experience" date: system-generated # Module path and component files -installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game" +installed_path: "{project-root}/.bmad/bmgd/workflows/1-preproduction/brainstorm-game" template: false instructions: "{installed_path}/instructions.md" @@ -22,7 +22,7 @@ game_context: "{installed_path}/game-context.md" game_brain_methods: "{installed_path}/game-brain-methods.csv" # CORE brainstorming workflow to invoke -core_brainstorming: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml" +core_brainstorming: "{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml" standalone: true @@ -30,12 +30,12 @@ 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." author: "BMad" - instructions: "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md" + instructions: ".bmad/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md" template: false web_bundle_files: - - "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md" - - "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/game-context.md" - - "{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/game-brain-methods.csv" - - "{bmad_folder}/core/workflows/brainstorming/workflow.yaml" + - ".bmad/bmgd/workflows/1-preproduction/brainstorm-game/instructions.md" + - ".bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-context.md" + - ".bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-brain-methods.csv" + - ".bmad/core/workflows/brainstorming/workflow.yaml" existing_workflows: - - core_brainstorming: "{bmad_folder}/core/workflows/brainstorming/workflow.yaml" + - core_brainstorming: ".bmad/core/workflows/brainstorming/workflow.yaml" diff --git a/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md b/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md index 82eec249..3a41ac28 100644 --- a/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md +++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/instructions.md @@ -1,6 +1,6 @@ # Game Brief - Interactive Workflow Instructions -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml +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 all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} diff --git a/src/modules/bmgd/workflows/1-preproduction/game-brief/workflow.yaml b/src/modules/bmgd/workflows/1-preproduction/game-brief/workflow.yaml index 13db2b3c..c3d77089 100644 --- a/src/modules/bmgd/workflows/1-preproduction/game-brief/workflow.yaml +++ b/src/modules/bmgd/workflows/1-preproduction/game-brief/workflow.yaml @@ -4,7 +4,7 @@ description: "Interactive game brief creation workflow that guides users through author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -13,7 +13,7 @@ game_dev_experience: "{config_source}:game_dev_experience" date: system-generated # Module path and component files -installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/game-brief" +installed_path: "{project-root}/.bmad/bmgd/workflows/1-preproduction/game-brief" template: "{installed_path}/template.md" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" @@ -27,10 +27,10 @@ web_bundle: name: "game-brief" description: "Interactive game brief creation workflow that guides users through defining their game vision with multiple input sources and conversational collaboration" author: "BMad" - instructions: "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/instructions.md" - validation: "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/checklist.md" - template: "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/template.md" + instructions: ".bmad/bmgd/workflows/1-preproduction/game-brief/instructions.md" + validation: ".bmad/bmgd/workflows/1-preproduction/game-brief/checklist.md" + template: ".bmad/bmgd/workflows/1-preproduction/game-brief/template.md" web_bundle_files: - - "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/instructions.md" - - "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/checklist.md" - - "{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/template.md" + - ".bmad/bmgd/workflows/1-preproduction/game-brief/instructions.md" + - ".bmad/bmgd/workflows/1-preproduction/game-brief/checklist.md" + - ".bmad/bmgd/workflows/1-preproduction/game-brief/template.md" diff --git a/src/modules/bmgd/workflows/2-design/gdd/instructions-gdd.md b/src/modules/bmgd/workflows/2-design/gdd/instructions-gdd.md index e23bb8d1..5dcf6721 100644 --- a/src/modules/bmgd/workflows/2-design/gdd/instructions-gdd.md +++ b/src/modules/bmgd/workflows/2-design/gdd/instructions-gdd.md @@ -2,7 +2,7 @@ -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml +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 all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} @@ -35,7 +35,7 @@ This workflow requires: game brief, and may reference market research or brownfi - + mode: data data_request: project_config @@ -399,7 +399,7 @@ Your choice: - {project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/narrative/workflow.yaml + {project-root}/.bmad/bmm/workflows/2-plan-workflows/narrative/workflow.yaml Pass GDD context to narrative workflow Exit current workflow (narrative will hand off to solutioning when done) @@ -493,7 +493,7 @@ Which would you like to proceed with? - {project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/narrative/workflow.yaml + {project-root}/.bmad/bmm/workflows/2-plan-workflows/narrative/workflow.yaml Pass GDD context to narrative workflow diff --git a/src/modules/bmgd/workflows/2-design/gdd/workflow.yaml b/src/modules/bmgd/workflows/2-design/gdd/workflow.yaml index ee4644df..cafd8458 100644 --- a/src/modules/bmgd/workflows/2-design/gdd/workflow.yaml +++ b/src/modules/bmgd/workflows/2-design/gdd/workflow.yaml @@ -4,7 +4,7 @@ description: "Game Design Document workflow for all game project levels - from s author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -13,7 +13,7 @@ game_dev_experience: "{config_source}:game_dev_experience" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/gdd" +installed_path: "{project-root}/.bmad/bmgd/workflows/2-design/gdd" instructions: "{installed_path}/instructions-gdd.md" template: "{installed_path}/gdd-template.md" game_types_csv: "{installed_path}/game-types.csv" @@ -50,32 +50,32 @@ 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." author: "BMad" - instructions: "{bmad_folder}/bmgd/workflows/2-design/gdd/instructions-gdd.md" + instructions: ".bmad/bmgd/workflows/2-design/gdd/instructions-gdd.md" web_bundle_files: - - "{bmad_folder}/bmgd/workflows/2-design/gdd/instructions-gdd.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/gdd-template.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types.csv" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/action-platformer.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/adventure.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/card-game.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/fighting.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/horror.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/idle-incremental.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/metroidvania.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/moba.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/party-game.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/puzzle.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/racing.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/rhythm.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/roguelike.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/rpg.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/sandbox.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/shooter.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/simulation.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/sports.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/strategy.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/survival.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/text-based.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/tower-defense.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/turn-based-tactics.md" - - "{bmad_folder}/bmgd/workflows/2-design/gdd/game-types/visual-novel.md" + - ".bmad/bmgd/workflows/2-design/gdd/instructions-gdd.md" + - ".bmad/bmgd/workflows/2-design/gdd/gdd-template.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types.csv" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/action-platformer.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/adventure.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/card-game.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/fighting.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/horror.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/idle-incremental.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/metroidvania.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/moba.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/party-game.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/puzzle.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/racing.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/rhythm.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/roguelike.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/rpg.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/sandbox.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/shooter.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/simulation.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/sports.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/strategy.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/survival.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/text-based.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/tower-defense.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/turn-based-tactics.md" + - ".bmad/bmgd/workflows/2-design/gdd/game-types/visual-novel.md" diff --git a/src/modules/bmgd/workflows/2-design/narrative/instructions-narrative.md b/src/modules/bmgd/workflows/2-design/narrative/instructions-narrative.md index 3b6ab1ca..0dd9957c 100644 --- a/src/modules/bmgd/workflows/2-design/narrative/instructions-narrative.md +++ b/src/modules/bmgd/workflows/2-design/narrative/instructions-narrative.md @@ -2,7 +2,7 @@ -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml +The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml You MUST have already completed the GDD workflow Communicate all responses in {communication_language} This workflow creates detailed narrative content for story-driven games diff --git a/src/modules/bmgd/workflows/2-design/narrative/workflow.yaml b/src/modules/bmgd/workflows/2-design/narrative/workflow.yaml index 2bfd7991..08fe482a 100644 --- a/src/modules/bmgd/workflows/2-design/narrative/workflow.yaml +++ b/src/modules/bmgd/workflows/2-design/narrative/workflow.yaml @@ -4,7 +4,7 @@ description: "Narrative design workflow for story-driven games and applications. author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -13,7 +13,7 @@ game_dev_experience: "{config_source}:game_dev_experience" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/narrative" +installed_path: "{project-root}/.bmad/bmgd/workflows/2-design/narrative" instructions: "{installed_path}/instructions-narrative.md" template: "{installed_path}/narrative-template.md" @@ -26,7 +26,7 @@ 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." author: "BMad" - instructions: "{bmad_folder}/bmgd/workflows/2-design/narrative/instructions-narrative.md" + instructions: ".bmad/bmgd/workflows/2-design/narrative/instructions-narrative.md" web_bundle_files: - - "{bmad_folder}/bmgd/workflows/2-design/narrative/instructions-narrative.md" - - "{bmad_folder}/bmgd/workflows/2-design/narrative/narrative-template.md" + - ".bmad/bmgd/workflows/2-design/narrative/instructions-narrative.md" + - ".bmad/bmgd/workflows/2-design/narrative/narrative-template.md" diff --git a/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md b/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md index 9216a5bc..766b2323 100644 --- a/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md +++ b/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md @@ -2,7 +2,7 @@ -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml +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 This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level} The goal is ARCHITECTURAL DECISIONS that prevent AI agent conflicts, not detailed implementation specs diff --git a/src/modules/bmgd/workflows/3-technical/game-architecture/workflow.yaml b/src/modules/bmgd/workflows/3-technical/game-architecture/workflow.yaml index 0f5c5f5c..2887f9b7 100644 --- a/src/modules/bmgd/workflows/3-technical/game-architecture/workflow.yaml +++ b/src/modules/bmgd/workflows/3-technical/game-architecture/workflow.yaml @@ -4,7 +4,7 @@ description: "Collaborative game architecture workflow for AI-agent consistency. author: "BMad" # Critical variables -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -39,7 +39,7 @@ input_file_patterns: load_strategy: "INDEX_GUIDED" # Module path and component files -installed_path: "{project-root}/{bmad_folder}/bmgd/workflows/3-technical/game-architecture" +installed_path: "{project-root}/.bmad/bmgd/workflows/3-technical/game-architecture" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" template: "{installed_path}/architecture-template.md" diff --git a/src/modules/bmgd/workflows/4-production/code-review/instructions.md b/src/modules/bmgd/workflows/4-production/code-review/instructions.md index 6280b8eb..fe2c6f11 100644 --- a/src/modules/bmgd/workflows/4-production/code-review/instructions.md +++ b/src/modules/bmgd/workflows/4-production/code-review/instructions.md @@ -1,7 +1,7 @@ # Senior Developer Review - Workflow Instructions ````xml -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml +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 all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} @@ -354,7 +354,7 @@ Review was saved to story file, but sprint-status.yaml may be out of sync. - Run validation checklist at {installed_path}/checklist.md using {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml + Run validation checklist at {installed_path}/checklist.md using {project-root}/.bmad/core/tasks/validate-workflow.xml Report workflow completion. diff --git a/src/modules/bmgd/workflows/4-production/code-review/workflow.yaml b/src/modules/bmgd/workflows/4-production/code-review/workflow.yaml index 972363fe..52b9d724 100644 --- a/src/modules/bmgd/workflows/4-production/code-review/workflow.yaml +++ b/src/modules/bmgd/workflows/4-production/code-review/workflow.yaml @@ -4,7 +4,7 @@ description: "Perform a Senior Developer code review on a completed story flagge author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -15,7 +15,7 @@ sprint_artifacts: "{config_source}:sprint_artifacts" sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" template: false diff --git a/src/modules/bmgd/workflows/4-production/correct-course/checklist.md b/src/modules/bmgd/workflows/4-production/correct-course/checklist.md index 1cbe1bf0..7fb6dc06 100644 --- a/src/modules/bmgd/workflows/4-production/correct-course/checklist.md +++ b/src/modules/bmgd/workflows/4-production/correct-course/checklist.md @@ -1,6 +1,6 @@ # Change Navigation Checklist -This checklist is executed as part of: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml +This checklist is executed as part of: {project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml Work through each section systematically with the user, recording findings and impacts diff --git a/src/modules/bmgd/workflows/4-production/correct-course/instructions.md b/src/modules/bmgd/workflows/4-production/correct-course/instructions.md index 2adbb321..738aeea9 100644 --- a/src/modules/bmgd/workflows/4-production/correct-course/instructions.md +++ b/src/modules/bmgd/workflows/4-production/correct-course/instructions.md @@ -1,7 +1,7 @@ # Correct Course - Sprint Change Management Instructions -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} diff --git a/src/modules/bmgd/workflows/4-production/correct-course/workflow.yaml b/src/modules/bmgd/workflows/4-production/correct-course/workflow.yaml index 7f4850b6..5fc6fab7 100644 --- a/src/modules/bmgd/workflows/4-production/correct-course/workflow.yaml +++ b/src/modules/bmgd/workflows/4-production/correct-course/workflow.yaml @@ -3,7 +3,7 @@ name: "correct-course" description: "Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation" author: "BMad Method" -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -46,7 +46,7 @@ input_file_patterns: sharded: "{output_folder}/index.md" load_strategy: "INDEX_GUIDED" -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course" template: false instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmgd/workflows/4-production/create-story/instructions.md b/src/modules/bmgd/workflows/4-production/create-story/instructions.md index 3105620c..301ac3ab 100644 --- a/src/modules/bmgd/workflows/4-production/create-story/instructions.md +++ b/src/modules/bmgd/workflows/4-production/create-story/instructions.md @@ -1,7 +1,7 @@ # Create Story - Workflow Instructions (Spec-compliant, non-interactive by default) ````xml -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml +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 Generate all documents in {document_output_language} This workflow creates or updates the next user story from epics/PRD and architecture context, saving to the configured stories directory and optionally invoking Story Context. @@ -213,7 +213,7 @@ Will update existing story file rather than creating new one. - Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml + Validate against checklist at {installed_path}/checklist.md using .bmad/core/tasks/validate-workflow.xml Save document unconditionally (non-interactive default). In interactive mode, allow user confirmation. diff --git a/src/modules/bmgd/workflows/4-production/create-story/workflow.yaml b/src/modules/bmgd/workflows/4-production/create-story/workflow.yaml index 6846d9ed..fe358a8f 100644 --- a/src/modules/bmgd/workflows/4-production/create-story/workflow.yaml +++ b/src/modules/bmgd/workflows/4-production/create-story/workflow.yaml @@ -3,7 +3,7 @@ description: "Create the next user story markdown from epics/PRD and architectur author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,7 +12,7 @@ sprint_artifacts: "{config_source}:sprint_artifacts" story_dir: "{sprint_artifacts}" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/create-story" template: "{installed_path}/template.md" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmgd/workflows/4-production/dev-story/instructions.md b/src/modules/bmgd/workflows/4-production/dev-story/instructions.md index 26b05ad9..5ae08134 100644 --- a/src/modules/bmgd/workflows/4-production/dev-story/instructions.md +++ b/src/modules/bmgd/workflows/4-production/dev-story/instructions.md @@ -1,7 +1,7 @@ # Develop Story - Workflow Instructions ```xml -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml +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 all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} @@ -232,7 +232,7 @@ Story is marked Ready for Review in file, but sprint-status.yaml may be out of s - Optionally run the workflow validation task against the story using {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml + Optionally run the workflow validation task against the story using {project-root}/.bmad/core/tasks/validate-workflow.xml Prepare a concise summary in Dev Agent Record โ†’ Completion Notes Communicate to {user_name} that story implementation is complete and ready for review diff --git a/src/modules/bmgd/workflows/4-production/dev-story/workflow.yaml b/src/modules/bmgd/workflows/4-production/dev-story/workflow.yaml index e7f530c1..07beb9a8 100644 --- a/src/modules/bmgd/workflows/4-production/dev-story/workflow.yaml +++ b/src/modules/bmgd/workflows/4-production/dev-story/workflow.yaml @@ -3,7 +3,7 @@ description: "Execute a story by implementing tasks/subtasks, writing tests, val author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -49,7 +49,7 @@ input_file_patterns: load_strategy: "INDEX_GUIDED" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmgd/workflows/4-production/epic-tech-context/checklist.md b/src/modules/bmgd/workflows/4-production/epic-tech-context/checklist.md index 346d8dbe..72436218 100644 --- a/src/modules/bmgd/workflows/4-production/epic-tech-context/checklist.md +++ b/src/modules/bmgd/workflows/4-production/epic-tech-context/checklist.md @@ -1,7 +1,7 @@ # Tech Spec Validation Checklist ```xml - + Overview clearly ties to PRD goals Scope explicitly lists in-scope and out-of-scope Design lists all services/modules with responsibilities diff --git a/src/modules/bmgd/workflows/4-production/epic-tech-context/instructions.md b/src/modules/bmgd/workflows/4-production/epic-tech-context/instructions.md index 12857011..46fdfe1e 100644 --- a/src/modules/bmgd/workflows/4-production/epic-tech-context/instructions.md +++ b/src/modules/bmgd/workflows/4-production/epic-tech-context/instructions.md @@ -1,7 +1,7 @@ ```xml -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml +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 all responses in {communication_language} This workflow generates a comprehensive Technical Specification from PRD and Architecture, including detailed design, NFRs, acceptance criteria, and traceability mapping. @@ -132,7 +132,7 @@ Continuing to regenerate tech spec... - Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml + Validate against checklist at {installed_path}/checklist.md using .bmad/core/tasks/validate-workflow.xml Load the FULL file: {sprint_status} diff --git a/src/modules/bmgd/workflows/4-production/epic-tech-context/workflow.yaml b/src/modules/bmgd/workflows/4-production/epic-tech-context/workflow.yaml index b9119098..764bfabe 100644 --- a/src/modules/bmgd/workflows/4-production/epic-tech-context/workflow.yaml +++ b/src/modules/bmgd/workflows/4-production/epic-tech-context/workflow.yaml @@ -3,7 +3,7 @@ description: "Generate a comprehensive Technical Specification from PRD and Arch author: "BMAD BMM" # Critical variables -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -47,7 +47,7 @@ input_file_patterns: load_strategy: "INDEX_GUIDED" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/epic-tech-context" template: "{installed_path}/template.md" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmgd/workflows/4-production/retrospective/instructions.md b/src/modules/bmgd/workflows/4-production/retrospective/instructions.md index 13af2dd0..67074fa4 100644 --- a/src/modules/bmgd/workflows/4-production/retrospective/instructions.md +++ b/src/modules/bmgd/workflows/4-production/retrospective/instructions.md @@ -1,7 +1,7 @@ # Retrospective - Epic Completion Review Instructions -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/.bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} โš ๏ธ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmgd/workflows/4-production/retrospective/workflow.yaml b/src/modules/bmgd/workflows/4-production/retrospective/workflow.yaml index 797564ac..9f1066d9 100644 --- a/src/modules/bmgd/workflows/4-production/retrospective/workflow.yaml +++ b/src/modules/bmgd/workflows/4-production/retrospective/workflow.yaml @@ -3,7 +3,7 @@ name: "retrospective" description: "Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic" author: "BMad" -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,12 +12,12 @@ document_output_language: "{config_source}:document_output_language" date: system-generated sprint_artifacts: "{config_source}:sprint_artifacts" -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective" template: false instructions: "{installed_path}/instructions.md" required_inputs: - - agent_manifest: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv" + - agent_manifest: "{project-root}/.bmad/_cfg/agent-manifest.csv" # Smart input file references - handles both whole docs and sharded docs # Priority: Whole document first, then sharded version diff --git a/src/modules/bmgd/workflows/4-production/sprint-planning/instructions.md b/src/modules/bmgd/workflows/4-production/sprint-planning/instructions.md index e7fd436b..f6e95ee7 100644 --- a/src/modules/bmgd/workflows/4-production/sprint-planning/instructions.md +++ b/src/modules/bmgd/workflows/4-production/sprint-planning/instructions.md @@ -1,7 +1,7 @@ # Sprint Planning - Sprint Status Generator -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/.bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml ## ๐Ÿ“š Document Discovery - Full Epic Loading diff --git a/src/modules/bmgd/workflows/4-production/sprint-planning/workflow.yaml b/src/modules/bmgd/workflows/4-production/sprint-planning/workflow.yaml index f0c2a6f5..0cd4ad4a 100644 --- a/src/modules/bmgd/workflows/4-production/sprint-planning/workflow.yaml +++ b/src/modules/bmgd/workflows/4-production/sprint-planning/workflow.yaml @@ -3,7 +3,7 @@ description: "Generate and manage the sprint status tracking file for Phase 4 im author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -11,7 +11,7 @@ date: system-generated sprint_artifacts: "{config_source}:sprint_artifacts" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/sprint-planning" instructions: "{installed_path}/instructions.md" template: "{installed_path}/sprint-status-template.yaml" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmgd/workflows/4-production/story-context/checklist.md b/src/modules/bmgd/workflows/4-production/story-context/checklist.md index d2f77cea..f73f86df 100644 --- a/src/modules/bmgd/workflows/4-production/story-context/checklist.md +++ b/src/modules/bmgd/workflows/4-production/story-context/checklist.md @@ -1,7 +1,7 @@ # Story Context Assembly Checklist ```xml - + Story fields (asA/iWant/soThat) captured Acceptance criteria list matches story draft exactly (no invention) Tasks/subtasks captured as task list diff --git a/src/modules/bmgd/workflows/4-production/story-context/context-template.xml b/src/modules/bmgd/workflows/4-production/story-context/context-template.xml index c2988e09..3a099458 100644 --- a/src/modules/bmgd/workflows/4-production/story-context/context-template.xml +++ b/src/modules/bmgd/workflows/4-production/story-context/context-template.xml @@ -1,4 +1,4 @@ - + {{epic_id}} {{story_id}} diff --git a/src/modules/bmgd/workflows/4-production/story-context/instructions.md b/src/modules/bmgd/workflows/4-production/story-context/instructions.md index 8e9bad2b..7c3b3132 100644 --- a/src/modules/bmgd/workflows/4-production/story-context/instructions.md +++ b/src/modules/bmgd/workflows/4-production/story-context/instructions.md @@ -1,7 +1,7 @@ ```xml -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml +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 all responses in {communication_language} Generate all documents in {document_output_language} @@ -156,7 +156,7 @@ Validate output context file structure and content - Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml + Validate against checklist at {installed_path}/checklist.md using .bmad/core/tasks/validate-workflow.xml diff --git a/src/modules/bmgd/workflows/4-production/story-context/workflow.yaml b/src/modules/bmgd/workflows/4-production/story-context/workflow.yaml index ced3e654..69979931 100644 --- a/src/modules/bmgd/workflows/4-production/story-context/workflow.yaml +++ b/src/modules/bmgd/workflows/4-production/story-context/workflow.yaml @@ -4,7 +4,7 @@ description: "Assemble a dynamic Story Context XML by pulling latest documentati author: "BMad" # Critical variables -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -15,7 +15,7 @@ sprint_artifacts: "{config_source}:sprint_artifacts" sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-context" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/story-context" template: "{installed_path}/context-template.xml" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmgd/workflows/4-production/story-done/instructions.md b/src/modules/bmgd/workflows/4-production/story-done/instructions.md index 32ac01b4..61b795a2 100644 --- a/src/modules/bmgd/workflows/4-production/story-done/instructions.md +++ b/src/modules/bmgd/workflows/4-production/story-done/instructions.md @@ -1,6 +1,6 @@ # Story Approved Workflow Instructions (DEV Agent) -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml +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 all responses in {communication_language} diff --git a/src/modules/bmgd/workflows/4-production/story-done/workflow.yaml b/src/modules/bmgd/workflows/4-production/story-done/workflow.yaml index 3b4f60e9..09258368 100644 --- a/src/modules/bmgd/workflows/4-production/story-done/workflow.yaml +++ b/src/modules/bmgd/workflows/4-production/story-done/workflow.yaml @@ -4,7 +4,7 @@ description: "Marks a story as done (DoD complete) and moves it from its current author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -13,7 +13,7 @@ sprint_artifacts: "{config_source}:sprint_artifacts" sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/story-done" instructions: "{installed_path}/instructions.md" # Variables and inputs diff --git a/src/modules/bmgd/workflows/4-production/story-ready/instructions.md b/src/modules/bmgd/workflows/4-production/story-ready/instructions.md index 6f5dfdc6..a4389f22 100644 --- a/src/modules/bmgd/workflows/4-production/story-ready/instructions.md +++ b/src/modules/bmgd/workflows/4-production/story-ready/instructions.md @@ -1,6 +1,6 @@ # Story Ready Workflow Instructions (SM Agent) -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml +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 all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} diff --git a/src/modules/bmgd/workflows/4-production/story-ready/workflow.yaml b/src/modules/bmgd/workflows/4-production/story-ready/workflow.yaml index 3b63de0e..f5225caa 100644 --- a/src/modules/bmgd/workflows/4-production/story-ready/workflow.yaml +++ b/src/modules/bmgd/workflows/4-production/story-ready/workflow.yaml @@ -4,7 +4,7 @@ description: "Marks a drafted story as ready for development and moves it from T author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml" +config_source: "{project-root}/.bmad/bmgd/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -13,7 +13,7 @@ sprint_artifacts: "{config_source}:sprint_artifacts" sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-ready" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/story-ready" instructions: "{installed_path}/instructions.md" # Variables and inputs diff --git a/src/modules/bmm/agents/analyst.agent.yaml b/src/modules/bmm/agents/analyst.agent.yaml index 8f4ba7f1..a3ec0164 100644 --- a/src/modules/bmm/agents/analyst.agent.yaml +++ b/src/modules/bmm/agents/analyst.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/bmm/agents/analyst.md" + id: ".bmad/bmm/agents/analyst.md" name: Mary title: Business Analyst icon: ๐Ÿ“Š @@ -19,31 +19,31 @@ agent: menu: - trigger: workflow-status - workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml" description: Get workflow status or initialize a workflow if not already done (optional) - trigger: brainstorm-project - exec: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.md" - data: "{project-root}/{bmad_folder}/bmm/data/project-context-template.md" + exec: "{project-root}/.bmad/core/workflows/brainstorming/workflow.md" + data: "{project-root}/.bmad/bmm/data/project-context-template.md" description: Guided Project Brainstorming session with final report (optional) - trigger: research - exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.md" + exec: "{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.md" description: Guided Research scoped to market, domain, competitive analysis, or technical research (optional) - trigger: product-brief - exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief/workflow.md" + exec: "{project-root}/.bmad/bmm/workflows/1-analysis/product-brief/workflow.md" description: Create a Product Brief (recommended input for PRD) - trigger: document-project - workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/document-project/workflow.yaml" description: Document your existing project (optional, but recommended for existing brownfield project efforts) - multi: "[SPM] Start Party Mode (optionally suggest attendees and topic), [CH] Chat" triggers: - party-mode: - input: SPM or fuzzy match start party mode - - route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md" + - route: "{project-root}/.bmad/core/workflows/edit-agent/workflow.md" - data: what is being discussed or suggested with the command, along with custom party custom agents if specified - type: exec - expert-chat: diff --git a/src/modules/bmm/agents/architect.agent.yaml b/src/modules/bmm/agents/architect.agent.yaml index 07d9ad3a..48fa9161 100644 --- a/src/modules/bmm/agents/architect.agent.yaml +++ b/src/modules/bmm/agents/architect.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/bmm/agents/architect.md" + id: ".bmad/bmm/agents/architect.md" name: Winston title: Architect icon: ๐Ÿ—๏ธ @@ -19,30 +19,30 @@ agent: menu: - trigger: workflow-status - workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml" description: Get workflow status or initialize a workflow if not already done (optional) - trigger: create-architecture - exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.md" + exec: "{project-root}/.bmad/bmm/workflows/3-solutioning/architecture/workflow.md" description: Create an Architecture Document to Guide Development of a PRD (required for BMad Method projects) - trigger: implementation-readiness - exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness/workflow.md" + exec: "{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness/workflow.md" description: Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development) - trigger: create-excalidraw-diagram - workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-diagram/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-diagram/workflow.yaml" description: Create system architecture or technical diagram (Excalidraw) (Use any time you need a diagram) - trigger: create-excalidraw-dataflow - workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-dataflow/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-dataflow/workflow.yaml" description: Create data flow diagram (Excalidraw) (Use any time you need a diagram) - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Bring the whole team in to chat with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/bmm/agents/dev.agent.yaml b/src/modules/bmm/agents/dev.agent.yaml index 3e3fdc2d..bc2b7587 100644 --- a/src/modules/bmm/agents/dev.agent.yaml +++ b/src/modules/bmm/agents/dev.agent.yaml @@ -3,7 +3,7 @@ agent: webskip: true metadata: - id: "{bmad_folder}/bmm/agents/dev.md" + id: ".bmad/bmm/agents/dev.md" name: Amelia title: Developer Agent icon: ๐Ÿ’ป @@ -36,9 +36,9 @@ agent: menu: - trigger: develop-story - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml" description: "Execute Dev Story workflow (full BMM path with sprint-status)" - trigger: code-review - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review/workflow.yaml" description: "Perform a thorough clean context code review (Highly Recommended, use fresh context and different LLM)" diff --git a/src/modules/bmm/agents/pm.agent.yaml b/src/modules/bmm/agents/pm.agent.yaml index 40dcf7d0..610531d8 100644 --- a/src/modules/bmm/agents/pm.agent.yaml +++ b/src/modules/bmm/agents/pm.agent.yaml @@ -3,7 +3,7 @@ agent: metadata: - id: "{bmad_folder}/bmm/agents/pm.md" + id: ".bmad/bmm/agents/pm.md" name: John title: Product Manager icon: ๐Ÿ“‹ @@ -20,31 +20,31 @@ agent: menu: - trigger: workflow-status - workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml" description: Get workflow status or initialize a workflow if not already done (optional) - trigger: create-prd - exec: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/workflow.md" + exec: "{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/workflow.md" description: Create Product Requirements Document (PRD) (Required for BMad Method flow) - trigger: create-epics-and-stories - exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md" + exec: "{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md" description: Create Epics and User Stories from PRD (Required for BMad Method flow AFTER the Architecture is completed) - trigger: implementation-readiness - exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness/workflow.md" + exec: "{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness/workflow.md" description: Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development) - trigger: correct-course - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml" description: Course Correction Analysis (optional during implementation when things go off track) ide-only: true - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Bring the whole team in to chat with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml b/src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml index c909df4b..5b893fec 100644 --- a/src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml +++ b/src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/bmm/agents/quick-flow-solo-dev.md" + id: ".bmad/bmm/agents/quick-flow-solo-dev.md" name: Barry title: Quick Flow Solo Dev icon: ๐Ÿš€ @@ -20,17 +20,17 @@ agent: menu: - trigger: create-tech-spec - workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml" description: Architect a technical spec with implementation-ready stories (Required first step) - trigger: quick-dev - workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml" description: Implement the tech spec end-to-end solo (Core of Quick Flow) - trigger: code-review - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review/workflow.yaml" description: Review code and improve it (Highly Recommended, use fresh context and different LLM for best results) - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Bring in other experts when I need specialized backup diff --git a/src/modules/bmm/agents/sm.agent.yaml b/src/modules/bmm/agents/sm.agent.yaml index 8be3ee66..ee7ecc08 100644 --- a/src/modules/bmm/agents/sm.agent.yaml +++ b/src/modules/bmm/agents/sm.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/bmm/agents/sm.md" + id: ".bmad/bmm/agents/sm.md" name: Bob title: Scrum Master icon: ๐Ÿƒ @@ -25,31 +25,31 @@ agent: menu: - trigger: sprint-planning - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml" description: Generate or re-generate sprint-status.yaml from epic files (Required after Epics+Stories are created) - trigger: create-story - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml" description: Create a Draft Story (Required to prepare stories for development) - trigger: validate-create-story - validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml" + validate-workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml" description: Validate Story Draft (Highly Recommended, use fresh context and different LLM for best results) - trigger: epic-retrospective - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml" - data: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml" + data: "{project-root}/.bmad/_cfg/agent-manifest.csv" description: Facilitate team retrospective after an epic is completed (Optional) - trigger: correct-course - workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml" description: Execute correct-course task (When implementation is off-track) - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Bring the whole team in to chat with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/bmm/agents/tea.agent.yaml b/src/modules/bmm/agents/tea.agent.yaml index df18b836..12420629 100644 --- a/src/modules/bmm/agents/tea.agent.yaml +++ b/src/modules/bmm/agents/tea.agent.yaml @@ -3,7 +3,7 @@ agent: webskip: true metadata: - id: "{bmad_folder}/bmm/agents/tea.md" + id: ".bmad/bmm/agents/tea.md" name: Murat title: Master Test Architect icon: ๐Ÿงช @@ -22,49 +22,49 @@ agent: - Calculate risk vs value for every testing decision critical_actions: - - "Consult {project-root}/{bmad_folder}/bmm/testarch/tea-index.csv to select knowledge fragments under knowledge/ and load only the files needed for the current task" - - "Load the referenced fragment(s) from {project-root}/{bmad_folder}/bmm/testarch/knowledge/ before giving recommendations" + - "Consult {project-root}/.bmad/bmm/testarch/tea-index.csv to select knowledge fragments under knowledge/ and load only the files needed for the current task" + - "Load the referenced fragment(s) from {project-root}/.bmad/bmm/testarch/knowledge/ before giving recommendations" - "Cross-check recommendations with the current official Playwright, Cypress, Pact, and CI platform documentation" - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`" menu: - trigger: framework - workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/framework/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/testarch/framework/workflow.yaml" description: Initialize production-ready test framework architecture - trigger: atdd - workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/atdd/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/testarch/atdd/workflow.yaml" description: Generate E2E tests first, before starting implementation - trigger: automate - workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/automate/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/testarch/automate/workflow.yaml" description: Generate comprehensive test automation - trigger: test-design - workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-design/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/testarch/test-design/workflow.yaml" description: Create comprehensive test scenarios - trigger: trace - workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/trace/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/testarch/trace/workflow.yaml" description: Map requirements to tests (Phase 1) and make quality gate decision (Phase 2) - trigger: nfr-assess - workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/nfr-assess/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml" description: Validate non-functional requirements - trigger: ci - workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/ci/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/testarch/ci/workflow.yaml" description: Scaffold CI/CD quality pipeline - trigger: test-review - workflow: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-review/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/testarch/test-review/workflow.yaml" description: Review test quality using comprehensive knowledge base and best practices - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Bring the whole team in to chat with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/bmm/agents/tech-writer.agent.yaml b/src/modules/bmm/agents/tech-writer.agent.yaml index 6911c581..e0a62870 100644 --- a/src/modules/bmm/agents/tech-writer.agent.yaml +++ b/src/modules/bmm/agents/tech-writer.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/bmm/agents/tech-writer.md" + id: ".bmad/bmm/agents/tech-writer.md" name: Paige title: Technical Writer icon: ๐Ÿ“š @@ -17,12 +17,12 @@ agent: - Docs are living artifacts that evolve with code. Know when to simplify vs when to be detailed. critical_actions: - - "CRITICAL: Load COMPLETE file {project-root}/{bmad_folder}/bmm/data/documentation-standards.md into permanent memory and follow ALL rules within" + - "CRITICAL: Load COMPLETE file {project-root}/.bmad/bmm/data/documentation-standards.md into permanent memory and follow ALL rules within" - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`" menu: - trigger: document-project - workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/document-project/workflow.yaml" description: Comprehensive project documentation (brownfield analysis, architecture scanning) - trigger: generate-mermaid @@ -30,15 +30,15 @@ agent: description: Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state) - trigger: create-excalidraw-flowchart - workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-flowchart/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-flowchart/workflow.yaml" description: Create Excalidraw flowchart for processes and logic flows - trigger: create-excalidraw-diagram - workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-diagram/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-diagram/workflow.yaml" description: Create Excalidraw system architecture or technical diagram - trigger: create-excalidraw-dataflow - workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-dataflow/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-dataflow/workflow.yaml" description: Create Excalidraw data flow diagram - trigger: validate-doc @@ -54,14 +54,14 @@ agent: description: Create clear technical explanations with examples - trigger: standards-guide - action: "Display the complete documentation standards from {project-root}/{bmad_folder}bmm/data/documentation-standards.md in a clear, formatted way for the user." + action: "Display the complete documentation standards from {project-root}/.bmadbmm/data/documentation-standards.md in a clear, formatted way for the user." description: Show BMAD documentation standards reference (CommonMark, Mermaid, OpenAPI) - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Bring the whole team in to chat with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/bmm/agents/ux-designer.agent.yaml b/src/modules/bmm/agents/ux-designer.agent.yaml index 04ba4c86..c1fd228f 100644 --- a/src/modules/bmm/agents/ux-designer.agent.yaml +++ b/src/modules/bmm/agents/ux-designer.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/bmm/agents/ux-designer.md" + id: ".bmad/bmm/agents/ux-designer.md" name: Sally title: UX Designer icon: ๐ŸŽจ @@ -24,22 +24,22 @@ agent: menu: - trigger: create-ux-design - exec: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md" + exec: "{project-root}/.bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md" description: Generate a UX Design and UI Plan from a PRD (Recommended before creating Architecture) - trigger: validate-design - validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml" + validate-workflow: "{project-root}/.bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml" description: Validate UX Specification and Design Artifacts - trigger: create-excalidraw-wireframe - workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-wireframe/workflow.yaml" + workflow: "{project-root}/.bmad/bmm/workflows/diagrams/create-wireframe/workflow.yaml" description: Create website or app wireframe (Excalidraw) - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Bring the whole team in to chat with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/bmm/docs/agents-guide.md b/src/modules/bmm/docs/agents-guide.md index 8e8ad7c7..ccf74fa7 100644 --- a/src/modules/bmm/docs/agents-guide.md +++ b/src/modules/bmm/docs/agents-guide.md @@ -661,14 +661,14 @@ You can customize any agent's personality without modifying core agent files. ### Location -**Customization Directory:** `{project-root}/{bmad_folder}/_cfg/agents/` +**Customization Directory:** `{project-root}/.bmad/_cfg/agents/` **Naming Convention:** `{module}-{agent-name}.customize.yaml` **Examples:** ``` -{bmad_folder}/_cfg/agents/ +.bmad/_cfg/agents/ โ”œโ”€โ”€ bmm-pm.customize.yaml โ”œโ”€โ”€ bmm-dev.customize.yaml โ”œโ”€โ”€ cis-storyteller.customize.yaml @@ -768,9 +768,9 @@ Other agents collaborate with PM's specialized perspective. ```bash # Create customization file at: -# {project-root}/{bmad_folder}/_cfg/agents/{module}-{agent-name}.customize.yaml +# {project-root}/.bmad/_cfg/agents/{module}-{agent-name}.customize.yaml -# Example: {bmad_folder}/_cfg/agents/bmm-pm.customize.yaml +# Example: .bmad/_cfg/agents/bmm-pm.customize.yaml ``` **Step 2: Regenerate Agent Manifest** diff --git a/src/modules/bmm/docs/brownfield-guide.md b/src/modules/bmm/docs/brownfield-guide.md index 5aa808ee..ef027226 100644 --- a/src/modules/bmm/docs/brownfield-guide.md +++ b/src/modules/bmm/docs/brownfield-guide.md @@ -137,7 +137,7 @@ If you have documentation but files are huge (>500 lines, 10+ level 2 sections): ```bash # Load BMad Master or any agent - {bmad_folder}/core/tools/shard-doc.xml --input docs/massive-doc.md + .bmad/core/tools/shard-doc.xml --input docs/massive-doc.md ``` - Splits on level 2 sections by default @@ -147,7 +147,7 @@ If you have documentation but files are huge (>500 lines, 10+ level 2 sections): 2. **Then:** Run `index-docs` task to create navigation: ```bash - {bmad_folder}/core/tasks/index-docs.xml --directory ./docs + .bmad/core/tasks/index-docs.xml --directory ./docs ``` 3. **Finally:** Validate quality - if sharded docs still seem incomplete/outdated โ†’ Run `document-project` @@ -210,7 +210,7 @@ If you have **good, current documentation** but it's in massive files: ```bash # For each massive doc (>500 lines or 10+ level 2 sections) -{bmad_folder}/core/tools/shard-doc.xml \ +.bmad/core/tools/shard-doc.xml \ --input docs/api-documentation.md \ --output docs/api/ \ --level 2 # Split on ## headers (default) @@ -219,7 +219,7 @@ If you have **good, current documentation** but it's in massive files: **Step 2: Generate index** ```bash -{bmad_folder}/core/tasks/index-docs.xml --directory ./docs +.bmad/core/tasks/index-docs.xml --directory ./docs ``` **Step 3: Validate** diff --git a/src/modules/bmm/docs/enterprise-agentic-development.md b/src/modules/bmm/docs/enterprise-agentic-development.md index fd60f9ba..17375817 100644 --- a/src/modules/bmm/docs/enterprise-agentic-development.md +++ b/src/modules/bmm/docs/enterprise-agentic-development.md @@ -425,7 +425,7 @@ Team C (2 devs): Analytics feature (3 epics) **Problem:** Teams customize BMad (agents, workflows, configs) but don't want personal tooling in main repo. -**Anti-pattern:** Adding `{bmad_folder}/` to `.gitignore` breaks IDE tools, submodule management. +**Anti-pattern:** Adding `.bmad/` to `.gitignore` breaks IDE tools, submodule management. ### The Solution: Git Submodules @@ -463,7 +463,7 @@ git commit -m "Add BMM as submodule" git clone https://github.com/your-org/your-project.git cd your-project git submodule update --init --recursive -# Make personal customizations in {bmad_folder}/ +# Make personal customizations in .bmad/ ``` ### Daily Workflow @@ -472,7 +472,7 @@ git submodule update --init --recursive ```bash cd /path/to/your-project -# BMad available at ./{bmad_folder}/, load agents normally +# BMad available at ./.bmad/, load agents normally ``` **Update personal config:** diff --git a/src/modules/bmm/docs/faq.md b/src/modules/bmm/docs/faq.md index 7766137e..53539c5f 100644 --- a/src/modules/bmm/docs/faq.md +++ b/src/modules/bmm/docs/faq.md @@ -199,24 +199,11 @@ PRDs are for Level 2-4 projects with multiple features requiring product-level c ### Q: How do I mark a story as done? -**A:** You have two options: +**A:** After dev-story completes and code-review passes: -**Option 1: Use story-done workflow (Recommended)** - -1. Load SM agent -2. Run `story-done` workflow -3. Workflow automatically updates `sprint-status.yaml` (created by sprint-planning at Phase 4 start) -4. Moves story from current status โ†’ `DONE` -5. Advances the story queue - -**Option 2: Manual update** - -1. After dev-story completes and code-review passes -2. Open `sprint-status.yaml` (created by sprint-planning) -3. Change the story status from `review` to `done` -4. Save the file - -The story-done workflow is faster and ensures proper status file updates. +1. Open `sprint-status.yaml` (created by sprint-planning) +2. Change the story status from `review` to `done` +3. Save the file ### Q: Can I work on multiple stories at once? @@ -371,7 +358,7 @@ See [IDE Setup Guides](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/do ### Q: Can I customize agents? -**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `{bmad_folder}/_cfg/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options. +**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `.bmad/_cfg/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options. **Note:** While source agents in this repo are YAML, they install as `.md` files with XML-style tags - a format any LLM can read and follow. diff --git a/src/modules/bmm/docs/images/workflow-method-greenfield.excalidraw b/src/modules/bmm/docs/images/workflow-method-greenfield.excalidraw index f4d2411f..c7acf4f5 100644 --- a/src/modules/bmm/docs/images/workflow-method-greenfield.excalidraw +++ b/src/modules/bmm/docs/images/workflow-method-greenfield.excalidraw @@ -2934,7 +2934,7 @@ "gap": 1 }, "endBinding": { - "elementId": "proc-story-done", + "elementId": "proc-code-review", "focus": 0.04241833499478815, "gap": 1.3466869862454587 }, @@ -3189,7 +3189,7 @@ "lineHeight": 1.25 }, { - "id": "proc-story-done", + "id": "proc-code-review", "type": "rectangle", "x": 1169.3991588878014, "y": 947.2529662369525, @@ -3207,12 +3207,12 @@ "value": 8 }, "groupIds": [ - "proc-story-done-group" + "proc-code-review-group" ], "boundElements": [ { "type": "text", - "id": "proc-story-done-text" + "id": "proc-code-review-text" }, { "type": "arrow", @@ -3235,7 +3235,7 @@ "link": null }, { - "id": "proc-story-done-text", + "id": "proc-code-review-text", "type": "text", "x": 1187.9272045420983, "y": 972.2529662369525, @@ -3249,14 +3249,14 @@ "roughness": 0, "opacity": 100, "groupIds": [ - "proc-story-done-group" + "proc-code-review-group" ], "fontSize": 16, "fontFamily": 1, "text": "Code Review\n<>", "textAlign": "center", "verticalAlign": "middle", - "containerId": "proc-story-done", + "containerId": "proc-code-review", "locked": false, "version": 502, "versionNonce": 1242095014, @@ -3289,7 +3289,7 @@ "opacity": 100, "groupIds": [], "startBinding": { - "elementId": "proc-story-done", + "elementId": "proc-code-review", "focus": 0.014488632877232727, "gap": 8.284295421831303 }, diff --git a/src/modules/bmm/docs/party-mode.md b/src/modules/bmm/docs/party-mode.md index 41c15a0a..277c4981 100644 --- a/src/modules/bmm/docs/party-mode.md +++ b/src/modules/bmm/docs/party-mode.md @@ -27,7 +27,7 @@ Type `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent), and su **The basics:** -1. Party mode reads `{bmad_folder}/_cfg/agent-manifest.csv` +1. Party mode reads `.bmad/_cfg/agent-manifest.csv` 2. Loads ALL installed agents (already includes your customizations from install) 3. BMad Master orchestrates - picks 2-3 relevant agents per message based on topic 4. Agents respond in character, can agree/disagree/build on each other's ideas @@ -126,11 +126,11 @@ _(Multiple perspectives reveal the right answer)_ ## Agent Customization -Party mode uses agents from `{bmad_folder}/[module]/agents/*.md` - these already include any customizations you applied during install. +Party mode uses agents from `.bmad/[module]/agents/*.md` - these already include any customizations you applied during install. **To customize agents for party mode:** -1. Create customization file: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml` +1. Create customization file: `.bmad/_cfg/agents/bmm-pm.customize.yaml` 2. Run `npx bmad-method install` to rebuild agents 3. Customizations now active in party mode diff --git a/src/modules/bmm/docs/quick-spec-flow.md b/src/modules/bmm/docs/quick-spec-flow.md index cd3d5b15..dd114e4e 100644 --- a/src/modules/bmm/docs/quick-spec-flow.md +++ b/src/modules/bmm/docs/quick-spec-flow.md @@ -377,12 +377,6 @@ Checks: Quick Spec Flow works seamlessly with all Phase 4 implementation workflows: -### story-context (SM Agent) - -- โœ… Recognizes tech-spec.md as authoritative source -- โœ… Extracts context from tech-spec (replaces PRD) -- โœ… Generates XML context for complex scenarios - ### create-story (SM Agent) - โœ… Can work with tech-spec.md instead of PRD @@ -529,10 +523,6 @@ Quick Spec Flow is **fully standalone**: **A:** No problem! You can always transition to BMad Method by running workflow-init and create-prd. Your tech-spec becomes input for the PRD. -### Q: Do I need story-context for every story? - -**A:** Usually no! Tech-spec is comprehensive enough for most Quick Flow projects. Only use story-context for complex edge cases. - ### Q: Can I skip validation? **A:** No, validation always runs automatically. But it's fast and catches issues early! @@ -564,15 +554,11 @@ Starter templates save hours of setup time. Let Quick Spec Flow find the best on When validation runs, read the scores. They tell you if your spec is production-ready. -### 5. **Story Context is Optional** - -For single changes, try going directly to dev-story first. Only add story-context if you hit complexity. - -### 6. **Keep Single Changes Truly Atomic** +### 5. **Keep Single Changes Truly Atomic** If your "single change" needs 3+ files, it might be a multi-story feature. Let the workflow guide you. -### 7. **Validate Story Sequence for Multi-Story Features** +### 6. **Validate Story Sequence for Multi-Story Features** When you get multiple stories, check the dependency validation output. Proper sequence matters! diff --git a/src/modules/bmm/docs/quick-start.md b/src/modules/bmm/docs/quick-start.md index 3aff89ef..0560b6de 100644 --- a/src/modules/bmm/docs/quick-start.md +++ b/src/modules/bmm/docs/quick-start.md @@ -35,7 +35,7 @@ _Complete visual flowchart showing all phases, workflows, agents (color-coded), npx bmad-method@alpha install ``` -The interactive installer will guide you through setup and create a `{bmad_folder}/` folder with all agents and workflows. +The interactive installer will guide you through setup and create a `.bmad/` folder with all agents and workflows. --- diff --git a/src/modules/bmm/docs/test-architecture.md b/src/modules/bmm/docs/test-architecture.md index 2ab2da3c..76b75bf3 100644 --- a/src/modules/bmm/docs/test-architecture.md +++ b/src/modules/bmm/docs/test-architecture.md @@ -398,7 +398,7 @@ MCP provides additional capabilities on top of TEA's default AI-based approach: } ``` -**To disable**: Set `tea_use_mcp_enhancements: false` in `{bmad_folder}/bmm/config.yaml` OR remove MCPs from IDE config. +**To disable**: Set `tea_use_mcp_enhancements: false` in `.bmad/bmm/config.yaml` OR remove MCPs from IDE config. @@ -440,9 +440,9 @@ Provides fixture-based utilities that integrate into TEA's test generation and r **Utilities available** (11 total): api-request, network-recorder, auth-session, intercept-network-call, recurse, log, file-utils, burn-in, network-error-monitor, fixtures-composition -**Enable during BMAD installation** by answering "Yes" when prompted, or manually set `tea_use_playwright_utils: true` in `{bmad_folder}/bmm/config.yaml`. +**Enable during BMAD installation** by answering "Yes" when prompted, or manually set `tea_use_playwright_utils: true` in `.bmad/bmm/config.yaml`. -**To disable**: Set `tea_use_playwright_utils: false` in `{bmad_folder}/bmm/config.yaml`. +**To disable**: Set `tea_use_playwright_utils: false` in `.bmad/bmm/config.yaml`. diff --git a/src/modules/bmm/docs/troubleshooting.md b/src/modules/bmm/docs/troubleshooting.md index a3cd63bf..35ba5ce8 100644 --- a/src/modules/bmm/docs/troubleshooting.md +++ b/src/modules/bmm/docs/troubleshooting.md @@ -196,7 +196,7 @@ workflow-init asks: "Is this work in progress or previous effort?" 2. Verify agent has workflow: - PM agent: prd, tech-spec - Architect agent: create-architecture, validate-architecture - - SM agent: sprint-planning, create-story, story-context + - SM agent: sprint-planning, create-story 3. Try menu number instead of name 4. Check you're using correct agent for workflow @@ -219,23 +219,6 @@ workflow-init asks: "Is this work in progress or previous effort?" 3. **Run in Phase 4 only** - Ensure Phase 2/3 complete first 4. **Check file paths** - Epic files should be in correct output folder -### Problem: story-context generates empty or wrong context - -**Symptoms:** - -- Context file created but has no useful content -- Context doesn't reference existing code -- Missing technical guidance - -**Solution:** - -1. **Run epic-tech-context first** - story-context builds on epic context -2. **Check story file exists** - Verify story was created by create-story -3. **For brownfield**: - - Ensure document-project was run - - Verify docs/index.md exists with codebase context -4. **Try regenerating** - Sometimes needs fresh attempt with more specific story details - --- ## Context and Documentation Issues @@ -362,7 +345,7 @@ For most brownfield projects, **Deep scan is sufficient**. 1. **For brownfield**: - Ensure document-project captured existing architecture - Review architecture docs before implementing -2. **Check story-context** - Should document integration points +2. **Check story file** - Should document integration points 3. **In tech-spec/architecture** - Explicitly document: - Which existing modules to modify - What APIs/services to integrate with @@ -384,7 +367,7 @@ For most brownfield projects, **Deep scan is sufficient**. - Should detect existing patterns - Asks for confirmation before proceeding 2. **Review documentation** - Ensure document-project captured patterns -3. **Use story-context** - Injects pattern guidance per story +3. **Use comprehensive story files** - Include pattern guidance in story 4. **Add to code-review checklist**: - Pattern adherence - Convention consistency @@ -459,9 +442,7 @@ To change locations, edit config.yaml then re-run workflows. ``` 2. **Some workflows auto-update**: - sprint-planning creates file - - epic-tech-context changes epic to "contexted" - - create-story changes story to "drafted" - - story-context changes to "ready-for-dev" + - create-story changes story to "ready-for-dev" - dev-story may auto-update (check workflow) 3. **Re-run sprint-planning** to resync if needed @@ -657,8 +638,8 @@ If your issue isn't covered here: ### "Context generation failed" -**Cause:** Missing prerequisites (epic context, story file, or docs) -**Fix:** Verify epic-tech-context run, story file exists, docs present +**Cause:** Missing prerequisites (story file or docs) +**Fix:** Verify story file exists, docs present --- diff --git a/src/modules/bmm/docs/workflow-document-project-reference.md b/src/modules/bmm/docs/workflow-document-project-reference.md index 3bd8749e..48d6efe9 100644 --- a/src/modules/bmm/docs/workflow-document-project-reference.md +++ b/src/modules/bmm/docs/workflow-document-project-reference.md @@ -179,7 +179,7 @@ The workflow uses a single comprehensive CSV file: **documentation-requirements.csv** - Complete project analysis guide -- Location: `/{bmad_folder}/bmm/workflows/document-project/documentation-requirements.csv` +- Location: `/.bmad/bmm/workflows/document-project/documentation-requirements.csv` - 12 project types (web, mobile, backend, cli, library, desktop, game, data, extension, infra, embedded) - 24 columns combining: - **Detection columns**: `project_type_id`, `key_file_patterns` (identifies project type from codebase) diff --git a/src/modules/bmm/docs/workflows-implementation.md b/src/modules/bmm/docs/workflows-implementation.md index 16791617..73dfa432 100644 --- a/src/modules/bmm/docs/workflows-implementation.md +++ b/src/modules/bmm/docs/workflows-implementation.md @@ -152,10 +152,9 @@ Dependencies: Story 1.2 (DONE) โœ… **Recommendation:** Run `create-story` to generate Story 1.3 After create-story: -1. Run story-context -2. Run dev-story -3. Run code-review -4. Run story-done +1. Run dev-story +2. Run code-review +3. Update sprint-status.yaml to mark story done ``` See: [workflow-status instructions](../workflows/workflow-status/instructions.md) diff --git a/src/modules/bmm/module.yaml b/src/modules/bmm/module.yaml index 5803e965..ed988217 100644 --- a/src/modules/bmm/module.yaml +++ b/src/modules/bmm/module.yaml @@ -11,7 +11,6 @@ subheader: "Agent and Workflow Configuration for this module" ## user_name ## communication_language ## output_folder -## bmad_folder ## install_user_docs ## kb_install diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md index ab2af7ce..187b8310 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md @@ -3,7 +3,7 @@ name: 'step-01-init' description: 'Initialize the product brief workflow by detecting continuation state and setting up the document' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief' +workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief' # File References thisStepFile: '{workflow_path}/steps/step-01-init.md' diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md index 01b228ca..62d70d77 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md @@ -3,7 +3,7 @@ name: 'step-01b-continue' description: 'Resume the product brief workflow from where it was left off, ensuring smooth continuation' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief' +workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief' # File References thisStepFile: '{workflow_path}/steps/step-01b-continue.md' diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md index af1d60cc..a341fdb9 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md @@ -3,7 +3,7 @@ name: 'step-02-vision' description: 'Discover and define the core product vision, problem statement, and unique value proposition' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief' +workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief' # File References thisStepFile: '{workflow_path}/steps/step-02-vision.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 2: Product Vision Discovery diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md index 8c9edf10..e7a98973 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md @@ -3,7 +3,7 @@ name: 'step-03-users' description: 'Define target users with rich personas and map their key interactions with the product' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief' +workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief' # File References thisStepFile: '{workflow_path}/steps/step-03-users.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 3: Target Users Discovery diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md index 18b39fd2..3ec52bc1 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md @@ -3,7 +3,7 @@ name: 'step-04-metrics' description: 'Define comprehensive success metrics that include user success, business objectives, and key performance indicators' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief' +workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief' # File References thisStepFile: '{workflow_path}/steps/step-04-metrics.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 4: Success Metrics Definition diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md index e3429021..1b84767e 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md @@ -3,7 +3,7 @@ name: 'step-05-scope' description: 'Define MVP scope with clear boundaries and outline future vision while managing scope creep' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief' +workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief' # File References thisStepFile: '{workflow_path}/steps/step-05-scope.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 5: MVP Scope Definition diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md index 6d7239ef..13db46e0 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md @@ -3,7 +3,7 @@ name: 'step-06-complete' description: 'Complete the product brief workflow, update status files, and suggest next steps for the project' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief' +workflow_path: '{project-root}/.bmad/bmm/workflows/1-analysis/product-brief' # File References thisStepFile: '{workflow_path}/steps/step-06-complete.md' @@ -119,7 +119,10 @@ Provide guidance on logical next workflows: - Success metrics become specific acceptance criteria - MVP scope becomes detailed feature specifications -**Other Potential Next Steps:** 2. `workflow create-ux-design` - UX research and design 3. `workflow create-architecture` - Technical architecture planning 4. `workflow domain-research` - Deep market or domain research (if needed) +**Other Potential Next Steps:** + +2. `workflow create-ux-design` - UX research and design (can run parallel with PRD) +3. `workflow domain-research` - Deep market or domain research (if needed) **Strategic Considerations:** @@ -145,7 +148,6 @@ The brief captures everything needed to guide subsequent product development: - PRD workflow for detailed requirements? - UX design workflow for user experience planning? -- Architecture workflow for technical design? **Product Brief Complete**" diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/workflow.md b/src/modules/bmm/workflows/1-analysis/product-brief/workflow.md index a070d3ce..cc7fdd15 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/workflow.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/workflow.md @@ -49,10 +49,10 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/{bmad_folder}/bmm/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/bmm/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level` ### 2. First Step EXECUTION -Load, read the full file and then execute `{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md` to begin the workflow. +Load, read the full file and then execute `{project-root}/.bmad/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md` to begin the workflow. diff --git a/src/modules/bmm/workflows/1-analysis/research/workflow.md b/src/modules/bmm/workflows/1-analysis/research/workflow.md index 3441b90c..b02af79d 100644 --- a/src/modules/bmm/workflows/1-analysis/research/workflow.md +++ b/src/modules/bmm/workflows/1-analysis/research/workflow.md @@ -42,7 +42,7 @@ This uses **micro-file architecture** with **routing-based discovery**: ### Configuration Loading -Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve: +Load config from `{project-root}/.bmad/bmm/config.yaml` and resolve: - `project_name`, `output_folder`, `user_name` - `communication_language`, `document_output_language`, `user_skill_level` @@ -51,7 +51,7 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve: ### Paths -- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research` +- `installed_path` = `{project-root}/.bmad/bmm/workflows/1-analysis/research` - `template_path` = `{installed_path}/research.template.md` - `default_output_file` = `{output_folder}/analysis/research/{{research_type}}-{{topic}}-research-{{date}}.md` (dynamic based on research type) diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md index 540994d0..28dba6f8 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -154,7 +154,7 @@ Show the generated project understanding content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current project understanding content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current project understanding content - Process the enhanced project insights that come back - Ask user: "Accept these improvements to the project understanding? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -162,7 +162,7 @@ Show the generated project understanding content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current project understanding +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current project understanding - Process the collaborative insights and different perspectives that come back - Ask user: "Accept these changes to the project understanding? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md index b24dceb2..ba0cd167 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -160,7 +160,7 @@ Show the generated core experience content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current core experience content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current core experience content - Process the enhanced experience insights that come back - Ask user: "Accept these improvements to the core experience definition? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -168,7 +168,7 @@ Show the generated core experience content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current core experience definition +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current core experience definition - Process the collaborative experience improvements that come back - Ask user: "Accept these changes to the core experience definition? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md index 85d75864..efc52ded 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -163,7 +163,7 @@ Show the generated emotional response content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current emotional response content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current emotional response content - Process the enhanced emotional insights that come back - Ask user: "Accept these improvements to the emotional response definition? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -171,7 +171,7 @@ Show the generated emotional response content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current emotional response definition +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current emotional response definition - Process the collaborative emotional insights that come back - Ask user: "Accept these changes to the emotional response definition? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md index d575178d..d84abb75 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -178,7 +178,7 @@ Show the generated inspiration analysis content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current inspiration analysis content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current inspiration analysis content - Process the enhanced pattern insights that come back - Ask user: "Accept these improvements to the inspiration analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -186,7 +186,7 @@ Show the generated inspiration analysis content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current inspiration analysis +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current inspiration analysis - Process the collaborative pattern insights that come back - Ask user: "Accept these changes to the inspiration analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md index 87009183..ac33a424 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -196,7 +196,7 @@ Show the generated design system content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current design system content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current design system content - Process the enhanced design system insights that come back - Ask user: "Accept these improvements to the design system decision? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -204,7 +204,7 @@ Show the generated design system content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current design system choice +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current design system choice - Process the collaborative design system insights that come back - Ask user: "Accept these changes to the design system decision? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md index 09173626..a03e83bb 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -198,7 +198,7 @@ Show the generated defining experience content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current defining experience content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current defining experience content - Process the enhanced experience insights that come back - Ask user: "Accept these improvements to the defining experience? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -206,7 +206,7 @@ Show the generated defining experience content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current defining experience +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current defining experience - Process the collaborative experience insights that come back - Ask user: "Accept these changes to the defining experience? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md index 364f5ac6..d71b0853 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -168,7 +168,7 @@ Show the generated visual foundation content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current visual foundation content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current visual foundation content - Process the enhanced visual insights that come back - Ask user: "Accept these improvements to the visual foundation? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -176,7 +176,7 @@ Show the generated visual foundation content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current visual foundation +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current visual foundation - Process the collaborative visual insights that come back - Ask user: "Accept these changes to the visual foundation? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md index 185e5e83..2fcfaf7d 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -168,7 +168,7 @@ Show the generated design direction content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current design direction content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current design direction content - Process the enhanced design insights that come back - Ask user: "Accept these improvements to the design direction? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -176,7 +176,7 @@ Show the generated design direction content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current design direction +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current design direction - Process the collaborative design insights that come back - Ask user: "Accept these changes to the design direction? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md index 5f9ff973..c0142e93 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -186,7 +186,7 @@ Show the generated user journey content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current user journey content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current user journey content - Process the enhanced journey insights that come back - Ask user: "Accept these improvements to the user journeys? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -194,7 +194,7 @@ Show the generated user journey content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current user journeys +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current user journeys - Process the collaborative journey insights that come back - Ask user: "Accept these changes to the user journeys? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md index 96dcec31..d258ae82 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -192,7 +192,7 @@ Show the generated component strategy content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current component strategy content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current component strategy content - Process the enhanced component insights that come back - Ask user: "Accept these improvements to the component strategy? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -200,7 +200,7 @@ Show the generated component strategy content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current component strategy +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current component strategy - Process the collaborative component insights that come back - Ask user: "Accept these changes to the component strategy? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md index 99ea7dba..bf4f1ab6 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -181,7 +181,7 @@ Show the generated UX patterns content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current UX patterns content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current UX patterns content - Process the enhanced pattern insights that come back - Ask user: "Accept these improvements to the UX patterns? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -189,7 +189,7 @@ Show the generated UX patterns content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current UX patterns +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current UX patterns - Process the collaborative pattern insights that come back - Ask user: "Accept these changes to the UX patterns? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md index ffb28e91..c5a38ca2 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md @@ -29,8 +29,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -208,7 +208,7 @@ Show the generated responsive and accessibility content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current responsive/accessibility content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current responsive/accessibility content - Process the enhanced insights that come back - Ask user: "Accept these improvements to the responsive/accessibility strategy? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -216,7 +216,7 @@ Show the generated responsive and accessibility content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy - Process the collaborative insights that come back - Ask user: "Accept these changes to the responsive/accessibility strategy? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md index 1810e94d..affe2494 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md +++ b/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md @@ -25,7 +25,7 @@ This uses **micro-file architecture** for disciplined execution: ### Configuration Loading -Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve: +Load config from `{project-root}/.bmad/bmm/config.yaml` and resolve: - `project_name`, `output_folder`, `user_name` - `communication_language`, `document_output_language`, `user_skill_level` @@ -33,7 +33,7 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve: ### Paths -- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design` +- `installed_path` = `{project-root}/.bmad/bmm/workflows/2-plan-workflows/create-ux-design` - `template_path` = `{installed_path}/ux-design-template.md` - `default_output_file` = `{output_folder}/ux-design-specification.md` diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md index d0a29cad..7680c417 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md @@ -3,7 +3,7 @@ name: 'step-01-init' description: 'Initialize the PRD workflow by detecting continuation state and setting up the document' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-01-init.md' diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01b-continue.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01b-continue.md index 1b0abb30..0b1132c1 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01b-continue.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01b-continue.md @@ -3,7 +3,7 @@ name: 'step-01b-continue' description: 'Resume an interrupted PRD workflow from the last completed step' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-01b-continue.md' diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-02-discovery.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-02-discovery.md index c4be410a..ac480a17 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-02-discovery.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-02-discovery.md @@ -3,7 +3,7 @@ name: 'step-02-discovery' description: 'Conduct project and domain discovery with data-driven classification' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-02-discovery.md' @@ -16,8 +16,8 @@ projectTypesCSV: '{workflow_path}/project-types.csv' domainComplexityCSV: '{workflow_path}/domain-complexity.csv' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 2: Project & Domain Discovery diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md index 9c8f125c..566a291d 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md @@ -3,7 +3,7 @@ name: 'step-03-success' description: 'Define comprehensive success criteria covering user, business, and technical success' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-03-success.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/prd.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 3: Success Criteria Definition @@ -49,8 +49,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -228,7 +228,7 @@ Show the generated content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current success criteria content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current success criteria content - Process the enhanced success metrics that come back - Ask user: "Accept these improvements to the success criteria? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -236,7 +236,7 @@ Show the generated content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current success criteria +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current success criteria - Process the collaborative improvements to metrics and scope - Ask user: "Accept these changes to the success criteria? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md index e9b2d137..6a061357 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md @@ -3,7 +3,7 @@ name: 'step-04-journeys' description: 'Map ALL user types that interact with the system with narrative story-based journeys' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-04-journeys.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/prd.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 4: User Journey Mapping @@ -49,8 +49,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -222,7 +222,7 @@ Show the generated journey content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current journey content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current journey content - Process the enhanced journey insights that come back - Ask user: "Accept these improvements to the user journeys? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -230,7 +230,7 @@ Show the generated journey content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current journeys +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current journeys - Process the collaborative journey improvements and additions - Ask user: "Accept these changes to the user journeys? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -240,7 +240,7 @@ Show the generated journey content and present choices: - Append the final content to `{output_folder}/prd.md` - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]` -- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md` (or determine if step is optional based on domain complexity) +- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md` (or determine if step is optional based on domain complexity) ## APPEND TO DOCUMENT: diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md index 5fd01fc9..e904ff12 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md @@ -3,7 +3,7 @@ name: 'step-05-domain' description: 'Explore domain-specific requirements for complex domains (optional step)' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-05-domain.md' @@ -15,8 +15,8 @@ outputFile: '{output_folder}/prd.md' domainComplexityCSV: '{workflow_path}/domain-complexity.csv' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 5: Domain-Specific Exploration @@ -52,8 +52,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -71,7 +71,7 @@ Before proceeding with this step, verify: - Is `complexity_level` from step-02 equal to "high" and/or does the domain have specific regulatory/compliance needs? - Would domain exploration significantly impact the product requirements? -If NO to these questions, skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`. +If NO to these questions, skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`. ## YOUR TASK: @@ -83,7 +83,7 @@ Explore domain-specific requirements for complex domains that need specialized c Load domain-specific configuration for complex domains: -- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv` completely +- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv` completely - Find the row where `domain` matches the detected domain from step-02 - Extract these columns: - `key_concerns` (semicolon-separated list) @@ -207,7 +207,7 @@ Show the generated domain content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current domain content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current domain content - Process the enhanced domain insights that come back - Ask user: "Accept these domain requirement improvements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -215,7 +215,7 @@ Show the generated domain content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current domain requirements +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current domain requirements - Process the collaborative domain expertise and validation - Ask user: "Accept these changes to domain requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -225,7 +225,7 @@ Show the generated domain content and present choices: - Append the content to `{output_folder}/prd.md` - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]` -- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md` +- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md` ## APPEND TO DOCUMENT: @@ -257,7 +257,7 @@ When user selects 'C', append the content directly to the document using the str ## SKIP CONDITIONS: -Skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md` if: +Skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md` if: - `complexity_level` from step-02 is not "high" - Domain has no specific regulatory/compliance requirements @@ -265,6 +265,6 @@ Skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workf ## NEXT STEP: -After user selects 'C' and content is saved to document, load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`. +After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`. Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md index 45e33c09..94f04e55 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md @@ -3,7 +3,7 @@ name: 'step-06-innovation' description: 'Detect and explore innovative aspects of the product (optional step)' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-06-innovation.md' @@ -15,8 +15,8 @@ outputFile: '{output_folder}/prd.md' projectTypesCSV: '{workflow_path}/project-types.csv' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 6: Innovation Discovery @@ -52,8 +52,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -83,7 +83,7 @@ Detect and explore innovation patterns in the product, focusing on what makes it Load innovation signals specific to this project type: -- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely +- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely - Find the row where `project_type` matches detected type from step-02 - Extract `innovation_signals` (semicolon-separated list) - Extract `web_search_triggers` for potential innovation research @@ -186,7 +186,7 @@ Show the generated innovation content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current innovation content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current innovation content - Process the enhanced innovation insights that come back - Ask user: "Accept these improvements to the innovation analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -194,7 +194,7 @@ Show the generated innovation content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current innovation content +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current innovation content - Process the collaborative innovation exploration and ideation - Ask user: "Accept these changes to the innovation analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -204,7 +204,7 @@ Show the generated innovation content and present choices: - Append the final content to `{output_folder}/prd.md` - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]` -- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md` +- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md` ## NO INNOVATION DETECTED: @@ -215,7 +215,7 @@ If no genuine innovation signals are found after exploration: [A] Force innovation exploration - Let's try to find innovative angles [C] Continue - Skip innovation section and move to Project Type Analysis (Step 7 of 11)" -If user selects 'A', proceed with content generation anyway. If 'C', skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`. +If user selects 'A', proceed with content generation anyway. If 'C', skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`. ## APPEND TO DOCUMENT: @@ -247,7 +247,7 @@ When user selects 'C', append the content directly to the document using the str ## SKIP CONDITIONS: -Skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md` if: +Skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md` if: - No innovation signals detected in conversation - Product is incremental improvement rather than breakthrough @@ -256,6 +256,6 @@ Skip this step and load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workf ## NEXT STEP: -After user selects 'C' and content is saved to document (or step is skipped), load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`. +After user selects 'C' and content is saved to document (or step is skipped), load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`. Remember: Do NOT proceed to step-07 until user explicitly selects 'C' from the A/P/C menu (or confirms step skip)! diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md index af887c16..fa2fe95c 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md @@ -3,7 +3,7 @@ name: 'step-07-project-type' description: 'Conduct project-type specific discovery using CSV-driven guidance' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-07-project-type.md' @@ -15,8 +15,8 @@ outputFile: '{output_folder}/prd.md' projectTypesCSV: '{workflow_path}/project-types.csv' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 7: Project-Type Deep Dive @@ -52,8 +52,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -74,7 +74,7 @@ Conduct project-type specific discovery using CSV-driven guidance to define tech Load project-type specific configuration: -- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely +- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely - Find the row where `project_type` matches detected type from step-02 - Extract these columns: - `key_questions` (semicolon-separated list of discovery questions) @@ -182,7 +182,7 @@ Show the generated project-type content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current project-type content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current project-type content - Process the enhanced technical insights that come back - Ask user: "Accept these improvements to the technical requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -190,7 +190,7 @@ Show the generated project-type content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current project-type requirements +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current project-type requirements - Process the collaborative technical expertise and validation - Ask user: "Accept these changes to the technical requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -200,7 +200,7 @@ Show the generated project-type content and present choices: - Append the final content to `{output_folder}/prd.md` - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]` -- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md` +- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md` ## APPEND TO DOCUMENT: @@ -252,6 +252,6 @@ When user selects 'C', append the content directly to the document using the str ## NEXT STEP: -After user selects 'C' and content is saved to document, load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md` to define project scope. +After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md` to define project scope. Remember: Do NOT proceed to step-08 (Scoping) until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md index a2fe4602..5e4f5d21 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md @@ -3,7 +3,7 @@ name: 'step-08-scoping' description: 'Define MVP boundaries and prioritize features across development phases' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-08-scoping.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/prd.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 8: Scoping Exercise - MVP & Future Features @@ -50,8 +50,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -243,7 +243,7 @@ Show the scoping decisions and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with current scoping analysis +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with current scoping analysis - Process enhanced scoping insights that come back - Ask user: "Accept these improvements to the scoping decisions? (y/n)" - If yes: Update content, then return to A/P/C menu @@ -251,7 +251,7 @@ Show the scoping decisions and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with scoping context +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with scoping context - Process collaborative insights on MVP and roadmap decisions - Ask user: "Accept these changes to the scoping decisions? (y/n)" - If yes: Update content, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md index 66f83fb4..c09c35e1 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md @@ -3,7 +3,7 @@ name: 'step-09-functional' description: 'Synthesize all discovery into comprehensive functional requirements' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-09-functional.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/prd.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 9: Functional Requirements Synthesis @@ -49,8 +49,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -209,7 +209,7 @@ Show the generated functional requirements and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current FR list +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current FR list - Process the enhanced capability coverage that comes back - Ask user: "Accept these additions to the functional requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -217,7 +217,7 @@ Show the generated functional requirements and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current FR list +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current FR list - Process the collaborative capability validation and additions - Ask user: "Accept these changes to the functional requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -227,7 +227,7 @@ Show the generated functional requirements and present choices: - Append the final content to `{output_folder}/prd.md` - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9]` -- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md` +- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md` ## APPEND TO DOCUMENT: @@ -264,6 +264,6 @@ Emphasize to user: "This FR list is now binding. Any feature not listed here wil ## NEXT STEP: -After user selects 'C' and content is saved to document, load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md` to define non-functional requirements. +After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md` to define non-functional requirements. Remember: Do NOT proceed to step-10 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md index a99f0e0c..e7e59d99 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md @@ -3,7 +3,7 @@ name: 'step-10-nonfunctional' description: 'Define quality attributes that matter for this specific product' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-10-nonfunctional.md' @@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/prd.md' # Task References -advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml' -partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md' +advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml' +partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md' --- # Step 10: Non-Functional Requirements @@ -49,8 +49,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to this step's A/P/C menu - User accepts/rejects protocol changes before proceeding @@ -209,7 +209,7 @@ Show the generated NFR content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current NFR content +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current NFR content - Process the enhanced quality attribute insights that come back - Ask user: "Accept these improvements to the non-functional requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -217,7 +217,7 @@ Show the generated NFR content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current NFR list +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current NFR list - Process the collaborative technical validation and additions - Ask user: "Accept these changes to the non-functional requirements? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -227,7 +227,7 @@ Show the generated NFR content and present choices: - Append the final content to `{output_folder}/prd.md` - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]` -- Load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md` +- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md` ## APPEND TO DOCUMENT: @@ -288,6 +288,6 @@ When user selects 'C', append the content directly to the document using the str ## NEXT STEP: -After user selects 'C' and content is saved to document, load `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md` to finalize the PRD and complete the workflow. +After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md` to finalize the PRD and complete the workflow. Remember: Do NOT proceed to step-11 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md index c32de8d5..6effb50b 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md @@ -3,7 +3,7 @@ name: 'step-11-complete' description: 'Complete the PRD workflow, update status files, and suggest next steps' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd' +workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd' # File References thisStepFile: '{workflow_path}/steps/step-11-complete.md' diff --git a/src/modules/bmm/workflows/2-plan-workflows/prd/workflow.md b/src/modules/bmm/workflows/2-plan-workflows/prd/workflow.md index 224f24fe..ac170422 100644 --- a/src/modules/bmm/workflows/2-plan-workflows/prd/workflow.md +++ b/src/modules/bmm/workflows/2-plan-workflows/prd/workflow.md @@ -1,7 +1,7 @@ --- name: create-prd description: Creates a comprehensive PRDs through collaborative step-by-step discovery between two product managers working as peers. -main_config: '{project-root}/{bmad_folder}/bmm/config.yaml' +main_config: '{project-root}/.bmad/bmm/config.yaml' web_bundle: true --- diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-02-context.md b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-02-context.md index b63132ae..0dd7569f 100644 --- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-02-context.md +++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-02-context.md @@ -30,8 +30,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -169,7 +169,7 @@ Show the generated content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current context analysis +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current context analysis - Process the enhanced architectural insights that come back - Ask user: "Accept these enhancements to the project context analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu @@ -177,7 +177,7 @@ Show the generated content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current project context +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current project context - Process the collaborative improvements to architectural understanding - Ask user: "Accept these changes to the project context analysis? (y/n)" - If yes: Update content with improvements, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-03-starter.md b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-03-starter.md index 5fdca68c..52f7a792 100644 --- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-03-starter.md +++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-03-starter.md @@ -30,8 +30,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -276,7 +276,7 @@ Show the generated content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with current starter analysis +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with current starter analysis - Process enhanced insights about starter options or custom approaches - Ask user: "Accept these changes to the starter template evaluation? (y/n)" - If yes: Update content, then return to A/P/C menu @@ -284,7 +284,7 @@ Show the generated content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with starter evaluation context +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with starter evaluation context - Process collaborative insights about starter trade-offs - Ask user: "Accept these changes to the starter template evaluation? (y/n)" - If yes: Update content, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-04-decisions.md b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-04-decisions.md index 9b445169..a25f0d1d 100644 --- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-04-decisions.md +++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-04-decisions.md @@ -31,8 +31,8 @@ This step will generate content and present choices for each decision category: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -263,7 +263,7 @@ Show the generated decisions content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with specific decision categories +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with specific decision categories - Process enhanced insights about particular decisions - Ask user: "Accept these enhancements to the architectural decisions? (y/n)" - If yes: Update content, then return to A/P/C menu @@ -271,7 +271,7 @@ Show the generated decisions content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with architectural decisions context +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with architectural decisions context - Process collaborative insights about decision trade-offs - Ask user: "Accept these changes to the architectural decisions? (y/n)" - If yes: Update content, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-05-patterns.md b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-05-patterns.md index d58c67a6..12c8a70b 100644 --- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-05-patterns.md +++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-05-patterns.md @@ -31,8 +31,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -304,7 +304,7 @@ Show the generated patterns content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with current patterns +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with current patterns - Process enhanced consistency rules that come back - Ask user: "Accept these additional pattern refinements? (y/n)" - If yes: Update content, then return to A/P/C menu @@ -312,7 +312,7 @@ Show the generated patterns content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with implementation patterns context +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with implementation patterns context - Process collaborative insights about potential conflicts - Ask user: "Accept these changes to the implementation patterns? (y/n)" - If yes: Update content, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-06-structure.md b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-06-structure.md index 44315a39..64d6385a 100644 --- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-06-structure.md +++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-06-structure.md @@ -31,8 +31,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -324,7 +324,7 @@ Show the generated project structure content and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with current project structure +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with current project structure - Process enhanced organizational insights that come back - Ask user: "Accept these changes to the project structure? (y/n)" - If yes: Update content, then return to A/P/C menu @@ -332,7 +332,7 @@ Show the generated project structure content and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with project structure context +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with project structure context - Process collaborative insights about organization trade-offs - Ask user: "Accept these changes to the project structure? (y/n)" - If yes: Update content, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-07-validation.md b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-07-validation.md index 0bdaf868..79f44404 100644 --- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-07-validation.md +++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-07-validation.md @@ -31,8 +31,8 @@ This step will generate content and present choices: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding @@ -304,7 +304,7 @@ Show the validation results and present choices: #### If 'A' (Advanced Elicitation): -- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with validation issues +- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with validation issues - Process enhanced solutions for complex concerns - Ask user: "Accept these architectural improvements? (y/n)" - If yes: Update content, then return to A/P/C menu @@ -312,7 +312,7 @@ Show the validation results and present choices: #### If 'P' (Party Mode): -- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with validation context +- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with validation context - Process collaborative insights on implementation readiness - Ask user: "Accept these changes to the validation results? (y/n)" - If yes: Update content, then return to A/P/C menu diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-08-complete.md b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-08-complete.md index 703b2573..0abd424c 100644 --- a/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-08-complete.md +++ b/src/modules/bmm/workflows/3-solutioning/architecture/steps/step-08-complete.md @@ -314,7 +314,7 @@ The workflow will collaborate with you to create an optimized `project_context.m **Execute the Generate Project Context workflow:** -- Load and execute: `{project-root}/{bmad_folder}/bmm/workflows/generate-project-context/workflow.md` +- Load and execute: `{project-root}/.bmad/bmm/workflows/generate-project-context/workflow.md` - The workflow will handle discovery, generation, and completion of the project context file - After completion, return here for final handoff diff --git a/src/modules/bmm/workflows/3-solutioning/architecture/workflow.md b/src/modules/bmm/workflows/3-solutioning/architecture/workflow.md index 7d5deeb7..b235622e 100644 --- a/src/modules/bmm/workflows/3-solutioning/architecture/workflow.md +++ b/src/modules/bmm/workflows/3-solutioning/architecture/workflow.md @@ -28,7 +28,7 @@ This uses **micro-file architecture** for disciplined execution: ### Configuration Loading -Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve: +Load config from `{project-root}/.bmad/bmm/config.yaml` and resolve: - `project_name`, `output_folder`, `user_name` - `communication_language`, `document_output_language`, `user_skill_level` @@ -36,7 +36,7 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve: ### Paths -- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture` +- `installed_path` = `{project-root}/.bmad/bmm/workflows/3-solutioning/architecture` - `template_path` = `{installed_path}/architecture-decision-template.md` - `data_files_path` = `{installed_path}/data/` diff --git a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md index 9e8a5674..a0a1c656 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md +++ b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md @@ -3,7 +3,7 @@ name: 'step-01-validate-prerequisites' description: 'Validate required documents exist and extract all requirements for epic and story creation' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories' +workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories' # File References thisStepFile: '{workflow_path}/steps/step-01-validate-prerequisites.md' diff --git a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md index 7935510a..6c535058 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md +++ b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md @@ -3,7 +3,7 @@ name: 'step-02-design-epics' description: 'Design and approve the epics_list that will organize all requirements into user-value-focused epics' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories' +workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories' # File References thisStepFile: '{workflow_path}/steps/step-02-design-epics.md' diff --git a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md index bd0254af..860e5991 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md +++ b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md @@ -3,7 +3,7 @@ name: 'step-03-create-stories' description: 'Generate all epics with their stories following the template structure' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories' +workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories' # File References thisStepFile: '{workflow_path}/steps/step-03-create-stories.md' diff --git a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md index 22115133..c11595b9 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md +++ b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md @@ -3,7 +3,7 @@ name: 'step-04-final-validation' description: 'Validate complete coverage of all requirements and ensure implementation readiness' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories' +workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories' # File References thisStepFile: '{workflow_path}/steps/step-04-final-validation.md' diff --git a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md index 2975980a..ad0baacc 100644 --- a/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md +++ b/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md @@ -49,10 +49,10 @@ This uses **step-file architecture** for disciplined execution: ### 1. Configuration Loading -Load and read full config from {project-root}/{bmad_folder}/bmm/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/bmm/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` ### 2. First Step EXECUTION -Load, read the full file and then execute `{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md` to begin the workflow. +Load, read the full file and then execute `{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md` to begin the workflow. diff --git a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-01-document-discovery.md b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-01-document-discovery.md index 2badfe7c..87b44993 100644 --- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-01-document-discovery.md +++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-01-document-discovery.md @@ -3,7 +3,7 @@ name: 'step-01-document-discovery' description: 'Discover and inventory all project documents, handling duplicates and organizing file structure' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness' +workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness' # File References thisStepFile: '{workflow_path}/steps/step-01-document-discovery.md' diff --git a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-02-prd-analysis.md b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-02-prd-analysis.md index 8dac5241..2894a69d 100644 --- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-02-prd-analysis.md +++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-02-prd-analysis.md @@ -3,7 +3,7 @@ name: 'step-02-prd-analysis' description: 'Read and analyze PRD to extract all FRs and NFRs for coverage validation' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness' +workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness' # File References thisStepFile: '{workflow_path}/steps/step-02-prd-analysis.md' diff --git a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-03-epic-coverage-validation.md b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-03-epic-coverage-validation.md index 5e0789fc..75745637 100644 --- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-03-epic-coverage-validation.md +++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-03-epic-coverage-validation.md @@ -3,7 +3,7 @@ name: 'step-03-epic-coverage-validation' description: 'Validate that all PRD FRs are covered in epics and stories' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness' +workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness' # File References thisStepFile: '{workflow_path}/steps/step-03-epic-coverage-validation.md' @@ -102,11 +102,11 @@ Create coverage matrix: ``` ## FR Coverage Analysis -| FR Number | PRD Requirement | Epic Coverage | Status | -|-----------|----------------|---------------|---------| -| FR1 | [PRD text] | Epic X Story Y | โœ“ Covered | -| FR2 | [PRD text] | **NOT FOUND** | โŒ MISSING | -| FR3 | [PRD text] | Epic Z Story A | โœ“ Covered | +| FR Number | PRD Requirement | Epic Coverage | Status | +| --------- | --------------- | -------------- | --------- | +| FR1 | [PRD text] | Epic X Story Y | โœ“ Covered | +| FR2 | [PRD text] | **NOT FOUND** | โŒ MISSING | +| FR3 | [PRD text] | Epic Z Story A | โœ“ Covered | ``` ### 5. Document Missing Coverage diff --git a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-04-ux-alignment.md b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-04-ux-alignment.md index d02ddd94..1ef14ff1 100644 --- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-04-ux-alignment.md +++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-04-ux-alignment.md @@ -3,7 +3,7 @@ name: 'step-04-ux-alignment' description: 'Check for UX document and validate alignment with PRD and Architecture' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness' +workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness' # File References thisStepFile: '{workflow_path}/steps/step-04-ux-alignment.md' diff --git a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-05-epic-quality-review.md b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-05-epic-quality-review.md index 06b9cadb..d7e01274 100644 --- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-05-epic-quality-review.md +++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-05-epic-quality-review.md @@ -3,14 +3,14 @@ name: 'step-05-epic-quality-review' description: 'Validate epics and stories against create-epics-and-stories best practices' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness' +workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness' # File References thisStepFile: '{workflow_path}/steps/step-05-epic-quality-review.md' nextStepFile: '{workflow_path}/steps/step-06-final-assessment.md' workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/implementation-readiness-report-{{date}}.md' -epicsBestPractices: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories' +epicsBestPractices: '{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories' --- # Step 5: Epic Quality Review diff --git a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-06-final-assessment.md b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-06-final-assessment.md index 51fa82ee..d495da99 100644 --- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-06-final-assessment.md +++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/steps/step-06-final-assessment.md @@ -3,7 +3,7 @@ name: 'step-06-final-assessment' description: 'Compile final assessment and polish the readiness report' # Path Definitions -workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness' +workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness' # File References thisStepFile: '{workflow_path}/steps/step-06-final-assessment.md' diff --git a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/workflow.md b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/workflow.md index 2483cde8..e14c444a 100644 --- a/src/modules/bmm/workflows/3-solutioning/implementation-readiness/workflow.md +++ b/src/modules/bmm/workflows/3-solutioning/implementation-readiness/workflow.md @@ -45,7 +45,7 @@ web_bundle: false ### 1. Module Configuration Loading -Load and read full config from {project-root}/{bmad_folder}/bmm/config.yaml and resolve: +Load and read full config from {project-root}/.bmad/bmm/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` diff --git a/src/modules/bmm/workflows/4-implementation/code-review/instructions.xml b/src/modules/bmm/workflows/4-implementation/code-review/instructions.xml index bf8b7d69..cc45c49d 100644 --- a/src/modules/bmm/workflows/4-implementation/code-review/instructions.xml +++ b/src/modules/bmm/workflows/4-implementation/code-review/instructions.xml @@ -1,5 +1,5 @@ - The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml + 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 all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} diff --git a/src/modules/bmm/workflows/4-implementation/code-review/workflow.yaml b/src/modules/bmm/workflows/4-implementation/code-review/workflow.yaml index c055db20..c148ef89 100644 --- a/src/modules/bmm/workflows/4-implementation/code-review/workflow.yaml +++ b/src/modules/bmm/workflows/4-implementation/code-review/workflow.yaml @@ -4,7 +4,7 @@ description: "Perform an ADVERSARIAL Senior Developer code review that finds 3-1 author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -15,7 +15,7 @@ sprint_artifacts: "{config_source}:sprint_artifacts" sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review" instructions: "{installed_path}/instructions.xml" validation: "{installed_path}/checklist.md" template: false diff --git a/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md b/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md index 1cbe1bf0..7fb6dc06 100644 --- a/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md +++ b/src/modules/bmm/workflows/4-implementation/correct-course/checklist.md @@ -1,6 +1,6 @@ # Change Navigation Checklist -This checklist is executed as part of: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml +This checklist is executed as part of: {project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml Work through each section systematically with the user, recording findings and impacts diff --git a/src/modules/bmm/workflows/4-implementation/correct-course/instructions.md b/src/modules/bmm/workflows/4-implementation/correct-course/instructions.md index 2adbb321..738aeea9 100644 --- a/src/modules/bmm/workflows/4-implementation/correct-course/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/correct-course/instructions.md @@ -1,7 +1,7 @@ # Correct Course - Sprint Change Management Instructions -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} diff --git a/src/modules/bmm/workflows/4-implementation/correct-course/workflow.yaml b/src/modules/bmm/workflows/4-implementation/correct-course/workflow.yaml index 16e1ff0c..627cebb5 100644 --- a/src/modules/bmm/workflows/4-implementation/correct-course/workflow.yaml +++ b/src/modules/bmm/workflows/4-implementation/correct-course/workflow.yaml @@ -3,7 +3,7 @@ name: "correct-course" description: "Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation" author: "BMad Method" -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -46,7 +46,7 @@ input_file_patterns: sharded: "{output_folder}/index.md" load_strategy: "INDEX_GUIDED" -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course" template: false instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmm/workflows/4-implementation/create-story/checklist.md b/src/modules/bmm/workflows/4-implementation/create-story/checklist.md index 5dae46ed..7996fee1 100644 --- a/src/modules/bmm/workflows/4-implementation/create-story/checklist.md +++ b/src/modules/bmm/workflows/4-implementation/create-story/checklist.md @@ -33,7 +33,7 @@ This is a COMPETITION to create the **ULTIMATE story context** that makes LLM de ### **When Running from Create-Story Workflow:** -- The `{project_root}/{bmad_folder}/core/tasks/validate-workflow.xml` framework will automatically: +- The `{project_root}/.bmad/core/tasks/validate-workflow.xml` framework will automatically: - Load this checklist file - Load the newly created story file (`{story_file_path}`) - Load workflow variables from `{installed_path}/workflow.yaml` @@ -63,7 +63,7 @@ You will systematically re-do the entire story creation process, but with a crit 1. **Load the workflow configuration**: `{installed_path}/workflow.yaml` for variable inclusion 2. **Load the story file**: `{story_file_path}` (provided by user or discovered) -3. **Load validation framework**: `{project_root}/{bmad_folder}/core/tasks/validate-workflow.xml` +3. **Load validation framework**: `{project_root}/.bmad/core/tasks/validate-workflow.xml` 4. **Extract metadata**: epic_num, story_num, story_key, story_title from story file 5. **Resolve all workflow variables**: story_dir, output_folder, epics_file, architecture_file, etc. 6. **Understand current status**: What story implementation guidance is currently provided? diff --git a/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml b/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml index 48e33ffb..8665faec 100644 --- a/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml +++ b/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml @@ -1,5 +1,5 @@ - The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml + 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 all responses in {communication_language} and generate all documents in {document_output_language} @@ -310,7 +310,7 @@ - Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml + Validate against checklist at {installed_path}/checklist.md using .bmad/core/tasks/validate-workflow.xml Save story document unconditionally diff --git a/src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml b/src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml index 66edc1f5..ea0640c4 100644 --- a/src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml +++ b/src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml @@ -3,7 +3,7 @@ description: "Create the next user story from epics+stories with enhanced contex author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,7 +12,7 @@ sprint_artifacts: "{config_source}:sprint_artifacts" story_dir: "{sprint_artifacts}" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/create-story" template: "{installed_path}/template.md" instructions: "{installed_path}/instructions.xml" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml b/src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml index 1043648c..507abceb 100644 --- a/src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml +++ b/src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml @@ -1,5 +1,5 @@ - The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml + 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 all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} diff --git a/src/modules/bmm/workflows/4-implementation/dev-story/workflow.yaml b/src/modules/bmm/workflows/4-implementation/dev-story/workflow.yaml index ffcce684..9c0b00db 100644 --- a/src/modules/bmm/workflows/4-implementation/dev-story/workflow.yaml +++ b/src/modules/bmm/workflows/4-implementation/dev-story/workflow.yaml @@ -3,7 +3,7 @@ description: "Execute a story by implementing tasks/subtasks, writing tests, val author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -13,7 +13,7 @@ story_dir: "{config_source}:sprint_artifacts" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story" instructions: "{installed_path}/instructions.xml" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md b/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md index 4450a1ca..29fa52fb 100644 --- a/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/retrospective/instructions.md @@ -1,7 +1,7 @@ # Retrospective - Epic Completion Review Instructions -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/.bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language} โš ๏ธ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. diff --git a/src/modules/bmm/workflows/4-implementation/retrospective/workflow.yaml b/src/modules/bmm/workflows/4-implementation/retrospective/workflow.yaml index 716bb544..040c83a2 100644 --- a/src/modules/bmm/workflows/4-implementation/retrospective/workflow.yaml +++ b/src/modules/bmm/workflows/4-implementation/retrospective/workflow.yaml @@ -3,7 +3,7 @@ name: "retrospective" description: "Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic" author: "BMad" -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,12 +12,12 @@ document_output_language: "{config_source}:document_output_language" date: system-generated sprint_artifacts: "{config_source}:sprint_artifacts" -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective" template: false instructions: "{installed_path}/instructions.md" required_inputs: - - agent_manifest: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv" + - agent_manifest: "{project-root}/.bmad/_cfg/agent-manifest.csv" # Smart input file references - handles both whole docs and sharded docs # Priority: Whole document first, then sharded version diff --git a/src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md b/src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md index f9439f67..8bae8f67 100644 --- a/src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md @@ -1,7 +1,7 @@ # Sprint Planning - Sprint Status Generator -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/.bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml ## ๐Ÿ“š Document Discovery - Full Epic Loading diff --git a/src/modules/bmm/workflows/4-implementation/sprint-planning/workflow.yaml b/src/modules/bmm/workflows/4-implementation/sprint-planning/workflow.yaml index 3dab49e0..a8b23659 100644 --- a/src/modules/bmm/workflows/4-implementation/sprint-planning/workflow.yaml +++ b/src/modules/bmm/workflows/4-implementation/sprint-planning/workflow.yaml @@ -3,7 +3,7 @@ description: "Generate and manage the sprint status tracking file for Phase 4 im author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -11,7 +11,7 @@ date: system-generated sprint_artifacts: "{config_source}:sprint_artifacts" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/sprint-planning" instructions: "{installed_path}/instructions.md" template: "{installed_path}/sprint-status-template.yaml" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmm/workflows/4-implementation/sprint-status/instructions.md b/src/modules/bmm/workflows/4-implementation/sprint-status/instructions.md index 84a92ea4..cbf3a9f9 100644 --- a/src/modules/bmm/workflows/4-implementation/sprint-status/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/sprint-status/instructions.md @@ -1,7 +1,7 @@ # Sprint Status - Multi-Mode Service -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-status/workflow.yaml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/.bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml Modes: interactive (default), validate, data โš ๏ธ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines. @@ -53,11 +53,9 @@ Run `/bmad:bmm:workflows:sprint-planning` to generate it, then rerun sprint-stat 1. If any story status == in-progress โ†’ recommend `dev-story` for the first in-progress story 2. Else if any story status == review โ†’ recommend `code-review` for the first review story 3. Else if any story status == ready-for-dev โ†’ recommend `dev-story` - 4. Else if any story status == drafted โ†’ recommend `story-ready` - 5. Else if any story status == backlog โ†’ recommend `create-story` - 6. Else if any epic status == backlog โ†’ recommend `epic-tech-context` - 7. Else if retrospectives are optional โ†’ recommend `retrospective` - 8. Else โ†’ All implementation items done; suggest `workflow-status` to plan next phase + 4. Else if any story status == backlog โ†’ recommend `create-story` + 5. Else if retrospectives are optional โ†’ recommend `retrospective` + 6. Else โ†’ All implementation items done; suggest `workflow-status` to plan next phase Store selected recommendation as: next_story_id, next_workflow_id, next_agent (SM/DEV as appropriate) diff --git a/src/modules/bmm/workflows/4-implementation/sprint-status/workflow.yaml b/src/modules/bmm/workflows/4-implementation/sprint-status/workflow.yaml index 45a4d105..acb7a21f 100644 --- a/src/modules/bmm/workflows/4-implementation/sprint-status/workflow.yaml +++ b/src/modules/bmm/workflows/4-implementation/sprint-status/workflow.yaml @@ -4,7 +4,7 @@ description: "Summarize sprint-status.yaml, surface risks, and route to the righ author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -13,7 +13,7 @@ date: system-generated sprint_artifacts: "{config_source}:sprint_artifacts" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-status" +installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/sprint-status" instructions: "{installed_path}/instructions.md" # Inputs diff --git a/src/modules/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml b/src/modules/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml index 25abf76d..2660d8aa 100644 --- a/src/modules/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml +++ b/src/modules/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml @@ -4,7 +4,7 @@ description: "Conversational spec engineering - ask questions, investigate code, author: "BMad" # Config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" sprint_artifacts: "{config_source}:sprint_artifacts" user_name: "{config_source}:user_name" @@ -14,13 +14,13 @@ user_skill_level: "{config_source}:user_skill_level" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/create-tech-spec" +installed_path: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/create-tech-spec" instructions: "{installed_path}/instructions.md" # Related workflows -quick_dev_workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml" -party_mode_exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" -advanced_elicitation: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" +quick_dev_workflow: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml" +party_mode_exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" +advanced_elicitation: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" standalone: true web_bundle: false diff --git a/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml b/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml index 7c2de639..3d076cbd 100644 --- a/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml +++ b/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml @@ -4,7 +4,7 @@ description: "Flexible development - execute tech-specs OR direct instructions w author: "BMad" # Config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" sprint_artifacts: "{config_source}:sprint_artifacts" user_name: "{config_source}:user_name" @@ -16,18 +16,18 @@ date: system-generated project_context: "**/project-context.md" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/quick-dev" +installed_path: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/quick-dev" instructions: "{installed_path}/instructions.md" checklist: "{installed_path}/checklist.md" # Related workflows -create_tech_spec_workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml" -party_mode_exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" -advanced_elicitation: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" +create_tech_spec_workflow: "{project-root}/.bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml" +party_mode_exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" +advanced_elicitation: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" # Routing resources (lazy-loaded) -project_levels: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/project-levels.yaml" -workflow_init: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml" +project_levels: "{project-root}/.bmad/bmm/workflows/workflow-status/project-levels.yaml" +workflow_init: "{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml" standalone: true web_bundle: false diff --git a/src/modules/bmm/workflows/diagrams/create-dataflow/instructions.md b/src/modules/bmm/workflows/diagrams/create-dataflow/instructions.md index e4a3afb8..ca906486 100644 --- a/src/modules/bmm/workflows/diagrams/create-dataflow/instructions.md +++ b/src/modules/bmm/workflows/diagrams/create-dataflow/instructions.md @@ -1,7 +1,7 @@ # Create Data Flow Diagram - Workflow Instructions ```xml -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml +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 This workflow creates data flow diagrams (DFD) in Excalidraw format. diff --git a/src/modules/bmm/workflows/diagrams/create-dataflow/workflow.yaml b/src/modules/bmm/workflows/diagrams/create-dataflow/workflow.yaml index 2532c408..5af3a01c 100644 --- a/src/modules/bmm/workflows/diagrams/create-dataflow/workflow.yaml +++ b/src/modules/bmm/workflows/diagrams/create-dataflow/workflow.yaml @@ -3,18 +3,18 @@ description: "Create data flow diagrams (DFD) in Excalidraw format" author: "BMad" # Config values -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-dataflow" -shared_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/_shared" +installed_path: "{project-root}/.bmad/bmm/workflows/diagrams/create-dataflow" +shared_path: "{project-root}/.bmad/bmm/workflows/diagrams/_shared" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" # Core Excalidraw resources (universal knowledge) -helpers: "{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md" -json_validation: "{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md" +helpers: "{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md" +json_validation: "{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md" # Domain-specific resources (technical diagrams) templates: "{shared_path}/excalidraw-templates.yaml" diff --git a/src/modules/bmm/workflows/diagrams/create-diagram/instructions.md b/src/modules/bmm/workflows/diagrams/create-diagram/instructions.md index e22a55a8..dcdf5d34 100644 --- a/src/modules/bmm/workflows/diagrams/create-diagram/instructions.md +++ b/src/modules/bmm/workflows/diagrams/create-diagram/instructions.md @@ -1,7 +1,7 @@ # Create Diagram - Workflow Instructions ```xml -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml +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 This workflow creates system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format. @@ -134,7 +134,7 @@ - Validate against {{validation}} using {{bmad_folder}}/core/tasks/validate-workflow.xml + Validate against {{validation}} using {.bmad}/core/tasks/validate-workflow.xml diff --git a/src/modules/bmm/workflows/diagrams/create-diagram/workflow.yaml b/src/modules/bmm/workflows/diagrams/create-diagram/workflow.yaml index 8013d85d..c8c9ca06 100644 --- a/src/modules/bmm/workflows/diagrams/create-diagram/workflow.yaml +++ b/src/modules/bmm/workflows/diagrams/create-diagram/workflow.yaml @@ -3,18 +3,18 @@ description: "Create system architecture diagrams, ERDs, UML diagrams, or genera author: "BMad" # Config values -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-diagram" -shared_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/_shared" +installed_path: "{project-root}/.bmad/bmm/workflows/diagrams/create-diagram" +shared_path: "{project-root}/.bmad/bmm/workflows/diagrams/_shared" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" # Core Excalidraw resources (universal knowledge) -helpers: "{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md" -json_validation: "{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md" +helpers: "{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md" +json_validation: "{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md" # Domain-specific resources (technical diagrams) templates: "{shared_path}/excalidraw-templates.yaml" diff --git a/src/modules/bmm/workflows/diagrams/create-flowchart/instructions.md b/src/modules/bmm/workflows/diagrams/create-flowchart/instructions.md index 9cae5bdc..933ad960 100644 --- a/src/modules/bmm/workflows/diagrams/create-flowchart/instructions.md +++ b/src/modules/bmm/workflows/diagrams/create-flowchart/instructions.md @@ -1,7 +1,7 @@ # Create Flowchart - Workflow Instructions ```xml -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml +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 This workflow creates a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows. @@ -234,7 +234,7 @@ - Validate against checklist at {{validation}} using {{bmad_folder}}/core/tasks/validate-workflow.xml + Validate against checklist at {{validation}} using {.bmad}/core/tasks/validate-workflow.xml diff --git a/src/modules/bmm/workflows/diagrams/create-flowchart/workflow.yaml b/src/modules/bmm/workflows/diagrams/create-flowchart/workflow.yaml index 475b2d80..798f1ad9 100644 --- a/src/modules/bmm/workflows/diagrams/create-flowchart/workflow.yaml +++ b/src/modules/bmm/workflows/diagrams/create-flowchart/workflow.yaml @@ -3,18 +3,18 @@ description: "Create a flowchart visualization in Excalidraw format for processe author: "BMad" # Config values -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-flowchart" -shared_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/_shared" +installed_path: "{project-root}/.bmad/bmm/workflows/diagrams/create-flowchart" +shared_path: "{project-root}/.bmad/bmm/workflows/diagrams/_shared" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" # Core Excalidraw resources (universal knowledge) -helpers: "{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md" -json_validation: "{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md" +helpers: "{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md" +json_validation: "{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md" # Domain-specific resources (technical diagrams) templates: "{shared_path}/excalidraw-templates.yaml" diff --git a/src/modules/bmm/workflows/diagrams/create-wireframe/instructions.md b/src/modules/bmm/workflows/diagrams/create-wireframe/instructions.md index 0ff3645e..afc3a03c 100644 --- a/src/modules/bmm/workflows/diagrams/create-wireframe/instructions.md +++ b/src/modules/bmm/workflows/diagrams/create-wireframe/instructions.md @@ -1,7 +1,7 @@ # Create Wireframe - Workflow Instructions ```xml -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml +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 This workflow creates website or app wireframes in Excalidraw format. diff --git a/src/modules/bmm/workflows/diagrams/create-wireframe/workflow.yaml b/src/modules/bmm/workflows/diagrams/create-wireframe/workflow.yaml index a426ec6d..68e12360 100644 --- a/src/modules/bmm/workflows/diagrams/create-wireframe/workflow.yaml +++ b/src/modules/bmm/workflows/diagrams/create-wireframe/workflow.yaml @@ -3,18 +3,18 @@ description: "Create website or app wireframes in Excalidraw format" author: "BMad" # Config values -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-wireframe" -shared_path: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/_shared" +installed_path: "{project-root}/.bmad/bmm/workflows/diagrams/create-wireframe" +shared_path: "{project-root}/.bmad/bmm/workflows/diagrams/_shared" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" # Core Excalidraw resources (universal knowledge) -helpers: "{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md" -json_validation: "{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md" +helpers: "{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md" +json_validation: "{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md" # Domain-specific resources (technical diagrams) templates: "{shared_path}/excalidraw-templates.yaml" diff --git a/src/modules/bmm/workflows/document-project/instructions.md b/src/modules/bmm/workflows/document-project/instructions.md index 526a462b..591155a1 100644 --- a/src/modules/bmm/workflows/document-project/instructions.md +++ b/src/modules/bmm/workflows/document-project/instructions.md @@ -1,7 +1,7 @@ # Document Project Workflow Router -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/.bmad/bmm/workflows/document-project/workflow.yaml Communicate all responses in {communication_language} @@ -10,7 +10,7 @@ - + mode: data data_request: project_config @@ -36,7 +36,7 @@ - + mode: validate calling_workflow: document-project @@ -179,7 +179,7 @@ Your choice [1/2/3]: - + mode: update action: complete_workflow workflow_name: document-project diff --git a/src/modules/bmm/workflows/document-project/workflow.yaml b/src/modules/bmm/workflows/document-project/workflow.yaml index 7249d969..76f871dd 100644 --- a/src/modules/bmm/workflows/document-project/workflow.yaml +++ b/src/modules/bmm/workflows/document-project/workflow.yaml @@ -5,7 +5,7 @@ description: "Analyzes and documents brownfield projects by scanning codebase, a author: "BMad" # Critical variables -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -14,7 +14,7 @@ user_skill_level: "{config_source}:user_skill_level" date: system-generated # Module path and component files -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/document-project" +installed_path: "{project-root}/.bmad/bmm/workflows/document-project" template: false # This is an action workflow with multiple output files instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmm/workflows/document-project/workflows/deep-dive.yaml b/src/modules/bmm/workflows/document-project/workflows/deep-dive.yaml index e3421dd2..c9d8945f 100644 --- a/src/modules/bmm/workflows/document-project/workflows/deep-dive.yaml +++ b/src/modules/bmm/workflows/document-project/workflows/deep-dive.yaml @@ -4,22 +4,22 @@ description: "Exhaustive deep-dive documentation of specific project areas" author: "BMad" # This is a sub-workflow called by document-project/workflow.yaml -parent_workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml" +parent_workflow: "{project-root}/.bmad/bmm/workflows/document-project/workflow.yaml" # Critical variables inherited from parent -config_source: "{project-root}/{bmad_folder}/bmb/config.yaml" +config_source: "{project-root}/.bmad/bmb/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" date: system-generated # Module path and component files -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflows" +installed_path: "{project-root}/.bmad/bmm/workflows/document-project/workflows" template: false # Action workflow instructions: "{installed_path}/deep-dive-instructions.md" -validation: "{project-root}/{bmad_folder}/bmm/workflows/document-project/checklist.md" +validation: "{project-root}/.bmad/bmm/workflows/document-project/checklist.md" # Templates -deep_dive_template: "{project-root}/{bmad_folder}/bmm/workflows/document-project/templates/deep-dive-template.md" +deep_dive_template: "{project-root}/.bmad/bmm/workflows/document-project/templates/deep-dive-template.md" # Runtime inputs (passed from parent workflow) workflow_mode: "deep_dive" diff --git a/src/modules/bmm/workflows/document-project/workflows/full-scan.yaml b/src/modules/bmm/workflows/document-project/workflows/full-scan.yaml index 34a4d7f5..61c22feb 100644 --- a/src/modules/bmm/workflows/document-project/workflows/full-scan.yaml +++ b/src/modules/bmm/workflows/document-project/workflows/full-scan.yaml @@ -4,22 +4,22 @@ description: "Complete project documentation workflow (initial scan or full resc author: "BMad" # This is a sub-workflow called by document-project/workflow.yaml -parent_workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml" +parent_workflow: "{project-root}/.bmad/bmm/workflows/document-project/workflow.yaml" # Critical variables inherited from parent -config_source: "{project-root}/{bmad_folder}/bmb/config.yaml" +config_source: "{project-root}/.bmad/bmb/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" date: system-generated # Data files -documentation_requirements_csv: "{project-root}/{bmad_folder}/bmm/workflows/document-project/documentation-requirements.csv" +documentation_requirements_csv: "{project-root}/.bmad/bmm/workflows/document-project/documentation-requirements.csv" # Module path and component files -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflows" +installed_path: "{project-root}/.bmad/bmm/workflows/document-project/workflows" template: false # Action workflow instructions: "{installed_path}/full-scan-instructions.md" -validation: "{project-root}/{bmad_folder}/bmm/workflows/document-project/checklist.md" +validation: "{project-root}/.bmad/bmm/workflows/document-project/checklist.md" # Runtime inputs (passed from parent workflow) workflow_mode: "" # "initial_scan" or "full_rescan" diff --git a/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md b/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md index 84439c17..12fbc768 100644 --- a/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md +++ b/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md @@ -28,8 +28,8 @@ This step will generate content and present choices for each rule category: ## PROTOCOL INTEGRATION: -- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml -- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode +- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml +- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed - User accepts/rejects protocol changes before proceeding diff --git a/src/modules/bmm/workflows/generate-project-context/workflow.md b/src/modules/bmm/workflows/generate-project-context/workflow.md index 934ebff9..80638d07 100644 --- a/src/modules/bmm/workflows/generate-project-context/workflow.md +++ b/src/modules/bmm/workflows/generate-project-context/workflow.md @@ -27,7 +27,7 @@ This uses **micro-file architecture** for disciplined execution: ### Configuration Loading -Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve: +Load config from `{project-root}/.bmad/bmm/config.yaml` and resolve: - `project_name`, `output_folder`, `user_name` - `communication_language`, `document_output_language`, `user_skill_level` @@ -35,7 +35,7 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve: ### Paths -- `installed_path` = `{project-root}/{bmad_folder}/bmm/workflows/generate-project-context` +- `installed_path` = `{project-root}/.bmad/bmm/workflows/generate-project-context` - `template_path` = `{installed_path}/project-context-template.md` - `output_file` = `{output_folder}/project_context.md` diff --git a/src/modules/bmm/workflows/testarch/atdd/instructions.md b/src/modules/bmm/workflows/testarch/atdd/instructions.md index 82068208..a2f81a6b 100644 --- a/src/modules/bmm/workflows/testarch/atdd/instructions.md +++ b/src/modules/bmm/workflows/testarch/atdd/instructions.md @@ -2,7 +2,7 @@ # Acceptance Test-Driven Development (ATDD) -**Workflow ID**: `{bmad_folder}/bmm/testarch/atdd` +**Workflow ID**: `.bmad/bmm/testarch/atdd` **Version**: 4.0 (BMad v6) --- @@ -54,7 +54,7 @@ Generates failing acceptance tests BEFORE implementation following TDD's red-gre 5. **Load Knowledge Base Fragments** - **Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load: + **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load: **Core Patterns (Always load):** - `data-factories.md` - Factory patterns using faker (override patterns, nested factories, API seeding, 498 lines, 5 examples) diff --git a/src/modules/bmm/workflows/testarch/atdd/workflow.yaml b/src/modules/bmm/workflows/testarch/atdd/workflow.yaml index 4e6991f2..c084ec4e 100644 --- a/src/modules/bmm/workflows/testarch/atdd/workflow.yaml +++ b/src/modules/bmm/workflows/testarch/atdd/workflow.yaml @@ -4,7 +4,7 @@ description: "Generate failing acceptance tests before implementation using TDD author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/atdd" +installed_path: "{project-root}/.bmad/bmm/workflows/testarch/atdd" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" template: "{installed_path}/atdd-checklist-template.md" diff --git a/src/modules/bmm/workflows/testarch/automate/instructions.md b/src/modules/bmm/workflows/testarch/automate/instructions.md index 55dcebe7..3f494949 100644 --- a/src/modules/bmm/workflows/testarch/automate/instructions.md +++ b/src/modules/bmm/workflows/testarch/automate/instructions.md @@ -2,7 +2,7 @@ # Test Automation Expansion -**Workflow ID**: `{bmad_folder}/bmm/testarch/automate` +**Workflow ID**: `.bmad/bmm/testarch/automate` **Version**: 4.0 (BMad v6) --- @@ -87,7 +87,7 @@ Expands test automation coverage by generating comprehensive test suites at appr 6. **Load Knowledge Base Fragments** - **Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load: + **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load: **Core Testing Patterns (Always load):** - `test-levels-framework.md` - Test level selection (E2E vs API vs Component vs Unit with decision matrix, 467 lines, 4 examples) diff --git a/src/modules/bmm/workflows/testarch/automate/workflow.yaml b/src/modules/bmm/workflows/testarch/automate/workflow.yaml index c2704542..27925a70 100644 --- a/src/modules/bmm/workflows/testarch/automate/workflow.yaml +++ b/src/modules/bmm/workflows/testarch/automate/workflow.yaml @@ -4,7 +4,7 @@ description: "Expand test automation coverage after implementation or analyze ex author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/automate" +installed_path: "{project-root}/.bmad/bmm/workflows/testarch/automate" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" template: false diff --git a/src/modules/bmm/workflows/testarch/ci/instructions.md b/src/modules/bmm/workflows/testarch/ci/instructions.md index 9241e93c..2504b933 100644 --- a/src/modules/bmm/workflows/testarch/ci/instructions.md +++ b/src/modules/bmm/workflows/testarch/ci/instructions.md @@ -2,7 +2,7 @@ # CI/CD Pipeline Setup -**Workflow ID**: `{bmad_folder}/bmm/testarch/ci` +**Workflow ID**: `.bmad/bmm/testarch/ci` **Version**: 4.0 (BMad v6) --- diff --git a/src/modules/bmm/workflows/testarch/ci/workflow.yaml b/src/modules/bmm/workflows/testarch/ci/workflow.yaml index 03b09493..cd173c6f 100644 --- a/src/modules/bmm/workflows/testarch/ci/workflow.yaml +++ b/src/modules/bmm/workflows/testarch/ci/workflow.yaml @@ -4,7 +4,7 @@ description: "Scaffold CI/CD quality pipeline with test execution, burn-in loops author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/ci" +installed_path: "{project-root}/.bmad/bmm/workflows/testarch/ci" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmm/workflows/testarch/framework/instructions.md b/src/modules/bmm/workflows/testarch/framework/instructions.md index 9f02d69c..b3459c5d 100644 --- a/src/modules/bmm/workflows/testarch/framework/instructions.md +++ b/src/modules/bmm/workflows/testarch/framework/instructions.md @@ -2,7 +2,7 @@ # Test Framework Setup -**Workflow ID**: `{bmad_folder}/bmm/testarch/framework` +**Workflow ID**: `.bmad/bmm/testarch/framework` **Version**: 4.0 (BMad v6) --- @@ -355,7 +355,7 @@ Read `{config_source}` and check `config.tea_use_playwright_utils`. **If `config.tea_use_playwright_utils: true` (Playwright Utils Integration):** -Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` and load: +Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` and load: - `overview.md` - Playwright utils installation and design principles - `fixtures-composition.md` - mergeTests composition with playwright-utils @@ -375,7 +375,7 @@ Recommend adding burn-in and network-error-monitor to merged fixtures for enhanc **If `config.tea_use_playwright_utils: false` (Traditional Patterns):** -Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` and load: +Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` and load: - `fixture-architecture.md` - Pure function โ†’ fixture โ†’ `mergeTests` composition with auto-cleanup (406 lines, 5 examples) - `data-factories.md` - Faker-based factories with overrides, nested factories, API seeding, auto-cleanup (498 lines, 5 examples) diff --git a/src/modules/bmm/workflows/testarch/framework/workflow.yaml b/src/modules/bmm/workflows/testarch/framework/workflow.yaml index 3ccefdfa..da9f9fa0 100644 --- a/src/modules/bmm/workflows/testarch/framework/workflow.yaml +++ b/src/modules/bmm/workflows/testarch/framework/workflow.yaml @@ -4,7 +4,7 @@ description: "Initialize production-ready test framework architecture (Playwrigh author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/framework" +installed_path: "{project-root}/.bmad/bmm/workflows/testarch/framework" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" diff --git a/src/modules/bmm/workflows/testarch/nfr-assess/instructions.md b/src/modules/bmm/workflows/testarch/nfr-assess/instructions.md index a7c40e49..66d89c56 100644 --- a/src/modules/bmm/workflows/testarch/nfr-assess/instructions.md +++ b/src/modules/bmm/workflows/testarch/nfr-assess/instructions.md @@ -50,7 +50,7 @@ This workflow performs a comprehensive assessment of non-functional requirements **Actions:** -1. Load relevant knowledge fragments from `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv`: +1. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`: - `nfr-criteria.md` - Non-functional requirements criteria and thresholds (security, performance, reliability, maintainability with code examples, 658 lines, 4 examples) - `ci-burn-in.md` - CI/CD burn-in patterns for reliability validation (10-iteration detection, sharding, selective execution, 678 lines, 4 examples) - `test-quality.md` - Test quality expectations for maintainability (deterministic, isolated, explicit assertions, length/time limits, 658 lines, 5 examples) diff --git a/src/modules/bmm/workflows/testarch/nfr-assess/workflow.yaml b/src/modules/bmm/workflows/testarch/nfr-assess/workflow.yaml index 66754945..db71579e 100644 --- a/src/modules/bmm/workflows/testarch/nfr-assess/workflow.yaml +++ b/src/modules/bmm/workflows/testarch/nfr-assess/workflow.yaml @@ -4,7 +4,7 @@ description: "Assess non-functional requirements (performance, security, reliabi author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/nfr-assess" +installed_path: "{project-root}/.bmad/bmm/workflows/testarch/nfr-assess" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" template: "{installed_path}/nfr-report-template.md" diff --git a/src/modules/bmm/workflows/testarch/test-design/instructions.md b/src/modules/bmm/workflows/testarch/test-design/instructions.md index c96bf876..37bf4135 100644 --- a/src/modules/bmm/workflows/testarch/test-design/instructions.md +++ b/src/modules/bmm/workflows/testarch/test-design/instructions.md @@ -2,7 +2,7 @@ # Test Design and Risk Assessment -**Workflow ID**: `{bmad_folder}/bmm/testarch/test-design` +**Workflow ID**: `.bmad/bmm/testarch/test-design` **Version**: 4.0 (BMad v6) --- @@ -74,7 +74,7 @@ The workflow auto-detects which mode to use based on project phase. 3. **Load Knowledge Base Fragments (System-Level)** - **Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load: + **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load: - `nfr-criteria.md` - NFR validation approach (security, performance, reliability, maintainability) - `test-levels-framework.md` - Test levels strategy guidance - `risk-governance.md` - Testability risk identification @@ -108,7 +108,7 @@ The workflow auto-detects which mode to use based on project phase. 4. **Load Knowledge Base Fragments (Epic-Level)** - **Critical:** Consult `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv` to load: + **Critical:** Consult `{project-root}/.bmad/bmm/testarch/tea-index.csv` to load: - `risk-governance.md` - Risk classification framework (6 categories: TECH, SEC, PERF, DATA, BUS, OPS), automated scoring, gate decision engine, owner tracking (625 lines, 4 examples) - `probability-impact.md` - Risk scoring methodology (probability ร— impact matrix, automated classification, dynamic re-assessment, gate integration, 604 lines, 4 examples) - `test-levels-framework.md` - Test level selection guidance (E2E vs API vs Component vs Unit with decision matrix, characteristics, when to use each, 467 lines, 4 examples) diff --git a/src/modules/bmm/workflows/testarch/test-design/test-design-template.md b/src/modules/bmm/workflows/testarch/test-design/test-design-template.md index 0ed1c646..188530b5 100644 --- a/src/modules/bmm/workflows/testarch/test-design/test-design-template.md +++ b/src/modules/bmm/workflows/testarch/test-design/test-design-template.md @@ -281,5 +281,5 @@ --- **Generated by**: BMad TEA Agent - Test Architect Module -**Workflow**: `{bmad_folder}/bmm/testarch/test-design` +**Workflow**: `.bmad/bmm/testarch/test-design` **Version**: 4.0 (BMad v6) diff --git a/src/modules/bmm/workflows/testarch/test-design/workflow.yaml b/src/modules/bmm/workflows/testarch/test-design/workflow.yaml index 2915ae40..9a1042c1 100644 --- a/src/modules/bmm/workflows/testarch/test-design/workflow.yaml +++ b/src/modules/bmm/workflows/testarch/test-design/workflow.yaml @@ -4,7 +4,7 @@ description: "Dual-mode workflow: (1) System-level testability review in Solutio author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-design" +installed_path: "{project-root}/.bmad/bmm/workflows/testarch/test-design" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" template: "{installed_path}/test-design-template.md" diff --git a/src/modules/bmm/workflows/testarch/test-review/instructions.md b/src/modules/bmm/workflows/testarch/test-review/instructions.md index a0f49b57..c308db79 100644 --- a/src/modules/bmm/workflows/testarch/test-review/instructions.md +++ b/src/modules/bmm/workflows/testarch/test-review/instructions.md @@ -52,7 +52,7 @@ This workflow performs comprehensive test quality reviews using TEA's knowledge 1. Check playwright-utils flag: - Read `{config_source}` and check `config.tea_use_playwright_utils` -2. Load relevant knowledge fragments from `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv`: +2. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`: **Core Patterns (Always load):** - `test-quality.md` - Definition of Done (deterministic tests, isolated with cleanup, explicit assertions, <300 lines, <1.5 min, 658 lines, 5 examples) diff --git a/src/modules/bmm/workflows/testarch/test-review/workflow.yaml b/src/modules/bmm/workflows/testarch/test-review/workflow.yaml index 86a8b297..d44f8302 100644 --- a/src/modules/bmm/workflows/testarch/test-review/workflow.yaml +++ b/src/modules/bmm/workflows/testarch/test-review/workflow.yaml @@ -4,7 +4,7 @@ description: "Review test quality using comprehensive knowledge base and best pr author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/test-review" +installed_path: "{project-root}/.bmad/bmm/workflows/testarch/test-review" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" template: "{installed_path}/test-review-template.md" diff --git a/src/modules/bmm/workflows/testarch/trace/instructions.md b/src/modules/bmm/workflows/testarch/trace/instructions.md index e3511841..645fa65c 100644 --- a/src/modules/bmm/workflows/testarch/trace/instructions.md +++ b/src/modules/bmm/workflows/testarch/trace/instructions.md @@ -64,7 +64,7 @@ This phase focuses on mapping requirements to tests, analyzing coverage, and ide **Actions:** -1. Load relevant knowledge fragments from `{project-root}/{bmad_folder}/bmm/testarch/tea-index.csv`: +1. Load relevant knowledge fragments from `{project-root}/.bmad/bmm/testarch/tea-index.csv`: - `test-priorities-matrix.md` - P0/P1/P2/P3 risk framework with automated priority calculation, risk-based mapping, tagging strategy (389 lines, 2 examples) - `risk-governance.md` - Risk-based testing approach: 6 categories (TECH, SEC, PERF, DATA, BUS, OPS), automated scoring, gate decision engine, coverage traceability (625 lines, 4 examples) - `probability-impact.md` - Risk scoring methodology: probability ร— impact matrix, automated classification, dynamic re-assessment, gate integration (604 lines, 4 examples) @@ -476,10 +476,10 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE ## References -- Traceability Matrix: `{bmad_folder}/output/traceability-matrix.md` -- Test Design: `{bmad_folder}/output/test-design-epic-2.md` +- Traceability Matrix: `.bmad/output/traceability-matrix.md` +- Test Design: `.bmad/output/test-design-epic-2.md` - Test Results: `ci-artifacts/test-report-2025-01-15.xml` -- NFR Assessment: `{bmad_folder}/output/nfr-assessment-release-1.2.md` +- NFR Assessment: `.bmad/output/nfr-assessment-release-1.2.md` ``` 3. **Include evidence links** (if `require_evidence: true`): @@ -515,7 +515,7 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE - **Decision**: CONCERNS - **Reason**: P1 coverage 88% (below 90%) - - **Document**: [gate-decision-story-1.3.md]({bmad_folder}/output/gate-decision-story-1.3.md) + - **Document**: [gate-decision-story-1.3.md](.bmad/output/gate-decision-story-1.3.md) - **Action**: Deploy with follow-up story for AC-5 ``` @@ -536,7 +536,7 @@ This phase uses traceability results to make a quality gate decision (PASS/CONCE - Create follow-up story for AC-5 E2E test - Deploy to staging for validation - Full Report: {bmad_folder}/output/gate-decision-story-1.3.md + Full Report: .bmad/output/gate-decision-story-1.3.md ``` 3. **Request sign-off** (if `require_sign_off: true`): diff --git a/src/modules/bmm/workflows/testarch/trace/workflow.yaml b/src/modules/bmm/workflows/testarch/trace/workflow.yaml index cbd35e0c..41eb0e5f 100644 --- a/src/modules/bmm/workflows/testarch/trace/workflow.yaml +++ b/src/modules/bmm/workflows/testarch/trace/workflow.yaml @@ -4,7 +4,7 @@ description: "Generate requirements-to-tests traceability matrix, analyze covera author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -12,7 +12,7 @@ document_output_language: "{config_source}:document_output_language" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/testarch/trace" +installed_path: "{project-root}/.bmad/bmm/workflows/testarch/trace" instructions: "{installed_path}/instructions.md" validation: "{installed_path}/checklist.md" template: "{installed_path}/trace-template.md" diff --git a/src/modules/bmm/workflows/workflow-status/init/instructions.md b/src/modules/bmm/workflows/workflow-status/init/instructions.md index 2519fe14..92f63e45 100644 --- a/src/modules/bmm/workflows/workflow-status/init/instructions.md +++ b/src/modules/bmm/workflows/workflow-status/init/instructions.md @@ -1,6 +1,6 @@ # Workflow Init - Project Setup Instructions -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml You MUST have already loaded and processed: workflow-init/workflow.yaml Communicate in {communication_language} with {user_name} This workflow handles BOTH new projects AND legacy projects following the BMad Method diff --git a/src/modules/bmm/workflows/workflow-status/init/workflow.yaml b/src/modules/bmm/workflows/workflow-status/init/workflow.yaml index 13073936..19204b88 100644 --- a/src/modules/bmm/workflows/workflow-status/init/workflow.yaml +++ b/src/modules/bmm/workflows/workflow-status/init/workflow.yaml @@ -4,7 +4,7 @@ description: "Initialize a new BMM project by determining level, type, and creat author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" sprint_artifacts: "{config_source}:sprint_artifacts" user_name: "{config_source}:user_name" @@ -15,12 +15,12 @@ user_skill_level: "{config_source}:user_skill_level" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init" +installed_path: "{project-root}/.bmad/bmm/workflows/workflow-status/init" instructions: "{installed_path}/instructions.md" -template: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow-status-template.yaml" +template: "{project-root}/.bmad/bmm/workflows/workflow-status/workflow-status-template.yaml" # Path data files -path_files: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/paths/" +path_files: "{project-root}/.bmad/bmm/workflows/workflow-status/paths/" # Output configuration default_output_file: "{output_folder}/bmm-workflow-status.yaml" diff --git a/src/modules/bmm/workflows/workflow-status/instructions.md b/src/modules/bmm/workflows/workflow-status/instructions.md index 6ef9bd78..93d04302 100644 --- a/src/modules/bmm/workflows/workflow-status/instructions.md +++ b/src/modules/bmm/workflows/workflow-status/instructions.md @@ -1,7 +1,7 @@ # Workflow Status Check - Multi-Mode Service -The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml +The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml This workflow operates in multiple modes: interactive (default), validate, data, init-check, update Other workflows can call this as a service to avoid duplicating status logic โš ๏ธ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. @@ -42,7 +42,7 @@ Launching workflow-init to set up your project tracking... - + Exit workflow and let workflow-init take over diff --git a/src/modules/bmm/workflows/workflow-status/project-levels.yaml b/src/modules/bmm/workflows/workflow-status/project-levels.yaml index 1456d79f..f47f7f44 100644 --- a/src/modules/bmm/workflows/workflow-status/project-levels.yaml +++ b/src/modules/bmm/workflows/workflow-status/project-levels.yaml @@ -1,5 +1,5 @@ # BMM Project Scale Levels - Source of Truth -# Reference: /{bmad_folder}/bmm/README.md lines 77-85 +# Reference: /.bmad/bmm/README.md lines 77-85 levels: 0: diff --git a/src/modules/bmm/workflows/workflow-status/workflow.yaml b/src/modules/bmm/workflows/workflow-status/workflow.yaml index 761d41c0..c2576104 100644 --- a/src/modules/bmm/workflows/workflow-status/workflow.yaml +++ b/src/modules/bmm/workflows/workflow-status/workflow.yaml @@ -4,7 +4,7 @@ description: 'Lightweight status checker - answers "what should I do now?" for a author: "BMad" # Critical variables from config -config_source: "{project-root}/{bmad_folder}/bmm/config.yaml" +config_source: "{project-root}/.bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -13,7 +13,7 @@ user_skill_level: "{config_source}:user_skill_level" date: system-generated # Workflow components -installed_path: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status" +installed_path: "{project-root}/.bmad/bmm/workflows/workflow-status" instructions: "{installed_path}/instructions.md" # Template for status file creation (used by workflow-init) diff --git a/src/modules/cis/agents/README.md b/src/modules/cis/agents/README.md index 4df34e79..bf9edf91 100644 --- a/src/modules/cis/agents/README.md +++ b/src/modules/cis/agents/README.md @@ -96,7 +96,7 @@ Every CIS agent includes: ## Configuration -All agents load configuration from `/{bmad_folder}/cis/config.yaml`: +All agents load configuration from `/.bmad/cis/config.yaml`: - `project_name` - Project identification - `output_folder` - Where workflow results are saved diff --git a/src/modules/cis/agents/brainstorming-coach.agent.yaml b/src/modules/cis/agents/brainstorming-coach.agent.yaml index aeb9001c..3c7bde5f 100644 --- a/src/modules/cis/agents/brainstorming-coach.agent.yaml +++ b/src/modules/cis/agents/brainstorming-coach.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/cis/agents/brainstorming-coach.md" + id: ".bmad/cis/agents/brainstorming-coach.md" name: Carson title: Elite Brainstorming Specialist icon: ๐Ÿง  @@ -16,14 +16,14 @@ agent: menu: - trigger: brainstorm - workflow: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml" + workflow: "{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml" description: Guide me through Brainstorming any topic - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Consult with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/cis/agents/creative-problem-solver.agent.yaml b/src/modules/cis/agents/creative-problem-solver.agent.yaml index 832e4c9e..ac886ebd 100644 --- a/src/modules/cis/agents/creative-problem-solver.agent.yaml +++ b/src/modules/cis/agents/creative-problem-solver.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/cis/agents/creative-problem-solver.md" + id: ".bmad/cis/agents/creative-problem-solver.md" name: Dr. Quinn title: Master Problem Solver icon: ๐Ÿ”ฌ @@ -16,14 +16,14 @@ agent: menu: - trigger: solve - workflow: "{project-root}/{bmad_folder}/cis/workflows/problem-solving/workflow.yaml" + workflow: "{project-root}/.bmad/cis/workflows/problem-solving/workflow.yaml" description: Apply systematic problem-solving methodologies - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Consult with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/cis/agents/design-thinking-coach.agent.yaml b/src/modules/cis/agents/design-thinking-coach.agent.yaml index 05199ff2..b81e4b8c 100644 --- a/src/modules/cis/agents/design-thinking-coach.agent.yaml +++ b/src/modules/cis/agents/design-thinking-coach.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/cis/agents/design-thinking-coach.md" + id: ".bmad/cis/agents/design-thinking-coach.md" name: Maya title: Design Thinking Maestro icon: ๐ŸŽจ @@ -16,14 +16,14 @@ agent: menu: - trigger: design - workflow: "{project-root}/{bmad_folder}/cis/workflows/design-thinking/workflow.yaml" + workflow: "{project-root}/.bmad/cis/workflows/design-thinking/workflow.yaml" description: Guide human-centered design process - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Consult with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/cis/agents/innovation-strategist.agent.yaml b/src/modules/cis/agents/innovation-strategist.agent.yaml index babfb8ce..ccb94bba 100644 --- a/src/modules/cis/agents/innovation-strategist.agent.yaml +++ b/src/modules/cis/agents/innovation-strategist.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/cis/agents/innovation-strategist.md" + id: ".bmad/cis/agents/innovation-strategist.md" name: Victor title: Disruptive Innovation Oracle icon: โšก @@ -16,14 +16,14 @@ agent: menu: - trigger: innovate - workflow: "{project-root}/{bmad_folder}/cis/workflows/innovation-strategy/workflow.yaml" + workflow: "{project-root}/.bmad/cis/workflows/innovation-strategy/workflow.yaml" description: Identify disruption opportunities and business model innovation - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Consult with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/cis/agents/presentation-master.agent.yaml b/src/modules/cis/agents/presentation-master.agent.yaml index fef9b701..e879d81a 100644 --- a/src/modules/cis/agents/presentation-master.agent.yaml +++ b/src/modules/cis/agents/presentation-master.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/cis/agents/presentation-master.md" + id: ".bmad/cis/agents/presentation-master.md" name: Caravaggio title: Visual Communication + Presentation Expert icon: ๐ŸŽจ @@ -52,10 +52,10 @@ agent: description: Generate single expressive image that explains ideas creatively and memorably - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Consult with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/cis/agents/storyteller.agent.yaml b/src/modules/cis/agents/storyteller.agent.yaml index cffc28a0..a479839b 100644 --- a/src/modules/cis/agents/storyteller.agent.yaml +++ b/src/modules/cis/agents/storyteller.agent.yaml @@ -2,7 +2,7 @@ agent: metadata: - id: "{bmad_folder}/cis/agents/storyteller.md" + id: ".bmad/cis/agents/storyteller.md" name: Sophia title: Master Storyteller icon: ๐Ÿ“– @@ -16,14 +16,14 @@ agent: menu: - trigger: story - exec: "{project-root}/{bmad_folder}/cis/workflows/storytelling/workflow.yaml" + exec: "{project-root}/.bmad/cis/workflows/storytelling/workflow.yaml" description: Craft compelling narrative using proven frameworks - trigger: party-mode - exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" + exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md" description: Consult with other expert agents from the party - trigger: advanced-elicitation - exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" + exec: "{project-root}/.bmad/core/tasks/advanced-elicitation.xml" description: Advanced elicitation techniques to challenge the LLM to get better results web-only: true diff --git a/src/modules/cis/module.yaml b/src/modules/cis/module.yaml index 7e3fc888..cd4cdfb2 100644 --- a/src/modules/cis/module.yaml +++ b/src/modules/cis/module.yaml @@ -10,7 +10,6 @@ subheader: "No Configuration needed - uses Core Config only." ## user_name ## communication_language ## output_folder -## bmad_folder ## install_user_docs ## kb_install diff --git a/src/modules/cis/readme.md b/src/modules/cis/readme.md index 03e50244..3316e74f 100644 --- a/src/modules/cis/readme.md +++ b/src/modules/cis/readme.md @@ -103,7 +103,7 @@ agent cis/brainstorming-coach ## Configuration -Edit `/{bmad_folder}/cis/config.yaml`: +Edit `/.bmad/cis/config.yaml`: ```yaml output_folder: ./creative-outputs diff --git a/src/modules/cis/workflows/README.md b/src/modules/cis/workflows/README.md index 4056c7ef..f500ec5e 100644 --- a/src/modules/cis/workflows/README.md +++ b/src/modules/cis/workflows/README.md @@ -98,7 +98,7 @@ agent cis/brainstorming-coach ## Configuration -Edit `/{bmad_folder}/cis/config.yaml`: +Edit `/.bmad/cis/config.yaml`: | Setting | Purpose | Default | | ---------------------- | ----------------------- | ------------------ | diff --git a/src/modules/cis/workflows/design-thinking/instructions.md b/src/modules/cis/workflows/design-thinking/instructions.md index 2a95f5df..a42afd72 100644 --- a/src/modules/cis/workflows/design-thinking/instructions.md +++ b/src/modules/cis/workflows/design-thinking/instructions.md @@ -1,7 +1,7 @@ # Design Thinking Workflow Instructions -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/design-thinking/workflow.yaml +The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project_root}/.bmad/cis/workflows/design-thinking/workflow.yaml Load and understand design methods from: {design_methods} โš ๏ธ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. โš ๏ธ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately โ†’ SHOW checkpoint separator (โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”) โ†’ DISPLAY generated content โ†’ PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO โ†’ WAIT for user response. Never batch saves or skip checkpoints. diff --git a/src/modules/cis/workflows/design-thinking/workflow.yaml b/src/modules/cis/workflows/design-thinking/workflow.yaml index 5befcde1..26c90f4d 100644 --- a/src/modules/cis/workflows/design-thinking/workflow.yaml +++ b/src/modules/cis/workflows/design-thinking/workflow.yaml @@ -4,7 +4,7 @@ description: "Guide human-centered design processes using empathy-driven methodo author: "BMad" # Critical variables load from config_source -config_source: "{project-root}/{bmad_folder}/cis/config.yaml" +config_source: "{project-root}/.bmad/cis/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -14,7 +14,7 @@ date: system-generated # Example: data="{path}/product-context.md" provides project context # Module path and component files -installed_path: "{project-root}/{bmad_folder}/cis/workflows/design-thinking" +installed_path: "{project-root}/.bmad/cis/workflows/design-thinking" template: "{installed_path}/template.md" instructions: "{installed_path}/instructions.md" @@ -30,9 +30,9 @@ 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." author: "BMad" - instructions: "{bmad_folder}/cis/workflows/design-thinking/instructions.md" - template: "{bmad_folder}/cis/workflows/design-thinking/template.md" + instructions: ".bmad/cis/workflows/design-thinking/instructions.md" + template: ".bmad/cis/workflows/design-thinking/template.md" web_bundle_files: - - "{bmad_folder}/cis/workflows/design-thinking/instructions.md" - - "{bmad_folder}/cis/workflows/design-thinking/template.md" - - "{bmad_folder}/cis/workflows/design-thinking/design-methods.csv" + - ".bmad/cis/workflows/design-thinking/instructions.md" + - ".bmad/cis/workflows/design-thinking/template.md" + - ".bmad/cis/workflows/design-thinking/design-methods.csv" diff --git a/src/modules/cis/workflows/innovation-strategy/instructions.md b/src/modules/cis/workflows/innovation-strategy/instructions.md index 70318707..64e591c1 100644 --- a/src/modules/cis/workflows/innovation-strategy/instructions.md +++ b/src/modules/cis/workflows/innovation-strategy/instructions.md @@ -1,7 +1,7 @@ # Innovation Strategy Workflow Instructions -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/innovation-strategy/workflow.yaml +The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project_root}/.bmad/cis/workflows/innovation-strategy/workflow.yaml Load and understand innovation frameworks from: {innovation_frameworks} โš ๏ธ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. โš ๏ธ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately โ†’ SHOW checkpoint separator (โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”) โ†’ DISPLAY generated content โ†’ PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO โ†’ WAIT for user response. Never batch saves or skip checkpoints. diff --git a/src/modules/cis/workflows/innovation-strategy/workflow.yaml b/src/modules/cis/workflows/innovation-strategy/workflow.yaml index 5cd86b87..70651aa5 100644 --- a/src/modules/cis/workflows/innovation-strategy/workflow.yaml +++ b/src/modules/cis/workflows/innovation-strategy/workflow.yaml @@ -4,7 +4,7 @@ description: "Identify disruption opportunities and architect business model inn author: "BMad" # Critical variables load from config_source -config_source: "{project-root}/{bmad_folder}/cis/config.yaml" +config_source: "{project-root}/.bmad/cis/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -14,7 +14,7 @@ date: system-generated # Example: data="{path}/industry-analysis.md" provides market context # Module path and component files -installed_path: "{project-root}/{bmad_folder}/cis/workflows/innovation-strategy" +installed_path: "{project-root}/.bmad/cis/workflows/innovation-strategy" template: "{installed_path}/template.md" instructions: "{installed_path}/instructions.md" @@ -30,9 +30,9 @@ 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." author: "BMad" - instructions: "{bmad_folder}/cis/workflows/innovation-strategy/instructions.md" - template: "{bmad_folder}/cis/workflows/innovation-strategy/template.md" + instructions: ".bmad/cis/workflows/innovation-strategy/instructions.md" + template: ".bmad/cis/workflows/innovation-strategy/template.md" web_bundle_files: - - "{bmad_folder}/cis/workflows/innovation-strategy/instructions.md" - - "{bmad_folder}/cis/workflows/innovation-strategy/template.md" - - "{bmad_folder}/cis/workflows/innovation-strategy/innovation-frameworks.csv" + - ".bmad/cis/workflows/innovation-strategy/instructions.md" + - ".bmad/cis/workflows/innovation-strategy/template.md" + - ".bmad/cis/workflows/innovation-strategy/innovation-frameworks.csv" diff --git a/src/modules/cis/workflows/problem-solving/instructions.md b/src/modules/cis/workflows/problem-solving/instructions.md index a8a7af2f..5f2c3fdd 100644 --- a/src/modules/cis/workflows/problem-solving/instructions.md +++ b/src/modules/cis/workflows/problem-solving/instructions.md @@ -1,7 +1,7 @@ # Problem Solving Workflow Instructions -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/problem-solving/workflow.yaml +The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project_root}/.bmad/cis/workflows/problem-solving/workflow.yaml Load and understand solving methods from: {solving_methods} โš ๏ธ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. โš ๏ธ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately โ†’ SHOW checkpoint separator (โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”) โ†’ DISPLAY generated content โ†’ PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO โ†’ WAIT for user response. Never batch saves or skip checkpoints. diff --git a/src/modules/cis/workflows/problem-solving/workflow.yaml b/src/modules/cis/workflows/problem-solving/workflow.yaml index 18d36dd2..97e8694b 100644 --- a/src/modules/cis/workflows/problem-solving/workflow.yaml +++ b/src/modules/cis/workflows/problem-solving/workflow.yaml @@ -4,7 +4,7 @@ description: "Apply systematic problem-solving methodologies to crack complex ch author: "BMad" # Critical variables load from config_source -config_source: "{project-root}/{bmad_folder}/cis/config.yaml" +config_source: "{project-root}/.bmad/cis/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -14,7 +14,7 @@ date: system-generated # Example: data="{path}/problem-brief.md" provides context # Module path and component files -installed_path: "{project-root}/{bmad_folder}/cis/workflows/problem-solving" +installed_path: "{project-root}/.bmad/cis/workflows/problem-solving" template: "{installed_path}/template.md" instructions: "{installed_path}/instructions.md" @@ -30,9 +30,9 @@ 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." author: "BMad" - instructions: "{bmad_folder}/cis/workflows/problem-solving/instructions.md" - template: "{bmad_folder}/cis/workflows/problem-solving/template.md" + instructions: ".bmad/cis/workflows/problem-solving/instructions.md" + template: ".bmad/cis/workflows/problem-solving/template.md" web_bundle_files: - - "{bmad_folder}/cis/workflows/problem-solving/instructions.md" - - "{bmad_folder}/cis/workflows/problem-solving/template.md" - - "{bmad_folder}/cis/workflows/problem-solving/solving-methods.csv" + - ".bmad/cis/workflows/problem-solving/instructions.md" + - ".bmad/cis/workflows/problem-solving/template.md" + - ".bmad/cis/workflows/problem-solving/solving-methods.csv" diff --git a/src/modules/cis/workflows/storytelling/instructions.md b/src/modules/cis/workflows/storytelling/instructions.md index 9919580d..811e625b 100644 --- a/src/modules/cis/workflows/storytelling/instructions.md +++ b/src/modules/cis/workflows/storytelling/instructions.md @@ -3,8 +3,8 @@ ## Workflow -The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml -You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/storytelling/workflow.yaml +The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project_root}/.bmad/cis/workflows/storytelling/workflow.yaml Communicate all responses in {communication_language} โš ๏ธ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. โš ๏ธ CHECKPOINT PROTOCOL: After EVERY tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately โ†’ SHOW checkpoint separator (โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”) โ†’ DISPLAY generated content โ†’ PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO โ†’ WAIT for user response. Never batch saves or skip checkpoints. diff --git a/src/modules/cis/workflows/storytelling/workflow.yaml b/src/modules/cis/workflows/storytelling/workflow.yaml index 4e3bff42..49f57513 100644 --- a/src/modules/cis/workflows/storytelling/workflow.yaml +++ b/src/modules/cis/workflows/storytelling/workflow.yaml @@ -4,7 +4,7 @@ description: "Craft compelling narratives using proven story frameworks and tech author: "BMad" # Critical variables load from config_source -config_source: "{project-root}/{bmad_folder}/cis/config.yaml" +config_source: "{project-root}/.bmad/cis/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" @@ -14,7 +14,7 @@ date: system-generated # Example: data="{path}/brand-info.md" provides brand context # Module path and component files -installed_path: "{project-root}/{bmad_folder}/cis/workflows/storytelling" +installed_path: "{project-root}/.bmad/cis/workflows/storytelling" template: "{installed_path}/template.md" instructions: "{installed_path}/instructions.md" @@ -30,9 +30,9 @@ 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." author: "BMad" - instructions: "{bmad_folder}/cis/workflows/storytelling/instructions.md" - template: "{bmad_folder}/cis/workflows/storytelling/template.md" + instructions: ".bmad/cis/workflows/storytelling/instructions.md" + template: ".bmad/cis/workflows/storytelling/template.md" web_bundle_files: - - "{bmad_folder}/cis/workflows/storytelling/instructions.md" - - "{bmad_folder}/cis/workflows/storytelling/template.md" - - "{bmad_folder}/cis/workflows/storytelling/story-types.csv" + - ".bmad/cis/workflows/storytelling/instructions.md" + - ".bmad/cis/workflows/storytelling/template.md" + - ".bmad/cis/workflows/storytelling/story-types.csv" diff --git a/src/utility/models/agent-activation-ide.xml b/src/utility/models/agent-activation-ide.xml index 02cd032a..7e47c288 100644 --- a/src/utility/models/agent-activation-ide.xml +++ b/src/utility/models/agent-activation-ide.xml @@ -1,7 +1,7 @@ Load persona from this current file containing this activation you are reading now - Override with {project-root}/{bmad_folder}/_cfg/agents/{agent-filename} if exists (replace, not merge) + Override with {project-root}/.bmad/_cfg/agents/{agent-filename} if exists (replace, not merge) Execute critical-actions section if present in current agent XML Show greeting + numbered list of ALL commands IN ORDER from current agent's cmds section CRITICAL HALT. AWAIT user input. NEVER continue without it. @@ -12,7 +12,7 @@ When command has: run-progressive-workflow="path/to/x.yaml" You MUST: - 1. CRITICAL: Always LOAD {project-root}/{bmad_folder}/core/tasks/workflow.xml + 1. CRITICAL: Always LOAD {project-root}/.bmad/core/tasks/workflow.xml 2. READ its entire contents - the is the CORE OS for EXECUTING workflows 3. Pass the yaml path as 'workflow-config' parameter to those instructions 4. Follow workflow.xml instructions EXACTLY as written @@ -20,7 +20,7 @@ When command has: validate-workflow="path/to/workflow.yaml" You MUST: - 1. You MUST LOAD the file at: {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml + 1. You MUST LOAD the file at: {project-root}/.bmad/core/tasks/validate-workflow.xml 2. READ its entire contents and EXECUTE all instructions in that file 3. Pass the workflow, and also check the workflow location for a checklist.md to pass as the checklist 4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify diff --git a/src/utility/models/agent-activation-web.xml b/src/utility/models/agent-activation-web.xml index 95e23dc5..4545cf0b 100644 --- a/src/utility/models/agent-activation-web.xml +++ b/src/utility/models/agent-activation-web.xml @@ -7,14 +7,14 @@ All dependencies are bundled within this XML file as <file> elements with CDATA content. - When you need to access a file path like "{bmad_folder}/core/tasks/workflow.xml": - 1. Find the <file id="{bmad_folder}/core/tasks/workflow.xml"> element in this document + When you need to access a file path like ".bmad/core/tasks/workflow.xml": + 1. Find the <file id=".bmad/core/tasks/workflow.xml"> element in this document 2. Extract the content from within the CDATA section 3. Use that content as if you read it from the filesystem NEVER attempt to read files from filesystem - all files are bundled in this XML - File paths starting with "{bmad_folder}/" or "{project-root}/{bmad_folder}/" refer to <file id="..."> elements + File paths starting with ".bmad/" or "{project-root}/.bmad/" refer to <file id="..."> elements When instructions reference a file path, locate the corresponding <file> element by matching the id attribute YAML files are bundled with only their web_bundle section content (flattened to root level) diff --git a/src/utility/models/fragments/activation-steps.xml b/src/utility/models/fragments/activation-steps.xml index 3a6e0fe8..127fa6fd 100644 --- a/src/utility/models/fragments/activation-steps.xml +++ b/src/utility/models/fragments/activation-steps.xml @@ -1,6 +1,6 @@ Load persona from this current agent file (already in context) ๐Ÿšจ IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT: - - Load and read {project-root}/{bmad_folder}/{{module}}/config.yaml NOW + - Load and read {project-root}/.bmad/{{module}}/config.yaml NOW - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder} - VERIFY: If config not loaded, STOP and report error to user - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored diff --git a/src/utility/models/fragments/handler-validate-workflow.xml b/src/utility/models/fragments/handler-validate-workflow.xml index 883b1834..af01e463 100644 --- a/src/utility/models/fragments/handler-validate-workflow.xml +++ b/src/utility/models/fragments/handler-validate-workflow.xml @@ -1,6 +1,6 @@ When command has: validate-workflow="path/to/workflow.yaml" - 1. You MUST LOAD the file at: {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml + 1. You MUST LOAD the file at: {project-root}/.bmad/core/tasks/validate-workflow.xml 2. READ its entire contents and EXECUTE all instructions in that file 3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist 4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify diff --git a/src/utility/models/fragments/handler-workflow.xml b/src/utility/models/fragments/handler-workflow.xml index 8ecee8aa..72b14887 100644 --- a/src/utility/models/fragments/handler-workflow.xml +++ b/src/utility/models/fragments/handler-workflow.xml @@ -1,6 +1,6 @@ When menu item has: workflow="path/to/workflow.yaml" - 1. CRITICAL: Always LOAD {project-root}/{bmad_folder}/core/tasks/workflow.xml + 1. CRITICAL: Always LOAD {project-root}/.bmad/core/tasks/workflow.xml 2. Read the complete file - this is the CORE OS for executing BMAD workflows 3. Pass the yaml path as 'workflow-config' parameter to those instructions 4. Execute workflow.xml instructions precisely following all steps diff --git a/src/utility/models/fragments/web-bundle-activation-steps.xml b/src/utility/models/fragments/web-bundle-activation-steps.xml index 544d7b78..ce4fa813 100644 --- a/src/utility/models/fragments/web-bundle-activation-steps.xml +++ b/src/utility/models/fragments/web-bundle-activation-steps.xml @@ -10,14 +10,14 @@ All dependencies are bundled within this XML file as <file> elements with CDATA content. - When you need to access a file path like "{bmad_folder}/core/tasks/workflow.xml": - 1. Find the <file id="{bmad_folder}/core/tasks/workflow.xml"> element in this document + When you need to access a file path like ".bmad/core/tasks/workflow.xml": + 1. Find the <file id=".bmad/core/tasks/workflow.xml"> element in this document 2. Extract the content from within the CDATA section 3. Use that content as if you read it from the filesystem NEVER attempt to read files from filesystem - all files are bundled in this XML - File paths starting with "{bmad_folder}/" refer to <file id="..."> elements + File paths starting with ".bmad/" refer to <file id="..."> elements When instructions reference a file path, locate the corresponding <file> element by matching the id attribute YAML files are bundled with only their web_bundle section content (flattened to root level) diff --git a/tools/cli/README.md b/tools/cli/README.md index 0c8bf4bd..822567cb 100644 --- a/tools/cli/README.md +++ b/tools/cli/README.md @@ -105,7 +105,7 @@ The installer is a multi-stage system that handles agent compilation, IDE integr - Resolve module dependencies (4-pass system) 3. Install Core + Modules - - Copy files to {target}/{bmad_folder}/ + - Copy files to {target}/.bmad/ - Compile agents: YAML โ†’ Markdown/XML (forWebBundle: false) - Merge customize.yaml files if they exist - Inject activation blocks based on agent capabilities @@ -131,7 +131,7 @@ The installer is a multi-stage system that handles agent compilation, IDE integr ``` {target}/ -โ”œโ”€โ”€ {bmad_folder}/ +โ”œโ”€โ”€ .bmad/ โ”‚ โ”œโ”€โ”€ core/ # Always installed โ”‚ โ”œโ”€โ”€ {module}/ # Selected modules โ”‚ โ”‚ โ”œโ”€โ”€ agents/ # Compiled .md files @@ -239,7 +239,7 @@ Platform specifics are **IDE+module combination hooks** that execute custom logi ### Manifest System -The installer generates **5 manifest files** in `{target}/{bmad_folder}/_cfg/`: +The installer generates **5 manifest files** in `{target}/.bmad/_cfg/`: **1. Installation Manifest** (`manifest.yaml`) @@ -428,7 +428,7 @@ agent: identity: 'You are an experienced PM...' menu: - trigger: '*create-brief' - workflow: '{project-root}/{bmad_folder}/bmm/workflows/.../workflow.yaml' + workflow: '{project-root}/.bmad/bmm/workflows/.../workflow.yaml' ``` ### Output: IDE (Markdown with XML) @@ -441,7 +441,7 @@ agent: ```xml - Load {project-root}/{bmad_folder}/bmm/config.yaml at runtime + Load {project-root}/.bmad/bmm/config.yaml at runtime ... ... @@ -533,20 +533,20 @@ src/utility/models/fragments/ ## Key Differences: Installation vs Bundling -| Aspect | Installation (IDE) | Bundling (Web) | -| ----------------------- | ------------------------------------ | --------------------------------- | -| **Trigger** | `npm run install:bmad` | `npm run bundle` | -| **Entry Point** | `commands/install.js` | `bundlers/bundle-web.js` | -| **Compiler Flag** | `forWebBundle: false` | `forWebBundle: true` | -| **Output Format** | Markdown `.md` | Standalone XML `.xml` | -| **Output Location** | `{target}/{bmad_folder}/` + IDE dirs | `web-bundles/` | -| **Customization** | Merges `customize.yaml` | Base agents only | -| **Dependencies** | Referenced by path | Bundled inline (CDATA) | -| **Activation Fragment** | `activation-steps.xml` | `web-bundle-activation-steps.xml` | -| **Filesystem Access** | Required | Not needed | -| **Build Metadata** | Included (hash) | Excluded | -| **Path Format** | `{project-root}` placeholders | Stripped, wrapped as `` | -| **Use Case** | Local IDE development | Web deployment | +| Aspect | Installation (IDE) | Bundling (Web) | +| ----------------------- | ----------------------------- | --------------------------------- | +| **Trigger** | `npm run install:bmad` | `npm run bundle` | +| **Entry Point** | `commands/install.js` | `bundlers/bundle-web.js` | +| **Compiler Flag** | `forWebBundle: false` | `forWebBundle: true` | +| **Output Format** | Markdown `.md` | Standalone XML `.xml` | +| **Output Location** | `{target}/.bmad/` + IDE dirs | `web-bundles/` | +| **Customization** | Merges `customize.yaml` | Base agents only | +| **Dependencies** | Referenced by path | Bundled inline (CDATA) | +| **Activation Fragment** | `activation-steps.xml` | `web-bundle-activation-steps.xml` | +| **Filesystem Access** | Required | Not needed | +| **Build Metadata** | Included (hash) | Excluded | +| **Path Format** | `{project-root}` placeholders | Stripped, wrapped as `` | +| **Use Case** | Local IDE development | Web deployment | **Activation Differences**: diff --git a/tools/cli/bundlers/web-bundler.js b/tools/cli/bundlers/web-bundler.js index 40578627..f0d10715 100644 --- a/tools/cli/bundlers/web-bundler.js +++ b/tools/cli/bundlers/web-bundler.js @@ -29,7 +29,7 @@ class WebBundler { // Temporary directory for generated manifests this.tempDir = path.join(process.cwd(), '.bundler-temp'); - this.tempManifestDir = path.join(this.tempDir, 'bmad', '_cfg'); + this.tempManifestDir = path.join(this.tempDir, '.bmad', '_cfg'); // Bundle statistics this.stats = { @@ -531,9 +531,9 @@ class WebBundler { } // Parse paths to extract module and workflow location - // Support both {project-root}/bmad/... and {project-root}/{bmad_folder}/... patterns - const sourceMatch = sourceWorkflowPath.match(/\{project-root\}\/(?:\{bmad_folder\}|bmad)\/([^/]+)\/workflows\/(.+)/); - const installMatch = installWorkflowPath.match(/\{project-root\}\/(?:\{bmad_folder\}|bmad)\/([^/]+)\/workflows\/(.+)/); + // Support both {project-root}/bmad/... and {project-root}/.bmad/... patterns + const sourceMatch = sourceWorkflowPath.match(/\{project-root\}\/(?:\.?bmad)\/([^/]+)\/workflows\/(.+)/); + const installMatch = installWorkflowPath.match(/\{project-root\}\/(?:\.?bmad)\/([^/]+)\/workflows\/(.+)/); if (!sourceMatch || !installMatch) { continue; @@ -584,9 +584,9 @@ class WebBundler { let yamlContent = await fs.readFile(workflowYamlPath, 'utf8'); // Replace config_source with new module reference - // Support both old format (bmad) and new format ({bmad_folder}) - const configSourcePattern = /config_source:\s*["']?\{project-root\}\/(?:\{bmad_folder\}|bmad)\/[^/]+\/config\.yaml["']?/g; - const newConfigSource = `config_source: "{project-root}/{bmad_folder}/${newModuleName}/config.yaml"`; + // Support both old format (bmad) and new format (.bmad) + const configSourcePattern = /config_source:\s*["']?\{project-root\}\/(?:\.?bmad)\/[^/]+\/config\.yaml["']?/g; + const newConfigSource = `config_source: "{project-root}/.bmad/${newModuleName}/config.yaml"`; const updatedYaml = yamlContent.replaceAll(configSourcePattern, newConfigSource); await fs.writeFile(workflowYamlPath, updatedYaml, 'utf8'); @@ -723,7 +723,7 @@ class WebBundler { /tools="([^"]+)"/g, /knowledge="([^"]+)"/g, /{project-root}\/([^"'\s<>]+)/g, // Legacy {project-root} paths - /\bbmad\/([^"'\s<>]+)/g, // Direct bmad/ paths (after {bmad_folder} replacement) + /\bbmad\/([^"'\s<>]+)/g, // Direct bmad/ paths (after .bmad replacement) ]; for (const pattern of patterns) { @@ -733,8 +733,8 @@ class WebBundler { let filePath = match[1]; // Remove {project-root} prefix if present filePath = filePath.replace(/^{project-root}\//, ''); - // Remove {bmad_folder} prefix if present (should be rare, mostly replaced already) - filePath = filePath.replace(/^{bmad_folder}\//, 'bmad/'); + // Remove .bmad prefix if present (should be rare, mostly replaced already) + filePath = filePath.replace(/^.bmad\//, 'bmad/'); // For bmad/ pattern, prepend 'bmad/' since it was captured without it if (pattern.source.includes(String.raw`\bbmad\/`)) { @@ -760,8 +760,8 @@ class WebBundler { while ((match = pattern.exec(xml)) !== null) { let workflowPath = match[1]; workflowPath = workflowPath.replace(/^{project-root}\//, ''); - // Remove {bmad_folder} prefix if present and replace with bmad - workflowPath = workflowPath.replace(/^{bmad_folder}\//, 'bmad/'); + // Remove .bmad prefix if present and replace with bmad + workflowPath = workflowPath.replace(/^.bmad\//, 'bmad/'); // Skip obvious placeholder/example paths if (workflowPath && workflowPath.endsWith('.yaml') && !workflowPath.includes('path/to/') && !workflowPath.includes('example')) { @@ -851,7 +851,7 @@ class WebBundler { if (deps) { for (const dep of deps) { let depPath = dep.replaceAll(/['"]/g, '').replace(/^{project-root}\//, ''); - depPath = depPath.replace(/^{bmad_folder}\//, 'bmad/'); + depPath = depPath.replace(/^.bmad\//, 'bmad/'); if (depPath && !processed.has(depPath)) { await this.processFileDependency(depPath, dependencies, processed, moduleName, warnings); } @@ -865,7 +865,7 @@ class WebBundler { if (templates) { for (const template of templates) { let templatePath = template.replaceAll(/['"]/g, '').replace(/^{project-root}\//, ''); - templatePath = templatePath.replace(/^{bmad_folder}\//, 'bmad/'); + templatePath = templatePath.replace(/^.bmad\//, 'bmad/'); if (templatePath && !processed.has(templatePath)) { await this.processFileDependency(templatePath, dependencies, processed, moduleName, warnings); } @@ -1053,13 +1053,13 @@ class WebBundler { bundleYamlContent = yamlContent; } - // Process {project-root} and {bmad_folder} references in the YAML content + // Process {project-root} and .bmad references in the YAML content bundleYamlContent = this.processProjectRootReferences(bundleYamlContent); // Include the YAML file with only web_bundle content, wrapped in XML // Process the workflow path to create a clean ID let yamlId = workflowPath.replace(/^{project-root}\//, ''); - yamlId = yamlId.replace(/^{bmad_folder}\//, 'bmad/'); + yamlId = yamlId.replace(/^.bmad\//, 'bmad/'); const wrappedYaml = this.wrapContentInXml(bundleYamlContent, yamlId, 'yaml'); dependencies.set(yamlId, wrappedYaml); @@ -1078,7 +1078,7 @@ class WebBundler { for (const bundleFilePath of bundleFiles) { // Process the file path to create a clean ID for checking if already processed let cleanFilePath = bundleFilePath.replace(/^{project-root}\//, ''); - cleanFilePath = cleanFilePath.replace(/^{bmad_folder}\//, 'bmad/'); + cleanFilePath = cleanFilePath.replace(/^.bmad\//, 'bmad/'); if (processed.has(cleanFilePath)) { continue; @@ -1087,7 +1087,7 @@ class WebBundler { const bundleActualPath = this.resolveFilePath(bundleFilePath, moduleName); if (!bundleActualPath || !(await fs.pathExists(bundleActualPath))) { - // Use the cleaned path in warnings (with {bmad_folder} replaced) + // Use the cleaned path in warnings (with .bmad replaced) warnings.push(cleanFilePath); continue; } @@ -1136,7 +1136,7 @@ class WebBundler { } let fileContent = await fs.readFile(actualPath, 'utf8'); - // Process {project-root} and {bmad_folder} references + // Process {project-root} and .bmad references fileContent = this.processProjectRootReferences(fileContent); const wrappedContent = this.wrapContentInXml(fileContent, coreWorkflowPath, 'xml'); dependencies.set(coreWorkflowPath, wrappedContent); @@ -1162,7 +1162,7 @@ class WebBundler { } let fileContent = await fs.readFile(actualPath, 'utf8'); - // Process {project-root} and {bmad_folder} references + // Process {project-root} and .bmad references fileContent = this.processProjectRootReferences(fileContent); const fileExt = path.extname(actualPath).toLowerCase().replace('.', ''); const wrappedContent = this.wrapContentInXml(fileContent, filePath, fileExt); @@ -1196,8 +1196,8 @@ class WebBundler { async processWildcardDependency(pattern, dependencies, processed, moduleName, warnings = []) { // Remove {project-root} prefix pattern = pattern.replace(/^{project-root}\//, ''); - // Replace {bmad_folder} with bmad - pattern = pattern.replace(/^{bmad_folder}\//, 'bmad/'); + // Replace .bmad with bmad + pattern = pattern.replace(/^.bmad\//, 'bmad/'); // Get directory and file pattern const lastSlash = pattern.lastIndexOf('/'); @@ -1265,9 +1265,6 @@ class WebBundler { resolveFilePath(filePath, moduleName) { // Remove {project-root} prefix filePath = filePath.replace(/^{project-root}\//, ''); - // Replace {bmad_folder} with bmad - filePath = filePath.replace(/^{bmad_folder}\//, 'bmad/'); - filePath = filePath.replace(/^{bmad_folder}$/, 'bmad'); // Check temp directory first for _cfg files if (filePath.startsWith('bmad/_cfg/')) { @@ -1278,11 +1275,6 @@ class WebBundler { } } - // Handle different path patterns for bmad files - // bmad/cis/tasks/brain-session.md -> src/modules/cis/tasks/brain-session.md - // bmad/core/tasks/create-doc.md -> src/core/tasks/create-doc.md - // bmad/bmm/templates/brief.md -> src/modules/bmm/templates/brief.md - let actualPath = filePath; if (filePath.startsWith('bmad/')) { @@ -1334,15 +1326,13 @@ class WebBundler { } /** - * Process and remove {project-root} references and replace {bmad_folder} with bmad + * Process and remove {project-root} references */ processProjectRootReferences(content) { // Remove {project-root}/ prefix (with slash) content = content.replaceAll('{project-root}/', ''); // Also remove {project-root} without slash content = content.replaceAll('{project-root}', ''); - // Replace {bmad_folder} with bmad - content = content.replaceAll('{bmad_folder}', 'bmad'); return content; } diff --git a/tools/cli/commands/build.js b/tools/cli/commands/build.js index ba84e199..95d2a77f 100644 --- a/tools/cli/commands/build.js +++ b/tools/cli/commands/build.js @@ -80,7 +80,7 @@ module.exports = { */ async function buildAgent(projectDir, agentName) { // First check standalone agents in bmad/agents/{agentname}/ - const standaloneAgentDir = path.join(projectDir, 'bmad', 'agents', agentName); + const standaloneAgentDir = path.join(projectDir, '.bmad', 'agents', agentName); let standaloneYamlPath = path.join(standaloneAgentDir, `${agentName}.agent.yaml`); // If exact match doesn't exist, look for any .agent.yaml file in the directory @@ -99,7 +99,7 @@ async function buildAgent(projectDir, agentName) { // Build the standalone agent console.log(chalk.cyan(` Building standalone agent ${agentName}...`)); - const customizePath = path.join(projectDir, 'bmad', '_cfg', 'agents', `${agentName}.customize.yaml`); + const customizePath = path.join(projectDir, '.bmad', '_cfg', 'agents', `${agentName}.customize.yaml`); const customizeExists = await fs.pathExists(customizePath); await builder.buildAgent(standaloneYamlPath, customizeExists ? customizePath : null, outputPath, { includeMetadata: true }); @@ -109,7 +109,7 @@ async function buildAgent(projectDir, agentName) { } // Find the agent YAML file in .claude/commands/bmad/ - const bmadCommandsDir = path.join(projectDir, '.claude', 'commands', 'bmad'); + const bmadCommandsDir = path.join(projectDir, '.claude', 'commands', '.bmad'); // Search all module directories for the agent const modules = await fs.readdir(bmadCommandsDir); @@ -149,7 +149,7 @@ async function buildAllAgents(projectDir) { let builtCount = 0; // First, build standalone agents in bmad/agents/ - const standaloneAgentsDir = path.join(projectDir, 'bmad', 'agents'); + const standaloneAgentsDir = path.join(projectDir, '.bmad', 'agents'); if (await fs.pathExists(standaloneAgentsDir)) { console.log(chalk.cyan('\nBuilding standalone agents...')); const agentDirs = await fs.readdir(standaloneAgentsDir); @@ -177,7 +177,7 @@ async function buildAllAgents(projectDir) { console.log(chalk.cyan(` Building standalone agent ${agentName}...`)); - const customizePath = path.join(projectDir, 'bmad', '_cfg', 'agents', `${agentName}.customize.yaml`); + const customizePath = path.join(projectDir, '.bmad', '_cfg', 'agents', `${agentName}.customize.yaml`); const customizeExists = await fs.pathExists(customizePath); await builder.buildAgent(agentYamlPath, customizeExists ? customizePath : null, outputPath, { includeMetadata: true }); diff --git a/tools/cli/installers/lib/core/config-collector.js b/tools/cli/installers/lib/core/config-collector.js index ae9f8074..f61e6411 100644 --- a/tools/cli/installers/lib/core/config-collector.js +++ b/tools/cli/installers/lib/core/config-collector.js @@ -696,15 +696,6 @@ class ConfigCollector { } } - // Special handling for bmad_folder: detect existing folder name - if (moduleName === 'core' && key === 'bmad_folder' && !existingValue && this.currentProjectDir) { - // Try to detect the existing BMAD folder name - const detectedFolder = await this.detectExistingBmadFolder(this.currentProjectDir); - if (detectedFolder) { - existingValue = detectedFolder; - } - } - // Special handling for user_name: default to system user if (moduleName === 'core' && key === 'user_name' && !existingValue) { item.default = this.getDefaultUsername(); diff --git a/tools/cli/installers/lib/core/installer.js b/tools/cli/installers/lib/core/installer.js index 44ad48ff..aadb34fc 100644 --- a/tools/cli/installers/lib/core/installer.js +++ b/tools/cli/installers/lib/core/installer.js @@ -14,7 +14,7 @@ * @architecture Orchestrator pattern - coordinates Detector, ModuleManager, IdeManager, and file operations to build complete BMAD installation * @dependencies fs-extra, ora, chalk, detector.js, module-manager.js, ide-manager.js, config.js * @entrypoints Called by install.js command via installer.install(config) - * @patterns Injection point processing (AgentVibes), placeholder replacement ({bmad_folder}), module dependency resolution + * @patterns Injection point processing (AgentVibes), placeholder replacement (.bmad), module dependency resolution * @related GitHub AgentVibes#34 (injection points), ui.js (user prompts), copyFileWithPlaceholderReplacement() */ @@ -67,7 +67,7 @@ class Installer { // Check if project directory exists if (!(await fs.pathExists(projectDir))) { // Project doesn't exist yet, return default - return path.join(projectDir, 'bmad'); + return path.join(projectDir, '.bmad'); } // V6+ strategy: Look for ANY directory with _cfg/manifest.yaml @@ -89,13 +89,13 @@ class Installer { // No V6+ installation found, return default // This will be used for new installations - return path.join(projectDir, 'bmad'); + return path.join(projectDir, '.bmad'); } /** * @function copyFileWithPlaceholderReplacement * @intent Copy files from BMAD source to installation directory with dynamic content transformation - * @why Enables installation-time customization: {bmad_folder} replacement + optional AgentVibes TTS injection + * @why Enables installation-time customization: .bmad replacement + optional AgentVibes TTS injection * @param {string} sourcePath - Absolute path to source file in BMAD repository * @param {string} targetPath - Absolute path to destination file in user's project * @param {string} bmadFolderName - User's chosen bmad folder name (default: 'bmad') @@ -105,11 +105,6 @@ class Installer { * @calledby installCore(), installModule(), IDE installers during file vendoring * @calls processTTSInjectionPoints(), fs.readFile(), fs.writeFile(), fs.copy() * - * AI NOTE: This is the core transformation pipeline for ALL BMAD installation file copies. - * It performs two transformations in sequence: - * 1. {bmad_folder} โ†’ user's custom folder name (e.g., ".bmad" or "bmad") - * 2. โ†’ TTS bash calls (if enabled) OR stripped (if disabled) - * * The injection point processing enables loose coupling between BMAD and TTS providers: * - BMAD source contains injection markers (not actual TTS code) * - At install-time, markers are replaced OR removed based on user preference @@ -140,16 +135,6 @@ class Installer { // Read the file content let content = await fs.readFile(sourcePath, 'utf8'); - // Replace {bmad_folder} placeholder with actual folder name - if (content.includes('{bmad_folder}')) { - content = content.replaceAll('{bmad_folder}', bmadFolderName); - } - - // Replace escape sequence {*bmad_folder*} with literal {bmad_folder} - if (content.includes('{*bmad_folder*}')) { - content = content.replaceAll('{*bmad_folder*}', '{bmad_folder}'); - } - // Process AgentVibes injection points (pass targetPath for tracking) content = this.processTTSInjectionPoints(content, targetPath); @@ -487,8 +472,8 @@ If AgentVibes party mode is enabled, immediately trigger TTS with agent's voice: }); } - // Get bmad_folder from config (default to 'bmad' for backwards compatibility) - const bmadFolderName = moduleConfigs.core && moduleConfigs.core.bmad_folder ? moduleConfigs.core.bmad_folder : 'bmad'; + // Always use .bmad as the folder name + const bmadFolderName = '.bmad'; this.bmadFolderName = bmadFolderName; // Store for use in other methods // Store AgentVibes configuration for injection point processing @@ -507,7 +492,6 @@ If AgentVibes party mode is enabled, immediately trigger TTS with agent's voice: // Resolve target directory (path.resolve handles platform differences) const projectDir = path.resolve(config.directory); - // Check if bmad_folder has changed from existing installation (only if project dir exists) let existingBmadDir = null; let existingBmadFolderName = null; @@ -516,54 +500,6 @@ If AgentVibes party mode is enabled, immediately trigger TTS with agent's voice: existingBmadFolderName = path.basename(existingBmadDir); } - const targetBmadDir = path.join(projectDir, bmadFolderName); - - // If bmad_folder changed during update/upgrade, back up old folder and do fresh install - if (existingBmadDir && (await fs.pathExists(existingBmadDir)) && existingBmadFolderName !== bmadFolderName) { - spinner.stop(); - console.log(chalk.yellow(`\nโš ๏ธ bmad_folder has changed: ${existingBmadFolderName} โ†’ ${bmadFolderName}`)); - console.log(chalk.yellow('This will result in a fresh installation to the new folder.')); - - const inquirer = require('inquirer'); - const { confirmFreshInstall } = await inquirer.prompt([ - { - type: 'confirm', - name: 'confirmFreshInstall', - message: chalk.cyan('Proceed with fresh install? (Your old folder will be backed up)'), - default: true, - }, - ]); - - if (!confirmFreshInstall) { - console.log(chalk.yellow('Installation cancelled.')); - return { success: false, cancelled: true }; - } - - spinner.start('Backing up existing installation...'); - - // Find a unique backup name - let backupDir = `${existingBmadDir}-bak`; - let counter = 1; - while (await fs.pathExists(backupDir)) { - backupDir = `${existingBmadDir}-bak-${counter}`; - counter++; - } - - // Rename the old folder to backup - await fs.move(existingBmadDir, backupDir); - - spinner.succeed(`Backed up ${existingBmadFolderName} โ†’ ${path.basename(backupDir)}`); - console.log(chalk.cyan('\n๐Ÿ“‹ Important:')); - console.log(chalk.dim(` - Your old installation has been backed up to: ${path.basename(backupDir)}`)); - console.log(chalk.dim(` - If you had custom agents or configurations, copy them from:`)); - console.log(chalk.dim(` ${path.basename(backupDir)}/_cfg/`)); - console.log(chalk.dim(` - To the new location:`)); - console.log(chalk.dim(` ${bmadFolderName}/_cfg/`)); - console.log(''); - - spinner.start('Starting fresh installation...'); - } - // Create a project directory if it doesn't exist (user already confirmed) if (!(await fs.pathExists(projectDir))) { spinner.text = 'Creating installation directory...'; @@ -1932,8 +1868,8 @@ If AgentVibes party mode is enabled, immediately trigger TTS with agent's voice: // DO NOT replace {project-root} - LLMs understand this placeholder at runtime // const processedContent = xmlContent.replaceAll('{project-root}', projectDir); - // Replace {bmad_folder} with actual folder name - xmlContent = xmlContent.replaceAll('{bmad_folder}', this.bmadFolderName || 'bmad'); + // Replace .bmad with actual folder name + xmlContent = xmlContent.replaceAll('.bmad', this.bmadFolderName || 'bmad'); // Replace {agent_sidecar_folder} if configured const coreConfig = this.configCollector.collectedConfig.core || {}; @@ -1980,7 +1916,7 @@ If AgentVibes party mode is enabled, immediately trigger TTS with agent's voice: // Resolve path variables const resolvedSidecarFolder = agentSidecarFolder .replaceAll('{project-root}', projectDir) - .replaceAll('{bmad_folder}', this.bmadFolderName || 'bmad'); + .replaceAll('.bmad', this.bmadFolderName || 'bmad'); // Create sidecar directory for this agent const agentSidecarDir = path.join(resolvedSidecarFolder, agentName); @@ -2674,7 +2610,6 @@ If AgentVibes party mode is enabled, immediately trigger TTS with agent's voice: lastModified: new Date().toISOString(), }; - // Check if bmad_folder has changed const existingBmadFolderName = path.basename(bmadDir); const newBmadFolderName = this.configCollector.collectedConfig.core?.bmad_folder || existingBmadFolderName; @@ -3272,7 +3207,7 @@ If AgentVibes party mode is enabled, immediately trigger TTS with agent's voice: const agentSidecarFolder = config.coreConfig?.agent_sidecar_folder; // Resolve path variables - const resolvedSidecarFolder = agentSidecarFolder.replaceAll('{project-root}', projectDir).replaceAll('{bmad_folder}', bmadDir); + const resolvedSidecarFolder = agentSidecarFolder.replaceAll('{project-root}', projectDir).replaceAll('.bmad', bmadDir); // Create sidecar directory for this agent const agentSidecarDir = path.join(resolvedSidecarFolder, finalAgentName); diff --git a/tools/cli/installers/lib/core/manifest-generator.js b/tools/cli/installers/lib/core/manifest-generator.js index 6ad7b790..cd382378 100644 --- a/tools/cli/installers/lib/core/manifest-generator.js +++ b/tools/cli/installers/lib/core/manifest-generator.js @@ -23,7 +23,7 @@ class ManifestGenerator { /** * Generate all manifests for the installation - * @param {string} bmadDir - BMAD installation directory + * @param {string} bmadDir - .bmad * @param {Array} selectedModules - Selected modules for installation * @param {Array} installedFiles - All installed files (optional, for hash tracking) */ diff --git a/tools/cli/installers/lib/custom/handler.js b/tools/cli/installers/lib/custom/handler.js index 3f6f46d0..23c4c493 100644 --- a/tools/cli/installers/lib/custom/handler.js +++ b/tools/cli/installers/lib/custom/handler.js @@ -255,7 +255,6 @@ class CustomHandler { let content = await fs.readFile(sourcePath, 'utf8'); // Replace placeholders - content = content.replaceAll('{bmad_folder}', config.bmad_folder || 'bmad'); content = content.replaceAll('{user_name}', config.user_name || 'User'); content = content.replaceAll('{communication_language}', config.communication_language || 'English'); content = content.replaceAll('{output_folder}', config.output_folder || 'docs'); @@ -321,7 +320,6 @@ class CustomHandler { if (await fs.pathExists(genericTemplatePath)) { // Copy with placeholder replacement let templateContent = await fs.readFile(genericTemplatePath, 'utf8'); - templateContent = templateContent.replaceAll('{bmad_folder}', config.bmad_folder || 'bmad'); await fs.writeFile(customizePath, templateContent, 'utf8'); console.log(chalk.dim(` Created customize: custom-${agentName}.customize.yaml`)); } @@ -332,7 +330,6 @@ class CustomHandler { // Replace placeholders in the compiled content let processedXml = xml; - processedXml = processedXml.replaceAll('{bmad_folder}', config.bmad_folder || 'bmad'); processedXml = processedXml.replaceAll('{user_name}', config.user_name || 'User'); processedXml = processedXml.replaceAll('{communication_language}', config.communication_language || 'English'); processedXml = processedXml.replaceAll('{output_folder}', config.output_folder || 'docs'); @@ -358,7 +355,7 @@ class CustomHandler { const projectDir = path.dirname(bmadDir); const resolvedSidecarFolder = config.agent_sidecar_folder .replaceAll('{project-root}', projectDir) - .replaceAll('{bmad_folder}', path.basename(bmadDir)); + .replaceAll('.bmad', path.basename(bmadDir)); // Create sidecar directory for this agent const agentSidecarDir = path.join(resolvedSidecarFolder, agentName); diff --git a/tools/cli/installers/lib/ide/_base-ide.js b/tools/cli/installers/lib/ide/_base-ide.js index 61aca482..e46f2b87 100644 --- a/tools/cli/installers/lib/ide/_base-ide.js +++ b/tools/cli/installers/lib/ide/_base-ide.js @@ -527,26 +527,26 @@ class BaseIdeSetup { } /** - * Write file with content (replaces {bmad_folder} placeholder) + * Write file with content (replaces .bmad placeholder) * @param {string} filePath - File path * @param {string} content - File content */ async writeFile(filePath, content) { - // Replace {bmad_folder} placeholder if present - if (typeof content === 'string' && content.includes('{bmad_folder}')) { - content = content.replaceAll('{bmad_folder}', this.bmadFolderName); + // Replace .bmad placeholder if present + if (typeof content === 'string' && content.includes('.bmad')) { + content = content.replaceAll('.bmad', this.bmadFolderName); } - // Replace escape sequence {*bmad_folder*} with literal {bmad_folder} - if (typeof content === 'string' && content.includes('{*bmad_folder*}')) { - content = content.replaceAll('{*bmad_folder*}', '{bmad_folder}'); + // Replace escape sequence .bmad with literal .bmad + if (typeof content === 'string' && content.includes('.bmad')) { + content = content.replaceAll('.bmad', '.bmad'); } await this.ensureDir(path.dirname(filePath)); await fs.writeFile(filePath, content, 'utf8'); } /** - * Copy file from source to destination (replaces {bmad_folder} placeholder in text files) + * Copy file from source to destination (replaces .bmad placeholder in text files) * @param {string} source - Source file path * @param {string} dest - Destination file path */ @@ -563,14 +563,14 @@ class BaseIdeSetup { // Read the file content let content = await fs.readFile(source, 'utf8'); - // Replace {bmad_folder} placeholder with actual folder name - if (content.includes('{bmad_folder}')) { - content = content.replaceAll('{bmad_folder}', this.bmadFolderName); + // Replace .bmad placeholder with actual folder name + if (content.includes('.bmad')) { + content = content.replaceAll('.bmad', this.bmadFolderName); } - // Replace escape sequence {*bmad_folder*} with literal {bmad_folder} - if (content.includes('{*bmad_folder*}')) { - content = content.replaceAll('{*bmad_folder*}', '{bmad_folder}'); + // Replace escape sequence .bmad with literal .bmad + if (content.includes('.bmad')) { + content = content.replaceAll('.bmad', '.bmad'); } // Write to dest with replaced content diff --git a/tools/cli/installers/lib/ide/gemini.js b/tools/cli/installers/lib/ide/gemini.js index 10dd04b9..978062a2 100644 --- a/tools/cli/installers/lib/ide/gemini.js +++ b/tools/cli/installers/lib/ide/gemini.js @@ -174,8 +174,8 @@ ${contentWithoutFrontmatter} // Note: {user_name} and other {config_values} are left as-is for runtime substitution by Gemini const tomlContent = template .replaceAll('{{title}}', title) - .replaceAll('{{*bmad_folder*}}', '{bmad_folder}') - .replaceAll('{{bmad_folder}}', this.bmadFolderName) + .replaceAll('{.bmad}', '.bmad') + .replaceAll('{.bmad}', this.bmadFolderName) .replaceAll('{{module}}', agent.module) .replaceAll('{{name}}', agent.name); @@ -196,8 +196,8 @@ ${contentWithoutFrontmatter} // Replace template variables const tomlContent = template .replaceAll('{{taskName}}', taskName) - .replaceAll('{{*bmad_folder*}}', '{bmad_folder}') - .replaceAll('{{bmad_folder}}', this.bmadFolderName) + .replaceAll('{.bmad}', '.bmad') + .replaceAll('{.bmad}', this.bmadFolderName) .replaceAll('{{module}}', task.module) .replaceAll('{{filename}}', task.filename); diff --git a/tools/cli/installers/lib/ide/shared/agent-command-generator.js b/tools/cli/installers/lib/ide/shared/agent-command-generator.js index 10c4e34f..f111dcb9 100644 --- a/tools/cli/installers/lib/ide/shared/agent-command-generator.js +++ b/tools/cli/installers/lib/ide/shared/agent-command-generator.js @@ -65,8 +65,8 @@ class AgentCommandGenerator { .replaceAll('{{module}}', agent.module) .replaceAll('{{path}}', agentPathInModule) .replaceAll('{{description}}', agent.description || `${agent.name} agent`) - .replaceAll('{bmad_folder}', this.bmadFolderName) - .replaceAll('{*bmad_folder*}', '{bmad_folder}'); + .replaceAll('.bmad', this.bmadFolderName) + .replaceAll('.bmad', '.bmad'); } /** diff --git a/tools/cli/installers/lib/ide/shared/workflow-command-generator.js b/tools/cli/installers/lib/ide/shared/workflow-command-generator.js index e3280e8c..921388ea 100644 --- a/tools/cli/installers/lib/ide/shared/workflow-command-generator.js +++ b/tools/cli/installers/lib/ide/shared/workflow-command-generator.js @@ -109,7 +109,7 @@ class WorkflowCommandGenerator { // Convert source path to installed path // From: /Users/.../src/modules/bmm/workflows/.../workflow.yaml - // To: {project-root}/{bmad_folder}/bmm/workflows/.../workflow.yaml + // To: {project-root}/.bmad/bmm/workflows/.../workflow.yaml let workflowPath = workflow.path; // Extract the relative path from source @@ -131,8 +131,8 @@ class WorkflowCommandGenerator { .replaceAll('{{module}}', workflow.module) .replaceAll('{{description}}', workflow.description) .replaceAll('{{workflow_path}}', workflowPath) - .replaceAll('{bmad_folder}', this.bmadFolderName) - .replaceAll('{*bmad_folder*}', '{bmad_folder}'); + .replaceAll('.bmad', this.bmadFolderName) + .replaceAll('.bmad', '.bmad'); } /** diff --git a/tools/cli/installers/lib/ide/templates/agent-command-template.md b/tools/cli/installers/lib/ide/templates/agent-command-template.md index 4f895542..be2461fa 100644 --- a/tools/cli/installers/lib/ide/templates/agent-command-template.md +++ b/tools/cli/installers/lib/ide/templates/agent-command-template.md @@ -6,7 +6,7 @@ description: '{{description}}' You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. -1. LOAD the FULL agent file from @{bmad_folder}/{{module}}/agents/{{path}} +1. LOAD the FULL agent file from @.bmad/{{module}}/agents/{{path}} 2. READ its entire contents - this contains the complete agent persona, menu, and instructions 3. Execute ALL activation steps exactly as written in the agent file 4. Follow the agent's persona and menu system precisely diff --git a/tools/cli/installers/lib/ide/templates/gemini-agent-command.toml b/tools/cli/installers/lib/ide/templates/gemini-agent-command.toml index 7b03ac4e..2022c3f0 100644 --- a/tools/cli/installers/lib/ide/templates/gemini-agent-command.toml +++ b/tools/cli/installers/lib/ide/templates/gemini-agent-command.toml @@ -3,12 +3,12 @@ prompt = """ CRITICAL: You are now the BMad '{{title}}' agent. PRE-FLIGHT CHECKLIST: -1. [ ] IMMEDIATE ACTION: Load and parse @{{bmad_folder}}/{{module}}/config.yaml - store ALL config values in memory for use throughout the session. -2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at @{{bmad_folder}}/{{module}}/agents/{{name}}.md. +1. [ ] IMMEDIATE ACTION: Load and parse @{.bmad}/{{module}}/config.yaml - store ALL config values in memory for use throughout the session. +2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at @{.bmad}/{{module}}/agents/{{name}}.md. 3. [ ] CONFIRM: The user's name from config is {user_name}. Only after all checks are complete, greet the user by name and display the menu. Acknowledge this checklist is complete in your first response. -AGENT DEFINITION: @{{bmad_folder}}/{{module}}/agents/{{name}}.md +AGENT DEFINITION: @{.bmad}/{{module}}/agents/{{name}}.md """ diff --git a/tools/cli/installers/lib/ide/templates/gemini-task-command.toml b/tools/cli/installers/lib/ide/templates/gemini-task-command.toml index 4a8ee6a1..a6c10647 100644 --- a/tools/cli/installers/lib/ide/templates/gemini-task-command.toml +++ b/tools/cli/installers/lib/ide/templates/gemini-task-command.toml @@ -3,10 +3,10 @@ prompt = """ Execute the following BMad Method task workflow: PRE-FLIGHT CHECKLIST: -1. [ ] IMMEDIATE ACTION: Load and parse @{{bmad_folder}}/{{module}}/config.yaml. -2. [ ] IMMEDIATE ACTION: Read and load the task definition at @{{bmad_folder}}/{{module}}/tasks/{{filename}}. +1. [ ] IMMEDIATE ACTION: Load and parse @{.bmad}/{{module}}/config.yaml. +2. [ ] IMMEDIATE ACTION: Read and load the task definition at @{.bmad}/{{module}}/tasks/{{filename}}. Follow all instructions and complete the task as defined. -TASK DEFINITION: @{{bmad_folder}}/{{module}}/tasks/{{filename}} +TASK DEFINITION: @{.bmad}/{{module}}/tasks/{{filename}} """ diff --git a/tools/cli/installers/lib/ide/templates/workflow-command-template.md b/tools/cli/installers/lib/ide/templates/workflow-command-template.md index 27b55e03..4d00f3a8 100644 --- a/tools/cli/installers/lib/ide/templates/workflow-command-template.md +++ b/tools/cli/installers/lib/ide/templates/workflow-command-template.md @@ -5,7 +5,7 @@ description: '{{description}}' IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded: -1. Always LOAD the FULL @{bmad_folder}/core/tasks/workflow.xml +1. Always LOAD the FULL @.bmad/core/tasks/workflow.xml 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{{workflow_path}} 3. Pass the yaml path {{workflow_path}} as 'workflow-config' parameter to the workflow.xml instructions 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions diff --git a/tools/cli/installers/lib/modules/manager.js b/tools/cli/installers/lib/modules/manager.js index bd8e538e..23bd74d3 100644 --- a/tools/cli/installers/lib/modules/manager.js +++ b/tools/cli/installers/lib/modules/manager.js @@ -47,7 +47,7 @@ class ModuleManager { } /** - * Copy a file and replace {bmad_folder} placeholder with actual folder name + * Copy a file and replace .bmad placeholder with actual folder name * @param {string} sourcePath - Source file path * @param {string} targetPath - Target file path */ @@ -62,14 +62,14 @@ class ModuleManager { // Read the file content let content = await fs.readFile(sourcePath, 'utf8'); - // Replace escape sequence {*bmad_folder*} with literal {bmad_folder} - if (content.includes('{*bmad_folder*}')) { - content = content.replaceAll('{*bmad_folder*}', '{bmad_folder}'); + // Replace escape sequence .bmad with literal .bmad + if (content.includes('.bmad')) { + content = content.replaceAll('.bmad', '.bmad'); } - // Replace {bmad_folder} placeholder with actual folder name - if (content.includes('{bmad_folder}')) { - content = content.replaceAll('{bmad_folder}', this.bmadFolderName); + // Replace .bmad placeholder with actual folder name + if (content.includes('.bmad')) { + content = content.replaceAll('.bmad', this.bmadFolderName); } // Write to target with replaced content @@ -695,8 +695,8 @@ class ModuleManager { // IMPORTANT: Replace escape sequence and placeholder BEFORE parsing YAML // Otherwise parsing will fail on the placeholder - yamlContent = yamlContent.replaceAll('{*bmad_folder*}', '{bmad_folder}'); - yamlContent = yamlContent.replaceAll('{bmad_folder}', this.bmadFolderName); + yamlContent = yamlContent.replaceAll('.bmad', '.bmad'); + yamlContent = yamlContent.replaceAll('.bmad', this.bmadFolderName); try { // First check if web_bundle exists by parsing @@ -853,9 +853,9 @@ class ModuleManager { // Compile with customizations if any const { xml } = compileAgent(yamlContent, {}, agentName, relativePath, { config: this.coreConfig }); - // Replace {bmad_folder} placeholder if needed - if (xml.includes('{bmad_folder}') && this.bmadFolderName) { - const processedXml = xml.replaceAll('{bmad_folder}', this.bmadFolderName); + // Replace .bmad placeholder if needed + if (xml.includes('.bmad') && this.bmadFolderName) { + const processedXml = xml.replaceAll('.bmad', this.bmadFolderName); await fs.writeFile(targetMdPath, processedXml, 'utf8'); } else { await fs.writeFile(targetMdPath, xml, 'utf8'); @@ -872,7 +872,7 @@ class ModuleManager { const projectDir = path.dirname(bmadDir); const resolvedSidecarFolder = agentSidecarFolder .replaceAll('{project-root}', projectDir) - .replaceAll('{bmad_folder}', path.basename(bmadDir)); + .replaceAll('.bmad', path.basename(bmadDir)); // Create sidecar directory for this agent const agentSidecarDir = path.join(resolvedSidecarFolder, agentName); @@ -1030,10 +1030,10 @@ class ModuleManager { const installWorkflowPath = item['workflow-install']; // Where to copy TO // Parse SOURCE workflow path - // Handle both {bmad_folder} placeholder and hardcoded 'bmad' - // Example: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml + // Handle both .bmad placeholder and hardcoded 'bmad' + // Example: {project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml // Or: {project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml - const sourceMatch = sourceWorkflowPath.match(/\{project-root\}\/(?:\{bmad_folder\}|bmad)\/([^/]+)\/workflows\/(.+)/); + const sourceMatch = sourceWorkflowPath.match(/\{project-root\}\/(?:\.bmad)\/([^/]+)\/workflows\/(.+)/); if (!sourceMatch) { console.warn(chalk.yellow(` Could not parse workflow path: ${sourceWorkflowPath}`)); continue; @@ -1042,9 +1042,9 @@ class ModuleManager { const [, sourceModule, sourceWorkflowSubPath] = sourceMatch; // Parse INSTALL workflow path - // Handle both {bmad_folder} placeholder and hardcoded 'bmad' - // Example: {project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml - const installMatch = installWorkflowPath.match(/\{project-root\}\/(?:\{bmad_folder\}|bmad)\/([^/]+)\/workflows\/(.+)/); + // Handle.bmad + // Example: {project-root}/.bmad/bmgd/workflows/4-production/create-story/workflow.yaml + const installMatch = installWorkflowPath.match(/\{project-root\}\/(\.bmad)\/([^/]+)\/workflows\/(.+)/); if (!installMatch) { console.warn(chalk.yellow(` Could not parse workflow-install path: ${installWorkflowPath}`)); continue; @@ -1096,9 +1096,9 @@ class ModuleManager { async updateWorkflowConfigSource(workflowYamlPath, newModuleName) { let yamlContent = await fs.readFile(workflowYamlPath, 'utf8'); - // Replace config_source: "{project-root}/{bmad_folder}/OLD_MODULE/config.yaml" - // with config_source: "{project-root}/{bmad_folder}/NEW_MODULE/config.yaml" - // Note: At this point {bmad_folder} has already been replaced with actual folder name + // Replace config_source: "{project-root}/.bmad/OLD_MODULE/config.yaml" + // with config_source: "{project-root}/.bmad/NEW_MODULE/config.yaml" + // Note: At this point .bmad has already been replaced with actual folder name const configSourcePattern = /config_source:\s*["']?\{project-root\}\/[^/]+\/[^/]+\/config\.yaml["']?/g; const newConfigSource = `config_source: "{project-root}/${this.bmadFolderName}/${newModuleName}/config.yaml"`; diff --git a/tools/cli/lib/agent/compiler.js b/tools/cli/lib/agent/compiler.js index fbb72ded..d381b34e 100644 --- a/tools/cli/lib/agent/compiler.js +++ b/tools/cli/lib/agent/compiler.js @@ -59,7 +59,7 @@ function buildSimpleActivation(criticalActions = [], menuItems = [], deploymentT // Standard steps activation += ` Load persona from this current agent file (already in context)\n`; - activation += ` Load and read {project-root}/{bmad_folder}/core/config.yaml to get {user_name}, {communication_language}, {output_folder}\n`; + activation += ` Load and read {project-root}/.bmad/core/config.yaml to get {user_name}, {communication_language}, {output_folder}\n`; activation += ` Remember: user's name is {user_name}\n`; // Agent-specific steps from critical_actions @@ -119,7 +119,7 @@ function buildSimpleActivation(criticalActions = [], menuItems = [], deploymentT if (usedHandlers.has('workflow')) { activation += ` When menu item has: workflow="path/to/workflow.yaml" - 1. CRITICAL: Always LOAD {project-root}/{bmad_folder}/core/tasks/workflow.xml + 1. CRITICAL: Always LOAD {project-root}/.bmad/core/tasks/workflow.xml 2. Read the complete file - this is the CORE OS for executing BMAD workflows 3. Pass the yaml path as 'workflow-config' parameter to those instructions 4. Execute workflow.xml instructions precisely following all steps @@ -150,7 +150,7 @@ function buildSimpleActivation(criticalActions = [], menuItems = [], deploymentT if (usedHandlers.has('validate-workflow')) { activation += ` When menu item has: validate-workflow="path/to/workflow.yaml" - 1. CRITICAL: Always LOAD {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml + 1. CRITICAL: Always LOAD {project-root}/.bmad/core/tasks/validate-workflow.xml 2. Read the complete file - this is the CORE OS for validating BMAD workflows 3. Pass the workflow.yaml path as 'workflow' parameter to those instructions 4. Pass any checklist.md from the workflow location as 'checklist' parameter if available diff --git a/tools/cli/lib/agent/installer.js b/tools/cli/lib/agent/installer.js index 2c9e30eb..14140615 100644 --- a/tools/cli/lib/agent/installer.js +++ b/tools/cli/lib/agent/installer.js @@ -273,7 +273,7 @@ function installAgent(agentInfo, answers, targetPath, options = {}) { // Resolve path variables const resolvedSidecarFolder = agentSidecarFolder .replaceAll('{project-root}', options.projectRoot || process.cwd()) - .replaceAll('{bmad_folder}', options.bmadFolder || '.bmad'); + .replaceAll('.bmad', options.bmadFolder || '.bmad'); // Create sidecar directory for this agent const agentSidecarDir = path.join(resolvedSidecarFolder, agentFolderName); @@ -407,7 +407,7 @@ function detectBmadProject(targetPath) { // Walk up directory tree looking for BMAD installation while (checkPath !== root) { - const possibleNames = ['.bmad', 'bmad']; + const possibleNames = ['.bmad']; for (const name of possibleNames) { const bmadFolder = path.join(checkPath, name); const cfgFolder = path.join(bmadFolder, '_cfg'); diff --git a/tools/cli/lib/ui.js b/tools/cli/lib/ui.js index 71c2d5aa..f0ef3f99 100644 --- a/tools/cli/lib/ui.js +++ b/tools/cli/lib/ui.js @@ -136,7 +136,7 @@ class UI { // Create the bmad directory based on core config const path = require('node:path'); const fs = require('fs-extra'); - const bmadFolderName = coreConfig.bmad_folder || 'bmad'; + const bmadFolderName = '.bmad'; const bmadDir = path.join(confirmedDirectory, bmadFolderName); await fs.ensureDir(bmadDir); @@ -810,103 +810,108 @@ class UI { */ async promptCustomContentLocation() { try { - CLIUtils.displaySection('Custom Content', 'Optional: Add custom agents, workflows, and modules'); - - const { hasCustomContent } = await inquirer.prompt([ - { - type: 'list', - name: 'hasCustomContent', - message: 'Do you have custom content to install?', - choices: [ - { name: 'No (skip custom content)', value: 'none' }, - { name: 'Enter a directory path', value: 'directory' }, - { name: 'Enter a URL', value: 'url' }, - ], - default: 'none', - }, - ]); - - if (hasCustomContent === 'none') { - return { hasCustomContent: false }; - } - - if (hasCustomContent === 'url') { - console.log(chalk.yellow('\nURL-based custom content installation is coming soon!')); - console.log(chalk.cyan('For now, please download your custom content and choose "Enter a directory path".\n')); - return { hasCustomContent: false }; - } - - if (hasCustomContent === 'directory') { - let customPath; - while (!customPath) { - let expandedPath; - const { directory } = await inquirer.prompt([ - { - type: 'input', - name: 'directory', - message: 'Enter directory to search for custom content (will scan subfolders):', - default: process.cwd(), // Use actual current working directory - validate: async (input) => { - if (!input || input.trim() === '') { - return 'Please enter a directory path'; - } - - try { - expandedPath = this.expandUserPath(input.trim()); - } catch (error) { - return error.message; - } - - // Check if the path exists - const pathExists = await fs.pathExists(expandedPath); - if (!pathExists) { - return 'Directory does not exist'; - } - - return true; - }, - }, - ]); - - // Now expand the path for use after the prompt - expandedPath = this.expandUserPath(directory.trim()); - - // Check if directory has custom content - const customHandler = new CustomHandler(); - const customFiles = await customHandler.findCustomContent(expandedPath); - - if (customFiles.length === 0) { - console.log(chalk.yellow(`\nNo custom content found in ${expandedPath}`)); - - const { tryAgain } = await inquirer.prompt([ - { - type: 'confirm', - name: 'tryAgain', - message: 'Try a different directory?', - default: true, - }, - ]); - - if (tryAgain) { - continue; - } else { - return { hasCustomContent: false }; - } - } - - customPath = expandedPath; - console.log(chalk.green(`\nโœ“ Found ${customFiles.length} custom content item(s):`)); - for (const file of customFiles) { - const relativePath = path.relative(expandedPath, path.dirname(file)); - const folderName = path.dirname(file).split(path.sep).pop(); - console.log(chalk.dim(` โ€ข ${folderName} ${chalk.gray(`(${relativePath})`)}`)); - } - } - - return { hasCustomContent: true, customPath }; - } - + // Skip custom content installation - always return false return { hasCustomContent: false }; + + // TODO: Custom content installation temporarily disabled + // CLIUtils.displaySection('Custom Content', 'Optional: Add custom agents, workflows, and modules'); + + // const { hasCustomContent } = await inquirer.prompt([ + // { + // type: 'list', + // name: 'hasCustomContent', + // message: 'Do you have custom content to install?', + // choices: [ + // { name: 'No (skip custom content)', value: 'none' }, + // { name: 'Enter a directory path', value: 'directory' }, + // { name: 'Enter a URL', value: 'url' }, + // ], + // default: 'none', + // }, + // ]); + + // if (hasCustomContent === 'none') { + // return { hasCustomContent: false }; + // } + + // TODO: Custom content installation temporarily disabled + // if (hasCustomContent === 'url') { + // console.log(chalk.yellow('\nURL-based custom content installation is coming soon!')); + // console.log(chalk.cyan('For now, please download your custom content and choose "Enter a directory path".\n')); + // return { hasCustomContent: false }; + // } + + // if (hasCustomContent === 'directory') { + // let customPath; + // while (!customPath) { + // let expandedPath; + // const { directory } = await inquirer.prompt([ + // { + // type: 'input', + // name: 'directory', + // message: 'Enter directory to search for custom content (will scan subfolders):', + // default: process.cwd(), // Use actual current working directory + // validate: async (input) => { + // if (!input || input.trim() === '') { + // return 'Please enter a directory path'; + // } + + // try { + // expandedPath = this.expandUserPath(input.trim()); + // } catch (error) { + // return error.message; + // } + + // // Check if the path exists + // const pathExists = await fs.pathExists(expandedPath); + // if (!pathExists) { + // return 'Directory does not exist'; + // } + + // return true; + // }, + // }, + // ]); + + // // Now expand the path for use after the prompt + // expandedPath = this.expandUserPath(directory.trim()); + + // // Check if directory has custom content + // const customHandler = new CustomHandler(); + // const customFiles = await customHandler.findCustomContent(expandedPath); + + // if (customFiles.length === 0) { + // console.log(chalk.yellow(`\nNo custom content found in ${expandedPath}`)); + + // const { tryAgain } = await inquirer.prompt([ + // { + // type: 'confirm', + // name: 'tryAgain', + // message: 'Try a different directory?', + // default: true, + // }, + // ]); + + // if (tryAgain) { + // continue; + // } else { + // return { hasCustomContent: false }; + // } + // } + + // customPath = expandedPath; + // console.log(chalk.green(`\nโœ“ Found ${customFiles.length} custom content item(s):`)); + // for (const file of customFiles) { + // const relativePath = path.relative(expandedPath, path.dirname(file)); + // const folderName = path.dirname(file).split(path.sep).pop(); + // console.log(chalk.dim(` โ€ข ${folderName} ${chalk.gray(`(${relativePath})`)}`)); + // } + // } + + // return { hasCustomContent: true, customPath }; + // } + + // return { hasCustomContent: false }; } catch (error) { console.error(chalk.red('Error in custom content prompt:'), error); return { hasCustomContent: false }; @@ -1077,7 +1082,7 @@ class UI { * @calls checkAgentVibesInstalled(), inquirer.prompt(), chalk.green/yellow/dim() * * AI NOTE: This prompt is strategically positioned in installation flow: - * - AFTER core config (bmad_folder, user_name, etc) + * - AFTER core config (user_name, etc) * - BEFORE IDE selection (which can hang on Windows/PowerShell) * * Flow Logic: @@ -1205,129 +1210,134 @@ class UI { */ async promptCustomContentForExisting() { try { - CLIUtils.displaySection('Custom Content', 'Add new custom agents, workflows, or modules to your installation'); + // Skip custom content installation - always return false + return { hasCustomContent: false }; - const { hasCustomContent } = await inquirer.prompt([ - { - type: 'list', - name: 'hasCustomContent', - message: 'Do you want to add or update custom content?', - choices: [ - { - name: 'No, continue with current installation only', - value: false, - }, - { - name: 'Yes, I have custom content to add or update', - value: true, - }, - ], - default: false, - }, - ]); + // TODO: Custom content installation temporarily disabled + // CLIUtils.displaySection('Custom Content', 'Add new custom agents, workflows, or modules to your installation'); - if (!hasCustomContent) { - return { hasCustomContent: false }; - } + // const { hasCustomContent } = await inquirer.prompt([ + // { + // type: 'list', + // name: 'hasCustomContent', + // message: 'Do you want to add or update custom content?', + // choices: [ + // { + // name: 'No, continue with current installation only', + // value: false, + // }, + // { + // name: 'Yes, I have custom content to add or update', + // value: true, + // }, + // ], + // default: false, + // }, + // ]); - // Get directory path - const { customPath } = await inquirer.prompt([ - { - type: 'input', - name: 'customPath', - message: 'Enter directory to search for custom content (will scan subfolders):', - default: process.cwd(), - validate: async (input) => { - if (!input || input.trim() === '') { - return 'Please enter a directory path'; - } + // if (!hasCustomContent) { + // return { hasCustomContent: false }; + // } - // Normalize and check if path exists - const expandedPath = CLIUtils.expandPath(input.trim()); - const pathExists = await fs.pathExists(expandedPath); - if (!pathExists) { - return 'Directory does not exist'; - } + // TODO: Custom content installation temporarily disabled + // // Get directory path + // const { customPath } = await inquirer.prompt([ + // { + // type: 'input', + // name: 'customPath', + // message: 'Enter directory to search for custom content (will scan subfolders):', + // default: process.cwd(), + // validate: async (input) => { + // if (!input || input.trim() === '') { + // return 'Please enter a directory path'; + // } - // Check if it's actually a directory - const stats = await fs.stat(expandedPath); - if (!stats.isDirectory()) { - return 'Path must be a directory'; - } + // // Normalize and check if path exists + // const expandedPath = CLIUtils.expandPath(input.trim()); + // const pathExists = await fs.pathExists(expandedPath); + // if (!pathExists) { + // return 'Directory does not exist'; + // } - return true; - }, - transformer: (input) => { - return CLIUtils.expandPath(input); - }, - }, - ]); + // // Check if it's actually a directory + // const stats = await fs.stat(expandedPath); + // if (!stats.isDirectory()) { + // return 'Path must be a directory'; + // } - const resolvedPath = CLIUtils.expandPath(customPath); + // return true; + // }, + // transformer: (input) => { + // return CLIUtils.expandPath(input); + // }, + // }, + // ]); - // Find custom content - const customHandler = new CustomHandler(); - const customFiles = await customHandler.findCustomContent(resolvedPath); + // const resolvedPath = CLIUtils.expandPath(customPath); - if (customFiles.length === 0) { - console.log(chalk.yellow(`\nNo custom content found in ${resolvedPath}`)); + // // Find custom content + // const customHandler = new CustomHandler(); + // const customFiles = await customHandler.findCustomContent(resolvedPath); - const { tryDifferent } = await inquirer.prompt([ - { - type: 'confirm', - name: 'tryDifferent', - message: 'Try a different directory?', - default: true, - }, - ]); + // if (customFiles.length === 0) { + // console.log(chalk.yellow(`\nNo custom content found in ${resolvedPath}`)); - if (tryDifferent) { - return await this.promptCustomContentForExisting(); - } + // const { tryDifferent } = await inquirer.prompt([ + // { + // type: 'confirm', + // name: 'tryDifferent', + // message: 'Try a different directory?', + // default: true, + // }, + // ]); - return { hasCustomContent: false }; - } + // if (tryDifferent) { + // return await this.promptCustomContentForExisting(); + // } - // Display found items - console.log(chalk.cyan(`\nFound ${customFiles.length} custom content file(s):`)); - const customContentItems = []; + // return { hasCustomContent: false }; + // } - for (const customFile of customFiles) { - const customInfo = await customHandler.getCustomInfo(customFile); - if (customInfo) { - customContentItems.push({ - name: `${chalk.cyan('โœ“')} ${customInfo.name} ${chalk.gray(`(${customInfo.relativePath})`)}`, - value: `__CUSTOM_CONTENT__${customFile}`, - checked: true, - }); - } - } + // // Display found items + // console.log(chalk.cyan(`\nFound ${customFiles.length} custom content file(s):`)); + // const customContentItems = []; - // Add option to keep existing custom content - console.log(chalk.yellow('\nExisting custom modules will be preserved unless you remove them')); + // for (const customFile of customFiles) { + // const customInfo = await customHandler.getCustomInfo(customFile); + // if (customInfo) { + // customContentItems.push({ + // name: `${chalk.cyan('โœ“')} ${customInfo.name} ${chalk.gray(`(${customInfo.relativePath})`)}`, + // value: `__CUSTOM_CONTENT__${customFile}`, + // checked: true, + // }); + // } + // } - const { selectedFiles } = await inquirer.prompt([ - { - type: 'checkbox', - name: 'selectedFiles', - message: 'Select custom content to add:', - choices: customContentItems, - pageSize: 15, - validate: (answer) => { - if (answer.length === 0) { - return 'You must select at least one item'; - } - return true; - }, - }, - ]); + // // Add option to keep existing custom content + // console.log(chalk.yellow('\nExisting custom modules will be preserved unless you remove them')); - return { - hasCustomContent: true, - customPath: resolvedPath, - selected: true, - selectedFiles: selectedFiles, - }; + // const { selectedFiles } = await inquirer.prompt([ + // { + // type: 'checkbox', + // name: 'selectedFiles', + // message: 'Select custom content to add:', + // choices: customContentItems, + // pageSize: 15, + // validate: (answer) => { + // if (answer.length === 0) { + // return 'You must select at least one item'; + // } + // return true; + // }, + // }, + // ]); + + // return { + // hasCustomContent: true, + // customPath: resolvedPath, + // selected: true, + // selectedFiles: selectedFiles, + // }; } catch (error) { console.error(chalk.red('Error configuring custom content:'), error); return { hasCustomContent: false }; diff --git a/tools/cli/regenerate-manifests.js b/tools/cli/regenerate-manifests.js index c5a0d48b..c370497b 100644 --- a/tools/cli/regenerate-manifests.js +++ b/tools/cli/regenerate-manifests.js @@ -3,17 +3,16 @@ const { ManifestGenerator } = require('./installers/lib/core/manifest-generator' async function regenerateManifests() { const generator = new ManifestGenerator(); - const targetDir = process.argv[2] || 'z1'; - const bmadDir = path.join(process.cwd(), targetDir, 'bmad'); + const targetDir = process.argv[2]; // List of modules to include in manifests const selectedModules = ['bmb', 'bmm', 'cis']; console.log('Regenerating manifests with relative paths...'); - console.log('Target directory:', bmadDir); + console.log('Target directory: .bmad'); try { - const result = await generator.generateManifests(bmadDir, selectedModules, [], { ides: [] }); + const result = await generator.generateManifests('.bmad', selectedModules, [], { ides: [] }); console.log('โœ“ Manifests generated successfully:'); console.log(` - ${result.workflows} workflows`); console.log(` - ${result.agents} agents`); diff --git a/tools/migrate-custom-module-paths.js b/tools/migrate-custom-module-paths.js index ad82e981..843421a4 100755 --- a/tools/migrate-custom-module-paths.js +++ b/tools/migrate-custom-module-paths.js @@ -12,7 +12,7 @@ const chalk = require('chalk'); * Find BMAD directory in project */ function findBmadDir(projectDir = process.cwd()) { - const possibleNames = ['bmad', '.bmad']; + const possibleNames = ['.bmad']; for (const name of possibleNames) { const bmadDir = path.join(projectDir, name);