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.
85 lines
3.6 KiB
XML
85 lines
3.6 KiB
XML
<task id="{bmad_folder}/bmm/tasks/daily-standup.xml" name="Daily Standup">
|
|
<llm critical="true">
|
|
<i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
|
|
<i>DO NOT skip steps or change the sequence</i>
|
|
<i>HALT immediately when halt-conditions are met</i>
|
|
<i>Each action tag within a step tag is a REQUIRED action to complete that step</i>
|
|
<i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
|
|
</llm>
|
|
<flow>
|
|
<step n="1" title="Project Context Discovery">
|
|
<action>Check for stories folder at {project-root}{output_folder}/stories/</action>
|
|
<action>Find current story by identifying highest numbered story file</action>
|
|
<action>Read story status (In Progress, Ready for Review, etc.)</action>
|
|
<action>Extract agent notes from Dev Agent Record, TEA Results, PO Notes sections</action>
|
|
<action>Check for next story references from epics</action>
|
|
<action>Identify blockers from story sections</action>
|
|
</step>
|
|
|
|
<step n="2" title="Initialize Standup with Context">
|
|
<output>
|
|
🏃 DAILY STANDUP - Story-{{number}}: {{title}}
|
|
|
|
Current Sprint Status:
|
|
- Active Story: story-{{number}} ({{status}} - {{percentage}}% complete)
|
|
- Next in Queue: story-{{next-number}}: {{next-title}}
|
|
- Blockers: {{blockers-from-story}}
|
|
|
|
Team assembled based on story participants:
|
|
{{ List Agents from {project-root}/{bmad_folder}/_cfg/agent-manifest.csv }}
|
|
</output>
|
|
</step>
|
|
|
|
<step n="3" title="Structured Standup Discussion">
|
|
<action>Each agent provides three items referencing real story data</action>
|
|
<action>What I see: Their perspective on current work, citing story sections (1-2 sentences)</action>
|
|
<action>What concerns me: Issues from their domain or story blockers (1-2 sentences)</action>
|
|
<action>What I suggest: Actionable recommendations for progress (1-2 sentences)</action>
|
|
</step>
|
|
|
|
<step n="4" title="Create Standup Summary">
|
|
<output>
|
|
📋 STANDUP SUMMARY:
|
|
Key Items from Story File:
|
|
- {{completion-percentage}}% complete ({{tasks-complete}}/{{total-tasks}} tasks)
|
|
- Blocker: {{main-blocker}}
|
|
- Next: {{next-story-reference}}
|
|
|
|
Action Items:
|
|
- {{agent}}: {{action-item}}
|
|
- {{agent}}: {{action-item}}
|
|
- {{agent}}: {{action-item}}
|
|
|
|
Need extended discussion? Use *party-mode for detailed breakout.
|
|
</output>
|
|
</step>
|
|
</flow>
|
|
|
|
<agent-selection>
|
|
<context type="prd-review">
|
|
<i>Primary: Sarah (PO), Mary (Analyst), Winston (Architect)</i>
|
|
<i>Secondary: Murat (TEA), James (Dev)</i>
|
|
</context>
|
|
<context type="story-planning">
|
|
<i>Primary: Sarah (PO), Bob (SM), James (Dev)</i>
|
|
<i>Secondary: Murat (TEA)</i>
|
|
</context>
|
|
<context type="validate-architecture">
|
|
<i>Primary: Winston (Architect), James (Dev), Murat (TEA)</i>
|
|
<i>Secondary: Sarah (PO)</i>
|
|
</context>
|
|
<context type="implementation">
|
|
<i>Primary: James (Dev), Murat (TEA), Winston (Architect)</i>
|
|
<i>Secondary: Sarah (PO)</i>
|
|
</context>
|
|
</agent-selection>
|
|
|
|
<llm critical="true">
|
|
<i>This task extends party-mode with agile-specific structure</i>
|
|
<i>Time-box responses (standup = brief)</i>
|
|
<i>Focus on actionable items from real story data when available</i>
|
|
<i>End with clear next steps</i>
|
|
<i>No deep dives (suggest breakout if needed)</i>
|
|
<i>If no stories folder detected, run general standup format</i>
|
|
</llm>
|
|
</task> |