mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
- Default installation location changed to .bmad (hidden directory) for cleaner project root organization
Web Bundle Improvements:
- All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
- Advanced elicitation capabilities integrated into standalone agents
- All bundles enhanced with party mode agent manifests
- Added default-party.csv files to bmm, bmgd, and cis module teams
- The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
- New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)
Phase 4 Workflow Updates (In Progress):
- Initiated shift to separate phase 4 implementation artifacts from documentation
- Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
- Installer questions and configuration added for artifact path selection
- Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates
Additional Changes:
- New agent and action command header models for standardization
- Enhanced web-bundle-activation-steps fragment
- Updated web-bundler.js to support new structure
- VS Code settings updated for new .bmad directory
- Party mode instructions and workflow enhanced for better orchestration
IDE Installer Updates:
- Show version number of installer in cli
- improved Installer UX
- Gemini TOML Improved to have clear loading instructions with @ commands
- All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
89 lines
3.3 KiB
XML
89 lines
3.3 KiB
XML
<task id="{bmad_folder}/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
|
||
<objective>Run a checklist against a document with thorough analysis and produce a validation report</objective>
|
||
|
||
<inputs>
|
||
<input name="workflow" desc="Workflow path containing checklist.md" />
|
||
<input name="checklist" desc="Checklist to validate against (defaults to workflow's checklist.md)" />
|
||
<input name="document" desc="Document to validate (ask user if not specified)" />
|
||
</inputs>
|
||
|
||
<flow>
|
||
<step n="1" title="Setup">
|
||
<action>If checklist not provided, load checklist.md from workflow location</action>
|
||
<action>Try to fuzzy match for files similar to the input document name or if user did not provide the document. If document not
|
||
provided or unsure, ask user: "Which document should I validate?"</action>
|
||
<action>Load both the checklist and document</action>
|
||
</step>
|
||
|
||
<step n="2" title="Validate" critical="true">
|
||
<mandate>For EVERY checklist item, WITHOUT SKIPPING ANY:</mandate>
|
||
|
||
<for-each-item>
|
||
<action>Read requirement carefully</action>
|
||
<action>Search document for evidence along with any ancillary loaded documents or artifacts (quotes with line numbers)</action>
|
||
<action>Analyze deeply - look for explicit AND implied coverage</action>
|
||
|
||
<mark-as>
|
||
✓ PASS - Requirement fully met (provide evidence)
|
||
⚠ PARTIAL - Some coverage but incomplete (explain gaps)
|
||
✗ FAIL - Not met or severely deficient (explain why)
|
||
➖ N/A - Not applicable (explain reason)
|
||
</mark-as>
|
||
</for-each-item>
|
||
|
||
<critical>DO NOT SKIP ANY SECTIONS OR ITEMS</critical>
|
||
</step>
|
||
|
||
<step n="3" title="Generate Report">
|
||
<action>Create validation-report-{timestamp}.md in document's folder</action>
|
||
|
||
<report-format>
|
||
# Validation Report
|
||
|
||
**Document:** {document-path}
|
||
**Checklist:** {checklist-path}
|
||
**Date:** {timestamp}
|
||
|
||
## Summary
|
||
- Overall: X/Y passed (Z%)
|
||
- Critical Issues: {count}
|
||
|
||
## Section Results
|
||
|
||
### {Section Name}
|
||
Pass Rate: X/Y (Z%)
|
||
|
||
{For each item:}
|
||
[MARK] {Item description}
|
||
Evidence: {Quote with line# or explanation}
|
||
{If FAIL/PARTIAL: Impact: {why this matters}}
|
||
|
||
## Failed Items
|
||
{All ✗ items with recommendations}
|
||
|
||
## Partial Items
|
||
{All ⚠ items with what's missing}
|
||
|
||
## Recommendations
|
||
1. Must Fix: {critical failures}
|
||
2. Should Improve: {important gaps}
|
||
3. Consider: {minor improvements}
|
||
</report-format>
|
||
</step>
|
||
|
||
<step n="4" title="Summary for User">
|
||
<action>Present section-by-section summary</action>
|
||
<action>Highlight all critical issues</action>
|
||
<action>Provide path to saved report</action>
|
||
<action>HALT - do not continue unless user asks</action>
|
||
</step>
|
||
</flow>
|
||
|
||
<critical-rules>
|
||
<rule>NEVER skip sections - validate EVERYTHING</rule>
|
||
<rule>ALWAYS provide evidence (quotes + line numbers) for marks</rule>
|
||
<rule>Think deeply about each requirement - don't rush</rule>
|
||
<rule>Save report to document's folder automatically</rule>
|
||
<rule>HALT after presenting summary - wait for user</rule>
|
||
</critical-rules>
|
||
</task> |