ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

release: bump to v4.43.1

Browse Source
This commit is contained in:
github-actions[bot]
2025-09-09 23:53:00 +00:00
parent 2b247ea385
commit 4b75a1417f
35 changed files with 521 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
dist/teams/team-no-ui.txt vendored
View File

@@ -437,6 +437,7 @@ dependencies:
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
<!-- Powered by BMAD™ Core -->
# Advanced Elicitation Task
## Purpose
@@ -558,6 +559,7 @@ Choose a number (0-8) or 9 to proceed:
==================== START: .bmad-core/tasks/create-doc.md ====================
<!-- Powered by BMAD™ Core -->
# Create Document from Template (YAML Driven)
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -663,6 +665,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
<!-- Powered by BMAD™ Core -->
# KB Mode Interaction Task
## Purpose
@@ -742,6 +745,7 @@ Or ask me about anything else related to BMad-Method!
==================== START: .bmad-core/data/bmad-kb.md ====================
<!-- Powered by BMAD™ Core -->
# BMAD™ Knowledge Base
## Overview
@@ -844,6 +848,7 @@ npx bmad-method install
- **Cline**: VS Code extension with AI features
- **Roo Code**: Web-based IDE with agent support
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
- **Auggie CLI (Augment Code)**: AI-powered development environment
**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
@@ -1552,6 +1557,7 @@ Use the **expansion-creator** pack to build your own:
==================== START: .bmad-core/data/elicitation-methods.md ====================
<!-- Powered by BMAD™ Core -->
# Elicitation Methods Data
## Core Reflective Methods
@@ -1710,6 +1716,7 @@ Use the **expansion-creator** pack to build your own:
==================== START: .bmad-core/utils/workflow-management.md ====================
<!-- Powered by BMAD™ Core -->
# Workflow Management
Enables BMad orchestrator to manage and execute team workflows.
@@ -1783,6 +1790,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
<!-- Powered by BMAD™ Core -->
# Create Deep Research Prompt Task
This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -2065,6 +2073,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
==================== START: .bmad-core/tasks/document-project.md ====================
<!-- Powered by BMAD™ Core -->
# Document an Existing Project
## Purpose
@@ -2411,10 +2420,11 @@ Apply the advanced elicitation task after major sections to refine based on user
==================== END: .bmad-core/tasks/document-project.md ====================
==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
<!-- Powered by BMAD™ Core -->
---
## <!-- Powered by BMAD™ Core -->
docOutputLocation: docs/brainstorming-session-results.md
template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
---
# Facilitate Brainstorming Session Task
@@ -3502,6 +3512,7 @@ sections:
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
<!-- Powered by BMAD™ Core -->
# Brainstorming Techniques Data
## Creative Expansion
@@ -3542,6 +3553,7 @@ sections:
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
<!-- Powered by BMAD™ Core -->
# Create Brownfield Epic Task
## Purpose
@@ -3706,6 +3718,7 @@ The epic creation is successful when:
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
<!-- Powered by BMAD™ Core -->
# Create Brownfield Story Task
## Purpose
@@ -3857,6 +3870,7 @@ The story creation is successful when:
==================== START: .bmad-core/tasks/correct-course.md ====================
<!-- Powered by BMAD™ Core -->
# Correct Course Task
## Purpose
@@ -3931,6 +3945,7 @@ The story creation is successful when:
==================== START: .bmad-core/tasks/execute-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Checklist Validation Task
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -4021,6 +4036,7 @@ The LLM will:
==================== START: .bmad-core/tasks/shard-doc.md ====================
<!-- Powered by BMAD™ Core -->
# Document Sharding Task
## Purpose
@@ -4700,6 +4716,7 @@ sections:
==================== START: .bmad-core/checklists/change-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Change Navigation Checklist
**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
@@ -4886,6 +4903,7 @@ Keep it action-oriented and forward-looking.]]
==================== START: .bmad-core/checklists/pm-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Product Manager (PM) Requirements Checklist
This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
@@ -5260,6 +5278,7 @@ After presenting the report, ask if the user wants:
==================== START: .bmad-core/data/technical-preferences.md ====================
<!-- Powered by BMAD™ Core -->
# User-Defined Preferred Patterns and Preferences
None Listed
@@ -6031,8 +6050,8 @@ sections:
- **UI/UX Consistency:** {{ui_compatibility}}
- **Performance Impact:** {{performance_constraints}}
- id: tech-stack-alignment
title: Tech Stack Alignment
- id: tech-stack
title: Tech Stack
instruction: |
Ensure new components align with existing technology choices:
@@ -6194,8 +6213,8 @@ sections:
**Error Handling:** {{error_handling_strategy}}
- id: source-tree-integration
title: Source Tree Integration
- id: source-tree
title: Source Tree
instruction: |
Define how new code will integrate with existing project structure:
@@ -6264,7 +6283,7 @@ sections:
**Monitoring:** {{monitoring_approach}}
- id: coding-standards
title: Coding Standards and Conventions
title: Coding Standards
instruction: |
Ensure new code follows existing project conventions:
@@ -7450,6 +7469,7 @@ sections:
==================== START: .bmad-core/checklists/architect-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Architect Solution Validation Checklist
This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
@@ -7892,6 +7912,7 @@ After presenting the report, ask the user if they would like detailed analysis o
==================== START: .bmad-core/tasks/validate-next-story.md ====================
<!-- Powered by BMAD™ Core -->
# Validate Next Story Task
## Purpose
@@ -7913,7 +7934,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
### 1. Template Completeness Validation
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template
- Load `.bmad-core/templates/story-tmpl.yaml` and extract all section headings from the template
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
- **Agent section verification**: Confirm all sections from template exist for future agent use
@@ -8171,6 +8192,7 @@ sections:
==================== START: .bmad-core/checklists/po-master-checklist.md ====================
<!-- Powered by BMAD™ Core -->
# Product Owner (PO) Master Validation Checklist
This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
@@ -8722,7 +8744,7 @@ workflow:
- Dev Agent (New Chat): Address remaining items
- Return to QA for final approval
- repeat_development_cycle:
- step: repeat_development_cycle
action: continue_for_all_stories
notes: |
Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -8739,7 +8761,7 @@ workflow:
- Validate epic was completed correctly
- Document learnings and improvements
- workflow_end:
- step: workflow_end
action: project_complete
notes: |
All stories implemented and reviewed!
@@ -8924,7 +8946,7 @@ workflow:
- Dev Agent (New Chat): Address remaining items
- Return to QA for final approval
- repeat_development_cycle:
- step: repeat_development_cycle
action: continue_for_all_stories
notes: |
Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -8941,7 +8963,7 @@ workflow:
- Validate epic was completed correctly
- Document learnings and improvements
- workflow_end:
- step: workflow_end
action: project_complete
notes: |
All stories implemented and reviewed!