mirror of
https://github.com/bmad-code-org/BMAD-METHOD.git
synced 2026-01-30 04:32:02 +00:00
12d3492e0c
* feat: add link auditor tools and fix broken docs links - Add audit-doc-links.js to scan docs for broken links with auto-resolution - Add fix-doc-links.js to apply suggested fixes (dry-run by default) - Remove stale "Back to Core Concepts" breadcrumb links - Update BMad acronym to "Breakthrough Method of Agile AI Driven Development" - Update README links to docs.bmad-method.org - Simplify upgrade callout in getting-started tutorial Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: reorganize docs structure and archive v4 tutorial - Remove unused section index files (tutorials, how-to, explanation, reference) - Move getting-started-bmadv4.md to _archive - Update quick-start-bmgd.md to remove archived file reference - Update upgrade-to-v6.md - Update astro.config.mjs for new structure Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: ignore underscore directories in link checker Update check-doc-links.js to skip _archive, _planning, and other underscore-prefixed directories when validating links. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: add v4 users section to README Add links to v4 documentation archive and upgrade guide for users migrating from previous versions. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat: convert docs to site-relative links and add validation tools - Convert all relative links (./ ../) to site-relative paths (/path/) - Strip .md extensions and use trailing slashes for Astro/Starlight - Add fix-doc-links.js to convert relative links to site-relative - Add validate-doc-links.js to check links point to existing files - Remove old audit-doc-links.js and check-doc-links.js - Update build-docs.js to use new validation script - Add npm scripts: docs:fix-links, docs:validate-links - Update style guide with validation steps Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: standardize acronym to BMad across documentation Replace incorrect "BMAD" with correct "BMad" in text and frontmatter while preserving "BMAD-METHOD" in GitHub URLs. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: fix BMad acronym and remove draft README - Correct acronym to "Breakthrough Method of Agile AI Driven Development" - Remove unused README-draft.md Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: standardize BMad acronym in README Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: standardize FAQ format across all FAQ pages - Add TOC with jump links under "## Questions" - Use ### headers for questions (no Q: prefix) - Direct answers without **A:** prefix - Remove horizontal rules and "Related Documentation" sections - End each FAQ with issue/Discord CTA - Update style guide with new FAQ guidelines - Delete redundant faq/index.md (sidebar handles navigation) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: use repo-relative links with .md for GitHub compatibility Convert all documentation links to repo-relative format (/docs/path/file.md) so they work when browsing on GitHub. The rehype plugin strips /docs/ prefix and converts .md to trailing slash at build time for Astro/Starlight. - Update rehype-markdown-links.js to strip /docs/ prefix from absolute paths - Update fix-doc-links.js to generate /docs/ prefixed paths with .md extension - Convert 217 links across 64 files to new format Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: handle /docs/ prefix in link validator Update resolveLink to strip /docs/ prefix from repo-relative links before checking if files exist. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: restore FAQ index page Re-add the FAQ index page that was accidentally deleted, with updated repo-relative link format. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: Alex Verkhovsky <alexey.verkhovsky@gmail.com>
2.7 KiB
2.7 KiB
title, description
| title | description |
|---|---|
| How to Set Up Party Mode | How to set up and use Party Mode for multi-agent collaboration |
Use Party Mode to orchestrate dynamic multi-agent conversations with your entire BMad team.
When to Use This
- Exploring complex topics that benefit from diverse expert perspectives
- Brainstorming with agents who can build on each other's ideas
- Getting comprehensive views across multiple domains
- Strategic decisions with trade-offs
Prerequisites
- BMad Method installed with multiple agents
- Any agent loaded that supports party mode
Steps
1. Load Any Agent
Start with any agent that supports party mode (most do).
2. Start Party Mode
*party-mode
Or use the full path:
/bmad:core:workflows:party-mode
3. Introduce Your Topic
Present a topic or question for the group to discuss:
I'm trying to decide between a monolithic architecture
and microservices for our new platform.
4. Engage with the Discussion
The facilitator will:
- Select 2-3 most relevant agents based on expertise
- Let agents respond in character
- Enable natural cross-talk and debate
- Continue until you choose to exit
5. Exit When Ready
Type "exit" or "done" to conclude the session. Participating agents will say personalized farewells.
What Happens
- Agent Roster - Party Mode loads your complete agent roster
- Introduction - Available team members are introduced
- Topic Analysis - The facilitator analyzes your topic
- Agent Selection - 2-3 most relevant agents are selected
- Discussion - Agents respond, reference each other, engage in cross-talk
- Exit - Session concludes with farewells
Example Party Compositions
Product Strategy
- PM + Innovation Strategist (CIS) + Analyst
Technical Design
- Architect + Creative Problem Solver (CIS) + Game Architect
User Experience
- UX Designer + Design Thinking Coach (CIS) + Storyteller (CIS)
Quality Assessment
- TEA + DEV + Architect
Key Features
- Intelligent agent selection - Selects based on expertise needed
- Authentic personalities - Each agent maintains their unique voice
- Natural cross-talk - Agents reference and build on each other
- Optional TTS - Voice configurations for each agent
- Graceful exit - Personalized farewells
Tips
- Be specific about your topic for better agent selection
- Let the conversation flow naturally
- Ask follow-up questions to go deeper
- Take notes on key insights
- Use for strategic decisions, not routine tasks
Related
- Party Mode - Understanding Party Mode
- Agent Roles - Available agents