mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-29 16:14:59 +00:00

Brian Madison 7eb52520fa Major Enhancements:

- 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.

2025-11-09 17:39:05 -06:00

3.9 KiB

Raw Blame History

Story Approved Workflow Instructions (DEV Agent)

The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml You MUST have already loaded and processed: {installed_path}/workflow.yaml Communicate all responses in {communication_language}

This workflow is run by DEV agent AFTER user confirms a story is approved (Definition of Done is complete) Workflow: Update story file status to Done

Use {story_path} directly Read COMPLETE story file and parse sections Extract story_key from filename or story metadata Verify Status is "review" - if not, HALT with message: "Story status must be 'review' to mark as done" MUST read COMPLETE sprint-status.yaml file from start to end to preserve order Load the FULL file: {output_folder}/sprint-status.yaml Read ALL lines from beginning to end - do not skip any content Parse the development_status section completely

Find FIRST story (reading in order from top to bottom) where: - Key matches pattern: number-number-name (e.g., "1-2-user-auth") - NOT an epic key (epic-X) or retrospective (epic-X-retrospective) - Status value equals "review"

📋 No stories with status "review" found

All stories are either still in development or already done.

Next Steps:

Run dev-story to implement stories
Run code-review if stories need review first
Check sprint-status.yaml for current story states HALT

Use the first reviewed story found Find matching story file in {story_dir} using story_key pattern Read the COMPLETE story file

Extract story_id and story_title from the story file

Find the "Status:" line (usually at the top) Update story file: Change Status to "done"

Add completion notes to Dev Agent Record section: Find "## Dev Agent Record" section and add:

### Completion Notes
**Completed:** {date}
**Definition of Done:** All acceptance criteria met, code reviewed, tests passing

Save the story file

Load the FULL file: {output_folder}/sprint-status.yaml Find development_status key matching {story_key} Verify current status is "review" (expected previous state) Update development_status[{story_key}] = "done" Save file, preserving ALL comments and structure including STATUS DEFINITIONS ⚠️ Story file updated, but could not update sprint-status: {story_key} not found

Story is marked Done in file, but sprint-status.yaml may be out of sync.

Story Approved and Marked Done, {user_name}!

✅ Story file updated → Status: done ✅ Sprint status updated: review → done

Completed Story:

ID: {story_id}
Key: {story_key}
Title: {story_title}
Completed: {date}

Next Steps:

Continue with next story in your backlog
- Run create-story for next backlog story
- Or run dev-story if ready stories exist
Check epic completion status
- Run retrospective workflow to check if epic is complete
- Epic retrospective will verify all stories are done

```

3.9 KiB Raw Blame History

Story Approved Workflow Instructions (DEV Agent)

3.9 KiB

Raw Blame History