fix: documentation and trademark updates
This commit is contained in:
67
dist/teams/team-all.txt
vendored
67
dist/teams/team-all.txt
vendored
@@ -40,6 +40,7 @@ These references map directly to bundle sections:
|
||||
|
||||
|
||||
==================== START: .bmad-core/agent-teams/team-all.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
bundle:
|
||||
name: Team All
|
||||
icon: 👥
|
||||
@@ -654,6 +655,7 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/ux-expert.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -774,6 +776,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -878,6 +881,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
@@ -956,11 +960,12 @@ Or ask me about anything else related to BMad-Method!
|
||||
==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
# BMad Knowledge Base
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
|
||||
### Key Features
|
||||
|
||||
@@ -1059,7 +1064,7 @@ npx bmad-method install
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
|
||||
**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.
|
||||
**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.
|
||||
|
||||
**Verify Installation**:
|
||||
|
||||
@@ -1067,7 +1072,7 @@ npx bmad-method install
|
||||
- IDE-specific integration files created
|
||||
- All agent commands/rules/modes available
|
||||
|
||||
**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
|
||||
### Environment Selection Guide
|
||||
|
||||
@@ -1311,7 +1316,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
|
||||
### System Overview
|
||||
|
||||
The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
|
||||
### Key Architectural Components
|
||||
|
||||
@@ -1666,7 +1671,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
|
||||
- **Keep conversations focused** - One agent, one task per conversation
|
||||
- **Review everything** - Always review and approve before marking complete
|
||||
|
||||
## Contributing to BMad-Method
|
||||
## Contributing to BMAD-METHOD™
|
||||
|
||||
### Quick Contribution Guidelines
|
||||
|
||||
@@ -1698,7 +1703,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
|
||||
|
||||
### What Are Expansion Packs?
|
||||
|
||||
Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
|
||||
### Why Use Expansion Packs?
|
||||
|
||||
@@ -1765,6 +1770,7 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
@@ -1922,6 +1928,7 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/elicitation-methods.md ====================
|
||||
|
||||
==================== START: .bmad-core/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
@@ -1994,6 +2001,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
==================== END: .bmad-core/utils/workflow-management.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -2275,6 +2283,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -2621,6 +2630,7 @@ 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 -->
|
||||
---
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
|
||||
@@ -2915,10 +2925,11 @@ sections:
|
||||
content: |
|
||||
---
|
||||
|
||||
*Session facilitated using the BMAD-METHOD brainstorming framework*
|
||||
*Session facilitated using the BMAD-METHOD™ brainstorming framework*
|
||||
==================== END: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: competitor-analysis-template-v2
|
||||
name: Competitive Analysis Report
|
||||
@@ -3228,6 +3239,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/market-research-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: market-research-template-v2
|
||||
name: Market Research Report
|
||||
@@ -3483,6 +3495,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/market-research-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/project-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: project-brief-template-v2
|
||||
name: Project Brief
|
||||
@@ -3707,6 +3720,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/project-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
@@ -3746,6 +3760,7 @@ sections:
|
||||
==================== END: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -3835,6 +3850,7 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: architecture-template-v2
|
||||
name: Architecture Document
|
||||
@@ -4488,6 +4504,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-architecture-template-v2
|
||||
name: Brownfield Enhancement Architecture
|
||||
@@ -4967,6 +4984,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: frontend-architecture-template-v2
|
||||
name: Frontend Architecture Document
|
||||
@@ -5188,6 +5206,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: fullstack-architecture-template-v2
|
||||
name: Fullstack Architecture Document
|
||||
@@ -6014,6 +6033,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -6455,12 +6475,14 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
==================== END: .bmad-core/checklists/architect-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
==================== END: .bmad-core/data/technical-preferences.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/apply-qa-fixes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# apply-qa-fixes
|
||||
|
||||
Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.
|
||||
@@ -6612,6 +6634,7 @@ Fix plan:
|
||||
==================== END: .bmad-core/tasks/apply-qa-fixes.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -6749,6 +6772,7 @@ Provide a structured validation report including:
|
||||
==================== END: .bmad-core/tasks/validate-next-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
@@ -6846,6 +6870,7 @@ Be honest - it's better to flag issues now than have them discovered later.]]
|
||||
==================== END: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
@@ -7009,6 +7034,7 @@ The epic creation is successful when:
|
||||
==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -7159,6 +7185,7 @@ The story creation is successful when:
|
||||
==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -7232,6 +7259,7 @@ The story creation is successful when:
|
||||
==================== END: .bmad-core/tasks/correct-course.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -7420,6 +7448,7 @@ Document sharded successfully:
|
||||
==================== END: .bmad-core/tasks/shard-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-prd-template-v2
|
||||
name: Brownfield Enhancement PRD
|
||||
@@ -7703,6 +7732,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/prd-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: prd-template-v2
|
||||
name: Product Requirements Document
|
||||
@@ -7908,6 +7938,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/prd-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -8093,6 +8124,7 @@ Keep it action-oriented and forward-looking.]]
|
||||
==================== END: .bmad-core/checklists/change-checklist.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -8466,6 +8498,7 @@ After presenting the report, ask if the user wants:
|
||||
==================== END: .bmad-core/checklists/pm-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: story-template-v2
|
||||
name: Story Document
|
||||
@@ -8606,6 +8639,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -9041,6 +9075,7 @@ After presenting the report, ask if the user wants:
|
||||
==================== END: .bmad-core/checklists/po-master-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/nfr-assess.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# nfr-assess
|
||||
|
||||
Quick NFR validation focused on the core four: security, performance, reliability, maintainability.
|
||||
@@ -9387,6 +9422,7 @@ performance_deep_dive:
|
||||
==================== END: .bmad-core/tasks/nfr-assess.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/qa-gate.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# qa-gate
|
||||
|
||||
Create or update a quality gate decision file for a story based on review findings.
|
||||
@@ -9551,6 +9587,7 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
|
||||
==================== END: .bmad-core/tasks/qa-gate.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/review-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# review-story
|
||||
|
||||
Perform a comprehensive test architecture review with quality gate decision. This adaptive, risk-aware review creates both a story update and a detailed gate file.
|
||||
@@ -9868,6 +9905,7 @@ After review:
|
||||
==================== END: .bmad-core/tasks/review-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/risk-profile.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# risk-profile
|
||||
|
||||
Generate a comprehensive risk assessment matrix for a story implementation using probability × impact analysis.
|
||||
@@ -10224,6 +10262,7 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
|
||||
==================== END: .bmad-core/tasks/risk-profile.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/test-design.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# test-design
|
||||
|
||||
Create comprehensive test scenarios with appropriate test level recommendations for story implementation.
|
||||
@@ -10401,6 +10440,7 @@ Before finalizing, verify:
|
||||
==================== END: .bmad-core/tasks/test-design.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/trace-requirements.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# trace-requirements
|
||||
|
||||
Map story requirements to test cases using Given-When-Then patterns for comprehensive traceability.
|
||||
@@ -10668,6 +10708,7 @@ Trace matrix: qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md
|
||||
==================== END: .bmad-core/tasks/trace-requirements.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/qa-gate-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: qa-gate-template-v1
|
||||
name: Quality Gate Decision
|
||||
@@ -10773,6 +10814,7 @@ optional_fields_examples:
|
||||
==================== END: .bmad-core/templates/qa-gate-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -10888,6 +10930,7 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
||||
==================== END: .bmad-core/tasks/create-next-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Story Draft Checklist
|
||||
|
||||
The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
|
||||
@@ -11044,6 +11087,7 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
|
||||
==================== END: .bmad-core/checklists/story-draft-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create AI Frontend Prompt Task
|
||||
|
||||
## Purpose
|
||||
@@ -11098,6 +11142,7 @@ You will now synthesize the inputs and the above principles into a final, compre
|
||||
==================== END: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: frontend-spec-template-v2
|
||||
name: UI/UX Specification
|
||||
@@ -11450,6 +11495,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/brownfield-fullstack.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: brownfield-fullstack
|
||||
name: Brownfield Full-Stack Enhancement
|
||||
@@ -11750,6 +11796,7 @@ workflow:
|
||||
==================== END: .bmad-core/workflows/brownfield-fullstack.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/brownfield-service.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: brownfield-service
|
||||
name: Brownfield Service/API Enhancement
|
||||
@@ -11940,6 +11987,7 @@ workflow:
|
||||
==================== END: .bmad-core/workflows/brownfield-service.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/brownfield-ui.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: brownfield-ui
|
||||
name: Brownfield UI/Frontend Enhancement
|
||||
@@ -12140,6 +12188,7 @@ workflow:
|
||||
==================== END: .bmad-core/workflows/brownfield-ui.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/greenfield-fullstack.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: greenfield-fullstack
|
||||
name: Greenfield Full-Stack Application Development
|
||||
@@ -12383,6 +12432,7 @@ workflow:
|
||||
==================== END: .bmad-core/workflows/greenfield-fullstack.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/greenfield-service.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: greenfield-service
|
||||
name: Greenfield Service/API Development
|
||||
@@ -12592,6 +12642,7 @@ workflow:
|
||||
==================== END: .bmad-core/workflows/greenfield-service.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/greenfield-ui.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: greenfield-ui
|
||||
name: Greenfield UI/Frontend Development
|
||||
|
||||
56
dist/teams/team-fullstack.txt
vendored
56
dist/teams/team-fullstack.txt
vendored
@@ -40,6 +40,7 @@ These references map directly to bundle sections:
|
||||
|
||||
|
||||
==================== START: .bmad-core/agent-teams/team-fullstack.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
bundle:
|
||||
name: Team Fullstack
|
||||
icon: 🚀
|
||||
@@ -489,6 +490,7 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/po.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -609,6 +611,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -713,6 +716,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
@@ -791,11 +795,12 @@ Or ask me about anything else related to BMad-Method!
|
||||
==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
# BMad Knowledge Base
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
|
||||
### Key Features
|
||||
|
||||
@@ -894,7 +899,7 @@ npx bmad-method install
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
|
||||
**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.
|
||||
**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.
|
||||
|
||||
**Verify Installation**:
|
||||
|
||||
@@ -902,7 +907,7 @@ npx bmad-method install
|
||||
- IDE-specific integration files created
|
||||
- All agent commands/rules/modes available
|
||||
|
||||
**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
|
||||
### Environment Selection Guide
|
||||
|
||||
@@ -1146,7 +1151,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
|
||||
### System Overview
|
||||
|
||||
The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
|
||||
### Key Architectural Components
|
||||
|
||||
@@ -1501,7 +1506,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
|
||||
- **Keep conversations focused** - One agent, one task per conversation
|
||||
- **Review everything** - Always review and approve before marking complete
|
||||
|
||||
## Contributing to BMad-Method
|
||||
## Contributing to BMAD-METHOD™
|
||||
|
||||
### Quick Contribution Guidelines
|
||||
|
||||
@@ -1533,7 +1538,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
|
||||
|
||||
### What Are Expansion Packs?
|
||||
|
||||
Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
|
||||
### Why Use Expansion Packs?
|
||||
|
||||
@@ -1600,6 +1605,7 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
@@ -1757,6 +1763,7 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/elicitation-methods.md ====================
|
||||
|
||||
==================== START: .bmad-core/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
@@ -1829,6 +1836,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
==================== END: .bmad-core/utils/workflow-management.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -2110,6 +2118,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -2456,6 +2465,7 @@ 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 -->
|
||||
---
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
|
||||
@@ -2750,10 +2760,11 @@ sections:
|
||||
content: |
|
||||
---
|
||||
|
||||
*Session facilitated using the BMAD-METHOD brainstorming framework*
|
||||
*Session facilitated using the BMAD-METHOD™ brainstorming framework*
|
||||
==================== END: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: competitor-analysis-template-v2
|
||||
name: Competitive Analysis Report
|
||||
@@ -3063,6 +3074,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/market-research-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: market-research-template-v2
|
||||
name: Market Research Report
|
||||
@@ -3318,6 +3330,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/market-research-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/project-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: project-brief-template-v2
|
||||
name: Project Brief
|
||||
@@ -3542,6 +3555,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/project-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
@@ -3581,6 +3595,7 @@ sections:
|
||||
==================== END: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
@@ -3744,6 +3759,7 @@ The epic creation is successful when:
|
||||
==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -3894,6 +3910,7 @@ The story creation is successful when:
|
||||
==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -3967,6 +3984,7 @@ The story creation is successful when:
|
||||
==================== END: .bmad-core/tasks/correct-course.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -4056,6 +4074,7 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -4244,6 +4263,7 @@ Document sharded successfully:
|
||||
==================== END: .bmad-core/tasks/shard-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-prd-template-v2
|
||||
name: Brownfield Enhancement PRD
|
||||
@@ -4527,6 +4547,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/prd-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: prd-template-v2
|
||||
name: Product Requirements Document
|
||||
@@ -4732,6 +4753,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/prd-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -4917,6 +4939,7 @@ Keep it action-oriented and forward-looking.]]
|
||||
==================== END: .bmad-core/checklists/change-checklist.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -5290,12 +5313,14 @@ After presenting the report, ask if the user wants:
|
||||
==================== END: .bmad-core/checklists/pm-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
==================== END: .bmad-core/data/technical-preferences.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create AI Frontend Prompt Task
|
||||
|
||||
## Purpose
|
||||
@@ -5350,6 +5375,7 @@ You will now synthesize the inputs and the above principles into a final, compre
|
||||
==================== END: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: frontend-spec-template-v2
|
||||
name: UI/UX Specification
|
||||
@@ -5702,6 +5728,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: architecture-template-v2
|
||||
name: Architecture Document
|
||||
@@ -6355,6 +6382,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-architecture-template-v2
|
||||
name: Brownfield Enhancement Architecture
|
||||
@@ -6834,6 +6862,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: frontend-architecture-template-v2
|
||||
name: Frontend Architecture Document
|
||||
@@ -7055,6 +7084,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: fullstack-architecture-template-v2
|
||||
name: Fullstack Architecture Document
|
||||
@@ -7881,6 +7911,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -8322,6 +8353,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
==================== END: .bmad-core/checklists/architect-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -8459,6 +8491,7 @@ Provide a structured validation report including:
|
||||
==================== END: .bmad-core/tasks/validate-next-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: story-template-v2
|
||||
name: Story Document
|
||||
@@ -8599,6 +8632,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -9034,6 +9068,7 @@ After presenting the report, ask if the user wants:
|
||||
==================== END: .bmad-core/checklists/po-master-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/brownfield-fullstack.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: brownfield-fullstack
|
||||
name: Brownfield Full-Stack Enhancement
|
||||
@@ -9334,6 +9369,7 @@ workflow:
|
||||
==================== END: .bmad-core/workflows/brownfield-fullstack.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/brownfield-service.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: brownfield-service
|
||||
name: Brownfield Service/API Enhancement
|
||||
@@ -9524,6 +9560,7 @@ workflow:
|
||||
==================== END: .bmad-core/workflows/brownfield-service.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/brownfield-ui.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: brownfield-ui
|
||||
name: Brownfield UI/Frontend Enhancement
|
||||
@@ -9724,6 +9761,7 @@ workflow:
|
||||
==================== END: .bmad-core/workflows/brownfield-ui.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/greenfield-fullstack.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: greenfield-fullstack
|
||||
name: Greenfield Full-Stack Application Development
|
||||
@@ -9967,6 +10005,7 @@ workflow:
|
||||
==================== END: .bmad-core/workflows/greenfield-fullstack.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/greenfield-service.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: greenfield-service
|
||||
name: Greenfield Service/API Development
|
||||
@@ -10176,6 +10215,7 @@ workflow:
|
||||
==================== END: .bmad-core/workflows/greenfield-service.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/greenfield-ui.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: greenfield-ui
|
||||
name: Greenfield UI/Frontend Development
|
||||
|
||||
40
dist/teams/team-ide-minimal.txt
vendored
40
dist/teams/team-ide-minimal.txt
vendored
@@ -40,6 +40,7 @@ These references map directly to bundle sections:
|
||||
|
||||
|
||||
==================== START: .bmad-core/agent-teams/team-ide-minimal.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
bundle:
|
||||
name: Team IDE Minimal
|
||||
icon: ⚡
|
||||
@@ -408,6 +409,7 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/qa.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -528,6 +530,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -632,6 +635,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
@@ -710,11 +714,12 @@ Or ask me about anything else related to BMad-Method!
|
||||
==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
# BMad Knowledge Base
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
|
||||
### Key Features
|
||||
|
||||
@@ -813,7 +818,7 @@ npx bmad-method install
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
|
||||
**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.
|
||||
**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.
|
||||
|
||||
**Verify Installation**:
|
||||
|
||||
@@ -821,7 +826,7 @@ npx bmad-method install
|
||||
- IDE-specific integration files created
|
||||
- All agent commands/rules/modes available
|
||||
|
||||
**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
|
||||
### Environment Selection Guide
|
||||
|
||||
@@ -1065,7 +1070,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
|
||||
### System Overview
|
||||
|
||||
The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
|
||||
### Key Architectural Components
|
||||
|
||||
@@ -1420,7 +1425,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
|
||||
- **Keep conversations focused** - One agent, one task per conversation
|
||||
- **Review everything** - Always review and approve before marking complete
|
||||
|
||||
## Contributing to BMad-Method
|
||||
## Contributing to BMAD-METHOD™
|
||||
|
||||
### Quick Contribution Guidelines
|
||||
|
||||
@@ -1452,7 +1457,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
|
||||
|
||||
### What Are Expansion Packs?
|
||||
|
||||
Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
|
||||
### Why Use Expansion Packs?
|
||||
|
||||
@@ -1519,6 +1524,7 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
@@ -1676,6 +1682,7 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/elicitation-methods.md ====================
|
||||
|
||||
==================== START: .bmad-core/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
@@ -1748,6 +1755,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
==================== END: .bmad-core/utils/workflow-management.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -1821,6 +1829,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
==================== END: .bmad-core/tasks/correct-course.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -1910,6 +1919,7 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -2098,6 +2108,7 @@ Document sharded successfully:
|
||||
==================== END: .bmad-core/tasks/shard-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -2235,6 +2246,7 @@ Provide a structured validation report including:
|
||||
==================== END: .bmad-core/tasks/validate-next-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: story-template-v2
|
||||
name: Story Document
|
||||
@@ -2375,6 +2387,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -2560,6 +2573,7 @@ Keep it action-oriented and forward-looking.]]
|
||||
==================== END: .bmad-core/checklists/change-checklist.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -2995,6 +3009,7 @@ After presenting the report, ask if the user wants:
|
||||
==================== END: .bmad-core/checklists/po-master-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -3110,6 +3125,7 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
||||
==================== END: .bmad-core/tasks/create-next-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Story Draft Checklist
|
||||
|
||||
The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
|
||||
@@ -3266,6 +3282,7 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
|
||||
==================== END: .bmad-core/checklists/story-draft-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/apply-qa-fixes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# apply-qa-fixes
|
||||
|
||||
Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.
|
||||
@@ -3417,6 +3434,7 @@ Fix plan:
|
||||
==================== END: .bmad-core/tasks/apply-qa-fixes.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
@@ -3514,6 +3532,7 @@ Be honest - it's better to flag issues now than have them discovered later.]]
|
||||
==================== END: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/nfr-assess.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# nfr-assess
|
||||
|
||||
Quick NFR validation focused on the core four: security, performance, reliability, maintainability.
|
||||
@@ -3860,6 +3879,7 @@ performance_deep_dive:
|
||||
==================== END: .bmad-core/tasks/nfr-assess.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/qa-gate.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# qa-gate
|
||||
|
||||
Create or update a quality gate decision file for a story based on review findings.
|
||||
@@ -4024,6 +4044,7 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
|
||||
==================== END: .bmad-core/tasks/qa-gate.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/review-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# review-story
|
||||
|
||||
Perform a comprehensive test architecture review with quality gate decision. This adaptive, risk-aware review creates both a story update and a detailed gate file.
|
||||
@@ -4341,6 +4362,7 @@ After review:
|
||||
==================== END: .bmad-core/tasks/review-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/risk-profile.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# risk-profile
|
||||
|
||||
Generate a comprehensive risk assessment matrix for a story implementation using probability × impact analysis.
|
||||
@@ -4697,6 +4719,7 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
|
||||
==================== END: .bmad-core/tasks/risk-profile.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/test-design.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# test-design
|
||||
|
||||
Create comprehensive test scenarios with appropriate test level recommendations for story implementation.
|
||||
@@ -4874,6 +4897,7 @@ Before finalizing, verify:
|
||||
==================== END: .bmad-core/tasks/test-design.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/trace-requirements.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# trace-requirements
|
||||
|
||||
Map story requirements to test cases using Given-When-Then patterns for comprehensive traceability.
|
||||
@@ -5141,6 +5165,7 @@ Trace matrix: qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md
|
||||
==================== END: .bmad-core/tasks/trace-requirements.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/qa-gate-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: qa-gate-template-v1
|
||||
name: Quality Gate Decision
|
||||
@@ -5246,6 +5271,7 @@ optional_fields_examples:
|
||||
==================== END: .bmad-core/templates/qa-gate-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
50
dist/teams/team-no-ui.txt
vendored
50
dist/teams/team-no-ui.txt
vendored
@@ -40,6 +40,7 @@ These references map directly to bundle sections:
|
||||
|
||||
|
||||
==================== START: .bmad-core/agent-teams/team-no-ui.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
bundle:
|
||||
name: Team No UI
|
||||
icon: 🔧
|
||||
@@ -435,6 +436,7 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/po.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -555,6 +557,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -659,6 +662,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
@@ -737,11 +741,12 @@ Or ask me about anything else related to BMad-Method!
|
||||
==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
# BMad Knowledge Base
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
|
||||
### Key Features
|
||||
|
||||
@@ -840,7 +845,7 @@ npx bmad-method install
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
|
||||
**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.
|
||||
**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.
|
||||
|
||||
**Verify Installation**:
|
||||
|
||||
@@ -848,7 +853,7 @@ npx bmad-method install
|
||||
- IDE-specific integration files created
|
||||
- All agent commands/rules/modes available
|
||||
|
||||
**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
|
||||
### Environment Selection Guide
|
||||
|
||||
@@ -1092,7 +1097,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
|
||||
### System Overview
|
||||
|
||||
The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
|
||||
### Key Architectural Components
|
||||
|
||||
@@ -1447,7 +1452,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
|
||||
- **Keep conversations focused** - One agent, one task per conversation
|
||||
- **Review everything** - Always review and approve before marking complete
|
||||
|
||||
## Contributing to BMad-Method
|
||||
## Contributing to BMAD-METHOD™
|
||||
|
||||
### Quick Contribution Guidelines
|
||||
|
||||
@@ -1479,7 +1484,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
|
||||
|
||||
### What Are Expansion Packs?
|
||||
|
||||
Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
|
||||
### Why Use Expansion Packs?
|
||||
|
||||
@@ -1546,6 +1551,7 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
@@ -1703,6 +1709,7 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/elicitation-methods.md ====================
|
||||
|
||||
==================== START: .bmad-core/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
@@ -1775,6 +1782,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
==================== END: .bmad-core/utils/workflow-management.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -2056,6 +2064,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -2402,6 +2411,7 @@ 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 -->
|
||||
---
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
|
||||
@@ -2696,10 +2706,11 @@ sections:
|
||||
content: |
|
||||
---
|
||||
|
||||
*Session facilitated using the BMAD-METHOD brainstorming framework*
|
||||
*Session facilitated using the BMAD-METHOD™ brainstorming framework*
|
||||
==================== END: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: competitor-analysis-template-v2
|
||||
name: Competitive Analysis Report
|
||||
@@ -3009,6 +3020,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/market-research-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: market-research-template-v2
|
||||
name: Market Research Report
|
||||
@@ -3264,6 +3276,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/market-research-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/project-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: project-brief-template-v2
|
||||
name: Project Brief
|
||||
@@ -3488,6 +3501,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/project-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
@@ -3527,6 +3541,7 @@ sections:
|
||||
==================== END: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
@@ -3690,6 +3705,7 @@ The epic creation is successful when:
|
||||
==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -3840,6 +3856,7 @@ The story creation is successful when:
|
||||
==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -3913,6 +3930,7 @@ The story creation is successful when:
|
||||
==================== END: .bmad-core/tasks/correct-course.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -4002,6 +4020,7 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -4190,6 +4209,7 @@ Document sharded successfully:
|
||||
==================== END: .bmad-core/tasks/shard-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-prd-template-v2
|
||||
name: Brownfield Enhancement PRD
|
||||
@@ -4473,6 +4493,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/prd-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: prd-template-v2
|
||||
name: Product Requirements Document
|
||||
@@ -4678,6 +4699,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/prd-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -4863,6 +4885,7 @@ Keep it action-oriented and forward-looking.]]
|
||||
==================== END: .bmad-core/checklists/change-checklist.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -5236,12 +5259,14 @@ After presenting the report, ask if the user wants:
|
||||
==================== END: .bmad-core/checklists/pm-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
==================== END: .bmad-core/data/technical-preferences.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: architecture-template-v2
|
||||
name: Architecture Document
|
||||
@@ -5895,6 +5920,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-architecture-template-v2
|
||||
name: Brownfield Enhancement Architecture
|
||||
@@ -6374,6 +6400,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: frontend-architecture-template-v2
|
||||
name: Frontend Architecture Document
|
||||
@@ -6595,6 +6622,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: fullstack-architecture-template-v2
|
||||
name: Fullstack Architecture Document
|
||||
@@ -7421,6 +7449,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -7862,6 +7891,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
==================== END: .bmad-core/checklists/architect-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -7999,6 +8029,7 @@ Provide a structured validation report including:
|
||||
==================== END: .bmad-core/tasks/validate-next-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: story-template-v2
|
||||
name: Story Document
|
||||
@@ -8139,6 +8170,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -8574,6 +8606,7 @@ After presenting the report, ask if the user wants:
|
||||
==================== END: .bmad-core/checklists/po-master-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/greenfield-service.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: greenfield-service
|
||||
name: Greenfield Service/API Development
|
||||
@@ -8783,6 +8816,7 @@ workflow:
|
||||
==================== END: .bmad-core/workflows/greenfield-service.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/workflows/brownfield-service.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: brownfield-service
|
||||
name: Brownfield Service/API Enhancement
|
||||
|
||||
Reference in New Issue
Block a user