mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
7eb52520fa
- 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.
56 lines
1.8 KiB
YAML
56 lines
1.8 KiB
YAML
# Sprint Status Template
|
|
# This is an EXAMPLE showing the expected format
|
|
# The actual file will be generated with all epics/stories from your epic files
|
|
|
|
# generated: {date}
|
|
# project: {project_name}
|
|
# project_key: {project_key}
|
|
# tracking_system: {tracking_system}
|
|
# story_location: {story_location}
|
|
|
|
# STATUS DEFINITIONS:
|
|
# ==================
|
|
# Epic Status:
|
|
# - backlog: Epic exists in epic file but not contexted
|
|
# - contexted: Next epic tech context created by *epic-tech-context (required)
|
|
#
|
|
# Story Status:
|
|
# - backlog: Story only exists in epic file
|
|
# - drafted: Story file created in stories folder by *create-story
|
|
# - ready-for-dev: Draft approved and story context created by *story-ready
|
|
# - in-progress: Developer actively working on implementation by *dev-story
|
|
# - review: Implementation complete, ready for review by *code-review
|
|
# - done: Story completed by *story-done
|
|
#
|
|
# Retrospective Status:
|
|
# - optional: Can be completed but not required
|
|
# - completed: Retrospective has been done by *retrospective
|
|
#
|
|
# WORKFLOW NOTES:
|
|
# ===============
|
|
# - Epics should be 'contexted' before stories can be 'drafted'
|
|
# - SM typically drafts next story ONLY after previous one is 'done' to incorporate learnings
|
|
# - Dev moves story to 'review', dev reviews, then Dev moves to 'done'
|
|
|
|
# EXAMPLE STRUCTURE (your actual epics/stories will replace these):
|
|
|
|
generated: 05-06-2-2025 21:30
|
|
project: My Awesome Project
|
|
project_key: jira-1234
|
|
tracking_system: file-system
|
|
story_location: "{project-root}/docs/stories"
|
|
|
|
development_status:
|
|
epic-1: contexted
|
|
1-1-user-authentication: done
|
|
1-2-account-management: drafted
|
|
1-3-plant-data-model: backlog
|
|
1-4-add-plant-manual: backlog
|
|
epic-1-retrospective: optional
|
|
|
|
epic-2: backlog
|
|
2-1-personality-system: backlog
|
|
2-2-chat-interface: backlog
|
|
2-3-llm-integration: backlog
|
|
epic-2-retrospective: optional
|