Deleted the trigger map poster documentation file, which contained a comprehensive overview of the WDS presentation page and its strategic visualization. This removal is part of a broader effort to streamline documentation and focus on more relevant content for the WDS community.
Updated the trigger map documentation to remove member-specific language from the community opportunities section, enhancing clarity and focus. This change aims to streamline the presentation of opportunities available to all community members, making the information more accessible and straightforward.
Updated the trigger map documentation to shift focus from business goals to community opportunities, highlighting real-world benefits for WDS members. Key changes include rephrasing objectives to reflect member-centric outcomes such as speaking engagements, published case studies, and client project opportunities. This revision aims to clarify the value of WDS for community members and enhance understanding of how WDS success translates into career advancement and professional recognition.
Updated the trigger map documentation to emphasize the primary goal of building a community of 50 evangelists, restructuring existing objectives for better alignment with WDS adoption and community growth. Added detailed timelines and insights to clarify the connection between evangelists and overall project success, ensuring a clearer roadmap for stakeholders. This revision aims to enhance understanding of strategic priorities and their impact on user engagement.
Updated the trigger map documentation to enhance clarity and organization of business objectives. Introduced a new primary goal focused on building a core evangelist community, and restructured existing objectives to better align with WDS adoption and community growth. Added business impact statements to emphasize the connection between WDS success and company revenue opportunities. This revision aims to provide a clearer roadmap for stakeholders and enhance understanding of strategic goals.
Enhanced the trigger map documentation by introducing a strategic visualization diagram that outlines business goals, target user groups, and driving forces. Added detailed sections on how to read the diagram, key insights for development focus, critical success factors, and emotional transformation goals. This update aims to provide a comprehensive understanding of the WDS methodology and its impact on user engagement and empowerment.
Revised the WDS documentation by renaming and reorganizing files for clarity and consistency. Key changes include updating the paths for agent activation files, removing outdated content, and enhancing the installation and quick start guides. Added a formal positioning statement and expanded the target user profiles to better reflect the intended audience. Improved the trigger mapping instructions with new diagram formatting rules and visual elements to enhance user understanding. This update aims to streamline the onboarding process and improve overall user experience.
Major improvements:
- All agents now use consistent 2-letter menu codes (compound triggers)
- Phase 1-3 workflows updated to use planning_artifacts folder
- Windows installer fixed with inquirer multiselection resolution
- Chat and party mode auto-injected into all agents
- All agents pass comprehensive validation checks
- Restored agent files from Docusaurus merge
* fix: restore agent files accidentally modified in Docusaurus merge
Restores 25 agent files to their pre-merge state:
- Trigger format with shortcuts (WS, CH, BP, etc.) restored
- Fuzzy matching syntax restored
- BMB module: restores separate agent-builder, module-builder,
workflow-builder agents; removes consolidated bmad-builder
Also updates test to match restored trigger format.
Note: Schema validation needs update in follow-up commit.
* fix: normalize trigger fuzzy match format for schema validation
- Add dashes to fuzzy match text to match kebab-case triggers
- Add missing 'chat' kebab in CH triggers (CH or chat or fuzzy match on chat)
- Relax schema to allow 1-3 char shortcuts and skip shortcut derivation check
- Remove compound-wrong-shortcut test fixture (no longer validated)
All 24 agent files now pass schema validation.
Revised the product brief to enhance clarity regarding design constraints and opportunities. Key changes include restructuring sections for better organization, introducing fixed layout elements, and emphasizing the flexibility within the design. Added detailed explanations of how AI can amplify expertise in design and project management, ensuring that the content is actionable and aligned with user needs.
Updated the product brief to enhance clarity and engagement by revising section titles and restructuring content. Key changes include renaming sections for better alignment with user goals, refining the use of terminology, and improving the overall flow of information. Emphasized the importance of content concepts and user action goals throughout the document to facilitate understanding and usability.
Updated the product brief to enhance clarity and engagement for both designers and entrepreneurs. Key changes include refining the core message, emphasizing the designer's evolving role, and articulating the value of WDS as a structured methodology. Adjusted language to invite leadership and responsibility, while ensuring the content resonates with both target audiences. Improved success criteria to reflect a focus on clear communication and accessible learning.
Enhanced the Hero Section of the product brief by including a reference sketch and detailed visual elements. This addition aims to improve user understanding of WDS through clear visual representation and structured content.
Deleted the "About WDS" and "Where to Go Next" markdown files to streamline the documentation and remove redundant content. This cleanup helps focus on more relevant resources for users.
Major improvements:
- Path segregation implementation across 90+ workflow files
- Windows installer fixed with inquirer v9.x upgrade
- Custom installation messages via install-messages.yaml
- Two-version auto upgrade with config preservation
- Quick-dev workflow refactor with adversarial review
- Doc site auto-generation on merge
- Streamlined personas and cleaned up documentation
* docs: remove dead links in test architecture documentation
* docs: updated test architecture documentation for clarity and consistenc
* docs: update test architecture documentation for clarity and consistency
* docs: addressed PR comments
* feat: add documentation website with Docusaurus build pipeline
* feat(docs): add AI discovery meta tags for llms.txt files
- Add global headTags with ai-terms, llms, llms-full meta tags
- Update landing page link to clarify AI context purpose
* fix(docs): restore accidentally deleted faq.md and glossary.md
Files were removed in 12dd97fe during path restructuring.
* fix(docs): update broken project-readme links to GitHub URL
* feat(schema): add compound trigger format validation
* fix(bmgd): add workflow status update to game-architecture completion
The game-architecture workflow was not updating the bmgd-workflow-status.yaml
file on completion, unlike other BMGD workflows (narrative, brainstorm-game).
Changes:
- Add step 4 "Update Workflow Status" to update create-architecture status
- Renumber subsequent steps (5-8 → 6-9)
- Add success metric for workflow status update
- Add failure condition for missing status update
* feat(bmgd): add generate-project-context workflow for game development
Adds a new workflow to create optimized project-context.md files for AI agent
consistency in game development projects.
New workflow files:
- workflow.md: Main workflow entry point
- project-context-template.md: Template for context file
- steps/step-01-discover.md: Context discovery & initialization
- steps/step-02-generate.md: Rules generation with A/P/C menus
- steps/step-03-complete.md: Finalization & optimization
Integration:
- Added generate-project-context trigger to game-architect agent menu
- Added project context creation option to game-architecture completion step
- Renumbered steps 6-9 → 7-10 to accommodate new step 6
Adapted from BMM generate-project-context with game-specific:
- Engine patterns (Unity, Unreal, Godot)
- Performance and frame budget rules
- Platform-specific requirements
- Game testing patterns
* fix(bmgd): correct workflow-status filename and add sprint-planning update
- Fix all BMGD workflows to reference bmgd-workflow-status.yaml instead of bmm-workflow-status.yaml
- Add workflow-status update to sprint-planning workflow completion
Affected workflows:
- brainstorm-game (instructions.md, step-01-init.md, step-04-complete.md)
- game-brief (instructions.md)
- narrative (instructions-narrative.md, step-11-complete.md)
- game-architecture (instructions.md)
- sprint-planning (instructions.md)
---------
Co-authored-by: Scott Jennings <scott.jennings+CIGINT@cloudimperiumgames.com>
Co-authored-by: Brian <bmadcode@gmail.com>
- Fix XML syntax error in dev-story/instructions.xml:20 (goto element)
- Fix path typo in tech-writer.agent.yaml (_bmadbmm → _bmad/bmm)
- Fix wrong route in analyst.agent.yaml (edit-agent → party-mode)
- Comment out unimplemented validate-create-story in sm.agent.yaml
- Comment out unimplemented validate-design in ux-designer.agent.yaml
- Remove misleading validate-create-story reference in create-story output
Fixes#1075
Related to #1163🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Brian <bmadcode@gmail.com>
- Updated course navigation to replace "Tutorial" with "Course" for consistency.
- Introduced new lessons on alignment signoff, including:
- Understanding alignment
- Creating alignment documents
- Negotiation and acceptance
- Securing commitment
- Enhanced project brief workflow with new templates for alignment documents and service agreements.
- Removed outdated tutorial files and streamlined project brief steps for clarity.
- Added new instructional content to guide users through the alignment process, ensuring stakeholder engagement before project initiation.
* fix(bmgd): add workflow status update to game-architecture completion
The game-architecture workflow was not updating the bmgd-workflow-status.yaml
file on completion, unlike other BMGD workflows (narrative, brainstorm-game).
Changes:
- Add step 4 "Update Workflow Status" to update create-architecture status
- Renumber subsequent steps (5-8 → 6-9)
- Add success metric for workflow status update
- Add failure condition for missing status update
* feat(bmgd): add generate-project-context workflow for game development
Adds a new workflow to create optimized project-context.md files for AI agent
consistency in game development projects.
New workflow files:
- workflow.md: Main workflow entry point
- project-context-template.md: Template for context file
- steps/step-01-discover.md: Context discovery & initialization
- steps/step-02-generate.md: Rules generation with A/P/C menus
- steps/step-03-complete.md: Finalization & optimization
Integration:
- Added generate-project-context trigger to game-architect agent menu
- Added project context creation option to game-architecture completion step
- Renumbered steps 6-9 → 7-10 to accommodate new step 6
Adapted from BMM generate-project-context with game-specific:
- Engine patterns (Unity, Unreal, Godot)
- Performance and frame budget rules
- Platform-specific requirements
- Game testing patterns
---------
Co-authored-by: Scott Jennings <scott.jennings+CIGINT@cloudimperiumgames.com>
Co-authored-by: Brian <bmadcode@gmail.com>
Brian Madison
Mårten Angner
Alex Verkhovsky
Murat K Ozcan
sjennings
Serhii