Compare commits
7 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
26f7eb74a7 | ||
|
|
37e5fd50dd | ||
|
|
52f6889089 | ||
|
|
f09e282d72 | ||
|
|
2b247ea385 | ||
|
|
925099dd8c | ||
|
|
a19561a16c |
40
PR-opencode-agents-generator.md
Normal file
40
PR-opencode-agents-generator.md
Normal file
@@ -0,0 +1,40 @@
|
||||
# feat(opencode): compact AGENTS.md generator and JSON-only integration
|
||||
|
||||
## What
|
||||
|
||||
Add JSON-only OpenCode integration and a compact AGENTS.md generator (no large embeds; clickable file links) with idempotent merges for BMAD instructions, agents, and commands.
|
||||
|
||||
## Why
|
||||
|
||||
Keep OpenCode config schema‑compliant and small, avoid key collisions, and provide a readable agents/tasks index without inflating AGENTS.md.
|
||||
|
||||
## How
|
||||
|
||||
- Ensure `.bmad-core/core-config.yaml` in `instructions`
|
||||
- Merge only selected packages’ agents/commands into opencode.json file
|
||||
- Orchestrators `mode: primary`; all agents enable `write`, `edit`, `bash`
|
||||
- Descriptions from `whenToUse`/task `Purpose` with sanitization + fallbacks
|
||||
- Explicit warnings for non‑BMAD collisions; AGENTS.md uses a strict 3‑column table with links
|
||||
|
||||
## Testing
|
||||
|
||||
- Run: `npx bmad-method install -f -i opencode`
|
||||
- Verify: `opencode.json[c]` updated/created as expected, `AGENTS.md` OpenCode section is compact with links
|
||||
- Pre‑push checks:
|
||||
|
||||
```bash
|
||||
npm run pre-release
|
||||
# or individually
|
||||
npm run validate
|
||||
npm run format:check
|
||||
npm run lint
|
||||
# if anything fails
|
||||
npm run fix
|
||||
# or
|
||||
npm run format
|
||||
npm run lint:fix
|
||||
```
|
||||
|
||||
Fixes #<issue-number>
|
||||
|
||||
Targets: `next` branch
|
||||
@@ -75,8 +75,6 @@ This makes it easy to benefit from the latest improvements, bug fixes, and new a
|
||||
|
||||
```bash
|
||||
npx bmad-method install
|
||||
# OR explicitly use stable tag:
|
||||
npx bmad-method@stable install
|
||||
# OR if you already have BMad installed:
|
||||
git pull
|
||||
npm run install:bmad
|
||||
|
||||
@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
|
||||
@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
|
||||
@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
@@ -101,10 +101,10 @@ dependencies:
|
||||
- project-brief-tmpl.yaml
|
||||
- story-tmpl.yaml
|
||||
workflows:
|
||||
- brownfield-fullstack.md
|
||||
- brownfield-service.md
|
||||
- brownfield-ui.md
|
||||
- greenfield-fullstack.md
|
||||
- greenfield-service.md
|
||||
- greenfield-ui.md
|
||||
- brownfield-fullstack.yaml
|
||||
- brownfield-service.yaml
|
||||
- brownfield-ui.yaml
|
||||
- greenfield-fullstack.yaml
|
||||
- greenfield-service.yaml
|
||||
- greenfield-ui.yaml
|
||||
```
|
||||
|
||||
@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
@@ -31,7 +31,7 @@ activation-instructions:
|
||||
- Assess user goal against available agents and workflows in this bundle
|
||||
- If clear match to an agent's expertise, suggest transformation with *agent command
|
||||
- If project-oriented, suggest *workflow-guidance to explore options
|
||||
- Load resources only when needed - never pre-load (Exception: Read `bmad-core/core-config.yaml` during activation)
|
||||
- Load resources only when needed - never pre-load (Exception: Read `.bmad-core/core-config.yaml` during activation)
|
||||
- CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
|
||||
agent:
|
||||
name: BMad Orchestrator
|
||||
|
||||
@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
|
||||
@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
|
||||
@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
|
||||
@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
@@ -35,11 +35,7 @@ agent:
|
||||
id: qa
|
||||
title: Test Architect & Quality Advisor
|
||||
icon: 🧪
|
||||
whenToUse: |
|
||||
Use for comprehensive test architecture review, quality gate decisions,
|
||||
and code improvement. Provides thorough analysis including requirements
|
||||
traceability, risk assessment, and test strategy.
|
||||
Advisory only - teams choose their quality bar.
|
||||
whenToUse: Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requirements traceability, risk assessment, and test strategy. Advisory only - teams choose their quality bar.
|
||||
customization: null
|
||||
persona:
|
||||
role: Test Architect with Quality Advisory Authority
|
||||
|
||||
@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
|
||||
@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
|
||||
activation-instructions:
|
||||
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
|
||||
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
|
||||
- STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
|
||||
- STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
|
||||
- DO NOT: Load any other agent files during activation
|
||||
- ONLY load dependency files when user selects them for execution via command or request of a task
|
||||
|
||||
@@ -15,7 +15,7 @@ First, determine the project type by checking:
|
||||
|
||||
2. Is this a BROWNFIELD project (enhancing existing system)?
|
||||
- Look for: References to existing codebase, enhancement/modification language
|
||||
- Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis
|
||||
- Check for: prd.md, architecture.md, existing system analysis
|
||||
|
||||
3. Does the project include UI/UX components?
|
||||
- Check for: frontend-architecture.md, UI/UX specifications, design files
|
||||
@@ -33,8 +33,8 @@ For GREENFIELD projects:
|
||||
|
||||
For BROWNFIELD projects:
|
||||
|
||||
- brownfield-prd.md - The brownfield enhancement requirements
|
||||
- brownfield-architecture.md - The enhancement architecture
|
||||
- prd.md - The brownfield enhancement requirements
|
||||
- architecture.md - The enhancement architecture
|
||||
- Existing project codebase access (CRITICAL - cannot proceed without this)
|
||||
- Current deployment configuration and infrastructure details
|
||||
- Database schemas, API documentation, monitoring setup
|
||||
|
||||
@@ -181,7 +181,7 @@ npx bmad-method install
|
||||
|
||||
## Core Configuration (core-config.yaml)
|
||||
|
||||
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
|
||||
### What is core-config.yaml?
|
||||
|
||||
|
||||
@@ -16,8 +16,8 @@ Implement fixes based on QA results (gate and assessments) for a specific story.
|
||||
```yaml
|
||||
required:
|
||||
- story_id: '{epic}.{story}' # e.g., "2.2"
|
||||
- qa_root: from `bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
|
||||
- story_root: from `bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
|
||||
- qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
|
||||
- story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
|
||||
|
||||
optional:
|
||||
- story_title: '{title}' # derive from story H1 if missing
|
||||
@@ -45,7 +45,7 @@ optional:
|
||||
|
||||
### 0) Load Core Config & Locate Story
|
||||
|
||||
- Read `bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
|
||||
- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
|
||||
- Locate story file in `{story_root}/{epic}.{story}.*.md`
|
||||
- HALT if missing and ask for correct story id/path
|
||||
|
||||
@@ -113,7 +113,7 @@ Status Rule:
|
||||
|
||||
## Blocking Conditions
|
||||
|
||||
- Missing `bmad-core/core-config.yaml`
|
||||
- Missing `.bmad-core/core-config.yaml`
|
||||
- Story file not found for `story_id`
|
||||
- No QA artifacts found (neither gate nor assessments)
|
||||
- HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)
|
||||
|
||||
@@ -9,11 +9,11 @@ Quick NFR validation focused on the core four: security, performance, reliabilit
|
||||
```yaml
|
||||
required:
|
||||
- story_id: '{epic}.{story}' # e.g., "1.3"
|
||||
- story_path: `bmad-core/core-config.yaml` for the `devStoryLocation`
|
||||
- story_path: `.bmad-core/core-config.yaml` for the `devStoryLocation`
|
||||
|
||||
optional:
|
||||
- architecture_refs: `bmad-core/core-config.yaml` for the `architecture.architectureFile`
|
||||
- technical_preferences: `bmad-core/core-config.yaml` for the `technicalPreferences`
|
||||
- architecture_refs: `.bmad-core/core-config.yaml` for the `architecture.architectureFile`
|
||||
- technical_preferences: `.bmad-core/core-config.yaml` for the `technicalPreferences`
|
||||
- acceptance_criteria: From story file
|
||||
```
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision
|
||||
|
||||
## Gate File Location
|
||||
|
||||
**ALWAYS** check the `bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
|
||||
**ALWAYS** check the `.bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
|
||||
|
||||
Slug rules:
|
||||
|
||||
@@ -126,7 +126,7 @@ waiver:
|
||||
|
||||
## Output Requirements
|
||||
|
||||
1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `bmad-core/core-config.yaml`
|
||||
1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `.bmad-core/core-config.yaml`
|
||||
2. **ALWAYS** append this exact format to story's QA Results section:
|
||||
|
||||
```text
|
||||
|
||||
@@ -186,7 +186,7 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
|
||||
**Template and Directory:**
|
||||
|
||||
- Render from `../templates/qa-gate-tmpl.yaml`
|
||||
- Create directory defined in `qa.qaLocation/gates` (see `bmad-core/core-config.yaml`) if missing
|
||||
- Create directory defined in `qa.qaLocation/gates` (see `.bmad-core/core-config.yaml`) if missing
|
||||
- Save to: `qa.qaLocation/gates/{epic}.{story}-{slug}.yml`
|
||||
|
||||
Gate file structure:
|
||||
|
||||
@@ -23,7 +23,7 @@ sections:
|
||||
1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead."
|
||||
|
||||
2. **REQUIRED INPUTS**:
|
||||
- Completed brownfield-prd.md
|
||||
- Completed prd.md
|
||||
- Existing project technical documentation (from docs folder or user-provided)
|
||||
- Access to existing project structure (IDE or uploaded files)
|
||||
|
||||
@@ -109,8 +109,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:
|
||||
|
||||
@@ -272,8 +272,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:
|
||||
|
||||
@@ -342,7 +342,7 @@ sections:
|
||||
**Monitoring:** {{monitoring_approach}}
|
||||
|
||||
- id: coding-standards
|
||||
title: Coding Standards and Conventions
|
||||
title: Coding Standards
|
||||
instruction: |
|
||||
Ensure new code follows existing project conventions:
|
||||
|
||||
|
||||
14
dist/agents/analyst.txt
vendored
14
dist/agents/analyst.txt
vendored
@@ -105,6 +105,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -226,6 +227,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
|
||||
==================== 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.
|
||||
@@ -508,6 +510,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -613,6 +616,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -959,10 +963,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
|
||||
@@ -2050,6 +2055,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -2152,6 +2158,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.
|
||||
|
||||
@@ -2230,7 +2237,7 @@ npx bmad-method install
|
||||
|
||||
## Core Configuration (core-config.yaml)
|
||||
|
||||
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
|
||||
### What is core-config.yaml?
|
||||
|
||||
@@ -2860,6 +2867,7 @@ Use the **expansion-creator** pack to build your own:
|
||||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
|
||||
18
dist/agents/architect.txt
vendored
18
dist/agents/architect.txt
vendored
@@ -106,6 +106,7 @@ dependencies:
|
||||
|
||||
==================== 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.
|
||||
@@ -388,6 +389,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -493,6 +495,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -840,6 +843,7 @@ Apply the advanced elicitation task after major sections to refine based on user
|
||||
|
||||
==================== 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.
|
||||
@@ -1608,7 +1612,7 @@ sections:
|
||||
1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead."
|
||||
|
||||
2. **REQUIRED INPUTS**:
|
||||
- Completed brownfield-prd.md
|
||||
- Completed prd.md
|
||||
- Existing project technical documentation (from docs folder or user-provided)
|
||||
- Access to existing project structure (IDE or uploaded files)
|
||||
|
||||
@@ -1694,8 +1698,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:
|
||||
|
||||
@@ -1857,8 +1861,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:
|
||||
|
||||
@@ -1927,7 +1931,7 @@ sections:
|
||||
**Monitoring:** {{monitoring_approach}}
|
||||
|
||||
- id: coding-standards
|
||||
title: Coding Standards and Conventions
|
||||
title: Coding Standards
|
||||
instruction: |
|
||||
Ensure new code follows existing project conventions:
|
||||
|
||||
@@ -3113,6 +3117,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.
|
||||
@@ -3555,6 +3560,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
60
dist/agents/bmad-master.txt
vendored
60
dist/agents/bmad-master.txt
vendored
@@ -117,17 +117,18 @@ dependencies:
|
||||
- project-brief-tmpl.yaml
|
||||
- story-tmpl.yaml
|
||||
workflows:
|
||||
- brownfield-fullstack.md
|
||||
- brownfield-service.md
|
||||
- brownfield-ui.md
|
||||
- greenfield-fullstack.md
|
||||
- greenfield-service.md
|
||||
- greenfield-ui.md
|
||||
- brownfield-fullstack.yaml
|
||||
- brownfield-service.yaml
|
||||
- brownfield-ui.yaml
|
||||
- greenfield-fullstack.yaml
|
||||
- greenfield-service.yaml
|
||||
- greenfield-ui.yaml
|
||||
```
|
||||
==================== END: .bmad-core/agents/bmad-master.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -249,6 +250,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
@@ -413,6 +415,7 @@ The epic creation is successful when:
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -564,6 +567,7 @@ The story creation is successful when:
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -638,6 +642,7 @@ The story creation is successful when:
|
||||
|
||||
==================== 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.
|
||||
@@ -920,6 +925,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -1025,6 +1031,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-core/tasks/create-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -1141,6 +1148,7 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
||||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -1488,6 +1496,7 @@ Apply the advanced elicitation task after major sections to refine based on user
|
||||
|
||||
==================== 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.
|
||||
@@ -1577,10 +1586,11 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.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
|
||||
@@ -1718,6 +1728,7 @@ Generate structured document with these sections:
|
||||
|
||||
==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create AI Frontend Prompt Task
|
||||
|
||||
## Purpose
|
||||
@@ -1773,6 +1784,7 @@ You will now synthesize the inputs and the above principles into a final, compre
|
||||
|
||||
==================== START: .bmad-core/tasks/index-docs.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Index Documentation Task
|
||||
|
||||
## Purpose
|
||||
@@ -1950,6 +1962,7 @@ Would you like to proceed with documentation indexing? Please provide the requir
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -2817,7 +2830,7 @@ sections:
|
||||
1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead."
|
||||
|
||||
2. **REQUIRED INPUTS**:
|
||||
- Completed brownfield-prd.md
|
||||
- Completed prd.md
|
||||
- Existing project technical documentation (from docs folder or user-provided)
|
||||
- Access to existing project structure (IDE or uploaded files)
|
||||
|
||||
@@ -2903,8 +2916,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:
|
||||
|
||||
@@ -3066,8 +3079,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:
|
||||
|
||||
@@ -3136,7 +3149,7 @@ sections:
|
||||
**Monitoring:** {{monitoring_approach}}
|
||||
|
||||
- id: coding-standards
|
||||
title: Coding Standards and Conventions
|
||||
title: Coding Standards
|
||||
instruction: |
|
||||
Ensure new code follows existing project conventions:
|
||||
|
||||
@@ -6097,6 +6110,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.
|
||||
@@ -6539,6 +6553,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
|
||||
==================== 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.
|
||||
@@ -6725,6 +6740,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.
|
||||
@@ -7099,6 +7115,7 @@ After presenting the report, ask if the user wants:
|
||||
|
||||
==================== 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.
|
||||
@@ -7114,7 +7131,7 @@ First, determine the project type by checking:
|
||||
|
||||
2. Is this a BROWNFIELD project (enhancing existing system)?
|
||||
- Look for: References to existing codebase, enhancement/modification language
|
||||
- Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis
|
||||
- Check for: prd.md, architecture.md, existing system analysis
|
||||
|
||||
3. Does the project include UI/UX components?
|
||||
- Check for: frontend-architecture.md, UI/UX specifications, design files
|
||||
@@ -7132,8 +7149,8 @@ For GREENFIELD projects:
|
||||
|
||||
For BROWNFIELD projects:
|
||||
|
||||
- brownfield-prd.md - The brownfield enhancement requirements
|
||||
- brownfield-architecture.md - The enhancement architecture
|
||||
- prd.md - The brownfield enhancement requirements
|
||||
- architecture.md - The enhancement architecture
|
||||
- Existing project codebase access (CRITICAL - cannot proceed without this)
|
||||
- Current deployment configuration and infrastructure details
|
||||
- Database schemas, API documentation, monitoring setup
|
||||
@@ -7535,6 +7552,7 @@ After presenting the report, ask if the user wants:
|
||||
|
||||
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
@@ -7633,6 +7651,7 @@ Be honest - it's better to flag issues now than have them discovered later.]]
|
||||
|
||||
==================== 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.
|
||||
@@ -7790,6 +7809,7 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
|
||||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -7892,6 +7912,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.
|
||||
|
||||
@@ -7970,7 +7991,7 @@ npx bmad-method install
|
||||
|
||||
## Core Configuration (core-config.yaml)
|
||||
|
||||
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
|
||||
### What is core-config.yaml?
|
||||
|
||||
@@ -8600,6 +8621,7 @@ Use the **expansion-creator** pack to build your own:
|
||||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
@@ -8640,6 +8662,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
|
||||
@@ -8798,6 +8821,7 @@ Use the **expansion-creator** pack to build your own:
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
9
dist/agents/bmad-orchestrator.txt
vendored
9
dist/agents/bmad-orchestrator.txt
vendored
@@ -168,6 +168,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -289,6 +290,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 ⚠️
|
||||
@@ -394,6 +396,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
|
||||
@@ -473,6 +476,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
|
||||
@@ -575,6 +579,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.
|
||||
|
||||
@@ -653,7 +658,7 @@ npx bmad-method install
|
||||
|
||||
## Core Configuration (core-config.yaml)
|
||||
|
||||
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
|
||||
### What is core-config.yaml?
|
||||
|
||||
@@ -1283,6 +1288,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
|
||||
@@ -1441,6 +1447,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.
|
||||
|
||||
15
dist/agents/dev.txt
vendored
15
dist/agents/dev.txt
vendored
@@ -64,6 +64,7 @@ persona:
|
||||
focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
|
||||
core_principles:
|
||||
- CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
|
||||
- CRITICAL: ALWAYS check current folder structure before starting your story tasks, don't create new working directory if it already exists. Create new one when you're sure it's a brand new project.
|
||||
- CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
|
||||
- CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
|
||||
- Numbered Options - Always use numbered lists when presenting choices to the user
|
||||
@@ -94,6 +95,7 @@ dependencies:
|
||||
|
||||
==================== 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.
|
||||
@@ -110,8 +112,8 @@ Implement fixes based on QA results (gate and assessments) for a specific story.
|
||||
```yaml
|
||||
required:
|
||||
- story_id: '{epic}.{story}' # e.g., "2.2"
|
||||
- qa_root: from `bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
|
||||
- story_root: from `bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
|
||||
- qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
|
||||
- story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
|
||||
|
||||
optional:
|
||||
- story_title: '{title}' # derive from story H1 if missing
|
||||
@@ -139,7 +141,7 @@ optional:
|
||||
|
||||
### 0) Load Core Config & Locate Story
|
||||
|
||||
- Read `bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
|
||||
- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
|
||||
- Locate story file in `{story_root}/{epic}.{story}.*.md`
|
||||
- HALT if missing and ask for correct story id/path
|
||||
|
||||
@@ -207,7 +209,7 @@ Status Rule:
|
||||
|
||||
## Blocking Conditions
|
||||
|
||||
- Missing `bmad-core/core-config.yaml`
|
||||
- Missing `.bmad-core/core-config.yaml`
|
||||
- Story file not found for `story_id`
|
||||
- No QA artifacts found (neither gate nor assessments)
|
||||
- HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)
|
||||
@@ -246,6 +248,7 @@ Fix plan:
|
||||
|
||||
==================== 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.
|
||||
@@ -336,6 +339,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -357,7 +361,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
|
||||
@@ -474,6 +478,7 @@ Provide a structured validation report including:
|
||||
|
||||
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
|
||||
10
dist/agents/pm.txt
vendored
10
dist/agents/pm.txt
vendored
@@ -105,6 +105,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
@@ -269,6 +270,7 @@ The epic creation is successful when:
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -420,6 +422,7 @@ The story creation is successful when:
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -494,6 +497,7 @@ The story creation is successful when:
|
||||
|
||||
==================== 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.
|
||||
@@ -776,6 +780,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -881,6 +886,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== 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.
|
||||
@@ -971,6 +977,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -1650,6 +1657,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.
|
||||
@@ -1836,6 +1844,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.
|
||||
@@ -2210,6 +2219,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
|
||||
|
||||
14
dist/agents/po.txt
vendored
14
dist/agents/po.txt
vendored
@@ -100,6 +100,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -174,6 +175,7 @@ dependencies:
|
||||
|
||||
==================== 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.
|
||||
@@ -264,6 +266,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -453,6 +456,7 @@ Document sharded successfully:
|
||||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -474,7 +478,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
|
||||
@@ -732,6 +736,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.
|
||||
@@ -918,6 +923,7 @@ Keep it action-oriented and forward-looking.]]
|
||||
|
||||
==================== 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.
|
||||
@@ -933,7 +939,7 @@ First, determine the project type by checking:
|
||||
|
||||
2. Is this a BROWNFIELD project (enhancing existing system)?
|
||||
- Look for: References to existing codebase, enhancement/modification language
|
||||
- Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis
|
||||
- Check for: prd.md, architecture.md, existing system analysis
|
||||
|
||||
3. Does the project include UI/UX components?
|
||||
- Check for: frontend-architecture.md, UI/UX specifications, design files
|
||||
@@ -951,8 +957,8 @@ For GREENFIELD projects:
|
||||
|
||||
For BROWNFIELD projects:
|
||||
|
||||
- brownfield-prd.md - The brownfield enhancement requirements
|
||||
- brownfield-architecture.md - The enhancement architecture
|
||||
- prd.md - The brownfield enhancement requirements
|
||||
- architecture.md - The enhancement architecture
|
||||
- Existing project codebase access (CRITICAL - cannot proceed without this)
|
||||
- Current deployment configuration and infrastructure details
|
||||
- Database schemas, API documentation, monitoring setup
|
||||
|
||||
25
dist/agents/qa.txt
vendored
25
dist/agents/qa.txt
vendored
@@ -55,11 +55,7 @@ agent:
|
||||
id: qa
|
||||
title: Test Architect & Quality Advisor
|
||||
icon: 🧪
|
||||
whenToUse: |
|
||||
Use for comprehensive test architecture review, quality gate decisions,
|
||||
and code improvement. Provides thorough analysis including requirements
|
||||
traceability, risk assessment, and test strategy.
|
||||
Advisory only - teams choose their quality bar.
|
||||
whenToUse: Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requirements traceability, risk assessment, and test strategy. Advisory only - teams choose their quality bar.
|
||||
customization: null
|
||||
persona:
|
||||
role: Test Architect with Quality Advisory Authority
|
||||
@@ -112,6 +108,7 @@ dependencies:
|
||||
|
||||
==================== 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.
|
||||
@@ -121,11 +118,11 @@ Quick NFR validation focused on the core four: security, performance, reliabilit
|
||||
```yaml
|
||||
required:
|
||||
- story_id: '{epic}.{story}' # e.g., "1.3"
|
||||
- story_path: `bmad-core/core-config.yaml` for the `devStoryLocation`
|
||||
- story_path: `.bmad-core/core-config.yaml` for the `devStoryLocation`
|
||||
|
||||
optional:
|
||||
- architecture_refs: `bmad-core/core-config.yaml` for the `architecture.architectureFile`
|
||||
- technical_preferences: `bmad-core/core-config.yaml` for the `technicalPreferences`
|
||||
- architecture_refs: `.bmad-core/core-config.yaml` for the `architecture.architectureFile`
|
||||
- technical_preferences: `.bmad-core/core-config.yaml` for the `technicalPreferences`
|
||||
- acceptance_criteria: From story file
|
||||
```
|
||||
|
||||
@@ -459,6 +456,7 @@ performance_deep_dive:
|
||||
|
||||
==================== 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.
|
||||
@@ -475,7 +473,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision
|
||||
|
||||
## Gate File Location
|
||||
|
||||
**ALWAYS** check the `bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
|
||||
**ALWAYS** check the `.bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
|
||||
|
||||
Slug rules:
|
||||
|
||||
@@ -585,7 +583,7 @@ waiver:
|
||||
|
||||
## Output Requirements
|
||||
|
||||
1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `bmad-core/core-config.yaml`
|
||||
1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `.bmad-core/core-config.yaml`
|
||||
2. **ALWAYS** append this exact format to story's QA Results section:
|
||||
|
||||
```text
|
||||
@@ -624,6 +622,7 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
|
||||
|
||||
==================== 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.
|
||||
@@ -810,7 +809,7 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
|
||||
**Template and Directory:**
|
||||
|
||||
- Render from `../templates/qa-gate-tmpl.yaml`
|
||||
- Create directory defined in `qa.qaLocation/gates` (see `bmad-core/core-config.yaml`) if missing
|
||||
- Create directory defined in `qa.qaLocation/gates` (see `.bmad-core/core-config.yaml`) if missing
|
||||
- Save to: `qa.qaLocation/gates/{epic}.{story}-{slug}.yml`
|
||||
|
||||
Gate file structure:
|
||||
@@ -942,6 +941,7 @@ After review:
|
||||
|
||||
==================== 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.
|
||||
@@ -1299,6 +1299,7 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.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.
|
||||
@@ -1477,6 +1478,7 @@ Before finalizing, verify:
|
||||
|
||||
==================== 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.
|
||||
@@ -1992,6 +1994,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
4
dist/agents/sm.txt
vendored
4
dist/agents/sm.txt
vendored
@@ -86,6 +86,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -160,6 +161,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-core/tasks/create-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -276,6 +278,7 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
||||
|
||||
==================== 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.
|
||||
@@ -507,6 +510,7 @@ sections:
|
||||
|
||||
==================== 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.
|
||||
|
||||
4
dist/agents/ux-expert.txt
vendored
4
dist/agents/ux-expert.txt
vendored
@@ -90,6 +90,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -195,6 +196,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== 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.
|
||||
@@ -285,6 +287,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create AI Frontend Prompt Task
|
||||
|
||||
## Purpose
|
||||
@@ -693,6 +696,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
@@ -96,6 +96,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -201,6 +202,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/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.
|
||||
@@ -291,6 +293,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
@@ -585,6 +588,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/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.
|
||||
@@ -867,6 +871,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -2176,6 +2181,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
|
||||
@@ -103,6 +103,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/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.
|
||||
@@ -810,6 +811,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done Checklist
|
||||
|
||||
## Story Completeness
|
||||
@@ -974,6 +976,7 @@ _Any specific concerns, recommendations, or clarifications needed before develop
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -89,6 +89,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Development Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -309,6 +310,7 @@ This task ensures game development stories are immediately actionable and enable
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/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.
|
||||
@@ -656,6 +658,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done Checklist
|
||||
|
||||
## Story Completeness
|
||||
|
||||
@@ -414,6 +414,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development BMad Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -668,6 +669,7 @@ This knowledge base provides the foundation for effective game development using
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
@@ -708,6 +710,7 @@ This knowledge base provides the foundation for effective game development using
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -822,6 +825,7 @@ The questions and perspectives offered should always consider:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/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.
|
||||
@@ -1104,6 +1108,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -1209,6 +1214,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -1555,10 +1561,11 @@ Apply the advanced elicitation task after major sections to refine based on user
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/document-project.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/facilitate-brainstorming-session.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
## <!-- Powered by BMAD™ Core -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-2d-phaser-game-dev/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
@@ -2646,6 +2653,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
@@ -2804,6 +2812,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
@@ -2883,6 +2892,7 @@ Or ask me about anything else related to BMad-Method!
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
@@ -2956,6 +2966,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/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.
|
||||
@@ -3046,6 +3057,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
@@ -4535,6 +4547,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
@@ -5357,6 +5370,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done Checklist
|
||||
|
||||
## Story Completeness
|
||||
@@ -5521,6 +5535,7 @@ _Any specific concerns, recommendations, or clarifications needed before develop
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines
|
||||
|
||||
## Overview
|
||||
@@ -6172,6 +6187,7 @@ These guidelines ensure consistent, high-quality game development that meets per
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Development Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -8718,6 +8734,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -8832,6 +8849,7 @@ The questions and perspectives offered should always consider:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Development Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -9052,6 +9070,7 @@ This task ensures game development stories are immediately actionable and enable
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
@@ -9346,6 +9365,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
@@ -9551,6 +9571,7 @@ _Outline immediate next actions for the team based on this assessment._
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done Checklist
|
||||
|
||||
## Story Completeness
|
||||
@@ -10081,6 +10102,7 @@ workflow:
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development BMad Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -10335,6 +10357,7 @@ This knowledge base provides the foundation for effective game development using
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -104,6 +104,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -209,6 +210,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/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.
|
||||
@@ -491,6 +493,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -680,6 +683,7 @@ Document sharded successfully:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -1027,6 +1031,7 @@ Apply the advanced elicitation task after major sections to refine based on user
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/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.
|
||||
@@ -1117,6 +1122,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -2265,6 +2271,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Architect Solution Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
|
||||
@@ -2660,6 +2667,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines (Unity & C#)
|
||||
|
||||
## Overview
|
||||
@@ -3250,6 +3258,7 @@ These guidelines ensure consistent, high-quality game development that meets per
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -101,6 +101,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -206,6 +207,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/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.
|
||||
@@ -296,6 +298,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -485,6 +488,7 @@ Document sharded successfully:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
@@ -779,6 +783,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/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.
|
||||
@@ -1061,6 +1066,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -2732,6 +2738,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
@@ -2937,6 +2944,7 @@ _Outline immediate next actions for the team based on this assessment._
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -98,6 +98,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/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.
|
||||
@@ -188,6 +189,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -209,7 +211,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
|
||||
@@ -326,6 +328,7 @@ Provide a structured validation report including:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
|
||||
@@ -89,6 +89,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -277,6 +278,7 @@ This task ensures game development stories are immediately actionable and enable
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/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.
|
||||
@@ -367,6 +369,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task - Game Development
|
||||
|
||||
## Purpose
|
||||
@@ -772,6 +775,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.
|
||||
|
||||
@@ -478,6 +478,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
@@ -1251,6 +1252,7 @@ This knowledge base provides the foundation for effective game development using
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
@@ -1291,6 +1293,7 @@ This knowledge base provides the foundation for effective game development using
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -1405,6 +1408,7 @@ The questions and perspectives offered should always consider:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/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.
|
||||
@@ -1687,6 +1691,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -1792,6 +1797,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -2138,10 +2144,11 @@ Apply the advanced elicitation task after major sections to refine based on user
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/facilitate-brainstorming-session.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
## <!-- Powered by BMAD™ Core -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-2d-unity-game-dev/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
@@ -3229,6 +3236,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
@@ -3387,6 +3395,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
@@ -3466,6 +3475,7 @@ Or ask me about anything else related to BMad-Method!
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
@@ -3539,6 +3549,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/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.
|
||||
@@ -3629,6 +3640,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -3818,6 +3830,7 @@ Document sharded successfully:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
@@ -5669,6 +5682,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
@@ -6908,6 +6922,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Architect Solution Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
|
||||
@@ -7303,6 +7318,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines (Unity & C#)
|
||||
|
||||
## Overview
|
||||
@@ -7893,6 +7909,7 @@ These guidelines ensure consistent, high-quality game development that meets per
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -7914,7 +7931,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
|
||||
@@ -8031,6 +8048,7 @@ Provide a structured validation report including:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
@@ -8159,6 +8177,7 @@ Be honest - it's better to flag issues now than have them discovered during play
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -8347,6 +8366,7 @@ This task ensures game development stories are immediately actionable and enable
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task - Game Development
|
||||
|
||||
## Purpose
|
||||
@@ -8752,6 +8772,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.
|
||||
@@ -11810,6 +11831,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -11924,6 +11946,7 @@ The questions and perspectives offered should always consider:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task - Game Development
|
||||
|
||||
## Purpose
|
||||
@@ -12069,6 +12092,7 @@ Based on the analysis and agreed path forward:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -12257,6 +12281,7 @@ This task ensures game development stories are immediately actionable and enable
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Brainstorming Techniques Task
|
||||
|
||||
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
|
||||
@@ -12551,6 +12576,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/validate-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Game Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -12755,6 +12781,7 @@ Based on validation results, provide specific recommendations for:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Architect Solution Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
|
||||
@@ -13150,6 +13177,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.
|
||||
@@ -13357,6 +13385,7 @@ Keep it technically precise and actionable.]]
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
@@ -13562,6 +13591,7 @@ _Outline immediate next actions for the team based on this assessment._
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
@@ -14056,6 +14086,7 @@ workflow:
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
@@ -14829,6 +14860,7 @@ This knowledge base provides the foundation for effective game development using
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines (Unity & C#)
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -117,6 +117,7 @@ Remember to present all options as numbered lists for easy selection.
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -222,6 +223,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Provide Feedback (Beta)
|
||||
@@ -248,6 +250,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 13. Quick Feedback (Serial)
|
||||
@@ -272,6 +275,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 16. Analyze Reader Feedback
|
||||
@@ -297,6 +301,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/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.
|
||||
@@ -387,6 +392,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -608,6 +614,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Beta‑Feedback Closure Checklist
|
||||
@@ -633,6 +640,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -844,6 +852,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
||||
@@ -116,6 +116,7 @@ Remember to present all options as numbered lists for easy selection.
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -221,6 +222,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/develop-character.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 3. Develop Character
|
||||
@@ -247,6 +249,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workshop Dialog
|
||||
|
||||
## Purpose
|
||||
@@ -313,6 +316,7 @@ Refined dialog with stronger voices and dramatic impact
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/character-depth-pass.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 9. Character Depth Pass
|
||||
@@ -337,6 +341,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/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.
|
||||
@@ -427,6 +432,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -643,6 +649,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 1. Character Consistency Checklist
|
||||
@@ -668,6 +675,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -115,6 +115,7 @@ Remember to present all options as numbered lists for easy selection.
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -220,6 +221,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workshop Dialog
|
||||
|
||||
## Purpose
|
||||
@@ -286,6 +288,7 @@ Refined dialog with stronger voices and dramatic impact
|
||||
|
||||
==================== START: .bmad-creative-writing/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.
|
||||
@@ -376,6 +379,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -592,6 +596,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 23. Comedic Timing & Humor Checklist
|
||||
@@ -617,6 +622,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -828,6 +834,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
||||
@@ -116,6 +116,7 @@ Remember to present all options as numbered lists for easy selection.
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -221,6 +222,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/final-polish.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 14. Final Polish
|
||||
@@ -246,6 +248,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Incorporate Feedback
|
||||
@@ -273,6 +276,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/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.
|
||||
@@ -363,6 +367,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -569,6 +574,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 4. Line‑Edit Quality Checklist
|
||||
@@ -594,6 +600,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Publication Readiness Checklist
|
||||
@@ -619,6 +626,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -118,6 +118,7 @@ Remember to present all options as numbered lists for easy selection.
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -223,6 +224,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Analyze Story Structure
|
||||
|
||||
## Purpose
|
||||
@@ -292,6 +294,7 @@ Comprehensive structural analysis with actionable recommendations
|
||||
|
||||
==================== START: .bmad-creative-writing/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.
|
||||
@@ -382,6 +385,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -602,6 +606,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/genre-tropes-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Genre Tropes Checklist (General)
|
||||
@@ -626,6 +631,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 17. Fantasy Magic System Consistency Checklist
|
||||
@@ -651,6 +657,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 15. Sci‑Fi Technology Plausibility Checklist
|
||||
@@ -675,6 +682,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 12. Romance Emotional Beats Checklist
|
||||
@@ -700,6 +708,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -911,6 +920,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
||||
@@ -116,6 +116,7 @@ Remember to present all options as numbered lists for easy selection.
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -221,6 +222,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/outline-scenes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 11. Outline Scenes
|
||||
@@ -246,6 +248,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/generate-scene-list.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Generate Scene List
|
||||
@@ -271,6 +274,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/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.
|
||||
@@ -361,6 +365,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -540,6 +545,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Plot Structure Checklist
|
||||
|
||||
## Opening
|
||||
@@ -601,6 +607,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -812,6 +819,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
||||
@@ -118,6 +118,7 @@ Remember to present all options as numbered lists for easy selection.
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -223,6 +224,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Analyze Story Structure
|
||||
|
||||
## Purpose
|
||||
@@ -292,6 +294,7 @@ Comprehensive structural analysis with actionable recommendations
|
||||
|
||||
==================== START: .bmad-creative-writing/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.
|
||||
@@ -382,6 +385,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -826,6 +830,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Plot Structure Checklist
|
||||
|
||||
## Opening
|
||||
@@ -887,6 +892,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
@@ -956,6 +962,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -117,6 +117,7 @@ Remember to present all options as numbered lists for easy selection.
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -222,6 +223,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/build-world.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. Build World
|
||||
@@ -248,6 +250,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/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.
|
||||
@@ -338,6 +341,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -551,6 +555,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/world-building-continuity-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. World‑Building Continuity Checklist
|
||||
@@ -576,6 +581,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 17. Fantasy Magic System Consistency Checklist
|
||||
@@ -601,6 +607,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/steampunk-gadget-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 25. Steampunk Gadget Plausibility Checklist
|
||||
@@ -626,6 +633,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -837,6 +845,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
||||
@@ -837,6 +837,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -1048,6 +1049,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
|
||||
==================== START: .bmad-creative-writing/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
@@ -1206,6 +1208,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -1327,6 +1330,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -1432,6 +1436,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
@@ -1511,6 +1516,7 @@ Or ask me about anything else related to BMad-Method!
|
||||
|
||||
==================== START: .bmad-creative-writing/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
@@ -1584,6 +1590,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Analyze Story Structure
|
||||
|
||||
## Purpose
|
||||
@@ -1653,6 +1660,7 @@ Comprehensive structural analysis with actionable recommendations
|
||||
|
||||
==================== START: .bmad-creative-writing/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.
|
||||
@@ -2066,6 +2074,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Plot Structure Checklist
|
||||
|
||||
## Opening
|
||||
@@ -2127,6 +2136,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
@@ -2196,6 +2206,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/develop-character.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 3. Develop Character
|
||||
@@ -2222,6 +2233,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workshop Dialog
|
||||
|
||||
## Purpose
|
||||
@@ -2288,6 +2300,7 @@ Refined dialog with stronger voices and dramatic impact
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/character-depth-pass.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 9. Character Depth Pass
|
||||
@@ -2407,6 +2420,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 1. Character Consistency Checklist
|
||||
@@ -2432,6 +2446,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/build-world.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. Build World
|
||||
@@ -2550,6 +2565,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/world-building-continuity-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. World‑Building Continuity Checklist
|
||||
@@ -2575,6 +2591,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 17. Fantasy Magic System Consistency Checklist
|
||||
@@ -2600,6 +2617,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/steampunk-gadget-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 25. Steampunk Gadget Plausibility Checklist
|
||||
@@ -2625,6 +2643,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/final-polish.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 14. Final Polish
|
||||
@@ -2650,6 +2669,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Incorporate Feedback
|
||||
@@ -2677,6 +2697,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 4. Line‑Edit Quality Checklist
|
||||
@@ -2702,6 +2723,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Publication Readiness Checklist
|
||||
@@ -2727,6 +2749,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Provide Feedback (Beta)
|
||||
@@ -2753,6 +2776,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 13. Quick Feedback (Serial)
|
||||
@@ -2777,6 +2801,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 16. Analyze Reader Feedback
|
||||
@@ -2902,6 +2927,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Beta‑Feedback Closure Checklist
|
||||
@@ -2927,6 +2953,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 23. Comedic Timing & Humor Checklist
|
||||
@@ -2952,6 +2979,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/outline-scenes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 11. Outline Scenes
|
||||
@@ -2977,6 +3005,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/generate-scene-list.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Generate Scene List
|
||||
@@ -3002,6 +3031,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/genre-tropes-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Genre Tropes Checklist (General)
|
||||
@@ -3026,6 +3056,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 15. Sci‑Fi Technology Plausibility Checklist
|
||||
@@ -3050,6 +3081,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 12. Romance Emotional Beats Checklist
|
||||
@@ -3786,6 +3818,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -3907,6 +3940,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 16. Analyze Reader Feedback
|
||||
@@ -3932,6 +3966,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Analyze Story Structure
|
||||
|
||||
## Purpose
|
||||
@@ -4001,6 +4036,7 @@ Comprehensive structural analysis with actionable recommendations
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/assemble-kdp-package.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# tasks/assemble-kdp-package.md
|
||||
@@ -4032,6 +4068,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/brainstorm-premise.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 1. Brainstorm Premise
|
||||
@@ -4057,6 +4094,7 @@ steps:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/build-world.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. Build World
|
||||
@@ -4083,6 +4121,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/character-depth-pass.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 9. Character Depth Pass
|
||||
@@ -4107,6 +4146,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -4212,6 +4252,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-draft-section.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 4. Create Draft Section (Chapter)
|
||||
@@ -4240,6 +4281,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/develop-character.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 3. Develop Character
|
||||
@@ -4266,6 +4308,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/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.
|
||||
@@ -4356,6 +4399,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/expand-premise.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 7. Expand Premise (Snowflake Step 2)
|
||||
@@ -4381,6 +4425,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/expand-synopsis.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 8. Expand Synopsis (Snowflake Step 4)
|
||||
@@ -4406,6 +4451,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/final-polish.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 14. Final Polish
|
||||
@@ -4431,6 +4477,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/generate-cover-brief.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# tasks/generate-cover-brief.md
|
||||
@@ -4458,6 +4505,7 @@ steps:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/generate-cover-prompts.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# tasks/generate-cover-prompts.md
|
||||
@@ -4486,6 +4534,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/generate-scene-list.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Generate Scene List
|
||||
@@ -4511,6 +4560,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Incorporate Feedback
|
||||
@@ -4538,6 +4588,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/outline-scenes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 11. Outline Scenes
|
||||
@@ -4563,6 +4614,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Provide Feedback (Beta)
|
||||
@@ -4589,6 +4641,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/publish-chapter.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 15. Publish Chapter
|
||||
@@ -4614,6 +4667,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 13. Quick Feedback (Serial)
|
||||
@@ -4638,6 +4692,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/select-next-arc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 12. Select Next Arc (Serial)
|
||||
@@ -4663,6 +4718,7 @@ inputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workshop Dialog
|
||||
|
||||
## Purpose
|
||||
@@ -4729,6 +4785,7 @@ Refined dialog with stronger voices and dramatic impact
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Beta‑Feedback Closure Checklist
|
||||
@@ -4754,6 +4811,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 1. Character Consistency Checklist
|
||||
@@ -4779,6 +4837,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 23. Comedic Timing & Humor Checklist
|
||||
@@ -4804,6 +4863,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/cyberpunk-aesthetic-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 24. Cyberpunk Aesthetic Consistency Checklist
|
||||
@@ -4829,6 +4889,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/ebook-formatting-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 14. eBook Formatting Checklist
|
||||
@@ -4852,6 +4913,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/epic-poetry-meter-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 22. Epic Poetry Meter & Form Checklist
|
||||
@@ -4877,6 +4939,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 17. Fantasy Magic System Consistency Checklist
|
||||
@@ -4902,6 +4965,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/foreshadowing-payoff-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 9. Foreshadowing & Payoff Checklist
|
||||
@@ -4926,6 +4990,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/historical-accuracy-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 18. Historical Accuracy Checklist
|
||||
@@ -4951,6 +5016,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/horror-suspense-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 16. Horror Suspense & Scare Checklist
|
||||
@@ -4976,6 +5042,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/kdp-cover-ready-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# checklists/kdp-cover-ready-checklist.md
|
||||
@@ -5003,6 +5070,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 4. Line‑Edit Quality Checklist
|
||||
@@ -5028,6 +5096,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/marketing-copy-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 13. Marketing Copy Checklist
|
||||
@@ -5053,6 +5122,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/mystery-clue-trail-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 11. Mystery Clue Trail Checklist
|
||||
@@ -5078,6 +5148,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/orbital-mechanics-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 21. Hard‑Science Orbital Mechanics Checklist
|
||||
@@ -5103,6 +5174,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Plot Structure Checklist
|
||||
|
||||
## Opening
|
||||
@@ -5164,6 +5236,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Publication Readiness Checklist
|
||||
@@ -5189,6 +5262,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 12. Romance Emotional Beats Checklist
|
||||
@@ -5214,6 +5288,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/scene-quality-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 3. Scene Quality Checklist
|
||||
@@ -5239,6 +5314,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 15. Sci‑Fi Technology Plausibility Checklist
|
||||
@@ -5263,6 +5339,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/sensitivity-representation-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 7. Sensitivity & Representation Checklist
|
||||
@@ -5288,6 +5365,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/steampunk-gadget-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 25. Steampunk Gadget Plausibility Checklist
|
||||
@@ -5313,6 +5391,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/thriller-pacing-stakes-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 19. Thriller Pacing & Stakes Checklist
|
||||
@@ -5338,6 +5417,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/timeline-continuity-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 8. Timeline & Continuity Checklist
|
||||
@@ -5363,6 +5443,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/world-building-continuity-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 2. World‑Building Continuity Checklist
|
||||
@@ -5388,6 +5469,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/ya-appropriateness-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 20. YA Appropriateness Checklist
|
||||
@@ -5413,6 +5495,7 @@ items:
|
||||
|
||||
==================== START: .bmad-creative-writing/workflows/book-cover-design-workflow.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Book Cover Design Assets
|
||||
|
||||
# ============================================================
|
||||
@@ -6147,6 +6230,7 @@ outputs:
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -6358,6 +6442,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
||||
@@ -286,7 +286,7 @@ optional:
|
||||
|
||||
### 0) Load Core Config & Locate Story
|
||||
|
||||
- Read `bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root`
|
||||
- Read `.bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root`
|
||||
- Locate story file in `{story_root}/{epic}.{story}.*.md`
|
||||
- HALT if missing and ask for correct story id/path
|
||||
|
||||
@@ -386,7 +386,7 @@ Status Rule:
|
||||
|
||||
## Blocking Conditions
|
||||
|
||||
- Missing `bmad-core/core-config.yaml`
|
||||
- Missing `.bmad-core/core-config.yaml`
|
||||
- Story file not found for `story_id`
|
||||
- No QA artifacts found (neither gate nor assessments)
|
||||
- HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)
|
||||
|
||||
@@ -55,11 +55,7 @@ agent:
|
||||
id: game-qa
|
||||
title: Game Test Architect & TDD Enforcer (Godot)
|
||||
icon: 🎮🧪
|
||||
whenToUse: |
|
||||
Use for Godot game testing architecture, test-driven development enforcement,
|
||||
performance validation, and gameplay quality assurance. Ensures all code is
|
||||
test-first, performance targets are met, and player experience is validated.
|
||||
Enforces GUT for GDScript and GoDotTest/GodotTestDriver for C# with TDD practices.
|
||||
whenToUse: Use for Godot game testing architecture, test-driven development enforcement, performance validation, and gameplay quality assurance. Ensures all code is test-first, performance targets are met, and player experience is validated. Enforces GUT for GDScript and GoDotTest/GodotTestDriver for C# with TDD practices.
|
||||
customization: null
|
||||
persona:
|
||||
role: Game Test Architect & TDD Champion for Godot Development
|
||||
|
||||
@@ -558,11 +558,7 @@ agent:
|
||||
id: game-qa
|
||||
title: Game Test Architect & TDD Enforcer (Godot)
|
||||
icon: 🎮🧪
|
||||
whenToUse: |
|
||||
Use for Godot game testing architecture, test-driven development enforcement,
|
||||
performance validation, and gameplay quality assurance. Ensures all code is
|
||||
test-first, performance targets are met, and player experience is validated.
|
||||
Enforces GUT for GDScript and GoDotTest/GodotTestDriver for C# with TDD practices.
|
||||
whenToUse: Use for Godot game testing architecture, test-driven development enforcement, performance validation, and gameplay quality assurance. Ensures all code is test-first, performance targets are met, and player experience is validated. Enforces GUT for GDScript and GoDotTest/GodotTestDriver for C# with TDD practices.
|
||||
customization: null
|
||||
persona:
|
||||
role: Game Test Architect & TDD Champion for Godot Development
|
||||
@@ -8943,7 +8939,7 @@ optional:
|
||||
|
||||
### 0) Load Core Config & Locate Story
|
||||
|
||||
- Read `bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root`
|
||||
- Read `.bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root`
|
||||
- Locate story file in `{story_root}/{epic}.{story}.*.md`
|
||||
- HALT if missing and ask for correct story id/path
|
||||
|
||||
@@ -9043,7 +9039,7 @@ Status Rule:
|
||||
|
||||
## Blocking Conditions
|
||||
|
||||
- Missing `bmad-core/core-config.yaml`
|
||||
- Missing `.bmad-core/core-config.yaml`
|
||||
- Story file not found for `story_id`
|
||||
- No QA artifacts found (neither gate nor assessments)
|
||||
- HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)
|
||||
@@ -19903,7 +19899,7 @@ optional:
|
||||
|
||||
### 0) Load Core Config & Locate Story
|
||||
|
||||
- Read `bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root`
|
||||
- Read `.bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root`
|
||||
- Locate story file in `{story_root}/{epic}.{story}.*.md`
|
||||
- HALT if missing and ask for correct story id/path
|
||||
|
||||
@@ -20003,7 +19999,7 @@ Status Rule:
|
||||
|
||||
## Blocking Conditions
|
||||
|
||||
- Missing `bmad-core/core-config.yaml`
|
||||
- Missing `.bmad-core/core-config.yaml`
|
||||
- Story file not found for `story_id`
|
||||
- No QA artifacts found (neither gate nor assessments)
|
||||
- HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)
|
||||
|
||||
@@ -102,6 +102,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-infrastructure-devops/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -207,6 +208,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
|
||||
==================== START: .bmad-infrastructure-devops/tasks/review-infrastructure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Infrastructure Review Task
|
||||
|
||||
## Purpose
|
||||
@@ -370,6 +372,7 @@ REPEAT by Asking the user if they would like to perform another Reflective, Elic
|
||||
|
||||
==================== START: .bmad-infrastructure-devops/tasks/validate-infrastructure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Infrastructure Validation Task
|
||||
|
||||
## Purpose
|
||||
@@ -1588,6 +1591,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-infrastructure-devops/checklists/infrastructure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Infrastructure Change Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for validating infrastructure changes before deployment to production. The DevOps/Platform Engineer should systematically work through each item, ensuring the infrastructure is secure, compliant, resilient, and properly implemented according to organizational standards.
|
||||
@@ -2076,6 +2080,7 @@ This checklist serves as a comprehensive framework for validating infrastructure
|
||||
|
||||
==================== START: .bmad-infrastructure-devops/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
116
dist/teams/team-all.txt
vendored
116
dist/teams/team-all.txt
vendored
@@ -338,6 +338,7 @@ persona:
|
||||
focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
|
||||
core_principles:
|
||||
- CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
|
||||
- CRITICAL: ALWAYS check current folder structure before starting your story tasks, don't create new working directory if it already exists. Create new one when you're sure it's a brand new project.
|
||||
- CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
|
||||
- CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
|
||||
- Numbered Options - Always use numbered lists when presenting choices to the user
|
||||
@@ -505,11 +506,7 @@ agent:
|
||||
id: qa
|
||||
title: Test Architect & Quality Advisor
|
||||
icon: 🧪
|
||||
whenToUse: |
|
||||
Use for comprehensive test architecture review, quality gate decisions,
|
||||
and code improvement. Provides thorough analysis including requirements
|
||||
traceability, risk assessment, and test strategy.
|
||||
Advisory only - teams choose their quality bar.
|
||||
whenToUse: Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requirements traceability, risk assessment, and test strategy. Advisory only - teams choose their quality bar.
|
||||
customization: null
|
||||
persona:
|
||||
role: Test Architect with Quality Advisory Authority
|
||||
@@ -656,6 +653,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -777,6 +775,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 ⚠️
|
||||
@@ -882,6 +881,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
|
||||
@@ -961,6 +961,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
|
||||
@@ -1063,6 +1064,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.
|
||||
|
||||
@@ -1141,7 +1143,7 @@ npx bmad-method install
|
||||
|
||||
## Core Configuration (core-config.yaml)
|
||||
|
||||
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
|
||||
### What is core-config.yaml?
|
||||
|
||||
@@ -1771,6 +1773,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
|
||||
@@ -1929,6 +1932,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.
|
||||
@@ -2002,6 +2006,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.
|
||||
@@ -2284,6 +2289,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
|
||||
@@ -2630,10 +2636,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
|
||||
@@ -3721,6 +3728,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
@@ -3761,6 +3769,7 @@ sections:
|
||||
|
||||
==================== 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.
|
||||
@@ -4529,7 +4538,7 @@ sections:
|
||||
1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead."
|
||||
|
||||
2. **REQUIRED INPUTS**:
|
||||
- Completed brownfield-prd.md
|
||||
- Completed prd.md
|
||||
- Existing project technical documentation (from docs folder or user-provided)
|
||||
- Access to existing project structure (IDE or uploaded files)
|
||||
|
||||
@@ -4615,8 +4624,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:
|
||||
|
||||
@@ -4778,8 +4787,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:
|
||||
|
||||
@@ -4848,7 +4857,7 @@ sections:
|
||||
**Monitoring:** {{monitoring_approach}}
|
||||
|
||||
- id: coding-standards
|
||||
title: Coding Standards and Conventions
|
||||
title: Coding Standards
|
||||
instruction: |
|
||||
Ensure new code follows existing project conventions:
|
||||
|
||||
@@ -6034,6 +6043,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.
|
||||
@@ -6476,6 +6486,7 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
@@ -6483,6 +6494,7 @@ None Listed
|
||||
|
||||
==================== 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.
|
||||
@@ -6499,8 +6511,8 @@ Implement fixes based on QA results (gate and assessments) for a specific story.
|
||||
```yaml
|
||||
required:
|
||||
- story_id: '{epic}.{story}' # e.g., "2.2"
|
||||
- qa_root: from `bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
|
||||
- story_root: from `bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
|
||||
- qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
|
||||
- story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
|
||||
|
||||
optional:
|
||||
- story_title: '{title}' # derive from story H1 if missing
|
||||
@@ -6528,7 +6540,7 @@ optional:
|
||||
|
||||
### 0) Load Core Config & Locate Story
|
||||
|
||||
- Read `bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
|
||||
- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
|
||||
- Locate story file in `{story_root}/{epic}.{story}.*.md`
|
||||
- HALT if missing and ask for correct story id/path
|
||||
|
||||
@@ -6596,7 +6608,7 @@ Status Rule:
|
||||
|
||||
## Blocking Conditions
|
||||
|
||||
- Missing `bmad-core/core-config.yaml`
|
||||
- Missing `.bmad-core/core-config.yaml`
|
||||
- Story file not found for `story_id`
|
||||
- No QA artifacts found (neither gate nor assessments)
|
||||
- HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)
|
||||
@@ -6635,6 +6647,7 @@ Fix plan:
|
||||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -6656,7 +6669,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
|
||||
@@ -6773,6 +6786,7 @@ Provide a structured validation report including:
|
||||
|
||||
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
@@ -6871,6 +6885,7 @@ Be honest - it's better to flag issues now than have them discovered later.]]
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
@@ -7035,6 +7050,7 @@ The epic creation is successful when:
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -7186,6 +7202,7 @@ The story creation is successful when:
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -7260,6 +7277,7 @@ The story creation is successful when:
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -7939,6 +7957,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.
|
||||
@@ -8125,6 +8144,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.
|
||||
@@ -8640,6 +8660,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.
|
||||
@@ -8655,7 +8676,7 @@ First, determine the project type by checking:
|
||||
|
||||
2. Is this a BROWNFIELD project (enhancing existing system)?
|
||||
- Look for: References to existing codebase, enhancement/modification language
|
||||
- Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis
|
||||
- Check for: prd.md, architecture.md, existing system analysis
|
||||
|
||||
3. Does the project include UI/UX components?
|
||||
- Check for: frontend-architecture.md, UI/UX specifications, design files
|
||||
@@ -8673,8 +8694,8 @@ For GREENFIELD projects:
|
||||
|
||||
For BROWNFIELD projects:
|
||||
|
||||
- brownfield-prd.md - The brownfield enhancement requirements
|
||||
- brownfield-architecture.md - The enhancement architecture
|
||||
- prd.md - The brownfield enhancement requirements
|
||||
- architecture.md - The enhancement architecture
|
||||
- Existing project codebase access (CRITICAL - cannot proceed without this)
|
||||
- Current deployment configuration and infrastructure details
|
||||
- Database schemas, API documentation, monitoring setup
|
||||
@@ -9076,6 +9097,7 @@ After presenting the report, ask if the user wants:
|
||||
|
||||
==================== 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.
|
||||
@@ -9085,11 +9107,11 @@ Quick NFR validation focused on the core four: security, performance, reliabilit
|
||||
```yaml
|
||||
required:
|
||||
- story_id: '{epic}.{story}' # e.g., "1.3"
|
||||
- story_path: `bmad-core/core-config.yaml` for the `devStoryLocation`
|
||||
- story_path: `.bmad-core/core-config.yaml` for the `devStoryLocation`
|
||||
|
||||
optional:
|
||||
- architecture_refs: `bmad-core/core-config.yaml` for the `architecture.architectureFile`
|
||||
- technical_preferences: `bmad-core/core-config.yaml` for the `technicalPreferences`
|
||||
- architecture_refs: `.bmad-core/core-config.yaml` for the `architecture.architectureFile`
|
||||
- technical_preferences: `.bmad-core/core-config.yaml` for the `technicalPreferences`
|
||||
- acceptance_criteria: From story file
|
||||
```
|
||||
|
||||
@@ -9423,6 +9445,7 @@ performance_deep_dive:
|
||||
|
||||
==================== 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.
|
||||
@@ -9439,7 +9462,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision
|
||||
|
||||
## Gate File Location
|
||||
|
||||
**ALWAYS** check the `bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
|
||||
**ALWAYS** check the `.bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
|
||||
|
||||
Slug rules:
|
||||
|
||||
@@ -9549,7 +9572,7 @@ waiver:
|
||||
|
||||
## Output Requirements
|
||||
|
||||
1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `bmad-core/core-config.yaml`
|
||||
1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `.bmad-core/core-config.yaml`
|
||||
2. **ALWAYS** append this exact format to story's QA Results section:
|
||||
|
||||
```text
|
||||
@@ -9588,6 +9611,7 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
|
||||
|
||||
==================== 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.
|
||||
@@ -9774,7 +9798,7 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
|
||||
**Template and Directory:**
|
||||
|
||||
- Render from `../templates/qa-gate-tmpl.yaml`
|
||||
- Create directory defined in `qa.qaLocation/gates` (see `bmad-core/core-config.yaml`) if missing
|
||||
- Create directory defined in `qa.qaLocation/gates` (see `.bmad-core/core-config.yaml`) if missing
|
||||
- Save to: `qa.qaLocation/gates/{epic}.{story}-{slug}.yml`
|
||||
|
||||
Gate file structure:
|
||||
@@ -9906,6 +9930,7 @@ After review:
|
||||
|
||||
==================== 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.
|
||||
@@ -10263,6 +10288,7 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.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.
|
||||
@@ -10441,6 +10467,7 @@ Before finalizing, verify:
|
||||
|
||||
==================== 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.
|
||||
@@ -10815,6 +10842,7 @@ optional_fields_examples:
|
||||
|
||||
==================== START: .bmad-core/tasks/create-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -10931,6 +10959,7 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
||||
|
||||
==================== 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.
|
||||
@@ -11088,6 +11117,7 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
|
||||
|
||||
==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create AI Frontend Prompt Task
|
||||
|
||||
## Purpose
|
||||
@@ -11657,7 +11687,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
|
||||
@@ -11674,7 +11704,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!
|
||||
@@ -11904,7 +11934,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
|
||||
@@ -11921,7 +11951,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!
|
||||
@@ -12102,7 +12132,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
|
||||
@@ -12119,7 +12149,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!
|
||||
@@ -12255,12 +12285,12 @@ workflow:
|
||||
condition: po_checklist_issues
|
||||
notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
|
||||
|
||||
- project_setup_guidance:
|
||||
- step: project_setup_guidance
|
||||
action: guide_project_structure
|
||||
condition: user_has_generated_ui
|
||||
notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo alongside backend repo. For monorepo, place in apps/web or packages/frontend directory. Review architecture document for specific guidance."
|
||||
|
||||
- development_order_guidance:
|
||||
- step: development_order_guidance
|
||||
action: guide_development_sequence
|
||||
notes: "Based on PRD stories: If stories are frontend-heavy, start with frontend project/directory first. If backend-heavy or API-first, start with backend. For tightly coupled features, follow story sequence in monorepo setup. Reference sharded PRD epics for development order."
|
||||
|
||||
@@ -12328,7 +12358,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
|
||||
@@ -12345,7 +12375,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!
|
||||
@@ -12548,7 +12578,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
|
||||
@@ -12565,7 +12595,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!
|
||||
@@ -12708,7 +12738,7 @@ workflow:
|
||||
condition: po_checklist_issues
|
||||
notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
|
||||
|
||||
- project_setup_guidance:
|
||||
- step: project_setup_guidance
|
||||
action: guide_project_structure
|
||||
condition: user_has_generated_ui
|
||||
notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance."
|
||||
@@ -12777,7 +12807,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
|
||||
@@ -12794,7 +12824,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!
|
||||
|
||||
79
dist/teams/team-fullstack.txt
vendored
79
dist/teams/team-fullstack.txt
vendored
@@ -491,6 +491,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -612,6 +613,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 ⚠️
|
||||
@@ -717,6 +719,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
|
||||
@@ -796,6 +799,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
|
||||
@@ -898,6 +902,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.
|
||||
|
||||
@@ -976,7 +981,7 @@ npx bmad-method install
|
||||
|
||||
## Core Configuration (core-config.yaml)
|
||||
|
||||
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
|
||||
### What is core-config.yaml?
|
||||
|
||||
@@ -1606,6 +1611,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
|
||||
@@ -1764,6 +1770,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.
|
||||
@@ -1837,6 +1844,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.
|
||||
@@ -2119,6 +2127,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
|
||||
@@ -2465,10 +2474,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
|
||||
@@ -3556,6 +3566,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
@@ -3596,6 +3607,7 @@ sections:
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
@@ -3760,6 +3772,7 @@ The epic creation is successful when:
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -3911,6 +3924,7 @@ The story creation is successful when:
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -3985,6 +3999,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.
|
||||
@@ -4075,6 +4090,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -4754,6 +4770,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.
|
||||
@@ -4940,6 +4957,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.
|
||||
@@ -5314,6 +5332,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
|
||||
@@ -5321,6 +5340,7 @@ None Listed
|
||||
|
||||
==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create AI Frontend Prompt Task
|
||||
|
||||
## Purpose
|
||||
@@ -6407,7 +6427,7 @@ sections:
|
||||
1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead."
|
||||
|
||||
2. **REQUIRED INPUTS**:
|
||||
- Completed brownfield-prd.md
|
||||
- Completed prd.md
|
||||
- Existing project technical documentation (from docs folder or user-provided)
|
||||
- Access to existing project structure (IDE or uploaded files)
|
||||
|
||||
@@ -6493,8 +6513,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:
|
||||
|
||||
@@ -6656,8 +6676,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:
|
||||
|
||||
@@ -6726,7 +6746,7 @@ sections:
|
||||
**Monitoring:** {{monitoring_approach}}
|
||||
|
||||
- id: coding-standards
|
||||
title: Coding Standards and Conventions
|
||||
title: Coding Standards
|
||||
instruction: |
|
||||
Ensure new code follows existing project conventions:
|
||||
|
||||
@@ -7912,6 +7932,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.
|
||||
@@ -8354,6 +8375,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
|
||||
@@ -8375,7 +8397,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
|
||||
@@ -8633,6 +8655,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.
|
||||
@@ -8648,7 +8671,7 @@ First, determine the project type by checking:
|
||||
|
||||
2. Is this a BROWNFIELD project (enhancing existing system)?
|
||||
- Look for: References to existing codebase, enhancement/modification language
|
||||
- Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis
|
||||
- Check for: prd.md, architecture.md, existing system analysis
|
||||
|
||||
3. Does the project include UI/UX components?
|
||||
- Check for: frontend-architecture.md, UI/UX specifications, design files
|
||||
@@ -8666,8 +8689,8 @@ For GREENFIELD projects:
|
||||
|
||||
For BROWNFIELD projects:
|
||||
|
||||
- brownfield-prd.md - The brownfield enhancement requirements
|
||||
- brownfield-architecture.md - The enhancement architecture
|
||||
- prd.md - The brownfield enhancement requirements
|
||||
- architecture.md - The enhancement architecture
|
||||
- Existing project codebase access (CRITICAL - cannot proceed without this)
|
||||
- Current deployment configuration and infrastructure details
|
||||
- Database schemas, API documentation, monitoring setup
|
||||
@@ -9230,7 +9253,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
|
||||
@@ -9247,7 +9270,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!
|
||||
@@ -9477,7 +9500,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
|
||||
@@ -9494,7 +9517,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!
|
||||
@@ -9675,7 +9698,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
|
||||
@@ -9692,7 +9715,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!
|
||||
@@ -9828,12 +9851,12 @@ workflow:
|
||||
condition: po_checklist_issues
|
||||
notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
|
||||
|
||||
- project_setup_guidance:
|
||||
- step: project_setup_guidance
|
||||
action: guide_project_structure
|
||||
condition: user_has_generated_ui
|
||||
notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo alongside backend repo. For monorepo, place in apps/web or packages/frontend directory. Review architecture document for specific guidance."
|
||||
|
||||
- development_order_guidance:
|
||||
- step: development_order_guidance
|
||||
action: guide_development_sequence
|
||||
notes: "Based on PRD stories: If stories are frontend-heavy, start with frontend project/directory first. If backend-heavy or API-first, start with backend. For tightly coupled features, follow story sequence in monorepo setup. Reference sharded PRD epics for development order."
|
||||
|
||||
@@ -9901,7 +9924,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
|
||||
@@ -9918,7 +9941,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!
|
||||
@@ -10121,7 +10144,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
|
||||
@@ -10138,7 +10161,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!
|
||||
@@ -10281,7 +10304,7 @@ workflow:
|
||||
condition: po_checklist_issues
|
||||
notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
|
||||
|
||||
- project_setup_guidance:
|
||||
- step: project_setup_guidance
|
||||
action: guide_project_structure
|
||||
condition: user_has_generated_ui
|
||||
notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance."
|
||||
@@ -10350,7 +10373,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
|
||||
@@ -10367,7 +10390,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!
|
||||
|
||||
61
dist/teams/team-ide-minimal.txt
vendored
61
dist/teams/team-ide-minimal.txt
vendored
@@ -309,6 +309,7 @@ persona:
|
||||
focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
|
||||
core_principles:
|
||||
- CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
|
||||
- CRITICAL: ALWAYS check current folder structure before starting your story tasks, don't create new working directory if it already exists. Create new one when you're sure it's a brand new project.
|
||||
- CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
|
||||
- CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
|
||||
- Numbered Options - Always use numbered lists when presenting choices to the user
|
||||
@@ -353,11 +354,7 @@ agent:
|
||||
id: qa
|
||||
title: Test Architect & Quality Advisor
|
||||
icon: 🧪
|
||||
whenToUse: |
|
||||
Use for comprehensive test architecture review, quality gate decisions,
|
||||
and code improvement. Provides thorough analysis including requirements
|
||||
traceability, risk assessment, and test strategy.
|
||||
Advisory only - teams choose their quality bar.
|
||||
whenToUse: Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requirements traceability, risk assessment, and test strategy. Advisory only - teams choose their quality bar.
|
||||
customization: null
|
||||
persona:
|
||||
role: Test Architect with Quality Advisory Authority
|
||||
@@ -410,6 +407,7 @@ dependencies:
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -531,6 +529,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 ⚠️
|
||||
@@ -636,6 +635,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
|
||||
@@ -715,6 +715,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
|
||||
@@ -817,6 +818,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.
|
||||
|
||||
@@ -895,7 +897,7 @@ npx bmad-method install
|
||||
|
||||
## Core Configuration (core-config.yaml)
|
||||
|
||||
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
|
||||
### What is core-config.yaml?
|
||||
|
||||
@@ -1525,6 +1527,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
|
||||
@@ -1683,6 +1686,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.
|
||||
@@ -1756,6 +1760,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -1830,6 +1835,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
|
||||
==================== 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.
|
||||
@@ -1920,6 +1926,7 @@ The LLM will:
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -2109,6 +2116,7 @@ Document sharded successfully:
|
||||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -2130,7 +2138,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
|
||||
@@ -2388,6 +2396,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.
|
||||
@@ -2574,6 +2583,7 @@ Keep it action-oriented and forward-looking.]]
|
||||
|
||||
==================== 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.
|
||||
@@ -2589,7 +2599,7 @@ First, determine the project type by checking:
|
||||
|
||||
2. Is this a BROWNFIELD project (enhancing existing system)?
|
||||
- Look for: References to existing codebase, enhancement/modification language
|
||||
- Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis
|
||||
- Check for: prd.md, architecture.md, existing system analysis
|
||||
|
||||
3. Does the project include UI/UX components?
|
||||
- Check for: frontend-architecture.md, UI/UX specifications, design files
|
||||
@@ -2607,8 +2617,8 @@ For GREENFIELD projects:
|
||||
|
||||
For BROWNFIELD projects:
|
||||
|
||||
- brownfield-prd.md - The brownfield enhancement requirements
|
||||
- brownfield-architecture.md - The enhancement architecture
|
||||
- prd.md - The brownfield enhancement requirements
|
||||
- architecture.md - The enhancement architecture
|
||||
- Existing project codebase access (CRITICAL - cannot proceed without this)
|
||||
- Current deployment configuration and infrastructure details
|
||||
- Database schemas, API documentation, monitoring setup
|
||||
@@ -3010,6 +3020,7 @@ After presenting the report, ask if the user wants:
|
||||
|
||||
==================== START: .bmad-core/tasks/create-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -3126,6 +3137,7 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
||||
|
||||
==================== 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.
|
||||
@@ -3283,6 +3295,7 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
|
||||
|
||||
==================== 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.
|
||||
@@ -3299,8 +3312,8 @@ Implement fixes based on QA results (gate and assessments) for a specific story.
|
||||
```yaml
|
||||
required:
|
||||
- story_id: '{epic}.{story}' # e.g., "2.2"
|
||||
- qa_root: from `bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
|
||||
- story_root: from `bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
|
||||
- qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
|
||||
- story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
|
||||
|
||||
optional:
|
||||
- story_title: '{title}' # derive from story H1 if missing
|
||||
@@ -3328,7 +3341,7 @@ optional:
|
||||
|
||||
### 0) Load Core Config & Locate Story
|
||||
|
||||
- Read `bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
|
||||
- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
|
||||
- Locate story file in `{story_root}/{epic}.{story}.*.md`
|
||||
- HALT if missing and ask for correct story id/path
|
||||
|
||||
@@ -3396,7 +3409,7 @@ Status Rule:
|
||||
|
||||
## Blocking Conditions
|
||||
|
||||
- Missing `bmad-core/core-config.yaml`
|
||||
- Missing `.bmad-core/core-config.yaml`
|
||||
- Story file not found for `story_id`
|
||||
- No QA artifacts found (neither gate nor assessments)
|
||||
- HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)
|
||||
@@ -3435,6 +3448,7 @@ Fix plan:
|
||||
|
||||
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
@@ -3533,6 +3547,7 @@ Be honest - it's better to flag issues now than have them discovered later.]]
|
||||
|
||||
==================== 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.
|
||||
@@ -3542,11 +3557,11 @@ Quick NFR validation focused on the core four: security, performance, reliabilit
|
||||
```yaml
|
||||
required:
|
||||
- story_id: '{epic}.{story}' # e.g., "1.3"
|
||||
- story_path: `bmad-core/core-config.yaml` for the `devStoryLocation`
|
||||
- story_path: `.bmad-core/core-config.yaml` for the `devStoryLocation`
|
||||
|
||||
optional:
|
||||
- architecture_refs: `bmad-core/core-config.yaml` for the `architecture.architectureFile`
|
||||
- technical_preferences: `bmad-core/core-config.yaml` for the `technicalPreferences`
|
||||
- architecture_refs: `.bmad-core/core-config.yaml` for the `architecture.architectureFile`
|
||||
- technical_preferences: `.bmad-core/core-config.yaml` for the `technicalPreferences`
|
||||
- acceptance_criteria: From story file
|
||||
```
|
||||
|
||||
@@ -3880,6 +3895,7 @@ performance_deep_dive:
|
||||
|
||||
==================== 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.
|
||||
@@ -3896,7 +3912,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision
|
||||
|
||||
## Gate File Location
|
||||
|
||||
**ALWAYS** check the `bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
|
||||
**ALWAYS** check the `.bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
|
||||
|
||||
Slug rules:
|
||||
|
||||
@@ -4006,7 +4022,7 @@ waiver:
|
||||
|
||||
## Output Requirements
|
||||
|
||||
1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `bmad-core/core-config.yaml`
|
||||
1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `.bmad-core/core-config.yaml`
|
||||
2. **ALWAYS** append this exact format to story's QA Results section:
|
||||
|
||||
```text
|
||||
@@ -4045,6 +4061,7 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
|
||||
|
||||
==================== 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.
|
||||
@@ -4231,7 +4248,7 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
|
||||
**Template and Directory:**
|
||||
|
||||
- Render from `../templates/qa-gate-tmpl.yaml`
|
||||
- Create directory defined in `qa.qaLocation/gates` (see `bmad-core/core-config.yaml`) if missing
|
||||
- Create directory defined in `qa.qaLocation/gates` (see `.bmad-core/core-config.yaml`) if missing
|
||||
- Save to: `qa.qaLocation/gates/{epic}.{story}-{slug}.yml`
|
||||
|
||||
Gate file structure:
|
||||
@@ -4363,6 +4380,7 @@ After review:
|
||||
|
||||
==================== 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.
|
||||
@@ -4720,6 +4738,7 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.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.
|
||||
@@ -4898,6 +4917,7 @@ Before finalizing, verify:
|
||||
|
||||
==================== 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.
|
||||
@@ -5272,6 +5292,7 @@ optional_fields_examples:
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
56
dist/teams/team-no-ui.txt
vendored
56
dist/teams/team-no-ui.txt
vendored
@@ -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.
|
||||
|
||||
@@ -922,7 +927,7 @@ npx bmad-method install
|
||||
|
||||
## Core Configuration (core-config.yaml)
|
||||
|
||||
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
|
||||
|
||||
### What is core-config.yaml?
|
||||
|
||||
@@ -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
|
||||
@@ -5945,7 +5964,7 @@ sections:
|
||||
1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead."
|
||||
|
||||
2. **REQUIRED INPUTS**:
|
||||
- Completed brownfield-prd.md
|
||||
- Completed prd.md
|
||||
- Existing project technical documentation (from docs folder or user-provided)
|
||||
- Access to existing project structure (IDE or uploaded files)
|
||||
|
||||
@@ -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.
|
||||
@@ -8186,7 +8208,7 @@ First, determine the project type by checking:
|
||||
|
||||
2. Is this a BROWNFIELD project (enhancing existing system)?
|
||||
- Look for: References to existing codebase, enhancement/modification language
|
||||
- Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis
|
||||
- Check for: prd.md, architecture.md, existing system analysis
|
||||
|
||||
3. Does the project include UI/UX components?
|
||||
- Check for: frontend-architecture.md, UI/UX specifications, design files
|
||||
@@ -8204,8 +8226,8 @@ For GREENFIELD projects:
|
||||
|
||||
For BROWNFIELD projects:
|
||||
|
||||
- brownfield-prd.md - The brownfield enhancement requirements
|
||||
- brownfield-architecture.md - The enhancement architecture
|
||||
- prd.md - The brownfield enhancement requirements
|
||||
- architecture.md - The enhancement architecture
|
||||
- Existing project codebase access (CRITICAL - cannot proceed without this)
|
||||
- Current deployment configuration and infrastructure details
|
||||
- Database schemas, API documentation, monitoring setup
|
||||
@@ -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!
|
||||
|
||||
@@ -187,6 +187,53 @@ If you want to do the planning on the web with Claude (Sonnet 4 or Opus), Gemini
|
||||
npx bmad-method install
|
||||
```
|
||||
|
||||
### OpenCode
|
||||
|
||||
BMAD integrates with OpenCode via a project-level `opencode.jsonc`/`opencode.json` (JSON-only, no Markdown fallback).
|
||||
|
||||
- Installation:
|
||||
- Run `npx bmad-method install` and choose `OpenCode` in the IDE list.
|
||||
- The installer will detect an existing `opencode.jsonc`/`opencode.json` or create a minimal `opencode.jsonc` if missing.
|
||||
- It will:
|
||||
- Ensure `instructions` includes `.bmad-core/core-config.yaml` (and each selected expansion pack’s `config.yaml`).
|
||||
- Merge BMAD agents and commands using file references (`{file:./.bmad-core/...}`), idempotently.
|
||||
- Preserve other top-level fields and user-defined entries.
|
||||
|
||||
- Prefixes and collisions:
|
||||
- You can opt-in to prefix agent keys with `bmad-` and command keys with `bmad:tasks:` to avoid name collisions.
|
||||
- If a key already exists and is not BMAD-managed, the installer will skip it and suggest enabling prefixes.
|
||||
|
||||
- What gets added:
|
||||
- `instructions`: `.bmad-core/core-config.yaml` plus any selected expansion pack `config.yaml` files.
|
||||
- `agent`: BMAD agents from core and selected packs.
|
||||
- `prompt`: `{file:./.bmad-core/agents/<id>.md}` (or pack path)
|
||||
- `mode`: `primary` for orchestrators, otherwise `all`
|
||||
- `tools`: `{ write: true, edit: true, bash: true }`
|
||||
- `description`: extracted from the agent’s `whenToUse`
|
||||
- `command`: BMAD tasks from core and selected packs.
|
||||
- `template`: `{file:./.bmad-core/tasks/<id>.md}` (or pack path)
|
||||
- `description`: extracted from the task’s “Purpose” section
|
||||
|
||||
- Selected Packages Only:
|
||||
- The installer includes agents and tasks only from the packages you selected in the earlier step (core and chosen packs).
|
||||
|
||||
- Refresh after changes:
|
||||
- Re-run:
|
||||
```bash
|
||||
npx bmad-method install -f -i opencode
|
||||
```
|
||||
- The installer safely updates entries without duplication and preserves your custom fields and comments.
|
||||
|
||||
- Optional convenience script:
|
||||
- You can add a script to your project’s `package.json` for quick refreshes:
|
||||
```json
|
||||
{
|
||||
"scripts": {
|
||||
"bmad:opencode": "bmad-method install -f -i opencode"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Codex (CLI & Web)
|
||||
|
||||
BMAD integrates with OpenAI Codex via `AGENTS.md` and committed core agent files.
|
||||
@@ -501,7 +548,7 @@ When creating custom web bundles or uploading to AI platforms, include your `tec
|
||||
|
||||
## Core Configuration
|
||||
|
||||
The `bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml.
|
||||
The `.bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml.
|
||||
|
||||
### Developer Context Files
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ activation-instructions:
|
||||
- Assess user goal against available agents and workflows in this bundle
|
||||
- If clear match to an agent's expertise, suggest transformation with *agent command
|
||||
- If project-oriented, suggest *workflow-guidance to explore options
|
||||
- Load resources only when needed - never pre-load (Exception: Read `bmad-core/core-config.yaml` during activation)
|
||||
- Load resources only when needed - never pre-load (Exception: Read `.bmad-core/core-config.yaml` during activation)
|
||||
- CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
|
||||
agent:
|
||||
name: BMad Orchestrator
|
||||
|
||||
@@ -34,8 +34,7 @@ agent:
|
||||
id: game-qa
|
||||
title: Game Test Architect & TDD Enforcer (Godot)
|
||||
icon: 🎮🧪
|
||||
whenToUse: |
|
||||
Use for Godot game testing architecture, test-driven development enforcement,
|
||||
whenToUse: Use for Godot game testing architecture, test-driven development enforcement,
|
||||
performance validation, and gameplay quality assurance. Ensures all code is
|
||||
test-first, performance targets are met, and player experience is validated.
|
||||
Enforces GUT for GDScript and GoDotTest/GodotTestDriver for C# with TDD practices.
|
||||
|
||||
@@ -50,7 +50,7 @@ optional:
|
||||
|
||||
### 0) Load Core Config & Locate Story
|
||||
|
||||
- Read `bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root`
|
||||
- Read `.bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root`
|
||||
- Locate story file in `{story_root}/{epic}.{story}.*.md`
|
||||
- HALT if missing and ask for correct story id/path
|
||||
|
||||
@@ -150,7 +150,7 @@ Status Rule:
|
||||
|
||||
## Blocking Conditions
|
||||
|
||||
- Missing `bmad-core/core-config.yaml`
|
||||
- Missing `.bmad-core/core-config.yaml`
|
||||
- Story file not found for `story_id`
|
||||
- No QA artifacts found (neither gate nor assessments)
|
||||
- HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)
|
||||
|
||||
47
package-lock.json
generated
47
package-lock.json
generated
@@ -1,17 +1,18 @@
|
||||
{
|
||||
"name": "bmad-method",
|
||||
"version": "4.42.1",
|
||||
"version": "4.43.0",
|
||||
"lockfileVersion": 3,
|
||||
"requires": true,
|
||||
"packages": {
|
||||
"": {
|
||||
"name": "bmad-method",
|
||||
"version": "4.42.1",
|
||||
"version": "4.43.0",
|
||||
"license": "MIT",
|
||||
"dependencies": {
|
||||
"@kayvan/markdown-tree-parser": "^1.6.1",
|
||||
"chalk": "^4.1.2",
|
||||
"commander": "^14.0.0",
|
||||
"comment-json": "^4.2.5",
|
||||
"fs-extra": "^11.3.1",
|
||||
"glob": "^11.0.3",
|
||||
"ignore": "^7.0.5",
|
||||
@@ -2950,6 +2951,12 @@
|
||||
"dev": true,
|
||||
"license": "MIT"
|
||||
},
|
||||
"node_modules/array-timsort": {
|
||||
"version": "1.0.3",
|
||||
"resolved": "https://registry.npmjs.org/array-timsort/-/array-timsort-1.0.3.tgz",
|
||||
"integrity": "sha512-/+3GRL7dDAGEfM6TseQk/U+mi18TU2Ms9I3UlLdUMhz2hbvGNTKdj9xniwXfUqgYhHxRx0+8UnKkvlNwVU+cWQ==",
|
||||
"license": "MIT"
|
||||
},
|
||||
"node_modules/array-union": {
|
||||
"version": "2.1.0",
|
||||
"resolved": "https://registry.npmjs.org/array-union/-/array-union-2.1.0.tgz",
|
||||
@@ -3674,6 +3681,22 @@
|
||||
"node": ">=20"
|
||||
}
|
||||
},
|
||||
"node_modules/comment-json": {
|
||||
"version": "4.2.5",
|
||||
"resolved": "https://registry.npmjs.org/comment-json/-/comment-json-4.2.5.tgz",
|
||||
"integrity": "sha512-bKw/r35jR3HGt5PEPm1ljsQQGyCrR8sFGNiN5L+ykDHdpO8Smxkrkla9Yi6NkQyUrb8V54PGhfMs6NrIwtxtdw==",
|
||||
"license": "MIT",
|
||||
"dependencies": {
|
||||
"array-timsort": "^1.0.3",
|
||||
"core-util-is": "^1.0.3",
|
||||
"esprima": "^4.0.1",
|
||||
"has-own-prop": "^2.0.0",
|
||||
"repeat-string": "^1.6.1"
|
||||
},
|
||||
"engines": {
|
||||
"node": ">= 6"
|
||||
}
|
||||
},
|
||||
"node_modules/compare-func": {
|
||||
"version": "2.0.0",
|
||||
"resolved": "https://registry.npmjs.org/compare-func/-/compare-func-2.0.0.tgz",
|
||||
@@ -3806,7 +3829,6 @@
|
||||
"version": "1.0.3",
|
||||
"resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.3.tgz",
|
||||
"integrity": "sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==",
|
||||
"dev": true,
|
||||
"license": "MIT"
|
||||
},
|
||||
"node_modules/cosmiconfig": {
|
||||
@@ -4845,7 +4867,6 @@
|
||||
"version": "4.0.1",
|
||||
"resolved": "https://registry.npmjs.org/esprima/-/esprima-4.0.1.tgz",
|
||||
"integrity": "sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==",
|
||||
"dev": true,
|
||||
"license": "BSD-2-Clause",
|
||||
"bin": {
|
||||
"esparse": "bin/esparse.js",
|
||||
@@ -5502,6 +5523,15 @@
|
||||
"node": ">=8"
|
||||
}
|
||||
},
|
||||
"node_modules/has-own-prop": {
|
||||
"version": "2.0.0",
|
||||
"resolved": "https://registry.npmjs.org/has-own-prop/-/has-own-prop-2.0.0.tgz",
|
||||
"integrity": "sha512-Pq0h+hvsVm6dDEa8x82GnLSYHOzNDt7f0ddFa3FqcQlgzEiptPqL+XrOJNavjOzSYiYWIrgeVYYgGlLmnxwilQ==",
|
||||
"license": "MIT",
|
||||
"engines": {
|
||||
"node": ">=8"
|
||||
}
|
||||
},
|
||||
"node_modules/highlight.js": {
|
||||
"version": "10.7.3",
|
||||
"resolved": "https://registry.npmjs.org/highlight.js/-/highlight.js-10.7.3.tgz",
|
||||
@@ -12050,6 +12080,15 @@
|
||||
"url": "https://opencollective.com/unified"
|
||||
}
|
||||
},
|
||||
"node_modules/repeat-string": {
|
||||
"version": "1.6.1",
|
||||
"resolved": "https://registry.npmjs.org/repeat-string/-/repeat-string-1.6.1.tgz",
|
||||
"integrity": "sha512-PV0dzCYDNfRi1jCDbJzpW7jNNDRuCOG/jI5ctQcGKt/clZD+YcPS3yIlWuTJMmESC8aevCFmWJy5wjAFgNqN6w==",
|
||||
"license": "MIT",
|
||||
"engines": {
|
||||
"node": ">=0.10"
|
||||
}
|
||||
},
|
||||
"node_modules/require-directory": {
|
||||
"version": "2.1.1",
|
||||
"resolved": "https://registry.npmjs.org/require-directory/-/require-directory-2.1.1.tgz",
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"$schema": "https://json.schemastore.org/package.json",
|
||||
"name": "bmad-method",
|
||||
"version": "4.43.0",
|
||||
"version": "4.44.1",
|
||||
"description": "Breakthrough Method of Agile AI-driven Development",
|
||||
"keywords": [
|
||||
"agile",
|
||||
@@ -75,6 +75,7 @@
|
||||
"@kayvan/markdown-tree-parser": "^1.6.1",
|
||||
"chalk": "^4.1.2",
|
||||
"commander": "^14.0.0",
|
||||
"comment-json": "^4.2.5",
|
||||
"fs-extra": "^11.3.1",
|
||||
"glob": "^11.0.3",
|
||||
"ignore": "^7.0.5",
|
||||
|
||||
@@ -49,7 +49,7 @@ program
|
||||
.option('-d, --directory <path>', 'Installation directory')
|
||||
.option(
|
||||
'-i, --ide <ide...>',
|
||||
'Configure for specific IDE(s) - can specify multiple (cursor, claude-code, windsurf, trae, roo, kilo, cline, gemini, qwen-code, github-copilot, codex, codex-web, auggie-cli, iflow-cli, other)',
|
||||
'Configure for specific IDE(s) - can specify multiple (cursor, claude-code, windsurf, trae, roo, kilo, cline, gemini, qwen-code, github-copilot, codex, codex-web, auggie-cli, iflow-cli, opencode, other)',
|
||||
)
|
||||
.option(
|
||||
'-e, --expansion-packs <packs...>',
|
||||
@@ -410,6 +410,7 @@ async function promptInstallation() {
|
||||
{ name: 'Auggie CLI (Augment Code)', value: 'auggie-cli' },
|
||||
{ name: 'Codex CLI', value: 'codex' },
|
||||
{ name: 'Codex Web', value: 'codex-web' },
|
||||
{ name: 'OpenCode', value: 'opencode' },
|
||||
],
|
||||
},
|
||||
]);
|
||||
@@ -478,6 +479,43 @@ async function promptInstallation() {
|
||||
answers.githubCopilotConfig = { configChoice };
|
||||
}
|
||||
|
||||
// Configure OpenCode immediately if selected
|
||||
if (ides.includes('opencode')) {
|
||||
console.log(chalk.cyan('\n⚙️ OpenCode Configuration'));
|
||||
console.log(
|
||||
chalk.dim(
|
||||
'OpenCode will include agents and tasks from the packages you selected above; choose optional key prefixes (defaults: no prefixes).\n',
|
||||
),
|
||||
);
|
||||
|
||||
const { useAgentPrefix, useCommandPrefix } = await inquirer.prompt([
|
||||
{
|
||||
type: 'confirm',
|
||||
name: 'useAgentPrefix',
|
||||
message: "Prefix agent keys with 'bmad-'? (e.g., 'bmad-dev')",
|
||||
default: true,
|
||||
},
|
||||
{
|
||||
type: 'confirm',
|
||||
name: 'useCommandPrefix',
|
||||
message: "Prefix command keys with 'bmad:tasks:'? (e.g., 'bmad:tasks:create-doc')",
|
||||
default: true,
|
||||
},
|
||||
]);
|
||||
|
||||
answers.openCodeConfig = {
|
||||
opencode: {
|
||||
useAgentPrefix,
|
||||
useCommandPrefix,
|
||||
},
|
||||
// pass previously selected packages so IDE setup only applies those
|
||||
selectedPackages: {
|
||||
includeCore: selectedItems.includes('bmad-core'),
|
||||
packs: answers.expansionPacks || [],
|
||||
},
|
||||
};
|
||||
}
|
||||
|
||||
// Configure Auggie CLI (Augment Code) immediately if selected
|
||||
if (ides.includes('auggie-cli')) {
|
||||
console.log(chalk.cyan('\n📍 Auggie CLI Location Configuration'));
|
||||
|
||||
@@ -171,3 +171,14 @@ ide-configurations:
|
||||
# 2. Commit `.bmad-core/` and `AGENTS.md` to your repository.
|
||||
# 3. Open the repo in Codex Web and reference agents naturally (e.g., "As dev, ...").
|
||||
# 4. Re-run this installer to refresh agent sections when the core changes.
|
||||
|
||||
opencode:
|
||||
name: OpenCode CLI
|
||||
format: jsonc-config
|
||||
file: opencode.jsonc
|
||||
instructions: |
|
||||
# To use BMAD agents with OpenCode CLI:
|
||||
# 1. The installer creates/updates `opencode.jsonc` at your project root.
|
||||
# 2. It ensures the BMAD core instructions file is referenced: `./.bmad-core/core-config.yaml`.
|
||||
# 3. If an existing `opencode.json` or `opencode.jsonc` is present, it is preserved and only `instructions` are minimally merged.
|
||||
# 4. Run `opencode` in this project to use your configured agents and commands.
|
||||
|
||||
@@ -3,6 +3,7 @@ const fs = require('fs-extra');
|
||||
const yaml = require('js-yaml');
|
||||
const chalk = require('chalk');
|
||||
const inquirer = require('inquirer');
|
||||
const cjson = require('comment-json');
|
||||
const fileManager = require('./file-manager');
|
||||
const configLoader = require('./config-loader');
|
||||
const { extractYamlFromAgent } = require('../../lib/yaml-utils');
|
||||
@@ -44,6 +45,9 @@ class IdeSetup extends BaseIdeSetup {
|
||||
case 'cursor': {
|
||||
return this.setupCursor(installDir, selectedAgent);
|
||||
}
|
||||
case 'opencode': {
|
||||
return this.setupOpenCode(installDir, selectedAgent, spinner, preConfiguredSettings);
|
||||
}
|
||||
case 'claude-code': {
|
||||
return this.setupClaudeCode(installDir, selectedAgent);
|
||||
}
|
||||
@@ -93,6 +97,643 @@ class IdeSetup extends BaseIdeSetup {
|
||||
}
|
||||
}
|
||||
|
||||
async setupOpenCode(installDir, selectedAgent, spinner = null, preConfiguredSettings = null) {
|
||||
// Minimal JSON-only integration per plan:
|
||||
// - If opencode.json or opencode.jsonc exists: only ensure instructions include .bmad-core/core-config.yaml
|
||||
// - If none exists: create minimal opencode.jsonc with $schema and instructions array including that file
|
||||
|
||||
const jsonPath = path.join(installDir, 'opencode.json');
|
||||
const jsoncPath = path.join(installDir, 'opencode.jsonc');
|
||||
const hasJson = await fileManager.pathExists(jsonPath);
|
||||
const hasJsonc = await fileManager.pathExists(jsoncPath);
|
||||
|
||||
// Determine key prefix preferences (with sensible defaults)
|
||||
// Defaults: non-prefixed (agents = "dev", commands = "create-doc")
|
||||
let useAgentPrefix = false;
|
||||
let useCommandPrefix = false;
|
||||
|
||||
// Allow pre-configuration (if passed) to skip prompts
|
||||
const pre = preConfiguredSettings && preConfiguredSettings.opencode;
|
||||
if (pre && typeof pre.useAgentPrefix === 'boolean') useAgentPrefix = pre.useAgentPrefix;
|
||||
if (pre && typeof pre.useCommandPrefix === 'boolean') useCommandPrefix = pre.useCommandPrefix;
|
||||
|
||||
// If no pre-config and in interactive mode, prompt the user
|
||||
if (!pre) {
|
||||
// Pause spinner during prompts if active
|
||||
let spinnerWasActive = false;
|
||||
if (spinner && spinner.isSpinning) {
|
||||
spinner.stop();
|
||||
spinnerWasActive = true;
|
||||
}
|
||||
|
||||
try {
|
||||
const resp = await inquirer.prompt([
|
||||
{
|
||||
type: 'confirm',
|
||||
name: 'useAgentPrefix',
|
||||
message:
|
||||
"Prefix agent keys with 'bmad-'? (Recommended to avoid collisions, e.g., 'bmad-dev')",
|
||||
default: true,
|
||||
},
|
||||
{
|
||||
type: 'confirm',
|
||||
name: 'useCommandPrefix',
|
||||
message:
|
||||
"Prefix command keys with 'bmad:tasks:'? (Recommended, e.g., 'bmad:tasks:create-doc')",
|
||||
default: true,
|
||||
},
|
||||
]);
|
||||
useAgentPrefix = resp.useAgentPrefix;
|
||||
useCommandPrefix = resp.useCommandPrefix;
|
||||
} catch {
|
||||
// Keep defaults if prompt fails or is not interactive
|
||||
} finally {
|
||||
if (spinner && spinnerWasActive) spinner.start();
|
||||
}
|
||||
}
|
||||
|
||||
const ensureInstructionRef = (obj) => {
|
||||
const preferred = '.bmad-core/core-config.yaml';
|
||||
const alt = './.bmad-core/core-config.yaml';
|
||||
if (!obj.instructions) obj.instructions = [];
|
||||
if (!Array.isArray(obj.instructions)) obj.instructions = [obj.instructions];
|
||||
// Normalize alternative form (with './') to preferred without './'
|
||||
obj.instructions = obj.instructions.map((it) =>
|
||||
typeof it === 'string' && it === alt ? preferred : it,
|
||||
);
|
||||
const hasPreferred = obj.instructions.some(
|
||||
(it) => typeof it === 'string' && it === preferred,
|
||||
);
|
||||
if (!hasPreferred) obj.instructions.push(preferred);
|
||||
return obj;
|
||||
};
|
||||
|
||||
const mergeBmadAgentsAndCommands = async (configObj) => {
|
||||
// Ensure objects exist
|
||||
if (!configObj.agent || typeof configObj.agent !== 'object') configObj.agent = {};
|
||||
if (!configObj.command || typeof configObj.command !== 'object') configObj.command = {};
|
||||
if (!configObj.instructions) configObj.instructions = [];
|
||||
if (!Array.isArray(configObj.instructions)) configObj.instructions = [configObj.instructions];
|
||||
|
||||
// Track a concise summary of changes
|
||||
const summary = {
|
||||
target: null,
|
||||
created: false,
|
||||
agentsAdded: 0,
|
||||
agentsUpdated: 0,
|
||||
agentsSkipped: 0,
|
||||
commandsAdded: 0,
|
||||
commandsUpdated: 0,
|
||||
commandsSkipped: 0,
|
||||
};
|
||||
|
||||
// Determine package scope: previously SELECTED packages in installer UI
|
||||
const selectedPackages = preConfiguredSettings?.selectedPackages || {
|
||||
includeCore: true,
|
||||
packs: [],
|
||||
};
|
||||
|
||||
// Helper: ensure an instruction path is present without './' prefix, de-duplicating './' variants
|
||||
const ensureInstructionPath = (pathNoDot) => {
|
||||
const withDot = `./${pathNoDot}`;
|
||||
// Normalize any existing './' variant to non './'
|
||||
configObj.instructions = configObj.instructions.map((it) =>
|
||||
typeof it === 'string' && it === withDot ? pathNoDot : it,
|
||||
);
|
||||
const has = configObj.instructions.some((it) => typeof it === 'string' && it === pathNoDot);
|
||||
if (!has) configObj.instructions.push(pathNoDot);
|
||||
};
|
||||
|
||||
// Helper: detect orchestrator agents to set as primary mode
|
||||
const isOrchestratorAgent = (agentId) => /(^|-)orchestrator$/i.test(agentId);
|
||||
|
||||
// Helper: extract whenToUse string from an agent markdown file
|
||||
const extractWhenToUseFromFile = async (absPath) => {
|
||||
try {
|
||||
const raw = await fileManager.readFile(absPath);
|
||||
const yamlMatch = raw.match(/```ya?ml\r?\n([\s\S]*?)```/);
|
||||
const yamlBlock = yamlMatch ? yamlMatch[1].trim() : null;
|
||||
if (!yamlBlock) return null;
|
||||
// Try quoted first, then unquoted
|
||||
const quoted = yamlBlock.match(/whenToUse:\s*"([^"]+)"/i);
|
||||
if (quoted && quoted[1]) return quoted[1].trim();
|
||||
const unquoted = yamlBlock.match(/whenToUse:\s*([^\n\r]+)/i);
|
||||
if (unquoted && unquoted[1]) return unquoted[1].trim();
|
||||
} catch {
|
||||
// ignore
|
||||
}
|
||||
return null;
|
||||
};
|
||||
|
||||
// Helper: extract Purpose string from a task file (YAML fenced block, Markdown heading, or inline 'Purpose:')
|
||||
const extractTaskPurposeFromFile = async (absPath) => {
|
||||
const cleanupAndSummarize = (text) => {
|
||||
if (!text) return null;
|
||||
let t = String(text);
|
||||
// Drop code fences and HTML comments
|
||||
t = t.replaceAll(/```[\s\S]*?```/g, '');
|
||||
t = t.replaceAll(/<!--([\s\S]*?)-->/g, '');
|
||||
// Normalize line endings
|
||||
t = t.replaceAll(/\r\n?/g, '\n');
|
||||
// Take the first non-empty paragraph
|
||||
const paragraphs = t.split(/\n\s*\n/g).map((p) => p.trim());
|
||||
let first = paragraphs.find((p) => p.length > 0) || '';
|
||||
// Remove leading list markers, quotes, and headings remnants
|
||||
first = first.replaceAll(/^\s*[>*-]\s+/gm, '');
|
||||
first = first.replaceAll(/^#{1,6}\s+/gm, '');
|
||||
// Strip simple Markdown formatting
|
||||
first = first.replaceAll(/\*\*([^*]+)\*\*/g, '$1').replaceAll(/\*([^*]+)\*/g, '$1');
|
||||
first = first.replaceAll(/`([^`]+)`/g, '$1');
|
||||
// Collapse whitespace
|
||||
first = first.replaceAll(/\s+/g, ' ').trim();
|
||||
if (!first) return null;
|
||||
// Prefer ending at a sentence boundary if long
|
||||
const maxLen = 320;
|
||||
if (first.length > maxLen) {
|
||||
const boundary = first.slice(0, maxLen + 40).match(/^[\s\S]*?[.!?](\s|$)/);
|
||||
const cut = boundary ? boundary[0] : first.slice(0, maxLen);
|
||||
return cut.trim();
|
||||
}
|
||||
return first;
|
||||
};
|
||||
|
||||
try {
|
||||
const raw = await fileManager.readFile(absPath);
|
||||
// 1) YAML fenced block: look for Purpose fields
|
||||
const yamlMatch = raw.match(/```ya?ml\r?\n([\s\S]*?)```/);
|
||||
const yamlBlock = yamlMatch ? yamlMatch[1].trim() : null;
|
||||
if (yamlBlock) {
|
||||
try {
|
||||
const data = yaml.load(yamlBlock);
|
||||
if (data) {
|
||||
let val = data.Purpose ?? data.purpose;
|
||||
if (!val && data.task && (data.task.Purpose || data.task.purpose)) {
|
||||
val = data.task.Purpose ?? data.task.purpose;
|
||||
}
|
||||
if (typeof val === 'string') {
|
||||
const cleaned = cleanupAndSummarize(val);
|
||||
if (cleaned) return cleaned;
|
||||
}
|
||||
}
|
||||
} catch {
|
||||
// ignore YAML parse errors
|
||||
}
|
||||
// Fallback regex inside YAML block
|
||||
const quoted = yamlBlock.match(/(?:^|\n)\s*(?:Purpose|purpose):\s*"([^"]+)"/);
|
||||
if (quoted && quoted[1]) {
|
||||
const cleaned = cleanupAndSummarize(quoted[1]);
|
||||
if (cleaned) return cleaned;
|
||||
}
|
||||
const unquoted = yamlBlock.match(/(?:^|\n)\s*(?:Purpose|purpose):\s*([^\n\r]+)/);
|
||||
if (unquoted && unquoted[1]) {
|
||||
const cleaned = cleanupAndSummarize(unquoted[1]);
|
||||
if (cleaned) return cleaned;
|
||||
}
|
||||
}
|
||||
|
||||
// 2) Markdown heading section: ## Purpose (any level >= 2)
|
||||
const headingRe = /^(#{2,6})\s*Purpose\s*$/im;
|
||||
const headingMatch = headingRe.exec(raw);
|
||||
if (headingMatch) {
|
||||
const headingLevel = headingMatch[1].length;
|
||||
const sectionStart = headingMatch.index + headingMatch[0].length;
|
||||
const rest = raw.slice(sectionStart);
|
||||
// Next heading of same or higher level ends the section
|
||||
const nextHeadingRe = new RegExp(`^#{1,${headingLevel}}\\s+[^\n]+`, 'im');
|
||||
const nextMatch = nextHeadingRe.exec(rest);
|
||||
const section = nextMatch ? rest.slice(0, nextMatch.index) : rest;
|
||||
const cleaned = cleanupAndSummarize(section);
|
||||
if (cleaned) return cleaned;
|
||||
}
|
||||
|
||||
// 3) Inline single-line fallback: Purpose: ...
|
||||
const inline = raw.match(/(?:^|\n)\s*Purpose\s*:\s*([^\n\r]+)/i);
|
||||
if (inline && inline[1]) {
|
||||
const cleaned = cleanupAndSummarize(inline[1]);
|
||||
if (cleaned) return cleaned;
|
||||
}
|
||||
} catch {
|
||||
// ignore
|
||||
}
|
||||
return null;
|
||||
};
|
||||
|
||||
// Build core sets
|
||||
const coreAgentIds = new Set();
|
||||
const coreTaskIds = new Set();
|
||||
if (selectedPackages.includeCore) {
|
||||
for (const id of await this.getCoreAgentIds(installDir)) coreAgentIds.add(id);
|
||||
for (const id of await this.getCoreTaskIds(installDir)) coreTaskIds.add(id);
|
||||
}
|
||||
|
||||
// Build packs info: { packId, packPath, packKey, agents:Set, tasks:Set }
|
||||
const packsInfo = [];
|
||||
if (Array.isArray(selectedPackages.packs)) {
|
||||
for (const packId of selectedPackages.packs) {
|
||||
const dotPackPath = path.join(installDir, `.${packId}`);
|
||||
const altPackPath = path.join(installDir, 'expansion-packs', packId);
|
||||
const packPath = (await fileManager.pathExists(dotPackPath))
|
||||
? dotPackPath
|
||||
: (await fileManager.pathExists(altPackPath))
|
||||
? altPackPath
|
||||
: null;
|
||||
if (!packPath) continue;
|
||||
|
||||
// Ensure pack config.yaml is added to instructions (relative path, no './')
|
||||
const packConfigAbs = path.join(packPath, 'config.yaml');
|
||||
if (await fileManager.pathExists(packConfigAbs)) {
|
||||
const relCfg = path.relative(installDir, packConfigAbs).replaceAll('\\', '/');
|
||||
ensureInstructionPath(relCfg);
|
||||
}
|
||||
|
||||
const packKey = packId.replace(/^bmad-/, '').replaceAll('/', '-');
|
||||
const info = { packId, packPath, packKey, agents: new Set(), tasks: new Set() };
|
||||
|
||||
const glob = require('glob');
|
||||
const agentsDir = path.join(packPath, 'agents');
|
||||
if (await fileManager.pathExists(agentsDir)) {
|
||||
const files = glob.sync('*.md', { cwd: agentsDir });
|
||||
for (const f of files) info.agents.add(path.basename(f, '.md'));
|
||||
}
|
||||
const tasksDir = path.join(packPath, 'tasks');
|
||||
if (await fileManager.pathExists(tasksDir)) {
|
||||
const files = glob.sync('*.md', { cwd: tasksDir });
|
||||
for (const f of files) info.tasks.add(path.basename(f, '.md'));
|
||||
}
|
||||
packsInfo.push(info);
|
||||
}
|
||||
}
|
||||
|
||||
// Generate agents - core first (respect optional agent prefix)
|
||||
for (const agentId of coreAgentIds) {
|
||||
const p = await this.findAgentPath(agentId, installDir); // prefers core
|
||||
if (!p) continue;
|
||||
const rel = path.relative(installDir, p).replaceAll('\\', '/');
|
||||
const fileRef = `{file:./${rel}}`;
|
||||
const baseKey = agentId;
|
||||
const key = useAgentPrefix
|
||||
? baseKey.startsWith('bmad-')
|
||||
? baseKey
|
||||
: `bmad-${baseKey}`
|
||||
: baseKey;
|
||||
const existing = configObj.agent[key];
|
||||
const whenToUse = await extractWhenToUseFromFile(p);
|
||||
const agentDef = {
|
||||
prompt: fileRef,
|
||||
mode: isOrchestratorAgent(agentId) ? 'primary' : 'all',
|
||||
tools: { write: true, edit: true, bash: true },
|
||||
...(whenToUse ? { description: whenToUse } : {}),
|
||||
};
|
||||
if (!existing) {
|
||||
configObj.agent[key] = agentDef;
|
||||
summary.agentsAdded++;
|
||||
} else if (
|
||||
existing &&
|
||||
typeof existing === 'object' &&
|
||||
typeof existing.prompt === 'string' &&
|
||||
existing.prompt.includes(rel)
|
||||
) {
|
||||
existing.prompt = agentDef.prompt;
|
||||
existing.mode = agentDef.mode;
|
||||
if (whenToUse) existing.description = whenToUse;
|
||||
existing.tools = { write: true, edit: true, bash: true };
|
||||
configObj.agent[key] = existing;
|
||||
summary.agentsUpdated++;
|
||||
} else {
|
||||
summary.agentsSkipped++;
|
||||
// Collision warning: key exists but does not appear BMAD-managed (different prompt path)
|
||||
console.log(
|
||||
chalk.yellow(
|
||||
`⚠︎ Skipped agent key '${key}' (existing entry not BMAD-managed). Tip: enable agent prefixes to avoid collisions.`,
|
||||
),
|
||||
);
|
||||
}
|
||||
}
|
||||
|
||||
// Generate agents - expansion packs (forced pack-specific prefix)
|
||||
for (const pack of packsInfo) {
|
||||
for (const agentId of pack.agents) {
|
||||
const p = path.join(pack.packPath, 'agents', `${agentId}.md`);
|
||||
if (!(await fileManager.pathExists(p))) continue;
|
||||
const rel = path.relative(installDir, p).replaceAll('\\', '/');
|
||||
const fileRef = `{file:./${rel}}`;
|
||||
const prefixedKey = `bmad-${pack.packKey}-${agentId}`;
|
||||
const existing = configObj.agent[prefixedKey];
|
||||
const whenToUse = await extractWhenToUseFromFile(p);
|
||||
const agentDef = {
|
||||
prompt: fileRef,
|
||||
mode: isOrchestratorAgent(agentId) ? 'primary' : 'all',
|
||||
tools: { write: true, edit: true, bash: true },
|
||||
...(whenToUse ? { description: whenToUse } : {}),
|
||||
};
|
||||
if (!existing) {
|
||||
configObj.agent[prefixedKey] = agentDef;
|
||||
summary.agentsAdded++;
|
||||
} else if (
|
||||
existing &&
|
||||
typeof existing === 'object' &&
|
||||
typeof existing.prompt === 'string' &&
|
||||
existing.prompt.includes(rel)
|
||||
) {
|
||||
existing.prompt = agentDef.prompt;
|
||||
existing.mode = agentDef.mode;
|
||||
if (whenToUse) existing.description = whenToUse;
|
||||
existing.tools = { write: true, edit: true, bash: true };
|
||||
configObj.agent[prefixedKey] = existing;
|
||||
summary.agentsUpdated++;
|
||||
} else {
|
||||
summary.agentsSkipped++;
|
||||
console.log(
|
||||
chalk.yellow(
|
||||
`⚠︎ Skipped agent key '${prefixedKey}' (existing entry not BMAD-managed). Tip: enable agent prefixes to avoid collisions.`,
|
||||
),
|
||||
);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
// Generate commands - core first (respect optional command prefix)
|
||||
for (const taskId of coreTaskIds) {
|
||||
const p = await this.findTaskPath(taskId, installDir); // prefers core/common
|
||||
if (!p) continue;
|
||||
const rel = path.relative(installDir, p).replaceAll('\\', '/');
|
||||
const fileRef = `{file:./${rel}}`;
|
||||
const key = useCommandPrefix ? `bmad:tasks:${taskId}` : `${taskId}`;
|
||||
const existing = configObj.command[key];
|
||||
const purpose = await extractTaskPurposeFromFile(p);
|
||||
const cmdDef = { template: fileRef, ...(purpose ? { description: purpose } : {}) };
|
||||
if (!existing) {
|
||||
configObj.command[key] = cmdDef;
|
||||
summary.commandsAdded++;
|
||||
} else if (
|
||||
existing &&
|
||||
typeof existing === 'object' &&
|
||||
typeof existing.template === 'string' &&
|
||||
existing.template.includes(rel)
|
||||
) {
|
||||
existing.template = cmdDef.template;
|
||||
if (purpose) existing.description = purpose;
|
||||
configObj.command[key] = existing;
|
||||
summary.commandsUpdated++;
|
||||
} else {
|
||||
summary.commandsSkipped++;
|
||||
console.log(
|
||||
chalk.yellow(
|
||||
`⚠︎ Skipped command key '${key}' (existing entry not BMAD-managed). Tip: enable command prefixes to avoid collisions.`,
|
||||
),
|
||||
);
|
||||
}
|
||||
}
|
||||
|
||||
// Generate commands - expansion packs (forced pack-specific prefix)
|
||||
for (const pack of packsInfo) {
|
||||
for (const taskId of pack.tasks) {
|
||||
const p = path.join(pack.packPath, 'tasks', `${taskId}.md`);
|
||||
if (!(await fileManager.pathExists(p))) continue;
|
||||
const rel = path.relative(installDir, p).replaceAll('\\', '/');
|
||||
const fileRef = `{file:./${rel}}`;
|
||||
const prefixedKey = `bmad:${pack.packKey}:${taskId}`;
|
||||
const existing = configObj.command[prefixedKey];
|
||||
const purpose = await extractTaskPurposeFromFile(p);
|
||||
const cmdDef = { template: fileRef, ...(purpose ? { description: purpose } : {}) };
|
||||
if (!existing) {
|
||||
configObj.command[prefixedKey] = cmdDef;
|
||||
summary.commandsAdded++;
|
||||
} else if (
|
||||
existing &&
|
||||
typeof existing === 'object' &&
|
||||
typeof existing.template === 'string' &&
|
||||
existing.template.includes(rel)
|
||||
) {
|
||||
existing.template = cmdDef.template;
|
||||
if (purpose) existing.description = purpose;
|
||||
configObj.command[prefixedKey] = existing;
|
||||
summary.commandsUpdated++;
|
||||
} else {
|
||||
summary.commandsSkipped++;
|
||||
console.log(
|
||||
chalk.yellow(
|
||||
`⚠︎ Skipped command key '${prefixedKey}' (existing entry not BMAD-managed). Tip: enable command prefixes to avoid collisions.`,
|
||||
),
|
||||
);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
return { configObj, summary };
|
||||
};
|
||||
|
||||
// Helper: generate AGENTS.md section for OpenCode (acts as system prompt memory)
|
||||
const generateOpenCodeAgentsMd = async () => {
|
||||
try {
|
||||
const filePath = path.join(installDir, 'AGENTS.md');
|
||||
const startMarker = '<!-- BEGIN: BMAD-AGENTS-OPENCODE -->';
|
||||
const endMarker = '<!-- END: BMAD-AGENTS-OPENCODE -->';
|
||||
|
||||
const agents = selectedAgent ? [selectedAgent] : await this.getAllAgentIds(installDir);
|
||||
const tasks = await this.getAllTaskIds(installDir);
|
||||
|
||||
let section = '';
|
||||
section += `${startMarker}\n`;
|
||||
section += `# BMAD-METHOD Agents and Tasks (OpenCode)\n\n`;
|
||||
section += `OpenCode reads AGENTS.md during initialization and uses it as part of its system prompt for the session. This section is auto-generated by BMAD-METHOD for OpenCode.\n\n`;
|
||||
section += `## How To Use With OpenCode\n\n`;
|
||||
section += `- Run \`opencode\` in this project. OpenCode will read \`AGENTS.md\` and your OpenCode config (opencode.json[c]).\n`;
|
||||
section += `- Reference a role naturally, e.g., "As dev, implement ..." or use commands defined in your BMAD tasks.\n`;
|
||||
section += `- Commit \`.bmad-core\` and \`AGENTS.md\` if you want teammates to share the same configuration.\n`;
|
||||
section += `- Refresh this section after BMAD updates: \`npx bmad-method install -f -i opencode\`.\n\n`;
|
||||
|
||||
section += `### Helpful Commands\n\n`;
|
||||
section += `- List agents: \`npx bmad-method list:agents\`\n`;
|
||||
section += `- Reinstall BMAD core and regenerate this section: \`npx bmad-method install -f -i opencode\`\n`;
|
||||
section += `- Validate configuration: \`npx bmad-method validate\`\n\n`;
|
||||
|
||||
// Brief context note for modes and tools
|
||||
section += `Note\n`;
|
||||
section += `- Orchestrators run as mode: primary; other agents as all.\n`;
|
||||
section += `- All agents have tools enabled: write, edit, bash.\n\n`;
|
||||
|
||||
section += `## Agents\n\n`;
|
||||
section += `### Directory\n\n`;
|
||||
section += `| Title | ID | When To Use |\n|---|---|---|\n`;
|
||||
|
||||
// Fallback descriptions for core agents (used if whenToUse is missing)
|
||||
const fallbackDescriptions = {
|
||||
'ux-expert':
|
||||
'Use for UI/UX design, wireframes, prototypes, front-end specs, and user experience optimization',
|
||||
sm: 'Use for story creation, epic management, retrospectives in party-mode, and agile process guidance',
|
||||
qa: 'Ensure quality strategy, test design, risk profiling, and QA gates across features',
|
||||
po: 'Backlog management, story refinement, acceptance criteria, sprint planning, prioritization decisions',
|
||||
pm: 'PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication',
|
||||
dev: 'Code implementation, debugging, refactoring, and development best practices',
|
||||
'bmad-orchestrator':
|
||||
'Workflow coordination, multi-agent tasks, role switching guidance, and when unsure which specialist to consult',
|
||||
'bmad-master':
|
||||
'Comprehensive cross-domain execution for tasks that do not require a specific persona',
|
||||
architect:
|
||||
'System design, architecture docs, technology selection, API design, and infrastructure planning',
|
||||
analyst:
|
||||
'Discovery/research, competitive analysis, project briefs, initial discovery, and brownfield documentation',
|
||||
};
|
||||
|
||||
const sanitizeDesc = (s) => {
|
||||
if (!s) return '';
|
||||
let t = String(s).trim();
|
||||
// Drop surrounding single/double/backtick quotes
|
||||
t = t.replaceAll(/^['"`]+|['"`]+$/g, '');
|
||||
// Collapse whitespace
|
||||
t = t.replaceAll(/\s+/g, ' ').trim();
|
||||
return t;
|
||||
};
|
||||
const agentSummaries = [];
|
||||
for (const agentId of agents) {
|
||||
const agentPath = await this.findAgentPath(agentId, installDir);
|
||||
if (!agentPath) continue;
|
||||
let whenToUse = '';
|
||||
try {
|
||||
const raw = await fileManager.readFile(agentPath);
|
||||
const yamlMatch = raw.match(/```ya?ml\r?\n([\s\S]*?)```/);
|
||||
const yamlBlock = yamlMatch ? yamlMatch[1].trim() : null;
|
||||
if (yamlBlock) {
|
||||
try {
|
||||
const data = yaml.load(yamlBlock);
|
||||
if (data && typeof data.whenToUse === 'string') {
|
||||
whenToUse = data.whenToUse;
|
||||
}
|
||||
} catch {
|
||||
// ignore YAML parse errors
|
||||
}
|
||||
if (!whenToUse) {
|
||||
// Fallback regex supporting single or double quotes
|
||||
const m1 = yamlBlock.match(/whenToUse:\s*"([^\n"]+)"/i);
|
||||
const m2 = yamlBlock.match(/whenToUse:\s*'([^\n']+)'/i);
|
||||
const m3 = yamlBlock.match(/whenToUse:\s*([^\n\r]+)/i);
|
||||
whenToUse = (m1?.[1] || m2?.[1] || m3?.[1] || '').trim();
|
||||
}
|
||||
}
|
||||
} catch {
|
||||
// ignore read/parse errors for agent metadata extraction
|
||||
}
|
||||
const title = await this.getAgentTitle(agentId, installDir);
|
||||
const finalDesc = sanitizeDesc(whenToUse) || fallbackDescriptions[agentId] || '—';
|
||||
agentSummaries.push({ agentId, title, whenToUse: finalDesc, path: agentPath });
|
||||
// Strict 3-column row
|
||||
section += `| ${title} | ${agentId} | ${finalDesc} |\n`;
|
||||
}
|
||||
section += `\n`;
|
||||
|
||||
for (const { agentId, title, whenToUse, path: agentPath } of agentSummaries) {
|
||||
const relativePath = path.relative(installDir, agentPath).replaceAll('\\', '/');
|
||||
section += `### ${title} (id: ${agentId})\n`;
|
||||
section += `Source: [${relativePath}](${relativePath})\n\n`;
|
||||
if (whenToUse) section += `- When to use: ${whenToUse}\n`;
|
||||
section += `- How to activate: Mention "As ${agentId}, ..." to get role-aligned behavior\n`;
|
||||
section += `- Full definition: open the source file above (content not embedded)\n\n`;
|
||||
}
|
||||
|
||||
if (tasks && tasks.length > 0) {
|
||||
section += `## Tasks\n\n`;
|
||||
section += `These are reusable task briefs; use the paths to open them as needed.\n\n`;
|
||||
for (const taskId of tasks) {
|
||||
const taskPath = await this.findTaskPath(taskId, installDir);
|
||||
if (!taskPath) continue;
|
||||
const relativePath = path.relative(installDir, taskPath).replaceAll('\\', '/');
|
||||
section += `### Task: ${taskId}\n`;
|
||||
section += `Source: [${relativePath}](${relativePath})\n`;
|
||||
section += `- How to use: Reference the task in your prompt or execute via your configured commands.\n`;
|
||||
section += `- Full brief: open the source file above (content not embedded)\n\n`;
|
||||
}
|
||||
}
|
||||
|
||||
section += `${endMarker}\n`;
|
||||
|
||||
let finalContent = '';
|
||||
if (await fileManager.pathExists(filePath)) {
|
||||
const existing = await fileManager.readFile(filePath);
|
||||
if (existing.includes(startMarker) && existing.includes(endMarker)) {
|
||||
const pattern = String.raw`${startMarker}[\s\S]*?${endMarker}`;
|
||||
const replaced = existing.replace(new RegExp(pattern, 'm'), section);
|
||||
finalContent = replaced;
|
||||
} else {
|
||||
finalContent = existing.trimEnd() + `\n\n` + section;
|
||||
}
|
||||
} else {
|
||||
finalContent += '# Project Agents\n\n';
|
||||
finalContent += 'This file provides guidance and memory for your coding CLI.\n\n';
|
||||
finalContent += section;
|
||||
}
|
||||
|
||||
await fileManager.writeFile(filePath, finalContent);
|
||||
console.log(chalk.green('✓ Created/updated AGENTS.md for OpenCode CLI integration'));
|
||||
console.log(
|
||||
chalk.dim(
|
||||
'OpenCode reads AGENTS.md automatically on init. Run `opencode` in this project to use BMAD agents.',
|
||||
),
|
||||
);
|
||||
} catch {
|
||||
console.log(chalk.yellow('⚠︎ Skipped creating AGENTS.md for OpenCode (write failed)'));
|
||||
}
|
||||
};
|
||||
|
||||
if (hasJson || hasJsonc) {
|
||||
// Preserve existing top-level fields; only touch instructions
|
||||
const targetPath = hasJsonc ? jsoncPath : jsonPath;
|
||||
try {
|
||||
const raw = await fs.readFile(targetPath, 'utf8');
|
||||
// Use comment-json for both .json and .jsonc for resilience
|
||||
const parsed = cjson.parse(raw, undefined, true);
|
||||
ensureInstructionRef(parsed);
|
||||
const { configObj, summary } = await mergeBmadAgentsAndCommands(parsed);
|
||||
const output = cjson.stringify(parsed, null, 2);
|
||||
await fs.writeFile(targetPath, output + (output.endsWith('\n') ? '' : '\n'));
|
||||
console.log(
|
||||
chalk.green(
|
||||
'✓ Updated OpenCode config: ensured BMAD instructions and merged agents/commands',
|
||||
),
|
||||
);
|
||||
// Summary output
|
||||
console.log(
|
||||
chalk.dim(
|
||||
` File: ${path.basename(targetPath)} | Agents +${summary.agentsAdded} ~${summary.agentsUpdated} ⨯${summary.agentsSkipped} | Commands +${summary.commandsAdded} ~${summary.commandsUpdated} ⨯${summary.commandsSkipped}`,
|
||||
),
|
||||
);
|
||||
// Ensure AGENTS.md is created/updated for OpenCode as well
|
||||
await generateOpenCodeAgentsMd();
|
||||
} catch (error) {
|
||||
console.log(chalk.red('✗ Failed to update existing OpenCode config'), error.message);
|
||||
return false;
|
||||
}
|
||||
return true;
|
||||
}
|
||||
|
||||
// Create minimal opencode.jsonc
|
||||
const minimal = {
|
||||
$schema: 'https://opencode.ai/config.json',
|
||||
instructions: ['.bmad-core/core-config.yaml'],
|
||||
agent: {},
|
||||
command: {},
|
||||
};
|
||||
try {
|
||||
const { configObj, summary } = await mergeBmadAgentsAndCommands(minimal);
|
||||
const output = cjson.stringify(minimal, null, 2);
|
||||
await fs.writeFile(jsoncPath, output + (output.endsWith('\n') ? '' : '\n'));
|
||||
console.log(
|
||||
chalk.green('✓ Created opencode.jsonc with BMAD instructions, agents, and commands'),
|
||||
);
|
||||
console.log(
|
||||
chalk.dim(
|
||||
` File: opencode.jsonc | Agents +${summary.agentsAdded} | Commands +${summary.commandsAdded}`,
|
||||
),
|
||||
);
|
||||
// Also create/update AGENTS.md for OpenCode on new-config path
|
||||
await generateOpenCodeAgentsMd();
|
||||
return true;
|
||||
} catch (error) {
|
||||
console.log(chalk.red('✗ Failed to create opencode.jsonc'), error.message);
|
||||
return false;
|
||||
}
|
||||
}
|
||||
|
||||
async setupCodex(installDir, selectedAgent, options) {
|
||||
options = options ?? { webEnabled: false };
|
||||
// Codex reads AGENTS.md at the project root as project memory (CLI & Web).
|
||||
@@ -230,7 +871,6 @@ class IdeSetup extends BaseIdeSetup {
|
||||
if (options.webEnabled) {
|
||||
if (exists) {
|
||||
let gi = await fileManager.readFile(gitignorePath);
|
||||
// Remove lines that ignore BMAD dot-folders
|
||||
const updated = gi
|
||||
.split(/\r?\n/)
|
||||
.filter((l) => !/^\s*\.bmad-core\/?\s*$/.test(l) && !/^\s*\.bmad-\*\/?\s*$/.test(l))
|
||||
|
||||
@@ -409,10 +409,23 @@ class Installer {
|
||||
for (const ide of ides) {
|
||||
spinner.text = `Setting up ${ide} integration...`;
|
||||
let preConfiguredSettings = null;
|
||||
if (ide === 'github-copilot') {
|
||||
preConfiguredSettings = config.githubCopilotConfig;
|
||||
} else if (ide === 'auggie-cli') {
|
||||
preConfiguredSettings = config.augmentCodeConfig;
|
||||
switch (ide) {
|
||||
case 'github-copilot': {
|
||||
preConfiguredSettings = config.githubCopilotConfig;
|
||||
break;
|
||||
}
|
||||
case 'auggie-cli': {
|
||||
preConfiguredSettings = config.augmentCodeConfig;
|
||||
break;
|
||||
}
|
||||
case 'opencode': {
|
||||
preConfiguredSettings = config.openCodeConfig;
|
||||
break;
|
||||
}
|
||||
default: {
|
||||
// no pre-configured settings
|
||||
break;
|
||||
}
|
||||
}
|
||||
await ideSetup.setup(ide, installDir, config.agent, spinner, preConfiguredSettings);
|
||||
}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "bmad-method",
|
||||
"version": "4.43.0",
|
||||
"version": "4.44.1",
|
||||
"description": "BMad Method installer - AI-powered Agile development framework",
|
||||
"keywords": [
|
||||
"bmad",
|
||||
|
||||
Reference in New Issue
Block a user