Brian Madison 1868477238 refactor(config): replace hardcoded .bmad paths with {bmad_folder} placeholder
Remove hardcoded .bmad folder references throughout documentation and source files, replacing them with the configurable {bmad_folder} placeholder. This change enables users to customize the BMAD installation folder name via configuration, improving flexibility and reducing coupling to a specific directory structure.

Changes include:
- Update all documentation to reference {bmad_folder} instead of .bmad
- Remove legacy configuration files from .bmad and .claude directories
- Update workflow.xml and CLI documentation with new placeholder syntax
2025-11-12 20:22:47 -06:00

736 B

BMAD Method - iFlow CLI Instructions

Activating Agents

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/
  3. Select: Choose the agent or task command
  4. Execute: Run to activate

Command Structure

.iflow/commands/bmad/
├── agents/     # Agent commands
└── tasks/      # Task commands

Examples

/{bmad_folder}/agents/core-dev - Activate dev agent
/{bmad_folder}/tasks/core-setup - Execute setup task

Notes

  • Commands organized by type (agents/tasks)
  • Agent activates for session
  • Similar to Crush command structure