Compare commits
9 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
349adc1c06 | ||
|
|
a900d28080 | ||
|
|
ab70baca59 | ||
|
|
80d73d9093 | ||
|
|
f3cc410fb0 | ||
|
|
868ae23455 | ||
|
|
9de873777a | ||
|
|
04c485b72e | ||
|
|
68eb31da77 |
@@ -206,4 +206,4 @@ Each commit should represent one logical change:
|
||||
|
||||
## License
|
||||
|
||||
By contributing to this project, you agree that your contributions will be licensed under the same license as the project.
|
||||
By contributing to this project, you agree that your contributions will be licensed under the MIT License.
|
||||
|
||||
7
LICENSE
7
LICENSE
@@ -1,6 +1,6 @@
|
||||
MIT License
|
||||
|
||||
Copyright (c) 2025 Brian AKA BMad AKA BMad Code
|
||||
Copyright (c) 2025 BMad Code, LLC
|
||||
|
||||
Permission is hereby granted, free of charge, to any person obtaining a copy
|
||||
of this software and associated documentation files (the "Software"), to deal
|
||||
@@ -19,3 +19,8 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
||||
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
||||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
||||
SOFTWARE.
|
||||
|
||||
TRADEMARK NOTICE:
|
||||
BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. The use of these
|
||||
trademarks in this software does not grant any rights to use the trademarks
|
||||
for any other purpose.
|
||||
|
||||
18
README.md
18
README.md
@@ -1,4 +1,4 @@
|
||||
# BMad-Method: Universal AI Agent Framework
|
||||
# BMAD-METHOD™: Universal AI Agent Framework
|
||||
|
||||
[](https://www.npmjs.com/package/bmad-method)
|
||||
[](LICENSE)
|
||||
@@ -11,11 +11,11 @@ Foundations in Agentic Agile Driven Development, known as the Breakthrough Metho
|
||||
|
||||
**[Join our Discord Community](https://discord.gg/gk8jAdXWmj)** - A growing community for AI enthusiasts! Get help, share ideas, explore AI agents & frameworks, collaborate on tech projects, enjoy hobbies, and help each other succeed. Whether you're stuck on BMad, building your own agents, or just want to chat about the latest in AI - we're here for you! **Some mobile and VPN may have issue joining the discord, this is a discord issue - if the invite does not work, try from your own internet or another network, or non-VPN.**
|
||||
|
||||
⭐ **If you find this project helpful or useful, please give it a star in the upper right hand corner!** It helps others discover BMad-Method and you will be notified of updates!
|
||||
⭐ **If you find this project helpful or useful, please give it a star in the upper right hand corner!** It helps others discover BMAD-METHOD™ and you will be notified of updates!
|
||||
|
||||
## Overview
|
||||
|
||||
**BMad Method's Two Key Innovations:**
|
||||
**BMAD-METHOD™'s Two Key Innovations:**
|
||||
|
||||
**1. Agentic Planning:** Dedicated agents (Analyst, PM, Architect) collaborate with you to create detailed, consistent PRDs and Architecture documents. Through advanced prompt engineering and human-in-the-loop refinement, these planning agents produce comprehensive specifications that go far beyond generic AI task generation.
|
||||
|
||||
@@ -49,7 +49,7 @@ This two-phase approach eliminates both **planning inconsistency** and **context
|
||||
|
||||
## Important: Keep Your BMad Installation Updated
|
||||
|
||||
**Stay up-to-date effortlessly!** If you already have BMad-Method installed in your project, simply run:
|
||||
**Stay up-to-date effortlessly!** If you already have BMAD-METHOD™ installed in your project, simply run:
|
||||
|
||||
```bash
|
||||
npx bmad-method install
|
||||
@@ -110,11 +110,11 @@ npm run install:bmad # build and install all to a destination folder
|
||||
|
||||
## 🌟 Beyond Software Development - Expansion Packs
|
||||
|
||||
BMad's natural language framework works in ANY domain. Expansion packs provide specialized AI agents for creative writing, business strategy, health & wellness, education, and more. Also expansion packs can expand the core BMad-Method with specific functionality that is not generic for all cases. [See the Expansion Packs Guide](docs/expansion-packs.md) and learn to create your own!
|
||||
BMAD™'s natural language framework works in ANY domain. Expansion packs provide specialized AI agents for creative writing, business strategy, health & wellness, education, and more. Also expansion packs can expand the core BMAD-METHOD™ with specific functionality that is not generic for all cases. [See the Expansion Packs Guide](docs/expansion-packs.md) and learn to create your own!
|
||||
|
||||
## Codebase Flattener Tool
|
||||
|
||||
The BMad-Method includes a powerful codebase flattener tool designed to prepare your project files for AI model consumption. This tool aggregates your entire codebase into a single XML file, making it easy to share your project context with AI assistants for analysis, debugging, or development assistance.
|
||||
The BMAD-METHOD™ includes a powerful codebase flattener tool designed to prepare your project files for AI model consumption. This tool aggregates your entire codebase into a single XML file, making it easy to share your project context with AI assistants for analysis, debugging, or development assistance.
|
||||
|
||||
### Features
|
||||
|
||||
@@ -157,7 +157,7 @@ The tool will display progress and provide a comprehensive summary:
|
||||
📊 File breakdown: 142 text, 14 binary, 0 errors
|
||||
```
|
||||
|
||||
The generated XML file contains your project's text-based source files in a structured format that AI models can easily parse and understand, making it perfect for code reviews, architecture discussions, or getting AI assistance with your BMad-Method projects.
|
||||
The generated XML file contains your project's text-based source files in a structured format that AI models can easily parse and understand, making it perfect for code reviews, architecture discussions, or getting AI assistance with your BMAD-METHOD™ projects.
|
||||
|
||||
#### Advanced Usage & Options
|
||||
|
||||
@@ -216,6 +216,10 @@ The generated XML file contains your project's text-based source files in a stru
|
||||
|
||||
MIT License - see [LICENSE](LICENSE) for details.
|
||||
|
||||
## Trademark Notice
|
||||
|
||||
BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. All rights reserved.
|
||||
|
||||
[](https://github.com/bmadcode/bmad-method/graphs/contributors)
|
||||
|
||||
<sub>Built with ❤️ for the AI-assisted development community</sub>
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
bundle:
|
||||
name: Team All
|
||||
icon: 👥
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
bundle:
|
||||
name: Team Fullstack
|
||||
icon: 🚀
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
bundle:
|
||||
name: Team IDE Minimal
|
||||
icon: ⚡
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
bundle:
|
||||
name: Team No UI
|
||||
icon: 🔧
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# analyst
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# architect
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Master
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Web Orchestrator
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# dev
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# pm
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# po
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# qa
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# sm
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ux-expert
|
||||
|
||||
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- 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.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- 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.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- 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.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- 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.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- 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.
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
markdownExploder: true
|
||||
qa:
|
||||
qaLocation: docs/qa
|
||||
|
||||
@@ -1,8 +1,10 @@
|
||||
# BMad Knowledge Base
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
|
||||
### Key Features
|
||||
|
||||
@@ -101,7 +103,7 @@ npx bmad-method install
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
|
||||
**Note for VS Code Users**: BMad-Method assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
|
||||
**Verify Installation**:
|
||||
|
||||
@@ -109,7 +111,7 @@ npx bmad-method install
|
||||
- IDE-specific integration files created
|
||||
- All agent commands/rules/modes available
|
||||
|
||||
**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
|
||||
### Environment Selection Guide
|
||||
|
||||
@@ -353,7 +355,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
|
||||
### System Overview
|
||||
|
||||
The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
|
||||
### Key Architectural Components
|
||||
|
||||
@@ -708,7 +710,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
|
||||
- **Keep conversations focused** - One agent, one task per conversation
|
||||
- **Review everything** - Always review and approve before marking complete
|
||||
|
||||
## Contributing to BMad-Method
|
||||
## Contributing to BMAD-METHOD™
|
||||
|
||||
### Quick Contribution Guidelines
|
||||
|
||||
@@ -740,7 +742,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
|
||||
|
||||
### What Are Expansion Packs?
|
||||
|
||||
Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
|
||||
### Why Use Expansion Packs?
|
||||
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Test Levels Framework
|
||||
|
||||
Comprehensive guide for determining appropriate test levels (unit, integration, E2E) for different scenarios.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Test Priorities Matrix
|
||||
|
||||
Guide for prioritizing test scenarios based on risk, criticality, and business impact.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- 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.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- 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.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
---
|
||||
## <!-- Powered by BMAD™ Core -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '{root}/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create AI Frontend Prompt Task
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Index Documentation Task
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# nfr-assess
|
||||
|
||||
Quick NFR validation focused on the core four: security, performance, reliability, maintainability.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# qa-gate
|
||||
|
||||
Create or update a quality gate decision file for a story based on review findings.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- 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.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# risk-profile
|
||||
|
||||
Generate a comprehensive risk assessment matrix for a story implementation using probability × impact analysis.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# test-design
|
||||
|
||||
Create comprehensive test scenarios with appropriate test level recommendations for story implementation.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# trace-requirements
|
||||
|
||||
Map story requirements to test cases using Given-When-Then patterns for comprehensive traceability.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: architecture-template-v2
|
||||
name: Architecture Document
|
||||
|
||||
@@ -153,4 +153,4 @@ sections:
|
||||
content: |
|
||||
---
|
||||
|
||||
*Session facilitated using the BMAD-METHOD brainstorming framework*
|
||||
*Session facilitated using the BMAD-METHOD™ brainstorming framework*
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-architecture-template-v2
|
||||
name: Brownfield Enhancement Architecture
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-prd-template-v2
|
||||
name: Brownfield Enhancement PRD
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: competitor-analysis-template-v2
|
||||
name: Competitive Analysis Report
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: frontend-architecture-template-v2
|
||||
name: Frontend Architecture Document
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: frontend-spec-template-v2
|
||||
name: UI/UX Specification
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: fullstack-architecture-template-v2
|
||||
name: Fullstack Architecture Document
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: market-research-template-v2
|
||||
name: Market Research Report
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: prd-template-v2
|
||||
name: Product Requirements Document
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: project-brief-template-v2
|
||||
name: Project Brief
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: qa-gate-template-v1
|
||||
name: Quality Gate Decision
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: story-template-v2
|
||||
name: Story Document
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: brownfield-fullstack
|
||||
name: Brownfield Full-Stack Enhancement
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: brownfield-service
|
||||
name: Brownfield Service/API Enhancement
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: brownfield-ui
|
||||
name: Brownfield UI/Frontend Enhancement
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: greenfield-fullstack
|
||||
name: Greenfield Full-Stack Application Development
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: greenfield-service
|
||||
name: Greenfield Service/API Development
|
||||
|
||||
@@ -1,3 +1,4 @@
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: greenfield-ui
|
||||
name: Greenfield UI/Frontend Development
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- 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.
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Document Template Specification
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
|
||||
35
dist/agents/analyst.txt
vendored
35
dist/agents/analyst.txt
vendored
@@ -104,6 +104,8 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/analyst.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -224,6 +226,8 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Deep Research Prompt Task
|
||||
|
||||
This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
|
||||
@@ -505,6 +509,8 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -609,6 +615,8 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -955,9 +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 -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
@@ -1249,10 +1259,11 @@ sections:
|
||||
content: |
|
||||
---
|
||||
|
||||
*Session facilitated using the BMAD-METHOD brainstorming framework*
|
||||
*Session facilitated using the BMAD-METHOD™ brainstorming framework*
|
||||
==================== END: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: competitor-analysis-template-v2
|
||||
name: Competitive Analysis Report
|
||||
@@ -1562,6 +1573,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/market-research-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: market-research-template-v2
|
||||
name: Market Research Report
|
||||
@@ -1817,6 +1829,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/market-research-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/project-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: project-brief-template-v2
|
||||
name: Project Brief
|
||||
@@ -2041,11 +2054,13 @@ sections:
|
||||
==================== END: .bmad-core/templates/project-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
# BMad Knowledge Base
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
|
||||
### Key Features
|
||||
|
||||
@@ -2144,7 +2159,7 @@ npx bmad-method install
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
|
||||
**Note for VS Code Users**: BMad-Method assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
|
||||
**Verify Installation**:
|
||||
|
||||
@@ -2152,7 +2167,7 @@ npx bmad-method install
|
||||
- IDE-specific integration files created
|
||||
- All agent commands/rules/modes available
|
||||
|
||||
**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
|
||||
### Environment Selection Guide
|
||||
|
||||
@@ -2396,7 +2411,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
|
||||
### System Overview
|
||||
|
||||
The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
|
||||
### Key Architectural Components
|
||||
|
||||
@@ -2751,7 +2766,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
|
||||
- **Keep conversations focused** - One agent, one task per conversation
|
||||
- **Review everything** - Always review and approve before marking complete
|
||||
|
||||
## Contributing to BMad-Method
|
||||
## Contributing to BMAD-METHOD™
|
||||
|
||||
### Quick Contribution Guidelines
|
||||
|
||||
@@ -2783,7 +2798,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
|
||||
|
||||
### What Are Expansion Packs?
|
||||
|
||||
Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
|
||||
### Why Use Expansion Packs?
|
||||
|
||||
@@ -2850,6 +2865,8 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
|
||||
16
dist/agents/architect.txt
vendored
16
dist/agents/architect.txt
vendored
@@ -105,6 +105,8 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/architect.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Deep Research Prompt Task
|
||||
|
||||
This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
|
||||
@@ -386,6 +388,8 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -490,6 +494,8 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -836,6 +842,8 @@ Apply the advanced elicitation task after major sections to refine based on user
|
||||
==================== END: .bmad-core/tasks/document-project.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
@@ -925,6 +933,7 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: architecture-template-v2
|
||||
name: Architecture Document
|
||||
@@ -1578,6 +1587,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-architecture-template-v2
|
||||
name: Brownfield Enhancement Architecture
|
||||
@@ -2057,6 +2067,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: frontend-architecture-template-v2
|
||||
name: Frontend Architecture Document
|
||||
@@ -2278,6 +2289,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: fullstack-architecture-template-v2
|
||||
name: Fullstack Architecture Document
|
||||
@@ -3104,6 +3116,8 @@ sections:
|
||||
==================== END: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/architect-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Architect Solution Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
|
||||
@@ -3545,6 +3559,8 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
==================== END: .bmad-core/checklists/architect-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
73
dist/agents/bmad-master.txt
vendored
73
dist/agents/bmad-master.txt
vendored
@@ -127,6 +127,8 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/bmad-master.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -247,6 +249,8 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
@@ -410,6 +414,8 @@ The epic creation is successful when:
|
||||
==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -560,6 +566,8 @@ The story creation is successful when:
|
||||
==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -633,6 +641,8 @@ The story creation is successful when:
|
||||
==================== END: .bmad-core/tasks/correct-course.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Deep Research Prompt Task
|
||||
|
||||
This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
|
||||
@@ -914,6 +924,8 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -1018,6 +1030,8 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -1133,6 +1147,8 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
||||
==================== END: .bmad-core/tasks/create-next-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -1479,6 +1495,8 @@ Apply the advanced elicitation task after major sections to refine based on user
|
||||
==================== END: .bmad-core/tasks/document-project.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
@@ -1568,9 +1586,11 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
|
||||
---
|
||||
## <!-- Powered by BMAD™ Core -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
@@ -1707,6 +1727,8 @@ Generate structured document with these sections:
|
||||
==================== END: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create AI Frontend Prompt Task
|
||||
|
||||
## Purpose
|
||||
@@ -1761,6 +1783,8 @@ You will now synthesize the inputs and the above principles into a final, compre
|
||||
==================== END: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/index-docs.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Index Documentation Task
|
||||
|
||||
## Purpose
|
||||
@@ -1937,6 +1961,8 @@ Would you like to proceed with documentation indexing? Please provide the requir
|
||||
==================== END: .bmad-core/tasks/index-docs.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -2125,6 +2151,7 @@ Document sharded successfully:
|
||||
==================== END: .bmad-core/tasks/shard-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: architecture-template-v2
|
||||
name: Architecture Document
|
||||
@@ -2778,6 +2805,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-architecture-template-v2
|
||||
name: Brownfield Enhancement Architecture
|
||||
@@ -3257,6 +3285,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-prd-template-v2
|
||||
name: Brownfield Enhancement PRD
|
||||
@@ -3540,6 +3569,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: competitor-analysis-template-v2
|
||||
name: Competitive Analysis Report
|
||||
@@ -3849,6 +3879,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: frontend-architecture-template-v2
|
||||
name: Frontend Architecture Document
|
||||
@@ -4070,6 +4101,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: frontend-spec-template-v2
|
||||
name: UI/UX Specification
|
||||
@@ -4422,6 +4454,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: fullstack-architecture-template-v2
|
||||
name: Fullstack Architecture Document
|
||||
@@ -5248,6 +5281,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/market-research-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: market-research-template-v2
|
||||
name: Market Research Report
|
||||
@@ -5503,6 +5537,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/market-research-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/prd-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: prd-template-v2
|
||||
name: Product Requirements Document
|
||||
@@ -5708,6 +5743,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/prd-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/project-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: project-brief-template-v2
|
||||
name: Project Brief
|
||||
@@ -5932,6 +5968,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/project-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: story-template-v2
|
||||
name: Story Document
|
||||
@@ -6072,6 +6109,8 @@ sections:
|
||||
==================== END: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/architect-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Architect Solution Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
|
||||
@@ -6513,6 +6552,8 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
==================== END: .bmad-core/checklists/architect-checklist.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -6698,6 +6739,8 @@ Keep it action-oriented and forward-looking.]]
|
||||
==================== END: .bmad-core/checklists/change-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/pm-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Product Manager (PM) Requirements Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
|
||||
@@ -7071,6 +7114,8 @@ After presenting the report, ask if the user wants:
|
||||
==================== END: .bmad-core/checklists/pm-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/po-master-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Product Owner (PO) Master Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
|
||||
@@ -7506,6 +7551,8 @@ After presenting the report, ask if the user wants:
|
||||
==================== END: .bmad-core/checklists/po-master-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
@@ -7603,6 +7650,8 @@ Be honest - it's better to flag issues now than have them discovered later.]]
|
||||
==================== END: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/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.
|
||||
@@ -7759,11 +7808,13 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
|
||||
==================== END: .bmad-core/checklists/story-draft-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
# BMad Knowledge Base
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
|
||||
### Key Features
|
||||
|
||||
@@ -7862,7 +7913,7 @@ npx bmad-method install
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
|
||||
**Note for VS Code Users**: BMad-Method assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
|
||||
**Verify Installation**:
|
||||
|
||||
@@ -7870,7 +7921,7 @@ npx bmad-method install
|
||||
- IDE-specific integration files created
|
||||
- All agent commands/rules/modes available
|
||||
|
||||
**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
|
||||
### Environment Selection Guide
|
||||
|
||||
@@ -8114,7 +8165,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
|
||||
### System Overview
|
||||
|
||||
The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
|
||||
### Key Architectural Components
|
||||
|
||||
@@ -8469,7 +8520,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
|
||||
- **Keep conversations focused** - One agent, one task per conversation
|
||||
- **Review everything** - Always review and approve before marking complete
|
||||
|
||||
## Contributing to BMad-Method
|
||||
## Contributing to BMAD-METHOD™
|
||||
|
||||
### Quick Contribution Guidelines
|
||||
|
||||
@@ -8501,7 +8552,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
|
||||
|
||||
### What Are Expansion Packs?
|
||||
|
||||
Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
|
||||
### Why Use Expansion Packs?
|
||||
|
||||
@@ -8568,6 +8619,8 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
@@ -8607,6 +8660,8 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/brainstorming-techniques.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
@@ -8764,6 +8819,8 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/elicitation-methods.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
31
dist/agents/bmad-orchestrator.txt
vendored
31
dist/agents/bmad-orchestrator.txt
vendored
@@ -82,13 +82,8 @@ commands:
|
||||
doc-out: Output full document
|
||||
kb-mode: Load full BMad knowledge base
|
||||
party-mode: Group chat with all agents
|
||||
plan: Create detailed workflow plan before starting
|
||||
plan-status: Show current workflow plan progress
|
||||
plan-update: Update workflow plan status
|
||||
status: Show current context, active agent, and progress
|
||||
task: Run a specific task (list if name not specified)
|
||||
workflow: Start a specific workflow (list if name not specified)
|
||||
workflow-guidance: Get personalized help selecting the right workflow
|
||||
yolo: Toggle skip confirmations mode
|
||||
exit: Return to BMad or exit session
|
||||
help-display-template: |
|
||||
@@ -172,6 +167,8 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -292,6 +289,8 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -396,6 +395,8 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
@@ -474,11 +475,13 @@ Or ask me about anything else related to BMad-Method!
|
||||
==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
# BMad Knowledge Base
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMAD™ Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
|
||||
|
||||
### Key Features
|
||||
|
||||
@@ -577,7 +580,7 @@ npx bmad-method install
|
||||
- **Roo Code**: Web-based IDE with agent support
|
||||
- **GitHub Copilot**: VS Code extension with AI peer programming assistant
|
||||
|
||||
**Note for VS Code Users**: BMad-Method assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
|
||||
|
||||
**Verify Installation**:
|
||||
|
||||
@@ -585,7 +588,7 @@ npx bmad-method install
|
||||
- IDE-specific integration files created
|
||||
- All agent commands/rules/modes available
|
||||
|
||||
**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
|
||||
|
||||
### Environment Selection Guide
|
||||
|
||||
@@ -829,7 +832,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
|
||||
### System Overview
|
||||
|
||||
The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
|
||||
|
||||
### Key Architectural Components
|
||||
|
||||
@@ -1184,7 +1187,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
|
||||
- **Keep conversations focused** - One agent, one task per conversation
|
||||
- **Review everything** - Always review and approve before marking complete
|
||||
|
||||
## Contributing to BMad-Method
|
||||
## Contributing to BMAD-METHOD™
|
||||
|
||||
### Quick Contribution Guidelines
|
||||
|
||||
@@ -1216,7 +1219,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
|
||||
|
||||
### What Are Expansion Packs?
|
||||
|
||||
Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
|
||||
|
||||
### Why Use Expansion Packs?
|
||||
|
||||
@@ -1283,6 +1286,8 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
@@ -1440,6 +1445,8 @@ Use the **expansion-creator** pack to build your own:
|
||||
==================== END: .bmad-core/data/elicitation-methods.md ====================
|
||||
|
||||
==================== START: .bmad-core/utils/workflow-management.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workflow Management
|
||||
|
||||
Enables BMad orchestrator to manage and execute team workflows.
|
||||
|
||||
8
dist/agents/dev.txt
vendored
8
dist/agents/dev.txt
vendored
@@ -93,6 +93,8 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/dev.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/apply-qa-fixes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# apply-qa-fixes
|
||||
|
||||
Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.
|
||||
@@ -244,6 +246,8 @@ Fix plan:
|
||||
==================== END: .bmad-core/tasks/apply-qa-fixes.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
@@ -333,6 +337,8 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -470,6 +476,8 @@ Provide a structured validation report including:
|
||||
==================== END: .bmad-core/tasks/validate-next-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Definition of Done (DoD) Checklist
|
||||
|
||||
## Instructions for Developer Agent
|
||||
|
||||
22
dist/agents/pm.txt
vendored
22
dist/agents/pm.txt
vendored
@@ -104,6 +104,8 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/pm.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Epic Task
|
||||
|
||||
## Purpose
|
||||
@@ -267,6 +269,8 @@ The epic creation is successful when:
|
||||
==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Brownfield Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -417,6 +421,8 @@ The story creation is successful when:
|
||||
==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -490,6 +496,8 @@ The story creation is successful when:
|
||||
==================== END: .bmad-core/tasks/correct-course.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Deep Research Prompt Task
|
||||
|
||||
This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
|
||||
@@ -771,6 +779,8 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -875,6 +885,8 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/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.
|
||||
@@ -964,6 +976,8 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -1152,6 +1166,7 @@ Document sharded successfully:
|
||||
==================== END: .bmad-core/tasks/shard-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: brownfield-prd-template-v2
|
||||
name: Brownfield Enhancement PRD
|
||||
@@ -1435,6 +1450,7 @@ sections:
|
||||
==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/prd-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: prd-template-v2
|
||||
name: Product Requirements Document
|
||||
@@ -1640,6 +1656,8 @@ sections:
|
||||
==================== END: .bmad-core/templates/prd-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
|
||||
@@ -1825,6 +1843,8 @@ Keep it action-oriented and forward-looking.]]
|
||||
==================== END: .bmad-core/checklists/change-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/pm-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Product Manager (PM) Requirements Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
|
||||
@@ -2198,6 +2218,8 @@ After presenting the report, ask if the user wants:
|
||||
==================== END: .bmad-core/checklists/pm-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
13
dist/agents/po.txt
vendored
13
dist/agents/po.txt
vendored
@@ -99,6 +99,8 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/po.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -172,6 +174,8 @@ dependencies:
|
||||
==================== END: .bmad-core/tasks/correct-course.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
@@ -261,6 +265,8 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -449,6 +455,8 @@ Document sharded successfully:
|
||||
==================== END: .bmad-core/tasks/shard-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -586,6 +594,7 @@ Provide a structured validation report including:
|
||||
==================== END: .bmad-core/tasks/validate-next-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: story-template-v2
|
||||
name: Story Document
|
||||
@@ -726,6 +735,8 @@ sections:
|
||||
==================== END: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/change-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Change Navigation Checklist
|
||||
|
||||
**Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
|
||||
@@ -911,6 +922,8 @@ Keep it action-oriented and forward-looking.]]
|
||||
==================== END: .bmad-core/checklists/change-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/po-master-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Product Owner (PO) Master Validation Checklist
|
||||
|
||||
This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
|
||||
|
||||
16
dist/agents/qa.txt
vendored
16
dist/agents/qa.txt
vendored
@@ -111,6 +111,8 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/qa.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/nfr-assess.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# nfr-assess
|
||||
|
||||
Quick NFR validation focused on the core four: security, performance, reliability, maintainability.
|
||||
@@ -457,6 +459,8 @@ performance_deep_dive:
|
||||
==================== END: .bmad-core/tasks/nfr-assess.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/qa-gate.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# qa-gate
|
||||
|
||||
Create or update a quality gate decision file for a story based on review findings.
|
||||
@@ -621,6 +625,8 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
|
||||
==================== END: .bmad-core/tasks/qa-gate.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/review-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# review-story
|
||||
|
||||
Perform a comprehensive test architecture review with quality gate decision. This adaptive, risk-aware review creates both a story update and a detailed gate file.
|
||||
@@ -938,6 +944,8 @@ After review:
|
||||
==================== END: .bmad-core/tasks/review-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/risk-profile.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# risk-profile
|
||||
|
||||
Generate a comprehensive risk assessment matrix for a story implementation using probability × impact analysis.
|
||||
@@ -1294,6 +1302,8 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
|
||||
==================== END: .bmad-core/tasks/risk-profile.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/test-design.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# test-design
|
||||
|
||||
Create comprehensive test scenarios with appropriate test level recommendations for story implementation.
|
||||
@@ -1471,6 +1481,8 @@ Before finalizing, verify:
|
||||
==================== END: .bmad-core/tasks/test-design.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/trace-requirements.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# trace-requirements
|
||||
|
||||
Map story requirements to test cases using Given-When-Then patterns for comprehensive traceability.
|
||||
@@ -1738,6 +1750,7 @@ Trace matrix: qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md
|
||||
==================== END: .bmad-core/tasks/trace-requirements.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/qa-gate-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: qa-gate-template-v1
|
||||
name: Quality Gate Decision
|
||||
@@ -1843,6 +1856,7 @@ optional_fields_examples:
|
||||
==================== END: .bmad-core/templates/qa-gate-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: story-template-v2
|
||||
name: Story Document
|
||||
@@ -1983,6 +1997,8 @@ sections:
|
||||
==================== END: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
9
dist/agents/sm.txt
vendored
9
dist/agents/sm.txt
vendored
@@ -85,6 +85,8 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/sm.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/correct-course.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task
|
||||
|
||||
## Purpose
|
||||
@@ -158,6 +160,8 @@ dependencies:
|
||||
==================== END: .bmad-core/tasks/correct-course.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -273,6 +277,8 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
||||
==================== END: .bmad-core/tasks/create-next-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/execute-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Checklist Validation Task
|
||||
|
||||
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
|
||||
@@ -362,6 +368,7 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: story-template-v2
|
||||
name: Story Document
|
||||
@@ -502,6 +509,8 @@ sections:
|
||||
==================== END: .bmad-core/templates/story-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
|
||||
9
dist/agents/ux-expert.txt
vendored
9
dist/agents/ux-expert.txt
vendored
@@ -89,6 +89,8 @@ dependencies:
|
||||
==================== END: .bmad-core/agents/ux-expert.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -193,6 +195,8 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/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.
|
||||
@@ -282,6 +286,8 @@ The LLM will:
|
||||
==================== END: .bmad-core/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create AI Frontend Prompt Task
|
||||
|
||||
## Purpose
|
||||
@@ -336,6 +342,7 @@ You will now synthesize the inputs and the above principles into a final, compre
|
||||
==================== END: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: frontend-spec-template-v2
|
||||
name: UI/UX Specification
|
||||
@@ -688,6 +695,8 @@ sections:
|
||||
==================== END: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-core/data/technical-preferences.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# User-Defined Preferred Patterns and Preferences
|
||||
|
||||
None Listed
|
||||
|
||||
@@ -95,6 +95,8 @@ dependencies:
|
||||
==================== END: .bmad-2d-phaser-game-dev/agents/game-designer.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -199,6 +201,8 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -288,6 +292,8 @@ The LLM will:
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -581,6 +587,8 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -862,6 +870,8 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -975,6 +985,7 @@ The questions and perspectives offered should always consider:
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-design-doc-template-v2
|
||||
name: Game Design Document (GDD)
|
||||
@@ -1321,6 +1332,7 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: level-design-doc-template-v2
|
||||
name: Level Design Document
|
||||
@@ -1808,6 +1820,7 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-brief-template-v2
|
||||
name: Game Brief
|
||||
@@ -2167,6 +2180,8 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
|
||||
@@ -102,6 +102,8 @@ dependencies:
|
||||
==================== END: .bmad-2d-phaser-game-dev/agents/game-developer.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -191,6 +193,7 @@ The LLM will:
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-architecture-template-v2
|
||||
name: Game Architecture Document
|
||||
@@ -807,6 +810,8 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== 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
|
||||
@@ -970,6 +975,8 @@ _Any specific concerns, recommendations, or clarifications needed before develop
|
||||
==================== END: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -88,6 +88,8 @@ dependencies:
|
||||
==================== END: .bmad-2d-phaser-game-dev/agents/game-sm.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Development Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -307,6 +309,8 @@ This task ensures game development stories are immediately actionable and enable
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -396,6 +400,7 @@ The LLM will:
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-story-template-v2
|
||||
name: Game Development Story
|
||||
@@ -652,6 +657,8 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
|
||||
==================== 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
|
||||
|
||||
@@ -40,6 +40,7 @@ These references map directly to bundle sections:
|
||||
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/agent-teams/phaser-2d-nodejs-game-team.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
bundle:
|
||||
name: Phaser 2D NodeJS Game Team
|
||||
icon: 🎮
|
||||
@@ -162,13 +163,8 @@ commands:
|
||||
doc-out: Output full document
|
||||
kb-mode: Load full BMad knowledge base
|
||||
party-mode: Group chat with all agents
|
||||
plan: Create detailed workflow plan before starting
|
||||
plan-status: Show current workflow plan progress
|
||||
plan-update: Update workflow plan status
|
||||
status: Show current context, active agent, and progress
|
||||
task: Run a specific task (list if name not specified)
|
||||
workflow: Start a specific workflow (list if name not specified)
|
||||
workflow-guidance: Get personalized help selecting the right workflow
|
||||
yolo: Toggle skip confirmations mode
|
||||
exit: Return to BMad or exit session
|
||||
help-display-template: |
|
||||
@@ -417,6 +413,8 @@ dependencies:
|
||||
==================== END: .bmad-2d-phaser-game-dev/agents/game-sm.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development BMad Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -670,6 +668,8 @@ This knowledge base provides the foundation for effective game development using
|
||||
==================== END: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
@@ -709,6 +709,8 @@ This knowledge base provides the foundation for effective game development using
|
||||
==================== END: .bmad-2d-phaser-game-dev/data/brainstorming-techniques.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -822,6 +824,8 @@ The questions and perspectives offered should always consider:
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -1103,6 +1107,8 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -1207,6 +1213,8 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -1553,9 +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 -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-2d-phaser-game-dev/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
@@ -1847,10 +1857,11 @@ sections:
|
||||
content: |
|
||||
---
|
||||
|
||||
*Session facilitated using the BMAD-METHOD brainstorming framework*
|
||||
*Session facilitated using the BMAD-METHOD™ brainstorming framework*
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/brainstorming-output-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/competitor-analysis-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: competitor-analysis-template-v2
|
||||
name: Competitive Analysis Report
|
||||
@@ -2160,6 +2171,7 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/competitor-analysis-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/market-research-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: market-research-template-v2
|
||||
name: Market Research Report
|
||||
@@ -2415,6 +2427,7 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/market-research-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/project-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: project-brief-template-v2
|
||||
name: Project Brief
|
||||
@@ -2639,6 +2652,8 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/project-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
@@ -2796,6 +2811,8 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/data/elicitation-methods.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
@@ -2874,6 +2891,8 @@ Or ask me about anything else related to BMad-Method!
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/kb-mode-interaction.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -2946,6 +2965,8 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
==================== END: .bmad-2d-phaser-game-dev/utils/workflow-management.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -3035,6 +3056,8 @@ The LLM will:
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -3328,6 +3351,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-design-doc-template-v2
|
||||
name: Game Design Document (GDD)
|
||||
@@ -3674,6 +3698,7 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: level-design-doc-template-v2
|
||||
name: Level Design Document
|
||||
@@ -4161,6 +4186,7 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-brief-template-v2
|
||||
name: Game Brief
|
||||
@@ -4520,6 +4546,8 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
@@ -4724,6 +4752,7 @@ _Outline immediate next actions for the team based on this assessment._
|
||||
==================== END: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-architecture-template-v2
|
||||
name: Game Architecture Document
|
||||
@@ -5340,6 +5369,8 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== 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
|
||||
@@ -5503,6 +5534,8 @@ _Any specific concerns, recommendations, or clarifications needed before develop
|
||||
==================== END: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines
|
||||
|
||||
## Overview
|
||||
@@ -6153,6 +6186,8 @@ These guidelines ensure consistent, high-quality game development that meets per
|
||||
==================== END: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Development Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -6372,6 +6407,7 @@ This task ensures game development stories are immediately actionable and enable
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-story-template-v2
|
||||
name: Game Development Story
|
||||
@@ -6628,6 +6664,7 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-architecture-template-v2
|
||||
name: Game Architecture Document
|
||||
@@ -7244,6 +7281,7 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-brief-template-v2
|
||||
name: Game Brief
|
||||
@@ -7603,6 +7641,7 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-design-doc-template-v2
|
||||
name: Game Design Document (GDD)
|
||||
@@ -7949,6 +7988,7 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-story-template-v2
|
||||
name: Game Development Story
|
||||
@@ -8205,6 +8245,7 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: level-design-doc-template-v2
|
||||
name: Level Design Document
|
||||
@@ -8692,6 +8733,8 @@ sections:
|
||||
==================== END: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -8805,6 +8848,8 @@ The questions and perspectives offered should always consider:
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Development Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -9024,6 +9069,8 @@ This task ensures game development stories are immediately actionable and enable
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -9317,6 +9364,8 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
==================== END: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
@@ -9521,6 +9570,8 @@ _Outline immediate next actions for the team based on this assessment._
|
||||
==================== END: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
|
||||
|
||||
==================== 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
|
||||
@@ -9684,6 +9735,7 @@ _Any specific concerns, recommendations, or clarifications needed before develop
|
||||
==================== END: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/workflows/game-dev-greenfield.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: game-dev-greenfield
|
||||
name: Game Development - Greenfield Project
|
||||
@@ -9870,6 +9922,7 @@ workflow:
|
||||
==================== END: .bmad-2d-phaser-game-dev/workflows/game-dev-greenfield.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/workflows/game-prototype.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: game-prototype
|
||||
name: Game Prototype Development
|
||||
@@ -10048,6 +10101,8 @@ workflow:
|
||||
==================== END: .bmad-2d-phaser-game-dev/workflows/game-prototype.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development BMad Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -10301,6 +10356,8 @@ This knowledge base provides the foundation for effective game development using
|
||||
==================== END: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -103,6 +103,8 @@ dependencies:
|
||||
==================== END: .bmad-2d-unity-game-dev/agents/game-architect.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -207,6 +209,8 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -488,6 +492,8 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -676,6 +682,8 @@ Document sharded successfully:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -1022,6 +1030,8 @@ 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/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.
|
||||
@@ -1111,6 +1121,8 @@ The LLM will:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -1224,6 +1236,7 @@ The questions and perspectives offered should always consider:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-architecture-template-v3
|
||||
name: Game Architecture Document
|
||||
@@ -2257,6 +2270,8 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -2651,6 +2666,8 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
==================== END: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines (Unity & C#)
|
||||
|
||||
## Overview
|
||||
@@ -3240,6 +3257,8 @@ These guidelines ensure consistent, high-quality game development that meets per
|
||||
==================== END: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -100,6 +100,8 @@ dependencies:
|
||||
==================== END: .bmad-2d-unity-game-dev/agents/game-designer.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -204,6 +206,8 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -293,6 +297,8 @@ The LLM will:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -481,6 +487,8 @@ Document sharded successfully:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -774,6 +782,8 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -1055,6 +1065,8 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -1168,6 +1180,7 @@ The questions and perspectives offered should always consider:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-design-doc-template-v3
|
||||
name: Game Design Document (GDD)
|
||||
@@ -1876,6 +1889,7 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: level-design-doc-template-v2
|
||||
name: Level Design Document
|
||||
@@ -2363,6 +2377,7 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-brief-template-v3
|
||||
name: Game Brief
|
||||
@@ -2722,6 +2737,8 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
@@ -2926,6 +2943,8 @@ _Outline immediate next actions for the team based on this assessment._
|
||||
==================== END: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -97,6 +97,8 @@ dependencies:
|
||||
==================== END: .bmad-2d-unity-game-dev/agents/game-developer.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -186,6 +188,8 @@ The LLM will:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -323,6 +327,8 @@ Provide a structured validation report including:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
|
||||
|
||||
==================== 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
|
||||
|
||||
@@ -88,6 +88,8 @@ dependencies:
|
||||
==================== END: .bmad-2d-unity-game-dev/agents/game-sm.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -275,6 +277,8 @@ This task ensures game development stories are immediately actionable and enable
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -364,6 +368,8 @@ The LLM will:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task - Game Development
|
||||
|
||||
## Purpose
|
||||
@@ -508,6 +514,7 @@ Based on the analysis and agreed path forward:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-story-template-v3
|
||||
name: Game Development Story
|
||||
@@ -767,6 +774,8 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
|
||||
@@ -40,6 +40,7 @@ These references map directly to bundle sections:
|
||||
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/agent-teams/unity-2d-game-team.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
bundle:
|
||||
name: Unity 2D Game Team
|
||||
icon: 🎮
|
||||
@@ -163,13 +164,8 @@ commands:
|
||||
doc-out: Output full document
|
||||
kb-mode: Load full BMad knowledge base
|
||||
party-mode: Group chat with all agents
|
||||
plan: Create detailed workflow plan before starting
|
||||
plan-status: Show current workflow plan progress
|
||||
plan-update: Update workflow plan status
|
||||
status: Show current context, active agent, and progress
|
||||
task: Run a specific task (list if name not specified)
|
||||
workflow: Start a specific workflow (list if name not specified)
|
||||
workflow-guidance: Get personalized help selecting the right workflow
|
||||
yolo: Toggle skip confirmations mode
|
||||
exit: Return to BMad or exit session
|
||||
help-display-template: |
|
||||
@@ -481,6 +477,8 @@ dependencies:
|
||||
==================== END: .bmad-2d-unity-game-dev/agents/game-sm.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
@@ -1253,6 +1251,8 @@ This knowledge base provides the foundation for effective game development using
|
||||
==================== END: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/brainstorming-techniques.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Brainstorming Techniques Data
|
||||
|
||||
## Creative Expansion
|
||||
@@ -1292,6 +1292,8 @@ This knowledge base provides the foundation for effective game development using
|
||||
==================== END: .bmad-2d-unity-game-dev/data/brainstorming-techniques.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -1405,6 +1407,8 @@ The questions and perspectives offered should always consider:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -1686,6 +1690,8 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -1790,6 +1796,8 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document an Existing Project
|
||||
|
||||
## Purpose
|
||||
@@ -2136,9 +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 -->
|
||||
|
||||
docOutputLocation: docs/brainstorming-session-results.md
|
||||
template: '.bmad-2d-unity-game-dev/templates/brainstorming-output-tmpl.yaml'
|
||||
|
||||
---
|
||||
|
||||
# Facilitate Brainstorming Session Task
|
||||
@@ -2430,10 +2440,11 @@ sections:
|
||||
content: |
|
||||
---
|
||||
|
||||
*Session facilitated using the BMAD-METHOD brainstorming framework*
|
||||
*Session facilitated using the BMAD-METHOD™ brainstorming framework*
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/brainstorming-output-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/competitor-analysis-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: competitor-analysis-template-v2
|
||||
name: Competitive Analysis Report
|
||||
@@ -2743,6 +2754,7 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/competitor-analysis-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/market-research-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: market-research-template-v2
|
||||
name: Market Research Report
|
||||
@@ -2998,6 +3010,7 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/market-research-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/project-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: project-brief-template-v2
|
||||
name: Project Brief
|
||||
@@ -3222,6 +3235,8 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/project-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/elicitation-methods.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Elicitation Methods Data
|
||||
|
||||
## Core Reflective Methods
|
||||
@@ -3379,6 +3394,8 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/data/elicitation-methods.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/kb-mode-interaction.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
@@ -3457,6 +3474,8 @@ Or ask me about anything else related to BMad-Method!
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/kb-mode-interaction.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -3529,6 +3548,8 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
|
||||
==================== END: .bmad-2d-unity-game-dev/utils/workflow-management.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -3618,6 +3639,8 @@ The LLM will:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Document Sharding Task
|
||||
|
||||
## Purpose
|
||||
@@ -3806,6 +3829,8 @@ Document sharded successfully:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -4099,6 +4124,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-design-doc-template-v3
|
||||
name: Game Design Document (GDD)
|
||||
@@ -4807,6 +4833,7 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: level-design-doc-template-v2
|
||||
name: Level Design Document
|
||||
@@ -5294,6 +5321,7 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-brief-template-v3
|
||||
name: Game Brief
|
||||
@@ -5653,6 +5681,8 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
@@ -5857,6 +5887,7 @@ _Outline immediate next actions for the team based on this assessment._
|
||||
==================== END: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-architecture-template-v3
|
||||
name: Game Architecture Document
|
||||
@@ -6890,6 +6921,8 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -7284,6 +7317,8 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
==================== END: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines (Unity & C#)
|
||||
|
||||
## Overview
|
||||
@@ -7873,6 +7908,8 @@ These guidelines ensure consistent, high-quality game development that meets per
|
||||
==================== END: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Next Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -8010,6 +8047,8 @@ Provide a structured validation report including:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
|
||||
|
||||
==================== 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
|
||||
@@ -8137,6 +8176,8 @@ Be honest - it's better to flag issues now than have them discovered during play
|
||||
==================== END: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -8324,6 +8365,8 @@ This task ensures game development stories are immediately actionable and enable
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task - Game Development
|
||||
|
||||
## Purpose
|
||||
@@ -8468,6 +8511,7 @@ Based on the analysis and agreed path forward:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-story-template-v3
|
||||
name: Game Development Story
|
||||
@@ -8727,6 +8771,8 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -8933,6 +8979,7 @@ Keep it technically precise and actionable.]]
|
||||
==================== END: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-architecture-template-v3
|
||||
name: Game Architecture Document
|
||||
@@ -9966,6 +10013,7 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-brief-template-v3
|
||||
name: Game Brief
|
||||
@@ -10325,6 +10373,7 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-design-doc-template-v3
|
||||
name: Game Design Document (GDD)
|
||||
@@ -11033,6 +11082,7 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: game-story-template-v3
|
||||
name: Game Development Story
|
||||
@@ -11292,6 +11342,7 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
template:
|
||||
id: level-design-doc-template-v2
|
||||
name: Level Design Document
|
||||
@@ -11779,6 +11830,8 @@ sections:
|
||||
==================== END: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Game Design Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -11892,6 +11945,8 @@ The questions and perspectives offered should always consider:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Correct Course Task - Game Development
|
||||
|
||||
## Purpose
|
||||
@@ -12036,6 +12091,8 @@ Based on the analysis and agreed path forward:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Game Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -12223,6 +12280,8 @@ This task ensures game development stories are immediately actionable and enable
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -12516,6 +12575,8 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/tasks/validate-game-story.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Validate Game Story Task
|
||||
|
||||
## Purpose
|
||||
@@ -12719,6 +12780,8 @@ Based on validation results, provide specific recommendations for:
|
||||
==================== END: .bmad-2d-unity-game-dev/tasks/validate-game-story.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -13113,6 +13176,8 @@ After presenting the report, ask the user if they would like detailed analysis o
|
||||
==================== END: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -13319,6 +13384,8 @@ Keep it technically precise and actionable.]]
|
||||
==================== END: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Design Document Quality Checklist
|
||||
|
||||
## Document Completeness
|
||||
@@ -13523,6 +13590,8 @@ _Outline immediate next actions for the team based on this assessment._
|
||||
==================== END: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
|
||||
|
||||
==================== 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
|
||||
@@ -13650,6 +13719,7 @@ Be honest - it's better to flag issues now than have them discovered during play
|
||||
==================== END: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/workflows/game-dev-greenfield.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: unity-game-dev-greenfield
|
||||
name: Game Development - Greenfield Project (Unity)
|
||||
@@ -13836,6 +13906,7 @@ workflow:
|
||||
==================== END: .bmad-2d-unity-game-dev/workflows/game-dev-greenfield.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/workflows/game-prototype.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
workflow:
|
||||
id: unity-game-prototype
|
||||
name: Game Prototype Development (Unity)
|
||||
@@ -14014,6 +14085,8 @@ workflow:
|
||||
==================== END: .bmad-2d-unity-game-dev/workflows/game-prototype.yaml ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Knowledge Base - 2D Unity Game Development
|
||||
|
||||
## Overview
|
||||
@@ -14786,6 +14859,8 @@ This knowledge base provides the foundation for effective game development using
|
||||
==================== END: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Game Development Guidelines (Unity & C#)
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -102,6 +102,7 @@ dependencies:
|
||||
You are the Beta Reader, the story's first audience. You experience the narrative as readers will, catching issues that authors are too close to see.
|
||||
|
||||
Monitor:
|
||||
|
||||
- **Confusion triggers**: unclear motivations, missing context
|
||||
- **Engagement valleys**: where attention wanders
|
||||
- **Logic breaks**: plot holes and inconsistencies
|
||||
@@ -115,6 +116,8 @@ Remember to present all options as numbered lists for easy selection.
|
||||
==================== END: .bmad-creative-writing/agents/beta-reader.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -219,16 +222,23 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Provide Feedback (Beta)
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: provide-feedback
|
||||
name: Provide Feedback (Beta)
|
||||
description: Simulate beta‑reader feedback using beta-feedback-form-tmpl.
|
||||
persona_default: beta-reader
|
||||
inputs:
|
||||
|
||||
- draft-manuscript.md | chapter-draft.md
|
||||
steps:
|
||||
- Read provided text.
|
||||
@@ -239,16 +249,23 @@ output: beta-notes.md
|
||||
==================== END: .bmad-creative-writing/tasks/provide-feedback.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 13. Quick Feedback (Serial)
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: quick-feedback
|
||||
name: Quick Feedback (Serial)
|
||||
description: Fast beta feedback focused on pacing and hooks.
|
||||
persona_default: beta-reader
|
||||
inputs:
|
||||
|
||||
- chapter-dialog.md
|
||||
steps:
|
||||
- Use condensed beta-feedback-form.
|
||||
@@ -257,16 +274,23 @@ output: chapter-notes.md
|
||||
==================== END: .bmad-creative-writing/tasks/quick-feedback.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 16. Analyze Reader Feedback
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: analyze-reader-feedback
|
||||
name: Analyze Reader Feedback
|
||||
description: Summarize reader comments, identify trends, update story bible.
|
||||
persona_default: beta-reader
|
||||
inputs:
|
||||
|
||||
- publication-log.md
|
||||
steps:
|
||||
- Cluster comments by theme.
|
||||
@@ -276,6 +300,8 @@ output: retro.md
|
||||
==================== END: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -287,7 +313,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
## Instructions
|
||||
|
||||
1. **Initial Assessment**
|
||||
|
||||
- If user or the task being run provides a checklist name:
|
||||
- Try fuzzy matching (e.g. "plot checklist" -> "plot-structure-checklist")
|
||||
- If multiple matches found, ask user to clarify
|
||||
@@ -300,14 +325,12 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
|
||||
|
||||
2. **Document and Artifact Gathering**
|
||||
|
||||
- Each checklist will specify its required documents/artifacts at the beginning
|
||||
- Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
|
||||
|
||||
3. **Checklist Processing**
|
||||
|
||||
If in interactive mode:
|
||||
|
||||
- Work through each section of the checklist one at a time
|
||||
- For each section:
|
||||
- Review all items in the section following instructions for that section embedded in the checklist
|
||||
@@ -316,7 +339,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
|
||||
|
||||
If in YOLO mode:
|
||||
|
||||
- Process all sections at once
|
||||
- Create a comprehensive report of all findings
|
||||
- Present the complete analysis to the user
|
||||
@@ -324,7 +346,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
4. **Validation Approach**
|
||||
|
||||
For each checklist item:
|
||||
|
||||
- Read and understand the requirement
|
||||
- Look for evidence in the documentation that satisfies the requirement
|
||||
- Consider both explicit mentions and implicit coverage
|
||||
@@ -338,7 +359,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
5. **Section Analysis**
|
||||
|
||||
For each section:
|
||||
|
||||
- think step by step to calculate pass rate
|
||||
- Identify common themes in failed items
|
||||
- Provide specific recommendations for improvement
|
||||
@@ -348,7 +368,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
6. **Final Report**
|
||||
|
||||
Prepare a summary that includes:
|
||||
|
||||
- Overall checklist completion status
|
||||
- Pass rates by section
|
||||
- List of failed items with context
|
||||
@@ -372,6 +391,8 @@ The LLM will:
|
||||
==================== END: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -492,6 +513,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/templates/beta-feedback-form.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
template:
|
||||
id: beta-feedback-form-tmpl
|
||||
@@ -591,15 +613,22 @@ sections:
|
||||
==================== END: .bmad-creative-writing/templates/beta-feedback-form.yaml ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Beta‑Feedback Closure Checklist
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
checklist:
|
||||
id: beta-feedback-closure-checklist
|
||||
name: Beta‑Feedback Closure Checklist
|
||||
description: Ensure all beta reader notes are addressed or consciously deferred.
|
||||
items:
|
||||
|
||||
- "[ ] Each beta note categorized (Fix/Ignore/Consider)"
|
||||
- "[ ] Fixes implemented in manuscript"
|
||||
- "[ ] ‘Ignore’ notes documented with rationale"
|
||||
@@ -610,6 +639,8 @@ items:
|
||||
==================== END: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -715,24 +746,28 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Templates & Tools
|
||||
|
||||
### Character Development
|
||||
|
||||
- Comprehensive character profiles
|
||||
- Backstory builders
|
||||
- Voice and dialogue patterns
|
||||
- Relationship mapping
|
||||
|
||||
### Story Structure
|
||||
|
||||
- Three-act outlines
|
||||
- Save the Cat beat sheets
|
||||
- Hero's Journey mapping
|
||||
- Scene-by-scene breakdowns
|
||||
|
||||
### World Building
|
||||
|
||||
- Setting documentation
|
||||
- Magic/technology systems
|
||||
- Cultural development
|
||||
- Timeline tracking
|
||||
|
||||
### Publishing Support
|
||||
|
||||
- KDP formatting guidelines
|
||||
- Cover design briefs
|
||||
- Marketing copy templates
|
||||
@@ -741,6 +776,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Genre Support
|
||||
|
||||
### Built-in Genre Checklists
|
||||
|
||||
- Fantasy & Sci-Fi
|
||||
- Romance & Thriller
|
||||
- Mystery & Horror
|
||||
@@ -748,6 +784,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
- Young Adult
|
||||
|
||||
Each genre includes:
|
||||
|
||||
- Trope management
|
||||
- Reader expectations
|
||||
- Market positioning
|
||||
@@ -756,24 +793,28 @@ Each genre includes:
|
||||
## Best Practices
|
||||
|
||||
### Character Development
|
||||
|
||||
1. Start with internal conflict
|
||||
2. Build from wound/lie/want/need
|
||||
3. Create unique voice patterns
|
||||
4. Track arc progression
|
||||
|
||||
### Plot Construction
|
||||
|
||||
1. Begin with clear story question
|
||||
2. Escalate stakes progressively
|
||||
3. Plant setup/payoff pairs
|
||||
4. Balance pacing with character moments
|
||||
|
||||
### World Building
|
||||
|
||||
1. Maintain internal consistency
|
||||
2. Show through character experience
|
||||
3. Build only what serves story
|
||||
4. Track all established rules
|
||||
|
||||
### Revision Process
|
||||
|
||||
1. Complete draft before major edits
|
||||
2. Address structure before prose
|
||||
3. Read dialogue aloud
|
||||
@@ -810,14 +851,18 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
==================== END: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
||||
- **Act 1 (25%)**: Setup, inciting incident
|
||||
- **Act 2 (50%)**: Confrontation, complications
|
||||
- **Act 3 (25%)**: Resolution
|
||||
|
||||
## Save the Cat Beats
|
||||
|
||||
1. Opening Image (0-1%)
|
||||
2. Setup (1-10%)
|
||||
3. Theme Stated (5%)
|
||||
@@ -833,7 +878,9 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
13. Break into Three (80%)
|
||||
14. Finale (80-99%)
|
||||
15. Final Image (99-100%)
|
||||
|
||||
## Hero's Journey
|
||||
|
||||
1. Ordinary World
|
||||
2. Call to Adventure
|
||||
3. Refusal of Call
|
||||
@@ -848,6 +895,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
12. Return with Elixir
|
||||
|
||||
## Seven-Point Structure
|
||||
|
||||
1. Hook
|
||||
2. Plot Turn 1
|
||||
3. Pinch Point 1
|
||||
@@ -857,6 +905,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
7. Resolution
|
||||
|
||||
## Freytag's Pyramid
|
||||
|
||||
1. Exposition
|
||||
2. Rising Action
|
||||
3. Climax
|
||||
@@ -864,6 +913,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
5. Denouement
|
||||
|
||||
## Kishōtenketsu (Japanese)
|
||||
|
||||
- **Ki**: Introduction
|
||||
- **Shō**: Development
|
||||
- **Ten**: Twist
|
||||
|
||||
@@ -40,8 +40,10 @@ These references map directly to bundle sections:
|
||||
|
||||
|
||||
==================== START: .bmad-creative-writing/agents/book-critic.md ====================
|
||||
# Book Critic Agent Definition
|
||||
# -------------------------------------------------------
|
||||
# book-critic
|
||||
|
||||
CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
|
||||
|
||||
```yaml
|
||||
agent:
|
||||
name: Evelyn Clarke
|
||||
@@ -72,7 +74,8 @@ commands:
|
||||
- exit: Say goodbye as the Book Critic and abandon persona
|
||||
dependencies:
|
||||
tasks:
|
||||
- critical-review # ensure this task exists; otherwise agent handles logic inline
|
||||
- critical-review
|
||||
checklists:
|
||||
- genre-tropes-checklist # optional, enhances genre comparison
|
||||
- genre-tropes-checklist
|
||||
```
|
||||
==================== END: .bmad-creative-writing/agents/book-critic.md ====================
|
||||
|
||||
@@ -101,6 +101,7 @@ dependencies:
|
||||
You are the Character Psychologist, an expert in human nature and its fictional representation. You understand that compelling characters emerge from the intersection of desire, fear, and circumstance.
|
||||
|
||||
Focus on:
|
||||
|
||||
- **Core wounds** that shape worldview
|
||||
- **Defense mechanisms** that create behavior patterns
|
||||
- **Ghost/lie/want/need** framework
|
||||
@@ -114,6 +115,8 @@ Remember to present all options as numbered lists for easy selection.
|
||||
==================== END: .bmad-creative-writing/agents/character-psychologist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -218,16 +221,23 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/develop-character.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 3. Develop Character
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: develop-character
|
||||
name: Develop Character
|
||||
description: Produce rich character profiles with goals, flaws, arcs, and voice notes.
|
||||
persona_default: character-psychologist
|
||||
inputs:
|
||||
|
||||
- concept-brief.md
|
||||
steps:
|
||||
- Identify protagonist(s), antagonist(s), key side characters.
|
||||
@@ -238,15 +248,20 @@ output: characters.md
|
||||
==================== END: .bmad-creative-writing/tasks/develop-character.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workshop Dialog
|
||||
|
||||
## Purpose
|
||||
|
||||
Refine dialog for authenticity, character voice, and dramatic effectiveness.
|
||||
|
||||
## Process
|
||||
|
||||
### 1. Voice Audit
|
||||
|
||||
For each character, assess:
|
||||
|
||||
- Vocabulary level and word choice
|
||||
- Sentence structure preferences
|
||||
- Speech rhythms and patterns
|
||||
@@ -255,7 +270,9 @@ For each character, assess:
|
||||
- Emotional expression style
|
||||
|
||||
### 2. Subtext Analysis
|
||||
|
||||
For each exchange:
|
||||
|
||||
- What's being said directly
|
||||
- What's really being communicated
|
||||
- Power dynamics at play
|
||||
@@ -264,14 +281,18 @@ For each exchange:
|
||||
- Obstacles to directness
|
||||
|
||||
### 3. Flow Enhancement
|
||||
|
||||
- Remove unnecessary dialogue tags
|
||||
- Vary attribution methods
|
||||
- Add action beats
|
||||
- Incorporate silence/pauses
|
||||
- Balance dialog with narrative
|
||||
- Ensure natural interruptions
|
||||
|
||||
### 4. Conflict Injection
|
||||
|
||||
Where dialog lacks tension:
|
||||
|
||||
- Add opposing goals
|
||||
- Insert misunderstandings
|
||||
- Create subtext conflicts
|
||||
@@ -280,6 +301,7 @@ Where dialog lacks tension:
|
||||
- Add environmental pressure
|
||||
|
||||
### 5. Polish Pass
|
||||
|
||||
- Read aloud for rhythm
|
||||
- Check period authenticity
|
||||
- Verify character consistency
|
||||
@@ -288,20 +310,28 @@ Where dialog lacks tension:
|
||||
- Add distinctive character markers
|
||||
|
||||
## Output
|
||||
|
||||
Refined dialog with stronger voices and dramatic impact
|
||||
==================== END: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/character-depth-pass.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 9. Character Depth Pass
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: character-depth-pass
|
||||
name: Character Depth Pass
|
||||
description: Enrich character profiles with backstory and arc details.
|
||||
persona_default: character-psychologist
|
||||
inputs:
|
||||
|
||||
- character-summaries.md
|
||||
steps:
|
||||
- For each character, add formative events, internal conflicts, arc milestones.
|
||||
@@ -310,6 +340,8 @@ output: characters.md
|
||||
==================== END: .bmad-creative-writing/tasks/character-depth-pass.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -321,7 +353,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
## Instructions
|
||||
|
||||
1. **Initial Assessment**
|
||||
|
||||
- If user or the task being run provides a checklist name:
|
||||
- Try fuzzy matching (e.g. "plot checklist" -> "plot-structure-checklist")
|
||||
- If multiple matches found, ask user to clarify
|
||||
@@ -334,14 +365,12 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
|
||||
|
||||
2. **Document and Artifact Gathering**
|
||||
|
||||
- Each checklist will specify its required documents/artifacts at the beginning
|
||||
- Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
|
||||
|
||||
3. **Checklist Processing**
|
||||
|
||||
If in interactive mode:
|
||||
|
||||
- Work through each section of the checklist one at a time
|
||||
- For each section:
|
||||
- Review all items in the section following instructions for that section embedded in the checklist
|
||||
@@ -350,7 +379,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
|
||||
|
||||
If in YOLO mode:
|
||||
|
||||
- Process all sections at once
|
||||
- Create a comprehensive report of all findings
|
||||
- Present the complete analysis to the user
|
||||
@@ -358,7 +386,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
4. **Validation Approach**
|
||||
|
||||
For each checklist item:
|
||||
|
||||
- Read and understand the requirement
|
||||
- Look for evidence in the documentation that satisfies the requirement
|
||||
- Consider both explicit mentions and implicit coverage
|
||||
@@ -372,7 +399,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
5. **Section Analysis**
|
||||
|
||||
For each section:
|
||||
|
||||
- think step by step to calculate pass rate
|
||||
- Identify common themes in failed items
|
||||
- Provide specific recommendations for improvement
|
||||
@@ -382,7 +408,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
6. **Final Report**
|
||||
|
||||
Prepare a summary that includes:
|
||||
|
||||
- Overall checklist completion status
|
||||
- Pass rates by section
|
||||
- List of failed items with context
|
||||
@@ -406,6 +431,8 @@ The LLM will:
|
||||
==================== END: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -526,6 +553,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/templates/character-profile-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
template:
|
||||
id: character-profile
|
||||
@@ -620,15 +648,22 @@ sections:
|
||||
==================== END: .bmad-creative-writing/templates/character-profile-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 1. Character Consistency Checklist
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
checklist:
|
||||
id: character-consistency-checklist
|
||||
name: Character Consistency Checklist
|
||||
description: Verify character details and voice remain consistent throughout the manuscript.
|
||||
items:
|
||||
|
||||
- "[ ] Names spelled consistently (incl. diacritics)"
|
||||
- "[ ] Physical descriptors match across chapters"
|
||||
- "[ ] Goals and motivations do not contradict earlier scenes"
|
||||
@@ -639,6 +674,8 @@ items:
|
||||
==================== END: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -744,24 +781,28 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Templates & Tools
|
||||
|
||||
### Character Development
|
||||
|
||||
- Comprehensive character profiles
|
||||
- Backstory builders
|
||||
- Voice and dialogue patterns
|
||||
- Relationship mapping
|
||||
|
||||
### Story Structure
|
||||
|
||||
- Three-act outlines
|
||||
- Save the Cat beat sheets
|
||||
- Hero's Journey mapping
|
||||
- Scene-by-scene breakdowns
|
||||
|
||||
### World Building
|
||||
|
||||
- Setting documentation
|
||||
- Magic/technology systems
|
||||
- Cultural development
|
||||
- Timeline tracking
|
||||
|
||||
### Publishing Support
|
||||
|
||||
- KDP formatting guidelines
|
||||
- Cover design briefs
|
||||
- Marketing copy templates
|
||||
@@ -770,6 +811,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Genre Support
|
||||
|
||||
### Built-in Genre Checklists
|
||||
|
||||
- Fantasy & Sci-Fi
|
||||
- Romance & Thriller
|
||||
- Mystery & Horror
|
||||
@@ -777,6 +819,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
- Young Adult
|
||||
|
||||
Each genre includes:
|
||||
|
||||
- Trope management
|
||||
- Reader expectations
|
||||
- Market positioning
|
||||
@@ -785,24 +828,28 @@ Each genre includes:
|
||||
## Best Practices
|
||||
|
||||
### Character Development
|
||||
|
||||
1. Start with internal conflict
|
||||
2. Build from wound/lie/want/need
|
||||
3. Create unique voice patterns
|
||||
4. Track arc progression
|
||||
|
||||
### Plot Construction
|
||||
|
||||
1. Begin with clear story question
|
||||
2. Escalate stakes progressively
|
||||
3. Plant setup/payoff pairs
|
||||
4. Balance pacing with character moments
|
||||
|
||||
### World Building
|
||||
|
||||
1. Maintain internal consistency
|
||||
2. Show through character experience
|
||||
3. Build only what serves story
|
||||
4. Track all established rules
|
||||
|
||||
### Revision Process
|
||||
|
||||
1. Complete draft before major edits
|
||||
2. Address structure before prose
|
||||
3. Read dialogue aloud
|
||||
|
||||
@@ -100,6 +100,7 @@ dependencies:
|
||||
You are the Dialog Specialist, translator of human interaction into compelling fiction. You understand that great dialog does multiple jobs simultaneously.
|
||||
|
||||
Master:
|
||||
|
||||
- **Naturalistic flow** without real speech's redundancy
|
||||
- **Character-specific** vocabulary and rhythm
|
||||
- **Subtext and implication** over direct statement
|
||||
@@ -113,6 +114,8 @@ Remember to present all options as numbered lists for easy selection.
|
||||
==================== END: .bmad-creative-writing/agents/dialog-specialist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -217,15 +220,20 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Workshop Dialog
|
||||
|
||||
## Purpose
|
||||
|
||||
Refine dialog for authenticity, character voice, and dramatic effectiveness.
|
||||
|
||||
## Process
|
||||
|
||||
### 1. Voice Audit
|
||||
|
||||
For each character, assess:
|
||||
|
||||
- Vocabulary level and word choice
|
||||
- Sentence structure preferences
|
||||
- Speech rhythms and patterns
|
||||
@@ -234,7 +242,9 @@ For each character, assess:
|
||||
- Emotional expression style
|
||||
|
||||
### 2. Subtext Analysis
|
||||
|
||||
For each exchange:
|
||||
|
||||
- What's being said directly
|
||||
- What's really being communicated
|
||||
- Power dynamics at play
|
||||
@@ -243,14 +253,18 @@ For each exchange:
|
||||
- Obstacles to directness
|
||||
|
||||
### 3. Flow Enhancement
|
||||
|
||||
- Remove unnecessary dialogue tags
|
||||
- Vary attribution methods
|
||||
- Add action beats
|
||||
- Incorporate silence/pauses
|
||||
- Balance dialog with narrative
|
||||
- Ensure natural interruptions
|
||||
|
||||
### 4. Conflict Injection
|
||||
|
||||
Where dialog lacks tension:
|
||||
|
||||
- Add opposing goals
|
||||
- Insert misunderstandings
|
||||
- Create subtext conflicts
|
||||
@@ -259,6 +273,7 @@ Where dialog lacks tension:
|
||||
- Add environmental pressure
|
||||
|
||||
### 5. Polish Pass
|
||||
|
||||
- Read aloud for rhythm
|
||||
- Check period authenticity
|
||||
- Verify character consistency
|
||||
@@ -267,10 +282,13 @@ Where dialog lacks tension:
|
||||
- Add distinctive character markers
|
||||
|
||||
## Output
|
||||
|
||||
Refined dialog with stronger voices and dramatic impact
|
||||
==================== END: .bmad-creative-writing/tasks/workshop-dialog.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -282,7 +300,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
## Instructions
|
||||
|
||||
1. **Initial Assessment**
|
||||
|
||||
- If user or the task being run provides a checklist name:
|
||||
- Try fuzzy matching (e.g. "plot checklist" -> "plot-structure-checklist")
|
||||
- If multiple matches found, ask user to clarify
|
||||
@@ -295,14 +312,12 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
|
||||
|
||||
2. **Document and Artifact Gathering**
|
||||
|
||||
- Each checklist will specify its required documents/artifacts at the beginning
|
||||
- Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
|
||||
|
||||
3. **Checklist Processing**
|
||||
|
||||
If in interactive mode:
|
||||
|
||||
- Work through each section of the checklist one at a time
|
||||
- For each section:
|
||||
- Review all items in the section following instructions for that section embedded in the checklist
|
||||
@@ -311,7 +326,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
|
||||
|
||||
If in YOLO mode:
|
||||
|
||||
- Process all sections at once
|
||||
- Create a comprehensive report of all findings
|
||||
- Present the complete analysis to the user
|
||||
@@ -319,7 +333,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
4. **Validation Approach**
|
||||
|
||||
For each checklist item:
|
||||
|
||||
- Read and understand the requirement
|
||||
- Look for evidence in the documentation that satisfies the requirement
|
||||
- Consider both explicit mentions and implicit coverage
|
||||
@@ -333,7 +346,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
5. **Section Analysis**
|
||||
|
||||
For each section:
|
||||
|
||||
- think step by step to calculate pass rate
|
||||
- Identify common themes in failed items
|
||||
- Provide specific recommendations for improvement
|
||||
@@ -343,7 +355,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
6. **Final Report**
|
||||
|
||||
Prepare a summary that includes:
|
||||
|
||||
- Overall checklist completion status
|
||||
- Pass rates by section
|
||||
- List of failed items with context
|
||||
@@ -367,6 +378,8 @@ The LLM will:
|
||||
==================== END: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -487,6 +500,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/templates/character-profile-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
template:
|
||||
id: character-profile
|
||||
@@ -581,15 +595,22 @@ sections:
|
||||
==================== END: .bmad-creative-writing/templates/character-profile-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 23. Comedic Timing & Humor Checklist
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
checklist:
|
||||
id: comedic-timing-checklist
|
||||
name: Comedic Timing & Humor Checklist
|
||||
description: Ensure jokes land and humorous beats serve character/plot.
|
||||
items:
|
||||
|
||||
- "[ ] Setup, beat, punchline structure clear"
|
||||
- "[ ] Humor aligns with character voice"
|
||||
- "[ ] Cultural references understandable by target audience"
|
||||
@@ -600,6 +621,8 @@ items:
|
||||
==================== END: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -705,24 +728,28 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Templates & Tools
|
||||
|
||||
### Character Development
|
||||
|
||||
- Comprehensive character profiles
|
||||
- Backstory builders
|
||||
- Voice and dialogue patterns
|
||||
- Relationship mapping
|
||||
|
||||
### Story Structure
|
||||
|
||||
- Three-act outlines
|
||||
- Save the Cat beat sheets
|
||||
- Hero's Journey mapping
|
||||
- Scene-by-scene breakdowns
|
||||
|
||||
### World Building
|
||||
|
||||
- Setting documentation
|
||||
- Magic/technology systems
|
||||
- Cultural development
|
||||
- Timeline tracking
|
||||
|
||||
### Publishing Support
|
||||
|
||||
- KDP formatting guidelines
|
||||
- Cover design briefs
|
||||
- Marketing copy templates
|
||||
@@ -731,6 +758,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Genre Support
|
||||
|
||||
### Built-in Genre Checklists
|
||||
|
||||
- Fantasy & Sci-Fi
|
||||
- Romance & Thriller
|
||||
- Mystery & Horror
|
||||
@@ -738,6 +766,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
- Young Adult
|
||||
|
||||
Each genre includes:
|
||||
|
||||
- Trope management
|
||||
- Reader expectations
|
||||
- Market positioning
|
||||
@@ -746,24 +775,28 @@ Each genre includes:
|
||||
## Best Practices
|
||||
|
||||
### Character Development
|
||||
|
||||
1. Start with internal conflict
|
||||
2. Build from wound/lie/want/need
|
||||
3. Create unique voice patterns
|
||||
4. Track arc progression
|
||||
|
||||
### Plot Construction
|
||||
|
||||
1. Begin with clear story question
|
||||
2. Escalate stakes progressively
|
||||
3. Plant setup/payoff pairs
|
||||
4. Balance pacing with character moments
|
||||
|
||||
### World Building
|
||||
|
||||
1. Maintain internal consistency
|
||||
2. Show through character experience
|
||||
3. Build only what serves story
|
||||
4. Track all established rules
|
||||
|
||||
### Revision Process
|
||||
|
||||
1. Complete draft before major edits
|
||||
2. Address structure before prose
|
||||
3. Read dialogue aloud
|
||||
@@ -800,14 +833,18 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
==================== END: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
||||
- **Act 1 (25%)**: Setup, inciting incident
|
||||
- **Act 2 (50%)**: Confrontation, complications
|
||||
- **Act 3 (25%)**: Resolution
|
||||
|
||||
## Save the Cat Beats
|
||||
|
||||
1. Opening Image (0-1%)
|
||||
2. Setup (1-10%)
|
||||
3. Theme Stated (5%)
|
||||
@@ -823,7 +860,9 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
13. Break into Three (80%)
|
||||
14. Finale (80-99%)
|
||||
15. Final Image (99-100%)
|
||||
|
||||
## Hero's Journey
|
||||
|
||||
1. Ordinary World
|
||||
2. Call to Adventure
|
||||
3. Refusal of Call
|
||||
@@ -838,6 +877,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
12. Return with Elixir
|
||||
|
||||
## Seven-Point Structure
|
||||
|
||||
1. Hook
|
||||
2. Plot Turn 1
|
||||
3. Pinch Point 1
|
||||
@@ -847,6 +887,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
7. Resolution
|
||||
|
||||
## Freytag's Pyramid
|
||||
|
||||
1. Exposition
|
||||
2. Rising Action
|
||||
3. Climax
|
||||
@@ -854,6 +895,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
5. Denouement
|
||||
|
||||
## Kishōtenketsu (Japanese)
|
||||
|
||||
- **Ki**: Introduction
|
||||
- **Shō**: Development
|
||||
- **Ten**: Twist
|
||||
|
||||
@@ -101,6 +101,7 @@ dependencies:
|
||||
You are the Editor, defender of clear, powerful prose. You balance respect for authorial voice with the demands of readability and market expectations.
|
||||
|
||||
Focus on:
|
||||
|
||||
- **Micro-level**: word choice, sentence structure, grammar
|
||||
- **Meso-level**: paragraph flow, scene transitions, pacing
|
||||
- **Macro-level**: chapter structure, act breaks, overall arc
|
||||
@@ -114,6 +115,8 @@ Remember to present all options as numbered lists for easy selection.
|
||||
==================== END: .bmad-creative-writing/agents/editor.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -218,16 +221,23 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/final-polish.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 14. Final Polish
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: final-polish
|
||||
name: Final Polish
|
||||
description: Line‑edit for style, clarity, grammar.
|
||||
persona_default: editor
|
||||
inputs:
|
||||
|
||||
- chapter-dialog.md | polished-manuscript.md
|
||||
steps:
|
||||
- Correct grammar and tighten prose.
|
||||
@@ -237,16 +247,23 @@ output: chapter-final.md | final-manuscript.md
|
||||
==================== END: .bmad-creative-writing/tasks/final-polish.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 6. Incorporate Feedback
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: incorporate-feedback
|
||||
name: Incorporate Feedback
|
||||
description: Merge beta feedback into manuscript; accept, reject, or revise.
|
||||
persona_default: editor
|
||||
inputs:
|
||||
|
||||
- draft-manuscript.md
|
||||
- beta-notes.md
|
||||
steps:
|
||||
@@ -258,6 +275,8 @@ output: polished-manuscript.md
|
||||
==================== END: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -269,7 +288,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
## Instructions
|
||||
|
||||
1. **Initial Assessment**
|
||||
|
||||
- If user or the task being run provides a checklist name:
|
||||
- Try fuzzy matching (e.g. "plot checklist" -> "plot-structure-checklist")
|
||||
- If multiple matches found, ask user to clarify
|
||||
@@ -282,14 +300,12 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
|
||||
|
||||
2. **Document and Artifact Gathering**
|
||||
|
||||
- Each checklist will specify its required documents/artifacts at the beginning
|
||||
- Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
|
||||
|
||||
3. **Checklist Processing**
|
||||
|
||||
If in interactive mode:
|
||||
|
||||
- Work through each section of the checklist one at a time
|
||||
- For each section:
|
||||
- Review all items in the section following instructions for that section embedded in the checklist
|
||||
@@ -298,7 +314,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
|
||||
|
||||
If in YOLO mode:
|
||||
|
||||
- Process all sections at once
|
||||
- Create a comprehensive report of all findings
|
||||
- Present the complete analysis to the user
|
||||
@@ -306,7 +321,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
4. **Validation Approach**
|
||||
|
||||
For each checklist item:
|
||||
|
||||
- Read and understand the requirement
|
||||
- Look for evidence in the documentation that satisfies the requirement
|
||||
- Consider both explicit mentions and implicit coverage
|
||||
@@ -320,7 +334,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
5. **Section Analysis**
|
||||
|
||||
For each section:
|
||||
|
||||
- think step by step to calculate pass rate
|
||||
- Identify common themes in failed items
|
||||
- Provide specific recommendations for improvement
|
||||
@@ -330,7 +343,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
6. **Final Report**
|
||||
|
||||
Prepare a summary that includes:
|
||||
|
||||
- Overall checklist completion status
|
||||
- Pass rates by section
|
||||
- List of failed items with context
|
||||
@@ -354,6 +366,8 @@ The LLM will:
|
||||
==================== END: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -474,6 +488,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/templates/chapter-draft-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
template:
|
||||
id: chapter-draft-tmpl
|
||||
@@ -558,15 +573,22 @@ sections:
|
||||
==================== END: .bmad-creative-writing/templates/chapter-draft-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 4. Line‑Edit Quality Checklist
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
checklist:
|
||||
id: line-edit-quality-checklist
|
||||
name: Line‑Edit Quality Checklist
|
||||
description: Copy‑editing pass for clarity, grammar, and style.
|
||||
items:
|
||||
|
||||
- "[ ] Grammar/spelling free of errors"
|
||||
- "[ ] Passive voice minimized (target <15%)"
|
||||
- "[ ] Repetitious words/phrases trimmed"
|
||||
@@ -577,15 +599,22 @@ items:
|
||||
==================== END: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 5. Publication Readiness Checklist
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
checklist:
|
||||
id: publication-readiness-checklist
|
||||
name: Publication Readiness Checklist
|
||||
description: Final checks before releasing or submitting the manuscript.
|
||||
items:
|
||||
|
||||
- "[ ] Front matter complete (title, author, dedication)"
|
||||
- "[ ] Back matter complete (acknowledgments, about author)"
|
||||
- "[ ] Table of contents updated (digital)"
|
||||
@@ -596,6 +625,8 @@ items:
|
||||
==================== END: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -701,24 +732,28 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Templates & Tools
|
||||
|
||||
### Character Development
|
||||
|
||||
- Comprehensive character profiles
|
||||
- Backstory builders
|
||||
- Voice and dialogue patterns
|
||||
- Relationship mapping
|
||||
|
||||
### Story Structure
|
||||
|
||||
- Three-act outlines
|
||||
- Save the Cat beat sheets
|
||||
- Hero's Journey mapping
|
||||
- Scene-by-scene breakdowns
|
||||
|
||||
### World Building
|
||||
|
||||
- Setting documentation
|
||||
- Magic/technology systems
|
||||
- Cultural development
|
||||
- Timeline tracking
|
||||
|
||||
### Publishing Support
|
||||
|
||||
- KDP formatting guidelines
|
||||
- Cover design briefs
|
||||
- Marketing copy templates
|
||||
@@ -727,6 +762,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Genre Support
|
||||
|
||||
### Built-in Genre Checklists
|
||||
|
||||
- Fantasy & Sci-Fi
|
||||
- Romance & Thriller
|
||||
- Mystery & Horror
|
||||
@@ -734,6 +770,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
- Young Adult
|
||||
|
||||
Each genre includes:
|
||||
|
||||
- Trope management
|
||||
- Reader expectations
|
||||
- Market positioning
|
||||
@@ -742,24 +779,28 @@ Each genre includes:
|
||||
## Best Practices
|
||||
|
||||
### Character Development
|
||||
|
||||
1. Start with internal conflict
|
||||
2. Build from wound/lie/want/need
|
||||
3. Create unique voice patterns
|
||||
4. Track arc progression
|
||||
|
||||
### Plot Construction
|
||||
|
||||
1. Begin with clear story question
|
||||
2. Escalate stakes progressively
|
||||
3. Plant setup/payoff pairs
|
||||
4. Balance pacing with character moments
|
||||
|
||||
### World Building
|
||||
|
||||
1. Maintain internal consistency
|
||||
2. Show through character experience
|
||||
3. Build only what serves story
|
||||
4. Track all established rules
|
||||
|
||||
### Revision Process
|
||||
|
||||
1. Complete draft before major edits
|
||||
2. Address structure before prose
|
||||
3. Read dialogue aloud
|
||||
|
||||
@@ -103,6 +103,7 @@ dependencies:
|
||||
You are the Genre Specialist, guardian of reader satisfaction and genre innovation. You understand that genres are contracts with readers, promising specific experiences.
|
||||
|
||||
Navigate:
|
||||
|
||||
- **Core requirements** that define the genre
|
||||
- **Optional conventions** that enhance familiarity
|
||||
- **Trope subversion** opportunities
|
||||
@@ -116,6 +117,8 @@ Remember to present all options as numbered lists for easy selection.
|
||||
==================== END: .bmad-creative-writing/agents/genre-specialist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -220,14 +223,18 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Analyze Story Structure
|
||||
|
||||
## Purpose
|
||||
|
||||
Perform comprehensive structural analysis of a narrative work to identify strengths, weaknesses, and improvement opportunities.
|
||||
|
||||
## Process
|
||||
|
||||
### 1. Identify Structure Type
|
||||
|
||||
- Three-act structure
|
||||
- Five-act structure
|
||||
- Hero's Journey
|
||||
@@ -238,6 +245,7 @@ Perform comprehensive structural analysis of a narrative work to identify streng
|
||||
- Non-linear/experimental
|
||||
|
||||
### 2. Map Key Points
|
||||
|
||||
- **Opening**: Hook, world establishment, character introduction
|
||||
- **Inciting Incident**: What disrupts the status quo?
|
||||
- **Plot Point 1**: What locks in the conflict?
|
||||
@@ -245,7 +253,9 @@ Perform comprehensive structural analysis of a narrative work to identify streng
|
||||
- **Plot Point 2**: What raises stakes to maximum?
|
||||
- **Climax**: How does central conflict resolve?
|
||||
- **Resolution**: What new equilibrium emerges?
|
||||
|
||||
### 3. Analyze Pacing
|
||||
|
||||
- Scene length distribution
|
||||
- Tension escalation curve
|
||||
- Breather moment placement
|
||||
@@ -253,6 +263,7 @@ Perform comprehensive structural analysis of a narrative work to identify streng
|
||||
- Chapter break effectiveness
|
||||
|
||||
### 4. Evaluate Setup/Payoff
|
||||
|
||||
- Track all setups (promises to reader)
|
||||
- Verify each has satisfying payoff
|
||||
- Identify orphaned setups
|
||||
@@ -260,13 +271,16 @@ Perform comprehensive structural analysis of a narrative work to identify streng
|
||||
- Check Chekhov's guns
|
||||
|
||||
### 5. Assess Subplot Integration
|
||||
|
||||
- List all subplots
|
||||
- Track intersection with main plot
|
||||
- Evaluate resolution satisfaction
|
||||
- Check thematic reinforcement
|
||||
|
||||
### 6. Generate Report
|
||||
|
||||
Create structural report including:
|
||||
|
||||
- Structure diagram
|
||||
- Pacing chart
|
||||
- Problem areas
|
||||
@@ -274,10 +288,13 @@ Create structural report including:
|
||||
- Alternative structures
|
||||
|
||||
## Output
|
||||
|
||||
Comprehensive structural analysis with actionable recommendations
|
||||
==================== END: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -289,7 +306,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
## Instructions
|
||||
|
||||
1. **Initial Assessment**
|
||||
|
||||
- If user or the task being run provides a checklist name:
|
||||
- Try fuzzy matching (e.g. "plot checklist" -> "plot-structure-checklist")
|
||||
- If multiple matches found, ask user to clarify
|
||||
@@ -302,14 +318,12 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
|
||||
|
||||
2. **Document and Artifact Gathering**
|
||||
|
||||
- Each checklist will specify its required documents/artifacts at the beginning
|
||||
- Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
|
||||
|
||||
3. **Checklist Processing**
|
||||
|
||||
If in interactive mode:
|
||||
|
||||
- Work through each section of the checklist one at a time
|
||||
- For each section:
|
||||
- Review all items in the section following instructions for that section embedded in the checklist
|
||||
@@ -318,7 +332,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
|
||||
|
||||
If in YOLO mode:
|
||||
|
||||
- Process all sections at once
|
||||
- Create a comprehensive report of all findings
|
||||
- Present the complete analysis to the user
|
||||
@@ -326,7 +339,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
4. **Validation Approach**
|
||||
|
||||
For each checklist item:
|
||||
|
||||
- Read and understand the requirement
|
||||
- Look for evidence in the documentation that satisfies the requirement
|
||||
- Consider both explicit mentions and implicit coverage
|
||||
@@ -340,7 +352,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
5. **Section Analysis**
|
||||
|
||||
For each section:
|
||||
|
||||
- think step by step to calculate pass rate
|
||||
- Identify common themes in failed items
|
||||
- Provide specific recommendations for improvement
|
||||
@@ -350,7 +361,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
6. **Final Report**
|
||||
|
||||
Prepare a summary that includes:
|
||||
|
||||
- Overall checklist completion status
|
||||
- Pass rates by section
|
||||
- List of failed items with context
|
||||
@@ -374,6 +384,8 @@ The LLM will:
|
||||
==================== END: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -494,6 +506,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/templates/story-outline-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
template:
|
||||
id: story-outline
|
||||
@@ -592,15 +605,22 @@ sections:
|
||||
==================== END: .bmad-creative-writing/templates/story-outline-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/genre-tropes-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Genre Tropes Checklist (General)
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
checklist:
|
||||
id: genre-tropes-checklist
|
||||
name: Genre Tropes Checklist
|
||||
description: Confirm expected reader promises for chosen genre are addressed or subverted intentionally.
|
||||
items:
|
||||
|
||||
- "[ ] Core genre conventions present (e.g., mystery has a solvable puzzle)"
|
||||
- "[ ] Audience‑favored tropes used or consciously averted"
|
||||
- "[ ] Genre pacing beats hit (e.g., romance meet‑cute by 15%)"
|
||||
@@ -610,15 +630,22 @@ items:
|
||||
==================== END: .bmad-creative-writing/checklists/genre-tropes-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 17. Fantasy Magic System Consistency Checklist
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
checklist:
|
||||
id: fantasy-magic-system-checklist
|
||||
name: Fantasy Magic System Consistency Checklist
|
||||
description: Keep magical rules, costs, and exceptions coherent.
|
||||
items:
|
||||
|
||||
- "[ ] Core source and rules defined"
|
||||
- "[ ] Limitations create plot obstacles"
|
||||
- "[ ] Costs or risks for using magic stated"
|
||||
@@ -629,15 +656,22 @@ items:
|
||||
==================== END: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 15. Sci‑Fi Technology Plausibility Checklist
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
checklist:
|
||||
id: scifi-technology-plausibility-checklist
|
||||
name: Sci‑Fi Technology Plausibility Checklist
|
||||
description: Ensure advanced technologies feel believable and internally consistent.
|
||||
items:
|
||||
|
||||
- "[ ] Technology built on clear scientific principles or hand‑waved consistently"
|
||||
- "[ ] Limits and costs of tech established"
|
||||
- "[ ] Tech capabilities applied consistently to plot"
|
||||
@@ -647,15 +681,22 @@ items:
|
||||
==================== END: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 12. Romance Emotional Beats Checklist
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
checklist:
|
||||
id: romance-emotional-beats-checklist
|
||||
name: Romance Emotional Beats Checklist
|
||||
description: Track essential emotional beats in romance arcs.
|
||||
items:
|
||||
|
||||
- "[ ] Meet‑cute / inciting attraction"
|
||||
- "[ ] Growing intimacy montage"
|
||||
- "[ ] Midpoint commitment or confession moment"
|
||||
@@ -666,6 +707,8 @@ items:
|
||||
==================== END: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -771,24 +814,28 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Templates & Tools
|
||||
|
||||
### Character Development
|
||||
|
||||
- Comprehensive character profiles
|
||||
- Backstory builders
|
||||
- Voice and dialogue patterns
|
||||
- Relationship mapping
|
||||
|
||||
### Story Structure
|
||||
|
||||
- Three-act outlines
|
||||
- Save the Cat beat sheets
|
||||
- Hero's Journey mapping
|
||||
- Scene-by-scene breakdowns
|
||||
|
||||
### World Building
|
||||
|
||||
- Setting documentation
|
||||
- Magic/technology systems
|
||||
- Cultural development
|
||||
- Timeline tracking
|
||||
|
||||
### Publishing Support
|
||||
|
||||
- KDP formatting guidelines
|
||||
- Cover design briefs
|
||||
- Marketing copy templates
|
||||
@@ -797,6 +844,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Genre Support
|
||||
|
||||
### Built-in Genre Checklists
|
||||
|
||||
- Fantasy & Sci-Fi
|
||||
- Romance & Thriller
|
||||
- Mystery & Horror
|
||||
@@ -804,6 +852,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
- Young Adult
|
||||
|
||||
Each genre includes:
|
||||
|
||||
- Trope management
|
||||
- Reader expectations
|
||||
- Market positioning
|
||||
@@ -812,24 +861,28 @@ Each genre includes:
|
||||
## Best Practices
|
||||
|
||||
### Character Development
|
||||
|
||||
1. Start with internal conflict
|
||||
2. Build from wound/lie/want/need
|
||||
3. Create unique voice patterns
|
||||
4. Track arc progression
|
||||
|
||||
### Plot Construction
|
||||
|
||||
1. Begin with clear story question
|
||||
2. Escalate stakes progressively
|
||||
3. Plant setup/payoff pairs
|
||||
4. Balance pacing with character moments
|
||||
|
||||
### World Building
|
||||
|
||||
1. Maintain internal consistency
|
||||
2. Show through character experience
|
||||
3. Build only what serves story
|
||||
4. Track all established rules
|
||||
|
||||
### Revision Process
|
||||
|
||||
1. Complete draft before major edits
|
||||
2. Address structure before prose
|
||||
3. Read dialogue aloud
|
||||
@@ -866,14 +919,18 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
==================== END: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
||||
- **Act 1 (25%)**: Setup, inciting incident
|
||||
- **Act 2 (50%)**: Confrontation, complications
|
||||
- **Act 3 (25%)**: Resolution
|
||||
|
||||
## Save the Cat Beats
|
||||
|
||||
1. Opening Image (0-1%)
|
||||
2. Setup (1-10%)
|
||||
3. Theme Stated (5%)
|
||||
@@ -889,7 +946,9 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
13. Break into Three (80%)
|
||||
14. Finale (80-99%)
|
||||
15. Final Image (99-100%)
|
||||
|
||||
## Hero's Journey
|
||||
|
||||
1. Ordinary World
|
||||
2. Call to Adventure
|
||||
3. Refusal of Call
|
||||
@@ -904,6 +963,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
12. Return with Elixir
|
||||
|
||||
## Seven-Point Structure
|
||||
|
||||
1. Hook
|
||||
2. Plot Turn 1
|
||||
3. Pinch Point 1
|
||||
@@ -913,6 +973,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
7. Resolution
|
||||
|
||||
## Freytag's Pyramid
|
||||
|
||||
1. Exposition
|
||||
2. Rising Action
|
||||
3. Climax
|
||||
@@ -920,6 +981,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
5. Denouement
|
||||
|
||||
## Kishōtenketsu (Japanese)
|
||||
|
||||
- **Ki**: Introduction
|
||||
- **Shō**: Development
|
||||
- **Ten**: Twist
|
||||
|
||||
@@ -101,6 +101,7 @@ dependencies:
|
||||
You are the Narrative Designer, architect of stories that respond to reader/player choices. You balance authorial vision with participant agency.
|
||||
|
||||
Design for:
|
||||
|
||||
- **Meaningful choices** not false dilemmas
|
||||
- **Consequence chains** that feel logical
|
||||
- **Emotional investment** in decisions
|
||||
@@ -114,6 +115,8 @@ Remember to present all options as numbered lists for easy selection.
|
||||
==================== END: .bmad-creative-writing/agents/narrative-designer.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Create Document from Template (YAML Driven)
|
||||
|
||||
## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
|
||||
@@ -218,16 +221,23 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
==================== END: .bmad-creative-writing/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/outline-scenes.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 11. Outline Scenes
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: outline-scenes
|
||||
name: Outline Scenes
|
||||
description: Group scene list into chapters with act structure.
|
||||
persona_default: plot-architect
|
||||
inputs:
|
||||
|
||||
- scene-list.md
|
||||
steps:
|
||||
- Assign scenes to chapters.
|
||||
@@ -237,16 +247,23 @@ output: snowflake-outline.md
|
||||
==================== END: .bmad-creative-writing/tasks/outline-scenes.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/generate-scene-list.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
# 10. Generate Scene List
|
||||
|
||||
# ------------------------------------------------------------
|
||||
|
||||
---
|
||||
|
||||
task:
|
||||
id: generate-scene-list
|
||||
name: Generate Scene List
|
||||
description: Break synopsis into a numbered list of scenes.
|
||||
persona_default: plot-architect
|
||||
inputs:
|
||||
|
||||
- synopsis.md | story-outline.md
|
||||
steps:
|
||||
- Identify key beats.
|
||||
@@ -256,6 +273,8 @@ output: scene-list.md
|
||||
==================== END: .bmad-creative-writing/tasks/generate-scene-list.md ====================
|
||||
|
||||
==================== 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.
|
||||
@@ -267,7 +286,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
## Instructions
|
||||
|
||||
1. **Initial Assessment**
|
||||
|
||||
- If user or the task being run provides a checklist name:
|
||||
- Try fuzzy matching (e.g. "plot checklist" -> "plot-structure-checklist")
|
||||
- If multiple matches found, ask user to clarify
|
||||
@@ -280,14 +298,12 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
|
||||
|
||||
2. **Document and Artifact Gathering**
|
||||
|
||||
- Each checklist will specify its required documents/artifacts at the beginning
|
||||
- Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
|
||||
|
||||
3. **Checklist Processing**
|
||||
|
||||
If in interactive mode:
|
||||
|
||||
- Work through each section of the checklist one at a time
|
||||
- For each section:
|
||||
- Review all items in the section following instructions for that section embedded in the checklist
|
||||
@@ -296,7 +312,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
- Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
|
||||
|
||||
If in YOLO mode:
|
||||
|
||||
- Process all sections at once
|
||||
- Create a comprehensive report of all findings
|
||||
- Present the complete analysis to the user
|
||||
@@ -304,7 +319,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
4. **Validation Approach**
|
||||
|
||||
For each checklist item:
|
||||
|
||||
- Read and understand the requirement
|
||||
- Look for evidence in the documentation that satisfies the requirement
|
||||
- Consider both explicit mentions and implicit coverage
|
||||
@@ -318,7 +332,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
5. **Section Analysis**
|
||||
|
||||
For each section:
|
||||
|
||||
- think step by step to calculate pass rate
|
||||
- Identify common themes in failed items
|
||||
- Provide specific recommendations for improvement
|
||||
@@ -328,7 +341,6 @@ If the user asks or does not specify a specific checklist, list the checklists a
|
||||
6. **Final Report**
|
||||
|
||||
Prepare a summary that includes:
|
||||
|
||||
- Overall checklist completion status
|
||||
- Pass rates by section
|
||||
- List of failed items with context
|
||||
@@ -352,6 +364,8 @@ The LLM will:
|
||||
==================== END: .bmad-creative-writing/tasks/execute-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Advanced Elicitation Task
|
||||
|
||||
## Purpose
|
||||
@@ -472,6 +486,7 @@ Choose a number (0-8) or 9 to proceed:
|
||||
==================== END: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/templates/scene-list-tmpl.yaml ====================
|
||||
# <!-- Powered by BMAD™ Core -->
|
||||
---
|
||||
template:
|
||||
id: scene-list-tmpl
|
||||
@@ -529,9 +544,12 @@ sections:
|
||||
==================== END: .bmad-creative-writing/templates/scene-list-tmpl.yaml ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Plot Structure Checklist
|
||||
|
||||
## Opening
|
||||
|
||||
- [ ] Hook engages within first page
|
||||
- [ ] Genre/tone established early
|
||||
- [ ] World rules clear
|
||||
@@ -539,6 +557,7 @@ sections:
|
||||
- [ ] Status quo established before disruption
|
||||
|
||||
## Structure Fundamentals
|
||||
|
||||
- [ ] Inciting incident by 10-15% mark
|
||||
- [ ] Clear story question posed
|
||||
- [ ] Stakes established and clear
|
||||
@@ -546,12 +565,15 @@ sections:
|
||||
- [ ] B-story provides thematic counterpoint
|
||||
|
||||
## Rising Action
|
||||
|
||||
- [ ] Complications escalate logically
|
||||
- [ ] Try-fail cycles build tension
|
||||
- [ ] Subplots weave with main plot
|
||||
- [ ] False victories/defeats included
|
||||
- [ ] Character growth parallels plot
|
||||
|
||||
## Midpoint
|
||||
|
||||
- [ ] Major reversal or revelation
|
||||
- [ ] Stakes raised significantly
|
||||
- [ ] Protagonist approach shifts
|
||||
@@ -559,6 +581,7 @@ sections:
|
||||
- [ ] Point of no return crossed
|
||||
|
||||
## Crisis Building
|
||||
|
||||
- [ ] Bad guys close in (internal/external)
|
||||
- [ ] Protagonist plans fail
|
||||
- [ ] Allies fall away/betray
|
||||
@@ -566,6 +589,7 @@ sections:
|
||||
- [ ] Dark night of soul (character lowest)
|
||||
|
||||
## Climax
|
||||
|
||||
- [ ] Protagonist must act (no rescue)
|
||||
- [ ] Uses lessons learned
|
||||
- [ ] Internal/external conflicts merge
|
||||
@@ -573,6 +597,7 @@ sections:
|
||||
- [ ] Clear win/loss/transformation
|
||||
|
||||
## Resolution
|
||||
|
||||
- [ ] New equilibrium established
|
||||
- [ ] Loose threads tied
|
||||
- [ ] Character growth demonstrated
|
||||
@@ -581,6 +606,8 @@ sections:
|
||||
==================== END: .bmad-creative-writing/checklists/plot-structure-checklist.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# BMad Creative Writing Knowledge Base
|
||||
|
||||
## Overview
|
||||
@@ -686,24 +713,28 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Templates & Tools
|
||||
|
||||
### Character Development
|
||||
|
||||
- Comprehensive character profiles
|
||||
- Backstory builders
|
||||
- Voice and dialogue patterns
|
||||
- Relationship mapping
|
||||
|
||||
### Story Structure
|
||||
|
||||
- Three-act outlines
|
||||
- Save the Cat beat sheets
|
||||
- Hero's Journey mapping
|
||||
- Scene-by-scene breakdowns
|
||||
|
||||
### World Building
|
||||
|
||||
- Setting documentation
|
||||
- Magic/technology systems
|
||||
- Cultural development
|
||||
- Timeline tracking
|
||||
|
||||
### Publishing Support
|
||||
|
||||
- KDP formatting guidelines
|
||||
- Cover design briefs
|
||||
- Marketing copy templates
|
||||
@@ -712,6 +743,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
## Genre Support
|
||||
|
||||
### Built-in Genre Checklists
|
||||
|
||||
- Fantasy & Sci-Fi
|
||||
- Romance & Thriller
|
||||
- Mystery & Horror
|
||||
@@ -719,6 +751,7 @@ BMad Creative Writing transforms you into a "Creative Director" - orchestrating
|
||||
- Young Adult
|
||||
|
||||
Each genre includes:
|
||||
|
||||
- Trope management
|
||||
- Reader expectations
|
||||
- Market positioning
|
||||
@@ -727,24 +760,28 @@ Each genre includes:
|
||||
## Best Practices
|
||||
|
||||
### Character Development
|
||||
|
||||
1. Start with internal conflict
|
||||
2. Build from wound/lie/want/need
|
||||
3. Create unique voice patterns
|
||||
4. Track arc progression
|
||||
|
||||
### Plot Construction
|
||||
|
||||
1. Begin with clear story question
|
||||
2. Escalate stakes progressively
|
||||
3. Plant setup/payoff pairs
|
||||
4. Balance pacing with character moments
|
||||
|
||||
### World Building
|
||||
|
||||
1. Maintain internal consistency
|
||||
2. Show through character experience
|
||||
3. Build only what serves story
|
||||
4. Track all established rules
|
||||
|
||||
### Revision Process
|
||||
|
||||
1. Complete draft before major edits
|
||||
2. Address structure before prose
|
||||
3. Read dialogue aloud
|
||||
@@ -781,14 +818,18 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
==================== END: .bmad-creative-writing/data/bmad-kb.md ====================
|
||||
|
||||
==================== START: .bmad-creative-writing/data/story-structures.md ====================
|
||||
<!-- Powered by BMAD™ Core -->
|
||||
|
||||
# Story Structure Patterns
|
||||
|
||||
## Three-Act Structure
|
||||
|
||||
- **Act 1 (25%)**: Setup, inciting incident
|
||||
- **Act 2 (50%)**: Confrontation, complications
|
||||
- **Act 3 (25%)**: Resolution
|
||||
|
||||
## Save the Cat Beats
|
||||
|
||||
1. Opening Image (0-1%)
|
||||
2. Setup (1-10%)
|
||||
3. Theme Stated (5%)
|
||||
@@ -804,7 +845,9 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
13. Break into Three (80%)
|
||||
14. Finale (80-99%)
|
||||
15. Final Image (99-100%)
|
||||
|
||||
## Hero's Journey
|
||||
|
||||
1. Ordinary World
|
||||
2. Call to Adventure
|
||||
3. Refusal of Call
|
||||
@@ -819,6 +862,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
12. Return with Elixir
|
||||
|
||||
## Seven-Point Structure
|
||||
|
||||
1. Hook
|
||||
2. Plot Turn 1
|
||||
3. Pinch Point 1
|
||||
@@ -828,6 +872,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
7. Resolution
|
||||
|
||||
## Freytag's Pyramid
|
||||
|
||||
1. Exposition
|
||||
2. Rising Action
|
||||
3. Climax
|
||||
@@ -835,6 +880,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
|
||||
5. Denouement
|
||||
|
||||
## Kishōtenketsu (Japanese)
|
||||
|
||||
- **Ki**: Introduction
|
||||
- **Shō**: Development
|
||||
- **Ten**: Twist
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user