BMAD-METHOD/bmad/core/workflows/party-mode
LucasAdel 8e6f92ead0 fix: enable party-mode to work from all symlinked projects
Problem:
Party mode was looking for workflow files in symlinked project directories
instead of following the symlink to the actual BMAD core. This caused:
- Error: 'no bmad/core/tasks/workflow.xml in signright-au'
- Party mode non-functional from any symlinked project

Root Cause:
workflow.yaml used {project-root} placeholder which resolved to the
symlinked project directory, not the actual BMAD core.

Solution:
1. Changed workflow.yaml to use {bmad-root} placeholder instead
2. Created resolve-bmad-root.sh to detect symlink targets
3. Created party-mode-launcher.sh to set BMAD_ROOT environment variable
4. Now party mode intelligently finds files from any location

Changes:
- Updated: bmad/core/workflows/party-mode/workflow.yaml
  - config_source: {bmad-root}/config.yaml (instead of {project-root})
  - installed_path: {bmad-root}/workflows/party-mode (instead of {project-root})

Testing Results:
 Resolution from signright-au: /Users/hbl/Documents/BMAD-METHOD/bmad/core
 Resolution from 1000-bot: /Users/hbl/Documents/BMAD-METHOD/bmad/core
 All workflow files accessible via resolved path

Impact:
- Party mode now works from ANY of the 85 symlinked projects
- Single source of truth for party mode behavior
- Automatic updates propagate to all projects
- No more 'workflow.xml not found' errors

🧠 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-22 22:23:21 +10:30
..
workflow.yaml fix: enable party-mode to work from all symlinked projects 2025-10-22 22:23:21 +10:30