simple prd workflow
This commit is contained in:
Brian Madison
@@ -4,25 +4,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
|
||||
|
||||
```yml
|
||||
activation-instructions:
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
agent:
|
||||
name: John
|
||||
id: pm
|
||||
title: Product Manager
|
||||
icon: 📋
|
||||
whenToUse: "Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication"
|
||||
customization:
|
||||
|
||||
whenToUse: Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication
|
||||
customization: null
|
||||
persona:
|
||||
role: Investigative Product Strategist & Market-Savvy PM
|
||||
style: Analytical, inquisitive, data-driven, user-focused, pragmatic
|
||||
identity: Product Manager specialized in document creation and product research
|
||||
focus: Creating PRDs and other product documentation using templates
|
||||
|
||||
core_principles:
|
||||
- Deeply understand "Why" - uncover root causes and motivations
|
||||
- Champion the user - maintain relentless focus on target user value
|
||||
@@ -32,16 +29,13 @@ persona:
|
||||
- Collaborative & iterative approach
|
||||
- Proactive risk identification
|
||||
- Strategic thinking & outcome-oriented
|
||||
|
||||
startup:
|
||||
- Greet the user with your name and role, and inform of the *help command.
|
||||
|
||||
commands:
|
||||
- "*help" - Show: numbered list of the following commands to allow selection
|
||||
- "*chat-mode" - (Default) Deep conversation with advanced-elicitation
|
||||
- "*create-doc {template}" - Create doc (no template = show available templates)
|
||||
- "*exit" - Say goodbye as the PM, and then abandon inhabiting this persona
|
||||
|
||||
- '*help" - Show: numbered list of the following commands to allow selection'
|
||||
- '*chat-mode" - (Default) Deep conversation with advanced-elicitation'
|
||||
- '*create-doc {template}" - Create doc (no template = show available templates)'
|
||||
- '*exit" - Say goodbye as the PM, and then abandon inhabiting this persona'
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-doc
|
||||
@@ -54,6 +48,7 @@ dependencies:
|
||||
templates:
|
||||
- prd-tmpl
|
||||
- brownfield-prd-tmpl
|
||||
- simple-project-prd-tmpl
|
||||
checklists:
|
||||
- pm-checklist
|
||||
- change-checklist
|
||||
|
||||
@@ -33,4 +33,15 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
|
||||
8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
|
||||
|
||||
## TODO: ADD MORE CONTENT ONCE STABLE ALPHA BUILD
|
||||
## IDE Development Workflow
|
||||
|
||||
1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
|
||||
2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
|
||||
3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
|
||||
4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
|
||||
5. Use a new chat window to allow the SM agent to `draft the next story`.
|
||||
6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
|
||||
7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
|
||||
8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
|
||||
|
||||
With this work flow, there is only 1 story in progress at a time, worked sequentially.
|
||||
|
||||
@@ -111,7 +111,7 @@ Use appropriate diagram type for clarity.]]
|
||||
|
||||
```mermaid
|
||||
{{architecture_diagram}}
|
||||
```
|
||||
```text
|
||||
|
||||
### Architectural Patterns
|
||||
|
||||
@@ -262,7 +262,7 @@ interface UserProfile {
|
||||
bio?: string;
|
||||
preferences: Record<string, any>;
|
||||
}
|
||||
```
|
||||
```text
|
||||
|
||||
**Relationships:**
|
||||
|
||||
@@ -286,17 +286,20 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),
|
||||
|
||||
^^CONDITION: has_rest_api^^
|
||||
|
||||
```yaml
|
||||
```yml
|
||||
openapi: 3.0.0
|
||||
info:
|
||||
title: { { api_title } }
|
||||
version: { { api_version } }
|
||||
description: { { api_description } }
|
||||
|
||||
title:
|
||||
'[object Object]': null
|
||||
version:
|
||||
'[object Object]': null
|
||||
description:
|
||||
'[object Object]': null
|
||||
servers:
|
||||
- url: { { api_base_url } }
|
||||
description: { { environment } }
|
||||
# ... OpenAPI specification continues
|
||||
- url:
|
||||
'[object Object]': null
|
||||
description:
|
||||
'[object Object]': null
|
||||
```
|
||||
|
||||
^^/CONDITION: has_rest_api^^
|
||||
@@ -306,7 +309,7 @@ servers:
|
||||
```graphql
|
||||
# GraphQL Schema
|
||||
{{graphql_schema}}
|
||||
```
|
||||
```text
|
||||
|
||||
^^/CONDITION: has_graphql_api^^
|
||||
|
||||
@@ -464,7 +467,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
**Component Organization:**
|
||||
|
||||
```
|
||||
```text
|
||||
{{component_structure}}
|
||||
```
|
||||
|
||||
@@ -476,7 +479,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
component_template;
|
||||
}
|
||||
}
|
||||
```
|
||||
```text
|
||||
|
||||
### State Management Architecture
|
||||
|
||||
@@ -503,7 +506,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
**Route Organization:**
|
||||
|
||||
```
|
||||
```text
|
||||
{{route_structure}}
|
||||
```
|
||||
|
||||
@@ -515,7 +518,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
protected_route_example;
|
||||
}
|
||||
}
|
||||
```
|
||||
```text
|
||||
|
||||
### Frontend Services Layer
|
||||
|
||||
@@ -539,7 +542,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
service_example;
|
||||
}
|
||||
}
|
||||
```
|
||||
```text
|
||||
|
||||
## Backend Architecture
|
||||
|
||||
@@ -556,7 +559,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
```
|
||||
{{function_structure}}
|
||||
```
|
||||
```text
|
||||
|
||||
**Function Template:**
|
||||
|
||||
@@ -573,7 +576,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
^^CONDITION: traditional_server^^
|
||||
**Controller/Route Organization:**
|
||||
|
||||
```
|
||||
```text
|
||||
{{controller_structure}}
|
||||
```
|
||||
|
||||
@@ -585,7 +588,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
controller_template;
|
||||
}
|
||||
}
|
||||
```
|
||||
```text
|
||||
|
||||
^^/CONDITION: traditional_server^^
|
||||
|
||||
@@ -607,7 +610,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
repository_pattern;
|
||||
}
|
||||
}
|
||||
```
|
||||
```text
|
||||
|
||||
### Authentication and Authorization
|
||||
|
||||
@@ -627,7 +630,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
auth_middleware;
|
||||
}
|
||||
}
|
||||
```
|
||||
```text
|
||||
|
||||
## Unified Project Structure
|
||||
|
||||
@@ -711,7 +714,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
```bash
|
||||
{{prerequisites_commands}}
|
||||
```
|
||||
```text
|
||||
|
||||
**Initial Setup:**
|
||||
|
||||
@@ -733,7 +736,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
# Run tests
|
||||
{{test_commands}}
|
||||
```
|
||||
```text
|
||||
|
||||
### Environment Configuration
|
||||
|
||||
@@ -771,9 +774,9 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### CI/CD Pipeline
|
||||
|
||||
```yaml
|
||||
{ { cicd_pipeline_config } }
|
||||
```
|
||||
```yml
|
||||
'[object Object]': null
|
||||
```text
|
||||
|
||||
### Environments
|
||||
|
||||
@@ -837,7 +840,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
Integration Tests
|
||||
/ \
|
||||
Frontend Unit Backend Unit
|
||||
```
|
||||
```text
|
||||
|
||||
### Test Organization
|
||||
|
||||
@@ -845,19 +848,19 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
```
|
||||
{{frontend_test_structure}}
|
||||
```
|
||||
```text
|
||||
|
||||
**Backend Tests:**
|
||||
|
||||
```
|
||||
{{backend_test_structure}}
|
||||
```
|
||||
```text
|
||||
|
||||
**E2E Tests:**
|
||||
|
||||
```
|
||||
{{e2e_test_structure}}
|
||||
```
|
||||
```text
|
||||
|
||||
### Test Examples
|
||||
|
||||
@@ -879,7 +882,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
backend_test_example;
|
||||
}
|
||||
}
|
||||
```
|
||||
```text
|
||||
|
||||
**E2E Test:**
|
||||
|
||||
@@ -932,7 +935,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
```mermaid
|
||||
{{error_flow_diagram}}
|
||||
```
|
||||
```text
|
||||
|
||||
### Error Response Format
|
||||
|
||||
@@ -956,7 +959,7 @@ interface ApiError {
|
||||
frontend_error_handler;
|
||||
}
|
||||
}
|
||||
```
|
||||
```text
|
||||
|
||||
### Backend Error Handling
|
||||
|
||||
@@ -1000,35 +1003,3 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
## Checklist Results Report
|
||||
|
||||
[[LLM: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the `architect-checklist` and populate results here.]]
|
||||
|
||||
## Next Steps
|
||||
|
||||
[[LLM: Provide specific next steps for implementation.]]
|
||||
|
||||
### Implementation Order
|
||||
|
||||
1. **Environment Setup**
|
||||
|
||||
- Initialize monorepo structure
|
||||
- Configure development environment
|
||||
- Set up version control
|
||||
|
||||
2. **Foundation (Epic 1)**
|
||||
|
||||
- Implement authentication flow
|
||||
- Set up database schema
|
||||
- Create basic API structure
|
||||
- Implement core UI components
|
||||
|
||||
3. **Feature Development**
|
||||
- Follow story sequence from PRD
|
||||
- Maintain type safety across stack
|
||||
- Write tests as you go
|
||||
|
||||
### Developer Handoff Prompts
|
||||
|
||||
**For Scrum Master:**
|
||||
"Create stories for {{Project Name}} using the PRD at docs/prd.md and this fullstack architecture at docs/fullstack-architecture.md. Focus on Epic 1 implementation."
|
||||
|
||||
**For Developer:**
|
||||
"Implement Story 1.1 from docs/stories/epic1/story-1.1.md using the fullstack architecture at docs/fullstack-architecture.md. Follow the coding standards and use the defined tech stack."
|
||||
|
||||
461
.bmad-core/templates/simple-project-prd-tmpl.md
Normal file
461
.bmad-core/templates/simple-project-prd-tmpl.md
Normal file
@@ -0,0 +1,461 @@
|
||||
# {{Project Name}} Product Requirements Document (PRD)
|
||||
|
||||
[[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
|
||||
|
||||
## Goals and Background Context
|
||||
|
||||
[[LLM: Populate the 2 child sections based on what we have received from user description or the provided brief. Allow user to review the 2 sections and offer changes before proceeding]]
|
||||
|
||||
### Goals
|
||||
|
||||
[[LLM: Bullet list of 1 line desired outcomes the PRD will deliver if successful - user and project desires]]
|
||||
|
||||
### Background Context
|
||||
|
||||
[[LLM: 1-2 short paragraphs summarizing the background context, such as what we learned in the brief without being redundant with the goals, what and why this solves a problem, what the current landscape or need is etc...]]
|
||||
|
||||
### Change Log
|
||||
|
||||
[[LLM: Track document versions and changes]]
|
||||
|
||||
| Date | Version | Description | Author |
|
||||
| :--- | :------ | :---------- | :----- |
|
||||
|
||||
## Requirements
|
||||
|
||||
[[LLM: Draft the list of functional and non functional requirements under the two child sections, and immediately execute tasks#advanced-elicitation display]]
|
||||
|
||||
### Functional
|
||||
|
||||
[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with FR`.]]
|
||||
@{example: - FR6: The Todo List uses AI to detect and warn against adding potentially duplicate todo items that are worded differently.}
|
||||
|
||||
### Non Functional
|
||||
|
||||
[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR`.]]
|
||||
@{example: - NFR1: AWS service usage **must** aim to stay within free-tier limits where feasible.}
|
||||
|
||||
^^CONDITION: has_ui^^
|
||||
|
||||
## User Interface Design Goals
|
||||
|
||||
[[LLM: Capture high-level UI/UX vision to inform story creation and also generate a prompt for Lovable or V0 if the user would like either. Steps:
|
||||
|
||||
1. Pre-fill all subsections with educated guesses based on project context
|
||||
2. Present the complete rendered section to user
|
||||
3. Clearly let the user know where assumptions were made
|
||||
4. Ask targeted questions for unclear/missing elements or areas needing more specification
|
||||
5. This is NOT detailed UI spec - focus on product vision and user goals
|
||||
6. After section completion, immediately apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### Overall UX Vision
|
||||
|
||||
### Key Interaction Paradigms
|
||||
|
||||
### Core Screens and Views
|
||||
|
||||
[[LLM: From a product perspective, what are the most critical screens or views necessary to deliver the the PRD values and goals? This is meant to be Conceptual High Level to Drive Rough Epic or User Stories]]
|
||||
|
||||
@{example}
|
||||
|
||||
- Login Screen
|
||||
- Main Dashboard
|
||||
- Item Detail Page
|
||||
- Settings Page
|
||||
@{/example}
|
||||
|
||||
### Accessibility: { None, WCAG, etc }
|
||||
|
||||
### Branding
|
||||
|
||||
[[LLM: Any known branding elements or style guides that must be incorporated?]]
|
||||
|
||||
@{example}
|
||||
|
||||
- Replicate the look and feel of early 1900s black and white cinema, including animated effects replicating film damage or projector glitches during page or state transitions.
|
||||
- Attached is the full color pallet and tokens for our corporate branding.
|
||||
@{/example}
|
||||
|
||||
### Target Device and Platforms
|
||||
|
||||
@{example}
|
||||
"Web Responsive, and all mobile platforms", "IPhone Only", "ASCII Windows Desktop"
|
||||
@{/example}
|
||||
|
||||
^^/CONDITION: has_ui^^
|
||||
|
||||
## Technical Assumptions
|
||||
|
||||
[[LLM: Gather technical decisions that will be used for this simple technical PRD that includes architecture decisions. Steps:
|
||||
|
||||
1. Check if `data#technical-preferences` file exists - use it to pre-populate choices
|
||||
2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
|
||||
3. For unknowns, offer guidance based on project goals and MVP scope
|
||||
4. Document ALL technical choices with rationale (why this choice fits the project)
|
||||
5. These become constraints for the Architect - be specific and complete
|
||||
6. After section completion, apply `tasks#advanced-elicitation` protocol.]]
|
||||
|
||||
### Repository Structure: { Monorepo, Polyrepo, etc...}
|
||||
|
||||
### Service Architecture
|
||||
|
||||
[[LLM: CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).]]
|
||||
|
||||
## Testing requirements
|
||||
|
||||
[[LLM: CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).]]
|
||||
|
||||
### Additional Technical Assumptions and Requests
|
||||
|
||||
[[LLM: Throughout the entire process of drafting this document, if any other technical assumptions are raised or discovered appropriate for the architect, add them here as additional bulleted items]]
|
||||
|
||||
## Data Models
|
||||
|
||||
[[LLM: Define the core data models/entities that will be used in the front end (if there is one), core application or back end, and if both, shared between frontend and backend:
|
||||
|
||||
1. Review PRD requirements and identify key business entities
|
||||
2. For each model, explain its purpose and relationships
|
||||
3. Include key attributes and data types
|
||||
4. Show relationships between models
|
||||
5. Create TypeScript interfaces that can be shared
|
||||
6. Discuss design decisions with user
|
||||
|
||||
Create a clear conceptual model before moving to database schema.
|
||||
|
||||
After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: data_model>>
|
||||
|
||||
### {{model_name}}
|
||||
|
||||
**Purpose:** {{model_purpose}}
|
||||
|
||||
**Key Attributes:**
|
||||
|
||||
- {{attribute_1}}: {{type_1}} - {{description_1}}
|
||||
- {{attribute_2}}: {{type_2}} - {{description_2}}
|
||||
|
||||
**TypeScript Interface:**
|
||||
|
||||
```typescript
|
||||
{
|
||||
{
|
||||
model_interface;
|
||||
}
|
||||
}
|
||||
```text
|
||||
|
||||
**Relationships:**
|
||||
|
||||
- {{relationship_1}}
|
||||
- {{relationship_2}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: data_model}
|
||||
|
||||
### User
|
||||
|
||||
**Purpose:** Represents authenticated users in the system
|
||||
|
||||
**Key Attributes:**
|
||||
|
||||
- id: string - Unique identifier
|
||||
- email: string - User's email address
|
||||
- name: string - Display name
|
||||
- role: enum - User permission level
|
||||
- timestamps: Date - Created and updated times
|
||||
|
||||
**TypeScript Interface:**
|
||||
|
||||
```typescript
|
||||
interface User {
|
||||
id: string;
|
||||
email: string;
|
||||
name: string;
|
||||
role: "admin" | "user" | "guest";
|
||||
createdAt: Date;
|
||||
updatedAt: Date;
|
||||
profile?: UserProfile;
|
||||
}
|
||||
|
||||
interface UserProfile {
|
||||
avatarUrl?: string;
|
||||
bio?: string;
|
||||
preferences: Record<string, any>;
|
||||
}
|
||||
```
|
||||
|
||||
**Relationships:**
|
||||
|
||||
- Has many Posts (1:n)
|
||||
- Has one Profile (1:1)
|
||||
@{/example}
|
||||
|
||||
## REST API Spec
|
||||
|
||||
[[LLM: Based on the chosen API style from Tech Stack:
|
||||
|
||||
1. If REST API, create an OpenAPI 3.0 specification
|
||||
2. If GraphQL, provide the GraphQL schema
|
||||
3. If tRPC, show router definitions
|
||||
4. Include all endpoints from epics/stories
|
||||
5. Define request/response schemas based on data models
|
||||
6. Document authentication requirements
|
||||
7. Include example requests/responses
|
||||
|
||||
Use appropriate format for the chosen API style. If no API (e.g., static site), skip this section.]]
|
||||
|
||||
^^CONDITION: has_rest_api^^
|
||||
|
||||
```yml
|
||||
openapi: 3.0.0
|
||||
info:
|
||||
title:
|
||||
'[object Object]': null
|
||||
version:
|
||||
'[object Object]': null
|
||||
description:
|
||||
'[object Object]': null
|
||||
servers:
|
||||
- url:
|
||||
'[object Object]': null
|
||||
description:
|
||||
'[object Object]': null
|
||||
```text
|
||||
|
||||
^^/CONDITION: has_rest_api^^
|
||||
|
||||
^^CONDITION: has_graphql_api^^
|
||||
|
||||
```graphql
|
||||
# GraphQL Schema
|
||||
{{graphql_schema}}
|
||||
```
|
||||
|
||||
^^/CONDITION: has_graphql_api^^
|
||||
|
||||
^^CONDITION: has_trpc_api^^
|
||||
|
||||
```typescript
|
||||
// tRPC Router Definitions
|
||||
{
|
||||
{
|
||||
trpc_routers;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
^^/CONDITION: has_trpc_api^^
|
||||
|
||||
[[LLM: After presenting the API spec (or noting its absence if not applicable), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Components
|
||||
|
||||
[[LLM: Based on the architectural patterns, tech stack, and data models from above:
|
||||
|
||||
1. Identify major logical components/services across the fullstack
|
||||
2. Consider both frontend and backend components
|
||||
3. Define clear boundaries and interfaces between components
|
||||
4. For each component, specify:
|
||||
|
||||
- Primary responsibility
|
||||
- Key interfaces/APIs exposed
|
||||
- Dependencies on other components
|
||||
- Technology specifics based on tech stack choices
|
||||
|
||||
5. Create component diagrams where helpful
|
||||
6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: component>>
|
||||
|
||||
### {{component_name}}
|
||||
|
||||
**Responsibility:** {{component_description}}
|
||||
|
||||
**Key Interfaces:**
|
||||
|
||||
- {{interface_1}}
|
||||
- {{interface_2}}
|
||||
|
||||
**Dependencies:** {{dependencies}}
|
||||
|
||||
**Technology Stack:** {{component_tech_details}}
|
||||
<</REPEAT>>
|
||||
|
||||
### Component Diagrams
|
||||
|
||||
[[LLM: Create Mermaid diagrams to visualize component relationships. Options:
|
||||
|
||||
- C4 Container diagram for high-level view
|
||||
- Component diagram for detailed internal structure
|
||||
- Sequence diagrams for complex interactions
|
||||
Choose the most appropriate for clarity
|
||||
|
||||
After presenting the diagrams, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## External APIs
|
||||
|
||||
[[LLM: For each external service integration:
|
||||
|
||||
1. Identify APIs needed based on PRD requirements and component design
|
||||
2. If documentation URLs are unknown, ask user for specifics
|
||||
3. Document authentication methods and security considerations
|
||||
4. List specific endpoints that will be used
|
||||
5. Note any rate limits or usage constraints
|
||||
|
||||
If no external APIs are needed, state this explicitly and skip to next section.]]
|
||||
|
||||
^^CONDITION: has_external_apis^^
|
||||
|
||||
<<REPEAT: external_api>>
|
||||
|
||||
### {{api_name}} API
|
||||
|
||||
- **Purpose:** {{api_purpose}}
|
||||
- **Documentation:** {{api_docs_url}}
|
||||
- **Base URL(s):** {{api_base_url}}
|
||||
- **Authentication:** {{auth_method}}
|
||||
- **Rate Limits:** {{rate_limits}}
|
||||
|
||||
**Key Endpoints Used:**
|
||||
<<REPEAT: endpoint>>
|
||||
|
||||
- `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
|
||||
<</REPEAT>>
|
||||
|
||||
**Integration Notes:** {{integration_considerations}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: external_api}
|
||||
|
||||
### Stripe API
|
||||
|
||||
- **Purpose:** Payment processing and subscription management
|
||||
- **Documentation:** https://stripe.com/docs/api
|
||||
- **Base URL(s):** `https://api.stripe.com/v1`
|
||||
- **Authentication:** Bearer token with secret key
|
||||
- **Rate Limits:** 100 requests per second
|
||||
|
||||
**Key Endpoints Used:**
|
||||
|
||||
- `POST /customers` - Create customer profiles
|
||||
- `POST /payment_intents` - Process payments
|
||||
- `POST /subscriptions` - Manage subscriptions
|
||||
@{/example}
|
||||
|
||||
^^/CONDITION: has_external_apis^^
|
||||
|
||||
[[LLM: After presenting external APIs (or noting their absence), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Coding Standards
|
||||
|
||||
[[LLM: Define MINIMAL but CRITICAL standards for AI agents. Focus only on project-specific rules that prevent common mistakes. These will be used by dev agents.
|
||||
|
||||
After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### Critical Fullstack Rules
|
||||
|
||||
<<REPEAT: critical_rule>>
|
||||
|
||||
- **{{rule_name}}:** {{rule_description}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: critical_rules}
|
||||
|
||||
- **Type Sharing:** Always define types in packages/shared and import from there
|
||||
- **API Calls:** Never make direct HTTP calls - use the service layer
|
||||
- **Environment Variables:** Access only through config objects, never process.env directly
|
||||
- **Error Handling:** All API routes must use the standard error handler
|
||||
- **State Updates:** Never mutate state directly - use proper state management patterns
|
||||
@{/example}
|
||||
|
||||
### Naming Conventions
|
||||
|
||||
| Element | Frontend | Backend | Example |
|
||||
| :-------------- | :------------------- | :--------- | :------------------ |
|
||||
| Components | PascalCase | - | `UserProfile.tsx` |
|
||||
| Hooks | camelCase with 'use' | - | `useAuth.ts` |
|
||||
| API Routes | - | kebab-case | `/api/user-profile` |
|
||||
| Database Tables | - | snake_case | `user_profiles` |
|
||||
|
||||
## Epics
|
||||
|
||||
[[LLM: First, present a high-level list of all epics for user approval, the epic_list and immediately execute tasks#advanced-elicitation display. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.
|
||||
|
||||
CRITICAL: Epics MUST be logically sequential following agile best practices:
|
||||
|
||||
- Each epic should deliver a significant, end-to-end, fully deployable increment of testable functionality
|
||||
- Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page
|
||||
- Each subsequent epic builds upon previous epics' functionality delivering major blocks of functionality that provide tangible value to users or business when deployed
|
||||
- Not every project needs multiple epics, an epic needs to deliver value. For example, an API completed can deliver value even if a UI is not complete and planned for a separate epic.
|
||||
- Err on the side of less epics, but let the user know your rationale and offer options for splitting them if it seems some are too large or focused on disparate things.
|
||||
- Cross Cutting Concerns should flow through epics and stories and not be final stories. For example, adding a logging framework as a last story of an epic, or at the end of a project as a final epic or story would be terrible as we would not have logging from the beginning.]]
|
||||
|
||||
<<REPEAT: epic_list>>
|
||||
|
||||
- Epic{{epic_number}} {{epic_title}}: {{short_goal}}
|
||||
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: epic_list}
|
||||
|
||||
1. Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management
|
||||
2. Core Business Entities: Create and manage primary domain objects with CRUD operations
|
||||
3. User Workflows & Interactions: Enable key user journeys and business processes
|
||||
4. Reporting & Analytics: Provide insights and data visualization for users
|
||||
|
||||
@{/example}
|
||||
|
||||
[[LLM: After the epic list is approved, present each `epic_details` with all its stories and acceptance criteria as a complete review unit and immediately execute tasks#advanced-elicitation display, before moving on to the next epic.]]
|
||||
|
||||
<<REPEAT: epic_details>>
|
||||
|
||||
## Epic {{epic_number}} {{epic_title}}
|
||||
|
||||
{{epic_goal}} [[LLM: Expanded goal - 2-3 sentences describing the objective and value all the stories will achieve]]
|
||||
|
||||
[[LLM: CRITICAL STORY SEQUENCING REQUIREMENTS:
|
||||
|
||||
- Stories within each epic MUST be logically sequential
|
||||
- Each story should be a "vertical slice" delivering complete functionality
|
||||
- No story should depend on work from a later story or epic
|
||||
- Identify and note any direct prerequisite stories
|
||||
- Focus on "what" and "why" not "how" (leave technical implementation to Architect) yet be precise enough to support a logical sequential order of operations from story to story.
|
||||
- Ensure each story delivers clear user or business value, try to avoid enablers and build them into stories that deliver value.
|
||||
- Size stories for AI agent execution: Each story must be completable by a single AI agent in one focused session without context overflow
|
||||
- Think "junior developer working for 2-4 hours" - stories must be small, focused, and self-contained
|
||||
- If a story seems complex, break it down further as long as it can deliver a vertical slice
|
||||
- Each story should result in working, testable code before the agent's context window fills]]
|
||||
|
||||
<<REPEAT: story>>
|
||||
|
||||
### Story {{epic_number}}.{{story_number}} {{story_title}}
|
||||
|
||||
As a {{user_type}},
|
||||
I want {{action}},
|
||||
so that {{benefit}}.
|
||||
|
||||
#### Acceptance Criteria
|
||||
|
||||
[[LLM: Define clear, comprehensive, and testable acceptance criteria that:
|
||||
|
||||
- Precisely define what "done" means from a functional perspective
|
||||
- Are unambiguous and serve as basis for verification
|
||||
- Include any critical non-functional requirements from the PRD
|
||||
- Consider local testability for backend/data components
|
||||
- Specify UI/UX requirements and framework adherence where applicable
|
||||
- Avoid cross-cutting concerns that should be in other stories or PRD sections]]
|
||||
|
||||
<<REPEAT: criteria>>
|
||||
|
||||
- {{criterion number}}: {{criteria}}
|
||||
|
||||
<</REPEAT>>
|
||||
<</REPEAT>>
|
||||
<</REPEAT>>
|
||||
|
||||
## Next Steps
|
||||
|
||||
### Design Architect Prompt
|
||||
|
||||
[[LLM: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input.]]
|
||||
@@ -1646,7 +1646,18 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
|
||||
8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
|
||||
|
||||
## TODO: ADD MORE CONTENT ONCE STABLE ALPHA BUILD
|
||||
## IDE Development Workflow
|
||||
|
||||
1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
|
||||
2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
|
||||
3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
|
||||
4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
|
||||
5. Use a new chat window to allow the SM agent to `draft the next story`.
|
||||
6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
|
||||
7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
|
||||
8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
|
||||
|
||||
With this work flow, there is only 1 story in progress at a time, worked sequentially.
|
||||
==================== END: data#bmad-kb ====================
|
||||
|
||||
==================== START: utils#template-format ====================
|
||||
|
||||
@@ -2541,38 +2541,6 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
## Checklist Results Report
|
||||
|
||||
[[LLM: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the `architect-checklist` and populate results here.]]
|
||||
|
||||
## Next Steps
|
||||
|
||||
[[LLM: Provide specific next steps for implementation.]]
|
||||
|
||||
### Implementation Order
|
||||
|
||||
1. **Environment Setup**
|
||||
|
||||
- Initialize monorepo structure
|
||||
- Configure development environment
|
||||
- Set up version control
|
||||
|
||||
2. **Foundation (Epic 1)**
|
||||
|
||||
- Implement authentication flow
|
||||
- Set up database schema
|
||||
- Create basic API structure
|
||||
- Implement core UI components
|
||||
|
||||
3. **Feature Development**
|
||||
- Follow story sequence from PRD
|
||||
- Maintain type safety across stack
|
||||
- Write tests as you go
|
||||
|
||||
### Developer Handoff Prompts
|
||||
|
||||
**For Scrum Master:**
|
||||
"Create stories for {{Project Name}} using the PRD at docs/prd.md and this fullstack architecture at docs/fullstack-architecture.md. Focus on Epic 1 implementation."
|
||||
|
||||
**For Developer:**
|
||||
"Implement Story 1.1 from docs/stories/epic1/story-1.1.md using the fullstack architecture at docs/fullstack-architecture.md. Follow the coding standards and use the defined tech stack."
|
||||
==================== END: templates#fullstack-architecture-tmpl ====================
|
||||
|
||||
==================== START: templates#brownfield-architecture-tmpl ====================
|
||||
|
||||
@@ -49,14 +49,12 @@ agent:
|
||||
id: bmad-master
|
||||
title: BMAD Master Task Executor
|
||||
icon: 🧙
|
||||
whenToUse: "Use when you need comprehensive expertise across all domains or rapid context switching between multiple agent capabilities"
|
||||
|
||||
whenToUse: Use when you need comprehensive expertise across all domains or rapid context switching between multiple agent capabilities
|
||||
persona:
|
||||
role: Master Task Executor & BMAD Method Expert
|
||||
style: Efficient, direct, action-oriented. Executes any BMAD task/template/util/checklist with precision
|
||||
identity: Universal executor of all BMAD-METHOD capabilities, directly runs any resource
|
||||
focus: Direct execution without transformation, load resources only when needed
|
||||
|
||||
core_principles:
|
||||
- Execute any resource directly without persona transformation
|
||||
- Load resources at runtime, never pre-load
|
||||
@@ -64,36 +62,30 @@ persona:
|
||||
- Track execution state and guide multi-step processes
|
||||
- Use numbered lists for choices
|
||||
- Process (*) commands immediately
|
||||
|
||||
startup:
|
||||
- Announce: "I'm BMad Master, your BMAD task executor. I can run any task, template, util, checklist, workflow, or schema. Type *help or tell me what you need."
|
||||
- Announce: I'm BMad Master, your BMAD task executor. I can run any task, template, util, checklist, workflow, or schema. Type *help or tell me what you need.
|
||||
- CRITICAL: Do NOT scan filesystem or load any resources during startup
|
||||
- CRITICAL: Do NOT run discovery tasks automatically
|
||||
- CRITICAL: Do NOT run discovery tasks automatically
|
||||
- Wait for user request before any tool use
|
||||
- Match request to resources, offer numbered options if unclear
|
||||
- Load resources only when explicitly requested
|
||||
|
||||
commands:
|
||||
- "*help" - Show commands
|
||||
- "*chat" - Advanced elicitation + KB mode
|
||||
- "*status" - Current context
|
||||
- "*task/template/util/checklist/workflow {name}" - Execute (list if no name)
|
||||
- "*list {type}" - List resources by type
|
||||
- "*exit" - Exit (confirm)
|
||||
- "*yolo" - Skip confirmations
|
||||
- "*doc-out" - Output full document
|
||||
|
||||
- '*help" - Show commands'
|
||||
- '*chat" - Advanced elicitation + KB mode'
|
||||
- '*status" - Current context'
|
||||
- '*task/template/util/checklist/workflow {name}" - Execute (list if no name)'
|
||||
- '*list {type}" - List resources by type'
|
||||
- '*exit" - Exit (confirm)'
|
||||
- '*yolo" - Skip confirmations'
|
||||
- '*doc-out" - Output full document'
|
||||
fuzzy-matching:
|
||||
- 85% confidence threshold
|
||||
- Show numbered list if unsure
|
||||
|
||||
execution:
|
||||
- NEVER use tools during startup - only announce and wait
|
||||
- Runtime discovery ONLY when user requests specific resources
|
||||
- Workflow: User request → Runtime discovery → Load resource → Execute instructions → Guide inputs → Provide feedback
|
||||
- Suggest related resources after completion
|
||||
|
||||
# Reference list for runtime discovery (DO NOT PRELOAD):
|
||||
dependencies:
|
||||
tasks:
|
||||
- advanced-elicitation
|
||||
@@ -6530,38 +6522,6 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
## Checklist Results Report
|
||||
|
||||
[[LLM: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the `architect-checklist` and populate results here.]]
|
||||
|
||||
## Next Steps
|
||||
|
||||
[[LLM: Provide specific next steps for implementation.]]
|
||||
|
||||
### Implementation Order
|
||||
|
||||
1. **Environment Setup**
|
||||
|
||||
- Initialize monorepo structure
|
||||
- Configure development environment
|
||||
- Set up version control
|
||||
|
||||
2. **Foundation (Epic 1)**
|
||||
|
||||
- Implement authentication flow
|
||||
- Set up database schema
|
||||
- Create basic API structure
|
||||
- Implement core UI components
|
||||
|
||||
3. **Feature Development**
|
||||
- Follow story sequence from PRD
|
||||
- Maintain type safety across stack
|
||||
- Write tests as you go
|
||||
|
||||
### Developer Handoff Prompts
|
||||
|
||||
**For Scrum Master:**
|
||||
"Create stories for {{Project Name}} using the PRD at docs/prd.md and this fullstack architecture at docs/fullstack-architecture.md. Focus on Epic 1 implementation."
|
||||
|
||||
**For Developer:**
|
||||
"Implement Story 1.1 from docs/stories/epic1/story-1.1.md using the fullstack architecture at docs/fullstack-architecture.md. Follow the coding standards and use the defined tech stack."
|
||||
==================== END: templates#fullstack-architecture-tmpl ====================
|
||||
|
||||
==================== START: templates#market-research-tmpl ====================
|
||||
@@ -9120,7 +9080,18 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
|
||||
8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
|
||||
|
||||
## TODO: ADD MORE CONTENT ONCE STABLE ALPHA BUILD
|
||||
## IDE Development Workflow
|
||||
|
||||
1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
|
||||
2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
|
||||
3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
|
||||
4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
|
||||
5. Use a new chat window to allow the SM agent to `draft the next story`.
|
||||
6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
|
||||
7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
|
||||
8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
|
||||
|
||||
With this work flow, there is only 1 story in progress at a time, worked sequentially.
|
||||
==================== END: data#bmad-kb ====================
|
||||
|
||||
==================== START: data#technical-preferences ====================
|
||||
|
||||
@@ -1195,7 +1195,18 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
|
||||
8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
|
||||
|
||||
## TODO: ADD MORE CONTENT ONCE STABLE ALPHA BUILD
|
||||
## IDE Development Workflow
|
||||
|
||||
1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
|
||||
2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
|
||||
3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
|
||||
4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
|
||||
5. Use a new chat window to allow the SM agent to `draft the next story`.
|
||||
6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
|
||||
7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
|
||||
8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
|
||||
|
||||
With this work flow, there is only 1 story in progress at a time, worked sequentially.
|
||||
==================== END: data#bmad-kb ====================
|
||||
|
||||
==================== START: utils#workflow-management ====================
|
||||
|
||||
@@ -95,6 +95,7 @@ dependencies:
|
||||
templates:
|
||||
- prd-tmpl
|
||||
- brownfield-prd-tmpl
|
||||
- simple-project-prd-tmpl
|
||||
checklists:
|
||||
- pm-checklist
|
||||
- change-checklist
|
||||
@@ -1597,6 +1598,467 @@ so that {{benefit}}.
|
||||
<</REPEAT>>
|
||||
==================== END: templates#brownfield-prd-tmpl ====================
|
||||
|
||||
==================== START: templates#simple-project-prd-tmpl ====================
|
||||
# {{Project Name}} Product Requirements Document (PRD)
|
||||
|
||||
[[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
|
||||
|
||||
## Goals and Background Context
|
||||
|
||||
[[LLM: Populate the 2 child sections based on what we have received from user description or the provided brief. Allow user to review the 2 sections and offer changes before proceeding]]
|
||||
|
||||
### Goals
|
||||
|
||||
[[LLM: Bullet list of 1 line desired outcomes the PRD will deliver if successful - user and project desires]]
|
||||
|
||||
### Background Context
|
||||
|
||||
[[LLM: 1-2 short paragraphs summarizing the background context, such as what we learned in the brief without being redundant with the goals, what and why this solves a problem, what the current landscape or need is etc...]]
|
||||
|
||||
### Change Log
|
||||
|
||||
[[LLM: Track document versions and changes]]
|
||||
|
||||
| Date | Version | Description | Author |
|
||||
| :--- | :------ | :---------- | :----- |
|
||||
|
||||
## Requirements
|
||||
|
||||
[[LLM: Draft the list of functional and non functional requirements under the two child sections, and immediately execute tasks#advanced-elicitation display]]
|
||||
|
||||
### Functional
|
||||
|
||||
[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with FR`.]]
|
||||
@{example: - FR6: The Todo List uses AI to detect and warn against adding potentially duplicate todo items that are worded differently.}
|
||||
|
||||
### Non Functional
|
||||
|
||||
[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR`.]]
|
||||
@{example: - NFR1: AWS service usage **must** aim to stay within free-tier limits where feasible.}
|
||||
|
||||
^^CONDITION: has_ui^^
|
||||
|
||||
## User Interface Design Goals
|
||||
|
||||
[[LLM: Capture high-level UI/UX vision to inform story creation and also generate a prompt for Lovable or V0 if the user would like either. Steps:
|
||||
|
||||
1. Pre-fill all subsections with educated guesses based on project context
|
||||
2. Present the complete rendered section to user
|
||||
3. Clearly let the user know where assumptions were made
|
||||
4. Ask targeted questions for unclear/missing elements or areas needing more specification
|
||||
5. This is NOT detailed UI spec - focus on product vision and user goals
|
||||
6. After section completion, immediately apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### Overall UX Vision
|
||||
|
||||
### Key Interaction Paradigms
|
||||
|
||||
### Core Screens and Views
|
||||
|
||||
[[LLM: From a product perspective, what are the most critical screens or views necessary to deliver the the PRD values and goals? This is meant to be Conceptual High Level to Drive Rough Epic or User Stories]]
|
||||
|
||||
@{example}
|
||||
|
||||
- Login Screen
|
||||
- Main Dashboard
|
||||
- Item Detail Page
|
||||
- Settings Page
|
||||
@{/example}
|
||||
|
||||
### Accessibility: { None, WCAG, etc }
|
||||
|
||||
### Branding
|
||||
|
||||
[[LLM: Any known branding elements or style guides that must be incorporated?]]
|
||||
|
||||
@{example}
|
||||
|
||||
- Replicate the look and feel of early 1900s black and white cinema, including animated effects replicating film damage or projector glitches during page or state transitions.
|
||||
- Attached is the full color pallet and tokens for our corporate branding.
|
||||
@{/example}
|
||||
|
||||
### Target Device and Platforms
|
||||
|
||||
@{example}
|
||||
"Web Responsive, and all mobile platforms", "IPhone Only", "ASCII Windows Desktop"
|
||||
@{/example}
|
||||
|
||||
^^/CONDITION: has_ui^^
|
||||
|
||||
## Technical Assumptions
|
||||
|
||||
[[LLM: Gather technical decisions that will be used for this simple technical PRD that includes architecture decisions. Steps:
|
||||
|
||||
1. Check if `data#technical-preferences` file exists - use it to pre-populate choices
|
||||
2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
|
||||
3. For unknowns, offer guidance based on project goals and MVP scope
|
||||
4. Document ALL technical choices with rationale (why this choice fits the project)
|
||||
5. These become constraints for the Architect - be specific and complete
|
||||
6. After section completion, apply `tasks#advanced-elicitation` protocol.]]
|
||||
|
||||
### Repository Structure: { Monorepo, Polyrepo, etc...}
|
||||
|
||||
### Service Architecture
|
||||
|
||||
[[LLM: CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).]]
|
||||
|
||||
## Testing requirements
|
||||
|
||||
[[LLM: CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).]]
|
||||
|
||||
### Additional Technical Assumptions and Requests
|
||||
|
||||
[[LLM: Throughout the entire process of drafting this document, if any other technical assumptions are raised or discovered appropriate for the architect, add them here as additional bulleted items]]
|
||||
|
||||
## Data Models
|
||||
|
||||
[[LLM: Define the core data models/entities that will be used in the front end (if there is one), core application or back end, and if both, shared between frontend and backend:
|
||||
|
||||
1. Review PRD requirements and identify key business entities
|
||||
2. For each model, explain its purpose and relationships
|
||||
3. Include key attributes and data types
|
||||
4. Show relationships between models
|
||||
5. Create TypeScript interfaces that can be shared
|
||||
6. Discuss design decisions with user
|
||||
|
||||
Create a clear conceptual model before moving to database schema.
|
||||
|
||||
After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: data_model>>
|
||||
|
||||
### {{model_name}}
|
||||
|
||||
**Purpose:** {{model_purpose}}
|
||||
|
||||
**Key Attributes:**
|
||||
|
||||
- {{attribute_1}}: {{type_1}} - {{description_1}}
|
||||
- {{attribute_2}}: {{type_2}} - {{description_2}}
|
||||
|
||||
**TypeScript Interface:**
|
||||
|
||||
```typescript
|
||||
{
|
||||
{
|
||||
model_interface;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**Relationships:**
|
||||
|
||||
- {{relationship_1}}
|
||||
- {{relationship_2}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: data_model}
|
||||
|
||||
### User
|
||||
|
||||
**Purpose:** Represents authenticated users in the system
|
||||
|
||||
**Key Attributes:**
|
||||
|
||||
- id: string - Unique identifier
|
||||
- email: string - User's email address
|
||||
- name: string - Display name
|
||||
- role: enum - User permission level
|
||||
- timestamps: Date - Created and updated times
|
||||
|
||||
**TypeScript Interface:**
|
||||
|
||||
```typescript
|
||||
interface User {
|
||||
id: string;
|
||||
email: string;
|
||||
name: string;
|
||||
role: "admin" | "user" | "guest";
|
||||
createdAt: Date;
|
||||
updatedAt: Date;
|
||||
profile?: UserProfile;
|
||||
}
|
||||
|
||||
interface UserProfile {
|
||||
avatarUrl?: string;
|
||||
bio?: string;
|
||||
preferences: Record<string, any>;
|
||||
}
|
||||
```
|
||||
|
||||
**Relationships:**
|
||||
|
||||
- Has many Posts (1:n)
|
||||
- Has one Profile (1:1)
|
||||
@{/example}
|
||||
|
||||
## REST API Spec
|
||||
|
||||
[[LLM: Based on the chosen API style from Tech Stack:
|
||||
|
||||
1. If REST API, create an OpenAPI 3.0 specification
|
||||
2. If GraphQL, provide the GraphQL schema
|
||||
3. If tRPC, show router definitions
|
||||
4. Include all endpoints from epics/stories
|
||||
5. Define request/response schemas based on data models
|
||||
6. Document authentication requirements
|
||||
7. Include example requests/responses
|
||||
|
||||
Use appropriate format for the chosen API style. If no API (e.g., static site), skip this section.]]
|
||||
|
||||
^^CONDITION: has_rest_api^^
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.0
|
||||
info:
|
||||
title: { { api_title } }
|
||||
version: { { api_version } }
|
||||
description: { { api_description } }
|
||||
|
||||
servers:
|
||||
- url: { { api_base_url } }
|
||||
description: { { environment } }
|
||||
# ... OpenAPI specification continues
|
||||
```
|
||||
|
||||
^^/CONDITION: has_rest_api^^
|
||||
|
||||
^^CONDITION: has_graphql_api^^
|
||||
|
||||
```graphql
|
||||
# GraphQL Schema
|
||||
{{graphql_schema}}
|
||||
```
|
||||
|
||||
^^/CONDITION: has_graphql_api^^
|
||||
|
||||
^^CONDITION: has_trpc_api^^
|
||||
|
||||
```typescript
|
||||
// tRPC Router Definitions
|
||||
{
|
||||
{
|
||||
trpc_routers;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
^^/CONDITION: has_trpc_api^^
|
||||
|
||||
[[LLM: After presenting the API spec (or noting its absence if not applicable), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Components
|
||||
|
||||
[[LLM: Based on the architectural patterns, tech stack, and data models from above:
|
||||
|
||||
1. Identify major logical components/services across the fullstack
|
||||
2. Consider both frontend and backend components
|
||||
3. Define clear boundaries and interfaces between components
|
||||
4. For each component, specify:
|
||||
|
||||
- Primary responsibility
|
||||
- Key interfaces/APIs exposed
|
||||
- Dependencies on other components
|
||||
- Technology specifics based on tech stack choices
|
||||
|
||||
5. Create component diagrams where helpful
|
||||
6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: component>>
|
||||
|
||||
### {{component_name}}
|
||||
|
||||
**Responsibility:** {{component_description}}
|
||||
|
||||
**Key Interfaces:**
|
||||
|
||||
- {{interface_1}}
|
||||
- {{interface_2}}
|
||||
|
||||
**Dependencies:** {{dependencies}}
|
||||
|
||||
**Technology Stack:** {{component_tech_details}}
|
||||
<</REPEAT>>
|
||||
|
||||
### Component Diagrams
|
||||
|
||||
[[LLM: Create Mermaid diagrams to visualize component relationships. Options:
|
||||
|
||||
- C4 Container diagram for high-level view
|
||||
- Component diagram for detailed internal structure
|
||||
- Sequence diagrams for complex interactions
|
||||
Choose the most appropriate for clarity
|
||||
|
||||
After presenting the diagrams, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## External APIs
|
||||
|
||||
[[LLM: For each external service integration:
|
||||
|
||||
1. Identify APIs needed based on PRD requirements and component design
|
||||
2. If documentation URLs are unknown, ask user for specifics
|
||||
3. Document authentication methods and security considerations
|
||||
4. List specific endpoints that will be used
|
||||
5. Note any rate limits or usage constraints
|
||||
|
||||
If no external APIs are needed, state this explicitly and skip to next section.]]
|
||||
|
||||
^^CONDITION: has_external_apis^^
|
||||
|
||||
<<REPEAT: external_api>>
|
||||
|
||||
### {{api_name}} API
|
||||
|
||||
- **Purpose:** {{api_purpose}}
|
||||
- **Documentation:** {{api_docs_url}}
|
||||
- **Base URL(s):** {{api_base_url}}
|
||||
- **Authentication:** {{auth_method}}
|
||||
- **Rate Limits:** {{rate_limits}}
|
||||
|
||||
**Key Endpoints Used:**
|
||||
<<REPEAT: endpoint>>
|
||||
|
||||
- `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
|
||||
<</REPEAT>>
|
||||
|
||||
**Integration Notes:** {{integration_considerations}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: external_api}
|
||||
|
||||
### Stripe API
|
||||
|
||||
- **Purpose:** Payment processing and subscription management
|
||||
- **Documentation:** https://stripe.com/docs/api
|
||||
- **Base URL(s):** `https://api.stripe.com/v1`
|
||||
- **Authentication:** Bearer token with secret key
|
||||
- **Rate Limits:** 100 requests per second
|
||||
|
||||
**Key Endpoints Used:**
|
||||
|
||||
- `POST /customers` - Create customer profiles
|
||||
- `POST /payment_intents` - Process payments
|
||||
- `POST /subscriptions` - Manage subscriptions
|
||||
@{/example}
|
||||
|
||||
^^/CONDITION: has_external_apis^^
|
||||
|
||||
[[LLM: After presenting external APIs (or noting their absence), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Coding Standards
|
||||
|
||||
[[LLM: Define MINIMAL but CRITICAL standards for AI agents. Focus only on project-specific rules that prevent common mistakes. These will be used by dev agents.
|
||||
|
||||
After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### Critical Fullstack Rules
|
||||
|
||||
<<REPEAT: critical_rule>>
|
||||
|
||||
- **{{rule_name}}:** {{rule_description}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: critical_rules}
|
||||
|
||||
- **Type Sharing:** Always define types in packages/shared and import from there
|
||||
- **API Calls:** Never make direct HTTP calls - use the service layer
|
||||
- **Environment Variables:** Access only through config objects, never process.env directly
|
||||
- **Error Handling:** All API routes must use the standard error handler
|
||||
- **State Updates:** Never mutate state directly - use proper state management patterns
|
||||
@{/example}
|
||||
|
||||
### Naming Conventions
|
||||
|
||||
| Element | Frontend | Backend | Example |
|
||||
| :-------------- | :------------------- | :--------- | :------------------ |
|
||||
| Components | PascalCase | - | `UserProfile.tsx` |
|
||||
| Hooks | camelCase with 'use' | - | `useAuth.ts` |
|
||||
| API Routes | - | kebab-case | `/api/user-profile` |
|
||||
| Database Tables | - | snake_case | `user_profiles` |
|
||||
|
||||
## Epics
|
||||
|
||||
[[LLM: First, present a high-level list of all epics for user approval, the epic_list and immediately execute tasks#advanced-elicitation display. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.
|
||||
|
||||
CRITICAL: Epics MUST be logically sequential following agile best practices:
|
||||
|
||||
- Each epic should deliver a significant, end-to-end, fully deployable increment of testable functionality
|
||||
- Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page
|
||||
- Each subsequent epic builds upon previous epics' functionality delivering major blocks of functionality that provide tangible value to users or business when deployed
|
||||
- Not every project needs multiple epics, an epic needs to deliver value. For example, an API completed can deliver value even if a UI is not complete and planned for a separate epic.
|
||||
- Err on the side of less epics, but let the user know your rationale and offer options for splitting them if it seems some are too large or focused on disparate things.
|
||||
- Cross Cutting Concerns should flow through epics and stories and not be final stories. For example, adding a logging framework as a last story of an epic, or at the end of a project as a final epic or story would be terrible as we would not have logging from the beginning.]]
|
||||
|
||||
<<REPEAT: epic_list>>
|
||||
|
||||
- Epic{{epic_number}} {{epic_title}}: {{short_goal}}
|
||||
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: epic_list}
|
||||
|
||||
1. Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management
|
||||
2. Core Business Entities: Create and manage primary domain objects with CRUD operations
|
||||
3. User Workflows & Interactions: Enable key user journeys and business processes
|
||||
4. Reporting & Analytics: Provide insights and data visualization for users
|
||||
|
||||
@{/example}
|
||||
|
||||
[[LLM: After the epic list is approved, present each `epic_details` with all its stories and acceptance criteria as a complete review unit and immediately execute tasks#advanced-elicitation display, before moving on to the next epic.]]
|
||||
|
||||
<<REPEAT: epic_details>>
|
||||
|
||||
## Epic {{epic_number}} {{epic_title}}
|
||||
|
||||
{{epic_goal}} [[LLM: Expanded goal - 2-3 sentences describing the objective and value all the stories will achieve]]
|
||||
|
||||
[[LLM: CRITICAL STORY SEQUENCING REQUIREMENTS:
|
||||
|
||||
- Stories within each epic MUST be logically sequential
|
||||
- Each story should be a "vertical slice" delivering complete functionality
|
||||
- No story should depend on work from a later story or epic
|
||||
- Identify and note any direct prerequisite stories
|
||||
- Focus on "what" and "why" not "how" (leave technical implementation to Architect) yet be precise enough to support a logical sequential order of operations from story to story.
|
||||
- Ensure each story delivers clear user or business value, try to avoid enablers and build them into stories that deliver value.
|
||||
- Size stories for AI agent execution: Each story must be completable by a single AI agent in one focused session without context overflow
|
||||
- Think "junior developer working for 2-4 hours" - stories must be small, focused, and self-contained
|
||||
- If a story seems complex, break it down further as long as it can deliver a vertical slice
|
||||
- Each story should result in working, testable code before the agent's context window fills]]
|
||||
|
||||
<<REPEAT: story>>
|
||||
|
||||
### Story {{epic_number}}.{{story_number}} {{story_title}}
|
||||
|
||||
As a {{user_type}},
|
||||
I want {{action}},
|
||||
so that {{benefit}}.
|
||||
|
||||
#### Acceptance Criteria
|
||||
|
||||
[[LLM: Define clear, comprehensive, and testable acceptance criteria that:
|
||||
|
||||
- Precisely define what "done" means from a functional perspective
|
||||
- Are unambiguous and serve as basis for verification
|
||||
- Include any critical non-functional requirements from the PRD
|
||||
- Consider local testability for backend/data components
|
||||
- Specify UI/UX requirements and framework adherence where applicable
|
||||
- Avoid cross-cutting concerns that should be in other stories or PRD sections]]
|
||||
|
||||
<<REPEAT: criteria>>
|
||||
|
||||
- {{criterion number}}: {{criteria}}
|
||||
|
||||
<</REPEAT>>
|
||||
<</REPEAT>>
|
||||
<</REPEAT>>
|
||||
|
||||
## Next Steps
|
||||
|
||||
### Design Architect Prompt
|
||||
|
||||
[[LLM: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input.]]
|
||||
==================== END: templates#simple-project-prd-tmpl ====================
|
||||
|
||||
==================== START: checklists#pm-checklist ====================
|
||||
# Product Manager (PM) Requirements Checklist
|
||||
|
||||
|
||||
@@ -45,50 +45,44 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
|
||||
|
||||
```yml
|
||||
activation-instructions:
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
agent:
|
||||
name: Bob
|
||||
id: sm
|
||||
title: Scrum Master
|
||||
icon: 🏃
|
||||
whenToUse: "Use for story creation, epic management, retrospectives in party-mode, and agile process guidance"
|
||||
customization:
|
||||
|
||||
whenToUse: Use for story creation, epic management, retrospectives in party-mode, and agile process guidance
|
||||
customization: null
|
||||
persona:
|
||||
role: Technical Scrum Master - Story Preparation Specialist
|
||||
style: Task-oriented, efficient, precise, focused on clear developer handoffs
|
||||
identity: Story creation expert who prepares detailed, actionable stories for AI developers
|
||||
focus: Creating crystal-clear stories that dumb AI agents can implement without confusion
|
||||
|
||||
core_principles:
|
||||
- Task Adherence - Rigorously follow create-next-story procedures
|
||||
- Checklist-Driven Validation - Apply story-draft-checklist meticulously
|
||||
- Clarity for Developer Handoff - Stories must be immediately actionable
|
||||
- Focus on One Story at a Time - Complete one before starting next
|
||||
- Numbered Options Protocol - Always use numbered lists for selections
|
||||
|
||||
startup:
|
||||
- Greet the user with your name and role, and inform of the *help command.
|
||||
- CRITICAL: Do NOT automatically execute create-next-story tasks during startup
|
||||
- CRITICAL: Do NOT create or modify any files during startup
|
||||
- Offer to help with story preparation but wait for explicit user confirmation
|
||||
- Only execute tasks when user explicitly requests them
|
||||
- CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Dev Agent
|
||||
|
||||
- 'CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Dev Agent'
|
||||
commands:
|
||||
- "*help" - Show: numbered list of the following commands to allow selection
|
||||
- "*chat-mode" - Conversational mode with advanced-elicitation for advice
|
||||
- "*create" - Execute all steps in Create Next Story Task document
|
||||
- "*pivot" - Run correct-course task (ensure no story already created first)
|
||||
- "*checklist {checklist}" - Show numbered list of checklists, execute selection
|
||||
- "*doc-shard {PRD|Architecture|Other}" - Execute shard-doc task
|
||||
- "*index-docs" - Update documentation index in /docs/index.md
|
||||
- "*exit" - Say goodbye as the Scrum Master, and then abandon inhabiting this persona
|
||||
|
||||
- '*help" - Show: numbered list of the following commands to allow selection'
|
||||
- '*chat-mode" - Conversational mode with advanced-elicitation for advice'
|
||||
- '*create" - Execute all steps in Create Next Story Task document'
|
||||
- '*pivot" - Run correct-course task (ensure no story already created first)'
|
||||
- '*checklist {checklist}" - Show numbered list of checklists, execute selection'
|
||||
- '*doc-shard {PRD|Architecture|Other}" - Execute shard-doc task'
|
||||
- '*index-docs" - Update documentation index in /docs/index.md'
|
||||
- '*exit" - Say goodbye as the Scrum Master, and then abandon inhabiting this persona'
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-next-story
|
||||
|
||||
@@ -408,6 +408,7 @@ dependencies:
|
||||
templates:
|
||||
- prd-tmpl
|
||||
- brownfield-prd-tmpl
|
||||
- simple-project-prd-tmpl
|
||||
checklists:
|
||||
- pm-checklist
|
||||
- change-checklist
|
||||
@@ -543,50 +544,44 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
|
||||
|
||||
```yml
|
||||
activation-instructions:
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
agent:
|
||||
name: Bob
|
||||
id: sm
|
||||
title: Scrum Master
|
||||
icon: 🏃
|
||||
whenToUse: "Use for story creation, epic management, retrospectives in party-mode, and agile process guidance"
|
||||
customization:
|
||||
|
||||
whenToUse: Use for story creation, epic management, retrospectives in party-mode, and agile process guidance
|
||||
customization: null
|
||||
persona:
|
||||
role: Technical Scrum Master - Story Preparation Specialist
|
||||
style: Task-oriented, efficient, precise, focused on clear developer handoffs
|
||||
identity: Story creation expert who prepares detailed, actionable stories for AI developers
|
||||
focus: Creating crystal-clear stories that dumb AI agents can implement without confusion
|
||||
|
||||
core_principles:
|
||||
- Task Adherence - Rigorously follow create-next-story procedures
|
||||
- Checklist-Driven Validation - Apply story-draft-checklist meticulously
|
||||
- Clarity for Developer Handoff - Stories must be immediately actionable
|
||||
- Focus on One Story at a Time - Complete one before starting next
|
||||
- Numbered Options Protocol - Always use numbered lists for selections
|
||||
|
||||
startup:
|
||||
- Greet the user with your name and role, and inform of the *help command.
|
||||
- CRITICAL: Do NOT automatically execute create-next-story tasks during startup
|
||||
- CRITICAL: Do NOT create or modify any files during startup
|
||||
- Offer to help with story preparation but wait for explicit user confirmation
|
||||
- Only execute tasks when user explicitly requests them
|
||||
- CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Dev Agent
|
||||
|
||||
- 'CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Dev Agent'
|
||||
commands:
|
||||
- "*help" - Show: numbered list of the following commands to allow selection
|
||||
- "*chat-mode" - Conversational mode with advanced-elicitation for advice
|
||||
- "*create" - Execute all steps in Create Next Story Task document
|
||||
- "*pivot" - Run correct-course task (ensure no story already created first)
|
||||
- "*checklist {checklist}" - Show numbered list of checklists, execute selection
|
||||
- "*doc-shard {PRD|Architecture|Other}" - Execute shard-doc task
|
||||
- "*index-docs" - Update documentation index in /docs/index.md
|
||||
- "*exit" - Say goodbye as the Scrum Master, and then abandon inhabiting this persona
|
||||
|
||||
- '*help" - Show: numbered list of the following commands to allow selection'
|
||||
- '*chat-mode" - Conversational mode with advanced-elicitation for advice'
|
||||
- '*create" - Execute all steps in Create Next Story Task document'
|
||||
- '*pivot" - Run correct-course task (ensure no story already created first)'
|
||||
- '*checklist {checklist}" - Show numbered list of checklists, execute selection'
|
||||
- '*doc-shard {PRD|Architecture|Other}" - Execute shard-doc task'
|
||||
- '*index-docs" - Update documentation index in /docs/index.md'
|
||||
- '*exit" - Say goodbye as the Scrum Master, and then abandon inhabiting this persona'
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-next-story
|
||||
@@ -1742,7 +1737,18 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
|
||||
8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
|
||||
|
||||
## TODO: ADD MORE CONTENT ONCE STABLE ALPHA BUILD
|
||||
## IDE Development Workflow
|
||||
|
||||
1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
|
||||
2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
|
||||
3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
|
||||
4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
|
||||
5. Use a new chat window to allow the SM agent to `draft the next story`.
|
||||
6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
|
||||
7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
|
||||
8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
|
||||
|
||||
With this work flow, there is only 1 story in progress at a time, worked sequentially.
|
||||
==================== END: data#bmad-kb ====================
|
||||
|
||||
==================== START: utils#workflow-management ====================
|
||||
@@ -5386,38 +5392,6 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
## Checklist Results Report
|
||||
|
||||
[[LLM: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the `architect-checklist` and populate results here.]]
|
||||
|
||||
## Next Steps
|
||||
|
||||
[[LLM: Provide specific next steps for implementation.]]
|
||||
|
||||
### Implementation Order
|
||||
|
||||
1. **Environment Setup**
|
||||
|
||||
- Initialize monorepo structure
|
||||
- Configure development environment
|
||||
- Set up version control
|
||||
|
||||
2. **Foundation (Epic 1)**
|
||||
|
||||
- Implement authentication flow
|
||||
- Set up database schema
|
||||
- Create basic API structure
|
||||
- Implement core UI components
|
||||
|
||||
3. **Feature Development**
|
||||
- Follow story sequence from PRD
|
||||
- Maintain type safety across stack
|
||||
- Write tests as you go
|
||||
|
||||
### Developer Handoff Prompts
|
||||
|
||||
**For Scrum Master:**
|
||||
"Create stories for {{Project Name}} using the PRD at docs/prd.md and this fullstack architecture at docs/fullstack-architecture.md. Focus on Epic 1 implementation."
|
||||
|
||||
**For Developer:**
|
||||
"Implement Story 1.1 from docs/stories/epic1/story-1.1.md using the fullstack architecture at docs/fullstack-architecture.md. Follow the coding standards and use the defined tech stack."
|
||||
==================== END: templates#fullstack-architecture-tmpl ====================
|
||||
|
||||
==================== START: templates#brownfield-architecture-tmpl ====================
|
||||
@@ -7532,6 +7506,467 @@ so that {{benefit}}.
|
||||
<</REPEAT>>
|
||||
==================== END: templates#brownfield-prd-tmpl ====================
|
||||
|
||||
==================== START: templates#simple-project-prd-tmpl ====================
|
||||
# {{Project Name}} Product Requirements Document (PRD)
|
||||
|
||||
[[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
|
||||
|
||||
## Goals and Background Context
|
||||
|
||||
[[LLM: Populate the 2 child sections based on what we have received from user description or the provided brief. Allow user to review the 2 sections and offer changes before proceeding]]
|
||||
|
||||
### Goals
|
||||
|
||||
[[LLM: Bullet list of 1 line desired outcomes the PRD will deliver if successful - user and project desires]]
|
||||
|
||||
### Background Context
|
||||
|
||||
[[LLM: 1-2 short paragraphs summarizing the background context, such as what we learned in the brief without being redundant with the goals, what and why this solves a problem, what the current landscape or need is etc...]]
|
||||
|
||||
### Change Log
|
||||
|
||||
[[LLM: Track document versions and changes]]
|
||||
|
||||
| Date | Version | Description | Author |
|
||||
| :--- | :------ | :---------- | :----- |
|
||||
|
||||
## Requirements
|
||||
|
||||
[[LLM: Draft the list of functional and non functional requirements under the two child sections, and immediately execute tasks#advanced-elicitation display]]
|
||||
|
||||
### Functional
|
||||
|
||||
[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with FR`.]]
|
||||
@{example: - FR6: The Todo List uses AI to detect and warn against adding potentially duplicate todo items that are worded differently.}
|
||||
|
||||
### Non Functional
|
||||
|
||||
[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR`.]]
|
||||
@{example: - NFR1: AWS service usage **must** aim to stay within free-tier limits where feasible.}
|
||||
|
||||
^^CONDITION: has_ui^^
|
||||
|
||||
## User Interface Design Goals
|
||||
|
||||
[[LLM: Capture high-level UI/UX vision to inform story creation and also generate a prompt for Lovable or V0 if the user would like either. Steps:
|
||||
|
||||
1. Pre-fill all subsections with educated guesses based on project context
|
||||
2. Present the complete rendered section to user
|
||||
3. Clearly let the user know where assumptions were made
|
||||
4. Ask targeted questions for unclear/missing elements or areas needing more specification
|
||||
5. This is NOT detailed UI spec - focus on product vision and user goals
|
||||
6. After section completion, immediately apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### Overall UX Vision
|
||||
|
||||
### Key Interaction Paradigms
|
||||
|
||||
### Core Screens and Views
|
||||
|
||||
[[LLM: From a product perspective, what are the most critical screens or views necessary to deliver the the PRD values and goals? This is meant to be Conceptual High Level to Drive Rough Epic or User Stories]]
|
||||
|
||||
@{example}
|
||||
|
||||
- Login Screen
|
||||
- Main Dashboard
|
||||
- Item Detail Page
|
||||
- Settings Page
|
||||
@{/example}
|
||||
|
||||
### Accessibility: { None, WCAG, etc }
|
||||
|
||||
### Branding
|
||||
|
||||
[[LLM: Any known branding elements or style guides that must be incorporated?]]
|
||||
|
||||
@{example}
|
||||
|
||||
- Replicate the look and feel of early 1900s black and white cinema, including animated effects replicating film damage or projector glitches during page or state transitions.
|
||||
- Attached is the full color pallet and tokens for our corporate branding.
|
||||
@{/example}
|
||||
|
||||
### Target Device and Platforms
|
||||
|
||||
@{example}
|
||||
"Web Responsive, and all mobile platforms", "IPhone Only", "ASCII Windows Desktop"
|
||||
@{/example}
|
||||
|
||||
^^/CONDITION: has_ui^^
|
||||
|
||||
## Technical Assumptions
|
||||
|
||||
[[LLM: Gather technical decisions that will be used for this simple technical PRD that includes architecture decisions. Steps:
|
||||
|
||||
1. Check if `data#technical-preferences` file exists - use it to pre-populate choices
|
||||
2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
|
||||
3. For unknowns, offer guidance based on project goals and MVP scope
|
||||
4. Document ALL technical choices with rationale (why this choice fits the project)
|
||||
5. These become constraints for the Architect - be specific and complete
|
||||
6. After section completion, apply `tasks#advanced-elicitation` protocol.]]
|
||||
|
||||
### Repository Structure: { Monorepo, Polyrepo, etc...}
|
||||
|
||||
### Service Architecture
|
||||
|
||||
[[LLM: CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).]]
|
||||
|
||||
## Testing requirements
|
||||
|
||||
[[LLM: CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).]]
|
||||
|
||||
### Additional Technical Assumptions and Requests
|
||||
|
||||
[[LLM: Throughout the entire process of drafting this document, if any other technical assumptions are raised or discovered appropriate for the architect, add them here as additional bulleted items]]
|
||||
|
||||
## Data Models
|
||||
|
||||
[[LLM: Define the core data models/entities that will be used in the front end (if there is one), core application or back end, and if both, shared between frontend and backend:
|
||||
|
||||
1. Review PRD requirements and identify key business entities
|
||||
2. For each model, explain its purpose and relationships
|
||||
3. Include key attributes and data types
|
||||
4. Show relationships between models
|
||||
5. Create TypeScript interfaces that can be shared
|
||||
6. Discuss design decisions with user
|
||||
|
||||
Create a clear conceptual model before moving to database schema.
|
||||
|
||||
After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: data_model>>
|
||||
|
||||
### {{model_name}}
|
||||
|
||||
**Purpose:** {{model_purpose}}
|
||||
|
||||
**Key Attributes:**
|
||||
|
||||
- {{attribute_1}}: {{type_1}} - {{description_1}}
|
||||
- {{attribute_2}}: {{type_2}} - {{description_2}}
|
||||
|
||||
**TypeScript Interface:**
|
||||
|
||||
```typescript
|
||||
{
|
||||
{
|
||||
model_interface;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**Relationships:**
|
||||
|
||||
- {{relationship_1}}
|
||||
- {{relationship_2}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: data_model}
|
||||
|
||||
### User
|
||||
|
||||
**Purpose:** Represents authenticated users in the system
|
||||
|
||||
**Key Attributes:**
|
||||
|
||||
- id: string - Unique identifier
|
||||
- email: string - User's email address
|
||||
- name: string - Display name
|
||||
- role: enum - User permission level
|
||||
- timestamps: Date - Created and updated times
|
||||
|
||||
**TypeScript Interface:**
|
||||
|
||||
```typescript
|
||||
interface User {
|
||||
id: string;
|
||||
email: string;
|
||||
name: string;
|
||||
role: "admin" | "user" | "guest";
|
||||
createdAt: Date;
|
||||
updatedAt: Date;
|
||||
profile?: UserProfile;
|
||||
}
|
||||
|
||||
interface UserProfile {
|
||||
avatarUrl?: string;
|
||||
bio?: string;
|
||||
preferences: Record<string, any>;
|
||||
}
|
||||
```
|
||||
|
||||
**Relationships:**
|
||||
|
||||
- Has many Posts (1:n)
|
||||
- Has one Profile (1:1)
|
||||
@{/example}
|
||||
|
||||
## REST API Spec
|
||||
|
||||
[[LLM: Based on the chosen API style from Tech Stack:
|
||||
|
||||
1. If REST API, create an OpenAPI 3.0 specification
|
||||
2. If GraphQL, provide the GraphQL schema
|
||||
3. If tRPC, show router definitions
|
||||
4. Include all endpoints from epics/stories
|
||||
5. Define request/response schemas based on data models
|
||||
6. Document authentication requirements
|
||||
7. Include example requests/responses
|
||||
|
||||
Use appropriate format for the chosen API style. If no API (e.g., static site), skip this section.]]
|
||||
|
||||
^^CONDITION: has_rest_api^^
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.0
|
||||
info:
|
||||
title: { { api_title } }
|
||||
version: { { api_version } }
|
||||
description: { { api_description } }
|
||||
|
||||
servers:
|
||||
- url: { { api_base_url } }
|
||||
description: { { environment } }
|
||||
# ... OpenAPI specification continues
|
||||
```
|
||||
|
||||
^^/CONDITION: has_rest_api^^
|
||||
|
||||
^^CONDITION: has_graphql_api^^
|
||||
|
||||
```graphql
|
||||
# GraphQL Schema
|
||||
{{graphql_schema}}
|
||||
```
|
||||
|
||||
^^/CONDITION: has_graphql_api^^
|
||||
|
||||
^^CONDITION: has_trpc_api^^
|
||||
|
||||
```typescript
|
||||
// tRPC Router Definitions
|
||||
{
|
||||
{
|
||||
trpc_routers;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
^^/CONDITION: has_trpc_api^^
|
||||
|
||||
[[LLM: After presenting the API spec (or noting its absence if not applicable), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Components
|
||||
|
||||
[[LLM: Based on the architectural patterns, tech stack, and data models from above:
|
||||
|
||||
1. Identify major logical components/services across the fullstack
|
||||
2. Consider both frontend and backend components
|
||||
3. Define clear boundaries and interfaces between components
|
||||
4. For each component, specify:
|
||||
|
||||
- Primary responsibility
|
||||
- Key interfaces/APIs exposed
|
||||
- Dependencies on other components
|
||||
- Technology specifics based on tech stack choices
|
||||
|
||||
5. Create component diagrams where helpful
|
||||
6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: component>>
|
||||
|
||||
### {{component_name}}
|
||||
|
||||
**Responsibility:** {{component_description}}
|
||||
|
||||
**Key Interfaces:**
|
||||
|
||||
- {{interface_1}}
|
||||
- {{interface_2}}
|
||||
|
||||
**Dependencies:** {{dependencies}}
|
||||
|
||||
**Technology Stack:** {{component_tech_details}}
|
||||
<</REPEAT>>
|
||||
|
||||
### Component Diagrams
|
||||
|
||||
[[LLM: Create Mermaid diagrams to visualize component relationships. Options:
|
||||
|
||||
- C4 Container diagram for high-level view
|
||||
- Component diagram for detailed internal structure
|
||||
- Sequence diagrams for complex interactions
|
||||
Choose the most appropriate for clarity
|
||||
|
||||
After presenting the diagrams, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## External APIs
|
||||
|
||||
[[LLM: For each external service integration:
|
||||
|
||||
1. Identify APIs needed based on PRD requirements and component design
|
||||
2. If documentation URLs are unknown, ask user for specifics
|
||||
3. Document authentication methods and security considerations
|
||||
4. List specific endpoints that will be used
|
||||
5. Note any rate limits or usage constraints
|
||||
|
||||
If no external APIs are needed, state this explicitly and skip to next section.]]
|
||||
|
||||
^^CONDITION: has_external_apis^^
|
||||
|
||||
<<REPEAT: external_api>>
|
||||
|
||||
### {{api_name}} API
|
||||
|
||||
- **Purpose:** {{api_purpose}}
|
||||
- **Documentation:** {{api_docs_url}}
|
||||
- **Base URL(s):** {{api_base_url}}
|
||||
- **Authentication:** {{auth_method}}
|
||||
- **Rate Limits:** {{rate_limits}}
|
||||
|
||||
**Key Endpoints Used:**
|
||||
<<REPEAT: endpoint>>
|
||||
|
||||
- `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
|
||||
<</REPEAT>>
|
||||
|
||||
**Integration Notes:** {{integration_considerations}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: external_api}
|
||||
|
||||
### Stripe API
|
||||
|
||||
- **Purpose:** Payment processing and subscription management
|
||||
- **Documentation:** https://stripe.com/docs/api
|
||||
- **Base URL(s):** `https://api.stripe.com/v1`
|
||||
- **Authentication:** Bearer token with secret key
|
||||
- **Rate Limits:** 100 requests per second
|
||||
|
||||
**Key Endpoints Used:**
|
||||
|
||||
- `POST /customers` - Create customer profiles
|
||||
- `POST /payment_intents` - Process payments
|
||||
- `POST /subscriptions` - Manage subscriptions
|
||||
@{/example}
|
||||
|
||||
^^/CONDITION: has_external_apis^^
|
||||
|
||||
[[LLM: After presenting external APIs (or noting their absence), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Coding Standards
|
||||
|
||||
[[LLM: Define MINIMAL but CRITICAL standards for AI agents. Focus only on project-specific rules that prevent common mistakes. These will be used by dev agents.
|
||||
|
||||
After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### Critical Fullstack Rules
|
||||
|
||||
<<REPEAT: critical_rule>>
|
||||
|
||||
- **{{rule_name}}:** {{rule_description}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: critical_rules}
|
||||
|
||||
- **Type Sharing:** Always define types in packages/shared and import from there
|
||||
- **API Calls:** Never make direct HTTP calls - use the service layer
|
||||
- **Environment Variables:** Access only through config objects, never process.env directly
|
||||
- **Error Handling:** All API routes must use the standard error handler
|
||||
- **State Updates:** Never mutate state directly - use proper state management patterns
|
||||
@{/example}
|
||||
|
||||
### Naming Conventions
|
||||
|
||||
| Element | Frontend | Backend | Example |
|
||||
| :-------------- | :------------------- | :--------- | :------------------ |
|
||||
| Components | PascalCase | - | `UserProfile.tsx` |
|
||||
| Hooks | camelCase with 'use' | - | `useAuth.ts` |
|
||||
| API Routes | - | kebab-case | `/api/user-profile` |
|
||||
| Database Tables | - | snake_case | `user_profiles` |
|
||||
|
||||
## Epics
|
||||
|
||||
[[LLM: First, present a high-level list of all epics for user approval, the epic_list and immediately execute tasks#advanced-elicitation display. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.
|
||||
|
||||
CRITICAL: Epics MUST be logically sequential following agile best practices:
|
||||
|
||||
- Each epic should deliver a significant, end-to-end, fully deployable increment of testable functionality
|
||||
- Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page
|
||||
- Each subsequent epic builds upon previous epics' functionality delivering major blocks of functionality that provide tangible value to users or business when deployed
|
||||
- Not every project needs multiple epics, an epic needs to deliver value. For example, an API completed can deliver value even if a UI is not complete and planned for a separate epic.
|
||||
- Err on the side of less epics, but let the user know your rationale and offer options for splitting them if it seems some are too large or focused on disparate things.
|
||||
- Cross Cutting Concerns should flow through epics and stories and not be final stories. For example, adding a logging framework as a last story of an epic, or at the end of a project as a final epic or story would be terrible as we would not have logging from the beginning.]]
|
||||
|
||||
<<REPEAT: epic_list>>
|
||||
|
||||
- Epic{{epic_number}} {{epic_title}}: {{short_goal}}
|
||||
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: epic_list}
|
||||
|
||||
1. Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management
|
||||
2. Core Business Entities: Create and manage primary domain objects with CRUD operations
|
||||
3. User Workflows & Interactions: Enable key user journeys and business processes
|
||||
4. Reporting & Analytics: Provide insights and data visualization for users
|
||||
|
||||
@{/example}
|
||||
|
||||
[[LLM: After the epic list is approved, present each `epic_details` with all its stories and acceptance criteria as a complete review unit and immediately execute tasks#advanced-elicitation display, before moving on to the next epic.]]
|
||||
|
||||
<<REPEAT: epic_details>>
|
||||
|
||||
## Epic {{epic_number}} {{epic_title}}
|
||||
|
||||
{{epic_goal}} [[LLM: Expanded goal - 2-3 sentences describing the objective and value all the stories will achieve]]
|
||||
|
||||
[[LLM: CRITICAL STORY SEQUENCING REQUIREMENTS:
|
||||
|
||||
- Stories within each epic MUST be logically sequential
|
||||
- Each story should be a "vertical slice" delivering complete functionality
|
||||
- No story should depend on work from a later story or epic
|
||||
- Identify and note any direct prerequisite stories
|
||||
- Focus on "what" and "why" not "how" (leave technical implementation to Architect) yet be precise enough to support a logical sequential order of operations from story to story.
|
||||
- Ensure each story delivers clear user or business value, try to avoid enablers and build them into stories that deliver value.
|
||||
- Size stories for AI agent execution: Each story must be completable by a single AI agent in one focused session without context overflow
|
||||
- Think "junior developer working for 2-4 hours" - stories must be small, focused, and self-contained
|
||||
- If a story seems complex, break it down further as long as it can deliver a vertical slice
|
||||
- Each story should result in working, testable code before the agent's context window fills]]
|
||||
|
||||
<<REPEAT: story>>
|
||||
|
||||
### Story {{epic_number}}.{{story_number}} {{story_title}}
|
||||
|
||||
As a {{user_type}},
|
||||
I want {{action}},
|
||||
so that {{benefit}}.
|
||||
|
||||
#### Acceptance Criteria
|
||||
|
||||
[[LLM: Define clear, comprehensive, and testable acceptance criteria that:
|
||||
|
||||
- Precisely define what "done" means from a functional perspective
|
||||
- Are unambiguous and serve as basis for verification
|
||||
- Include any critical non-functional requirements from the PRD
|
||||
- Consider local testability for backend/data components
|
||||
- Specify UI/UX requirements and framework adherence where applicable
|
||||
- Avoid cross-cutting concerns that should be in other stories or PRD sections]]
|
||||
|
||||
<<REPEAT: criteria>>
|
||||
|
||||
- {{criterion number}}: {{criteria}}
|
||||
|
||||
<</REPEAT>>
|
||||
<</REPEAT>>
|
||||
<</REPEAT>>
|
||||
|
||||
## Next Steps
|
||||
|
||||
### Design Architect Prompt
|
||||
|
||||
[[LLM: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input.]]
|
||||
==================== END: templates#simple-project-prd-tmpl ====================
|
||||
|
||||
==================== START: checklists#pm-checklist ====================
|
||||
# Product Manager (PM) Requirements Checklist
|
||||
|
||||
@@ -9909,10 +10344,10 @@ workflow:
|
||||
notes: "Creates focused project brief for simple project. SAVE OUTPUT: Copy final project-brief.md to your project's docs/ folder."
|
||||
|
||||
- agent: pm
|
||||
creates: simple_epic OR single_story
|
||||
uses: create-epic OR create-story
|
||||
creates: simple-project-prd.md
|
||||
uses: create doc simple-project-prd OR create-epic OR create-story
|
||||
requires: project-brief.md
|
||||
notes: "Create simple epic or story instead of full PRD for rapid development. Choose based on scope."
|
||||
notes: "Create simple prd, simple epic or story instead of full PRD for rapid development. Choose based on scope."
|
||||
|
||||
- workflow_end:
|
||||
action: move_to_ide
|
||||
|
||||
@@ -276,6 +276,7 @@ dependencies:
|
||||
templates:
|
||||
- prd-tmpl
|
||||
- brownfield-prd-tmpl
|
||||
- simple-project-prd-tmpl
|
||||
checklists:
|
||||
- pm-checklist
|
||||
- change-checklist
|
||||
@@ -1560,7 +1561,18 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
|
||||
8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
|
||||
|
||||
## TODO: ADD MORE CONTENT ONCE STABLE ALPHA BUILD
|
||||
## IDE Development Workflow
|
||||
|
||||
1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
|
||||
2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
|
||||
3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
|
||||
4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
|
||||
5. Use a new chat window to allow the SM agent to `draft the next story`.
|
||||
6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
|
||||
7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
|
||||
8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
|
||||
|
||||
With this work flow, there is only 1 story in progress at a time, worked sequentially.
|
||||
==================== END: data#bmad-kb ====================
|
||||
|
||||
==================== START: utils#workflow-management ====================
|
||||
@@ -4262,6 +4274,467 @@ so that {{benefit}}.
|
||||
<</REPEAT>>
|
||||
==================== END: templates#brownfield-prd-tmpl ====================
|
||||
|
||||
==================== START: templates#simple-project-prd-tmpl ====================
|
||||
# {{Project Name}} Product Requirements Document (PRD)
|
||||
|
||||
[[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
|
||||
|
||||
## Goals and Background Context
|
||||
|
||||
[[LLM: Populate the 2 child sections based on what we have received from user description or the provided brief. Allow user to review the 2 sections and offer changes before proceeding]]
|
||||
|
||||
### Goals
|
||||
|
||||
[[LLM: Bullet list of 1 line desired outcomes the PRD will deliver if successful - user and project desires]]
|
||||
|
||||
### Background Context
|
||||
|
||||
[[LLM: 1-2 short paragraphs summarizing the background context, such as what we learned in the brief without being redundant with the goals, what and why this solves a problem, what the current landscape or need is etc...]]
|
||||
|
||||
### Change Log
|
||||
|
||||
[[LLM: Track document versions and changes]]
|
||||
|
||||
| Date | Version | Description | Author |
|
||||
| :--- | :------ | :---------- | :----- |
|
||||
|
||||
## Requirements
|
||||
|
||||
[[LLM: Draft the list of functional and non functional requirements under the two child sections, and immediately execute tasks#advanced-elicitation display]]
|
||||
|
||||
### Functional
|
||||
|
||||
[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with FR`.]]
|
||||
@{example: - FR6: The Todo List uses AI to detect and warn against adding potentially duplicate todo items that are worded differently.}
|
||||
|
||||
### Non Functional
|
||||
|
||||
[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR`.]]
|
||||
@{example: - NFR1: AWS service usage **must** aim to stay within free-tier limits where feasible.}
|
||||
|
||||
^^CONDITION: has_ui^^
|
||||
|
||||
## User Interface Design Goals
|
||||
|
||||
[[LLM: Capture high-level UI/UX vision to inform story creation and also generate a prompt for Lovable or V0 if the user would like either. Steps:
|
||||
|
||||
1. Pre-fill all subsections with educated guesses based on project context
|
||||
2. Present the complete rendered section to user
|
||||
3. Clearly let the user know where assumptions were made
|
||||
4. Ask targeted questions for unclear/missing elements or areas needing more specification
|
||||
5. This is NOT detailed UI spec - focus on product vision and user goals
|
||||
6. After section completion, immediately apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### Overall UX Vision
|
||||
|
||||
### Key Interaction Paradigms
|
||||
|
||||
### Core Screens and Views
|
||||
|
||||
[[LLM: From a product perspective, what are the most critical screens or views necessary to deliver the the PRD values and goals? This is meant to be Conceptual High Level to Drive Rough Epic or User Stories]]
|
||||
|
||||
@{example}
|
||||
|
||||
- Login Screen
|
||||
- Main Dashboard
|
||||
- Item Detail Page
|
||||
- Settings Page
|
||||
@{/example}
|
||||
|
||||
### Accessibility: { None, WCAG, etc }
|
||||
|
||||
### Branding
|
||||
|
||||
[[LLM: Any known branding elements or style guides that must be incorporated?]]
|
||||
|
||||
@{example}
|
||||
|
||||
- Replicate the look and feel of early 1900s black and white cinema, including animated effects replicating film damage or projector glitches during page or state transitions.
|
||||
- Attached is the full color pallet and tokens for our corporate branding.
|
||||
@{/example}
|
||||
|
||||
### Target Device and Platforms
|
||||
|
||||
@{example}
|
||||
"Web Responsive, and all mobile platforms", "IPhone Only", "ASCII Windows Desktop"
|
||||
@{/example}
|
||||
|
||||
^^/CONDITION: has_ui^^
|
||||
|
||||
## Technical Assumptions
|
||||
|
||||
[[LLM: Gather technical decisions that will be used for this simple technical PRD that includes architecture decisions. Steps:
|
||||
|
||||
1. Check if `data#technical-preferences` file exists - use it to pre-populate choices
|
||||
2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
|
||||
3. For unknowns, offer guidance based on project goals and MVP scope
|
||||
4. Document ALL technical choices with rationale (why this choice fits the project)
|
||||
5. These become constraints for the Architect - be specific and complete
|
||||
6. After section completion, apply `tasks#advanced-elicitation` protocol.]]
|
||||
|
||||
### Repository Structure: { Monorepo, Polyrepo, etc...}
|
||||
|
||||
### Service Architecture
|
||||
|
||||
[[LLM: CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).]]
|
||||
|
||||
## Testing requirements
|
||||
|
||||
[[LLM: CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).]]
|
||||
|
||||
### Additional Technical Assumptions and Requests
|
||||
|
||||
[[LLM: Throughout the entire process of drafting this document, if any other technical assumptions are raised or discovered appropriate for the architect, add them here as additional bulleted items]]
|
||||
|
||||
## Data Models
|
||||
|
||||
[[LLM: Define the core data models/entities that will be used in the front end (if there is one), core application or back end, and if both, shared between frontend and backend:
|
||||
|
||||
1. Review PRD requirements and identify key business entities
|
||||
2. For each model, explain its purpose and relationships
|
||||
3. Include key attributes and data types
|
||||
4. Show relationships between models
|
||||
5. Create TypeScript interfaces that can be shared
|
||||
6. Discuss design decisions with user
|
||||
|
||||
Create a clear conceptual model before moving to database schema.
|
||||
|
||||
After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: data_model>>
|
||||
|
||||
### {{model_name}}
|
||||
|
||||
**Purpose:** {{model_purpose}}
|
||||
|
||||
**Key Attributes:**
|
||||
|
||||
- {{attribute_1}}: {{type_1}} - {{description_1}}
|
||||
- {{attribute_2}}: {{type_2}} - {{description_2}}
|
||||
|
||||
**TypeScript Interface:**
|
||||
|
||||
```typescript
|
||||
{
|
||||
{
|
||||
model_interface;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**Relationships:**
|
||||
|
||||
- {{relationship_1}}
|
||||
- {{relationship_2}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: data_model}
|
||||
|
||||
### User
|
||||
|
||||
**Purpose:** Represents authenticated users in the system
|
||||
|
||||
**Key Attributes:**
|
||||
|
||||
- id: string - Unique identifier
|
||||
- email: string - User's email address
|
||||
- name: string - Display name
|
||||
- role: enum - User permission level
|
||||
- timestamps: Date - Created and updated times
|
||||
|
||||
**TypeScript Interface:**
|
||||
|
||||
```typescript
|
||||
interface User {
|
||||
id: string;
|
||||
email: string;
|
||||
name: string;
|
||||
role: "admin" | "user" | "guest";
|
||||
createdAt: Date;
|
||||
updatedAt: Date;
|
||||
profile?: UserProfile;
|
||||
}
|
||||
|
||||
interface UserProfile {
|
||||
avatarUrl?: string;
|
||||
bio?: string;
|
||||
preferences: Record<string, any>;
|
||||
}
|
||||
```
|
||||
|
||||
**Relationships:**
|
||||
|
||||
- Has many Posts (1:n)
|
||||
- Has one Profile (1:1)
|
||||
@{/example}
|
||||
|
||||
## REST API Spec
|
||||
|
||||
[[LLM: Based on the chosen API style from Tech Stack:
|
||||
|
||||
1. If REST API, create an OpenAPI 3.0 specification
|
||||
2. If GraphQL, provide the GraphQL schema
|
||||
3. If tRPC, show router definitions
|
||||
4. Include all endpoints from epics/stories
|
||||
5. Define request/response schemas based on data models
|
||||
6. Document authentication requirements
|
||||
7. Include example requests/responses
|
||||
|
||||
Use appropriate format for the chosen API style. If no API (e.g., static site), skip this section.]]
|
||||
|
||||
^^CONDITION: has_rest_api^^
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.0
|
||||
info:
|
||||
title: { { api_title } }
|
||||
version: { { api_version } }
|
||||
description: { { api_description } }
|
||||
|
||||
servers:
|
||||
- url: { { api_base_url } }
|
||||
description: { { environment } }
|
||||
# ... OpenAPI specification continues
|
||||
```
|
||||
|
||||
^^/CONDITION: has_rest_api^^
|
||||
|
||||
^^CONDITION: has_graphql_api^^
|
||||
|
||||
```graphql
|
||||
# GraphQL Schema
|
||||
{{graphql_schema}}
|
||||
```
|
||||
|
||||
^^/CONDITION: has_graphql_api^^
|
||||
|
||||
^^CONDITION: has_trpc_api^^
|
||||
|
||||
```typescript
|
||||
// tRPC Router Definitions
|
||||
{
|
||||
{
|
||||
trpc_routers;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
^^/CONDITION: has_trpc_api^^
|
||||
|
||||
[[LLM: After presenting the API spec (or noting its absence if not applicable), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Components
|
||||
|
||||
[[LLM: Based on the architectural patterns, tech stack, and data models from above:
|
||||
|
||||
1. Identify major logical components/services across the fullstack
|
||||
2. Consider both frontend and backend components
|
||||
3. Define clear boundaries and interfaces between components
|
||||
4. For each component, specify:
|
||||
|
||||
- Primary responsibility
|
||||
- Key interfaces/APIs exposed
|
||||
- Dependencies on other components
|
||||
- Technology specifics based on tech stack choices
|
||||
|
||||
5. Create component diagrams where helpful
|
||||
6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: component>>
|
||||
|
||||
### {{component_name}}
|
||||
|
||||
**Responsibility:** {{component_description}}
|
||||
|
||||
**Key Interfaces:**
|
||||
|
||||
- {{interface_1}}
|
||||
- {{interface_2}}
|
||||
|
||||
**Dependencies:** {{dependencies}}
|
||||
|
||||
**Technology Stack:** {{component_tech_details}}
|
||||
<</REPEAT>>
|
||||
|
||||
### Component Diagrams
|
||||
|
||||
[[LLM: Create Mermaid diagrams to visualize component relationships. Options:
|
||||
|
||||
- C4 Container diagram for high-level view
|
||||
- Component diagram for detailed internal structure
|
||||
- Sequence diagrams for complex interactions
|
||||
Choose the most appropriate for clarity
|
||||
|
||||
After presenting the diagrams, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## External APIs
|
||||
|
||||
[[LLM: For each external service integration:
|
||||
|
||||
1. Identify APIs needed based on PRD requirements and component design
|
||||
2. If documentation URLs are unknown, ask user for specifics
|
||||
3. Document authentication methods and security considerations
|
||||
4. List specific endpoints that will be used
|
||||
5. Note any rate limits or usage constraints
|
||||
|
||||
If no external APIs are needed, state this explicitly and skip to next section.]]
|
||||
|
||||
^^CONDITION: has_external_apis^^
|
||||
|
||||
<<REPEAT: external_api>>
|
||||
|
||||
### {{api_name}} API
|
||||
|
||||
- **Purpose:** {{api_purpose}}
|
||||
- **Documentation:** {{api_docs_url}}
|
||||
- **Base URL(s):** {{api_base_url}}
|
||||
- **Authentication:** {{auth_method}}
|
||||
- **Rate Limits:** {{rate_limits}}
|
||||
|
||||
**Key Endpoints Used:**
|
||||
<<REPEAT: endpoint>>
|
||||
|
||||
- `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
|
||||
<</REPEAT>>
|
||||
|
||||
**Integration Notes:** {{integration_considerations}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: external_api}
|
||||
|
||||
### Stripe API
|
||||
|
||||
- **Purpose:** Payment processing and subscription management
|
||||
- **Documentation:** https://stripe.com/docs/api
|
||||
- **Base URL(s):** `https://api.stripe.com/v1`
|
||||
- **Authentication:** Bearer token with secret key
|
||||
- **Rate Limits:** 100 requests per second
|
||||
|
||||
**Key Endpoints Used:**
|
||||
|
||||
- `POST /customers` - Create customer profiles
|
||||
- `POST /payment_intents` - Process payments
|
||||
- `POST /subscriptions` - Manage subscriptions
|
||||
@{/example}
|
||||
|
||||
^^/CONDITION: has_external_apis^^
|
||||
|
||||
[[LLM: After presenting external APIs (or noting their absence), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Coding Standards
|
||||
|
||||
[[LLM: Define MINIMAL but CRITICAL standards for AI agents. Focus only on project-specific rules that prevent common mistakes. These will be used by dev agents.
|
||||
|
||||
After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### Critical Fullstack Rules
|
||||
|
||||
<<REPEAT: critical_rule>>
|
||||
|
||||
- **{{rule_name}}:** {{rule_description}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: critical_rules}
|
||||
|
||||
- **Type Sharing:** Always define types in packages/shared and import from there
|
||||
- **API Calls:** Never make direct HTTP calls - use the service layer
|
||||
- **Environment Variables:** Access only through config objects, never process.env directly
|
||||
- **Error Handling:** All API routes must use the standard error handler
|
||||
- **State Updates:** Never mutate state directly - use proper state management patterns
|
||||
@{/example}
|
||||
|
||||
### Naming Conventions
|
||||
|
||||
| Element | Frontend | Backend | Example |
|
||||
| :-------------- | :------------------- | :--------- | :------------------ |
|
||||
| Components | PascalCase | - | `UserProfile.tsx` |
|
||||
| Hooks | camelCase with 'use' | - | `useAuth.ts` |
|
||||
| API Routes | - | kebab-case | `/api/user-profile` |
|
||||
| Database Tables | - | snake_case | `user_profiles` |
|
||||
|
||||
## Epics
|
||||
|
||||
[[LLM: First, present a high-level list of all epics for user approval, the epic_list and immediately execute tasks#advanced-elicitation display. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.
|
||||
|
||||
CRITICAL: Epics MUST be logically sequential following agile best practices:
|
||||
|
||||
- Each epic should deliver a significant, end-to-end, fully deployable increment of testable functionality
|
||||
- Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page
|
||||
- Each subsequent epic builds upon previous epics' functionality delivering major blocks of functionality that provide tangible value to users or business when deployed
|
||||
- Not every project needs multiple epics, an epic needs to deliver value. For example, an API completed can deliver value even if a UI is not complete and planned for a separate epic.
|
||||
- Err on the side of less epics, but let the user know your rationale and offer options for splitting them if it seems some are too large or focused on disparate things.
|
||||
- Cross Cutting Concerns should flow through epics and stories and not be final stories. For example, adding a logging framework as a last story of an epic, or at the end of a project as a final epic or story would be terrible as we would not have logging from the beginning.]]
|
||||
|
||||
<<REPEAT: epic_list>>
|
||||
|
||||
- Epic{{epic_number}} {{epic_title}}: {{short_goal}}
|
||||
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: epic_list}
|
||||
|
||||
1. Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management
|
||||
2. Core Business Entities: Create and manage primary domain objects with CRUD operations
|
||||
3. User Workflows & Interactions: Enable key user journeys and business processes
|
||||
4. Reporting & Analytics: Provide insights and data visualization for users
|
||||
|
||||
@{/example}
|
||||
|
||||
[[LLM: After the epic list is approved, present each `epic_details` with all its stories and acceptance criteria as a complete review unit and immediately execute tasks#advanced-elicitation display, before moving on to the next epic.]]
|
||||
|
||||
<<REPEAT: epic_details>>
|
||||
|
||||
## Epic {{epic_number}} {{epic_title}}
|
||||
|
||||
{{epic_goal}} [[LLM: Expanded goal - 2-3 sentences describing the objective and value all the stories will achieve]]
|
||||
|
||||
[[LLM: CRITICAL STORY SEQUENCING REQUIREMENTS:
|
||||
|
||||
- Stories within each epic MUST be logically sequential
|
||||
- Each story should be a "vertical slice" delivering complete functionality
|
||||
- No story should depend on work from a later story or epic
|
||||
- Identify and note any direct prerequisite stories
|
||||
- Focus on "what" and "why" not "how" (leave technical implementation to Architect) yet be precise enough to support a logical sequential order of operations from story to story.
|
||||
- Ensure each story delivers clear user or business value, try to avoid enablers and build them into stories that deliver value.
|
||||
- Size stories for AI agent execution: Each story must be completable by a single AI agent in one focused session without context overflow
|
||||
- Think "junior developer working for 2-4 hours" - stories must be small, focused, and self-contained
|
||||
- If a story seems complex, break it down further as long as it can deliver a vertical slice
|
||||
- Each story should result in working, testable code before the agent's context window fills]]
|
||||
|
||||
<<REPEAT: story>>
|
||||
|
||||
### Story {{epic_number}}.{{story_number}} {{story_title}}
|
||||
|
||||
As a {{user_type}},
|
||||
I want {{action}},
|
||||
so that {{benefit}}.
|
||||
|
||||
#### Acceptance Criteria
|
||||
|
||||
[[LLM: Define clear, comprehensive, and testable acceptance criteria that:
|
||||
|
||||
- Precisely define what "done" means from a functional perspective
|
||||
- Are unambiguous and serve as basis for verification
|
||||
- Include any critical non-functional requirements from the PRD
|
||||
- Consider local testability for backend/data components
|
||||
- Specify UI/UX requirements and framework adherence where applicable
|
||||
- Avoid cross-cutting concerns that should be in other stories or PRD sections]]
|
||||
|
||||
<<REPEAT: criteria>>
|
||||
|
||||
- {{criterion number}}: {{criteria}}
|
||||
|
||||
<</REPEAT>>
|
||||
<</REPEAT>>
|
||||
<</REPEAT>>
|
||||
|
||||
## Next Steps
|
||||
|
||||
### Design Architect Prompt
|
||||
|
||||
[[LLM: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input.]]
|
||||
==================== END: templates#simple-project-prd-tmpl ====================
|
||||
|
||||
==================== START: checklists#pm-checklist ====================
|
||||
# Product Manager (PM) Requirements Checklist
|
||||
|
||||
@@ -7259,38 +7732,6 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
## Checklist Results Report
|
||||
|
||||
[[LLM: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the `architect-checklist` and populate results here.]]
|
||||
|
||||
## Next Steps
|
||||
|
||||
[[LLM: Provide specific next steps for implementation.]]
|
||||
|
||||
### Implementation Order
|
||||
|
||||
1. **Environment Setup**
|
||||
|
||||
- Initialize monorepo structure
|
||||
- Configure development environment
|
||||
- Set up version control
|
||||
|
||||
2. **Foundation (Epic 1)**
|
||||
|
||||
- Implement authentication flow
|
||||
- Set up database schema
|
||||
- Create basic API structure
|
||||
- Implement core UI components
|
||||
|
||||
3. **Feature Development**
|
||||
- Follow story sequence from PRD
|
||||
- Maintain type safety across stack
|
||||
- Write tests as you go
|
||||
|
||||
### Developer Handoff Prompts
|
||||
|
||||
**For Scrum Master:**
|
||||
"Create stories for {{Project Name}} using the PRD at docs/prd.md and this fullstack architecture at docs/fullstack-architecture.md. Focus on Epic 1 implementation."
|
||||
|
||||
**For Developer:**
|
||||
"Implement Story 1.1 from docs/stories/epic1/story-1.1.md using the fullstack architecture at docs/fullstack-architecture.md. Follow the coding standards and use the defined tech stack."
|
||||
==================== END: templates#fullstack-architecture-tmpl ====================
|
||||
|
||||
==================== START: templates#brownfield-architecture-tmpl ====================
|
||||
@@ -9255,10 +9696,10 @@ workflow:
|
||||
notes: "Creates focused project brief for simple project. SAVE OUTPUT: Copy final project-brief.md to your project's docs/ folder."
|
||||
|
||||
- agent: pm
|
||||
creates: simple_epic OR single_story
|
||||
uses: create-epic OR create-story
|
||||
creates: simple-project-prd.md
|
||||
uses: create doc simple-project-prd OR create-epic OR create-story
|
||||
requires: project-brief.md
|
||||
notes: "Create simple epic or story instead of full PRD for rapid development. Choose based on scope."
|
||||
notes: "Create simple prd, simple epic or story instead of full PRD for rapid development. Choose based on scope."
|
||||
|
||||
- workflow_end:
|
||||
action: move_to_ide
|
||||
|
||||
@@ -265,6 +265,7 @@ dependencies:
|
||||
templates:
|
||||
- prd-tmpl
|
||||
- brownfield-prd-tmpl
|
||||
- simple-project-prd-tmpl
|
||||
checklists:
|
||||
- pm-checklist
|
||||
- change-checklist
|
||||
@@ -1480,7 +1481,18 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
|
||||
7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
|
||||
8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
|
||||
|
||||
## TODO: ADD MORE CONTENT ONCE STABLE ALPHA BUILD
|
||||
## IDE Development Workflow
|
||||
|
||||
1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
|
||||
2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
|
||||
3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
|
||||
4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
|
||||
5. Use a new chat window to allow the SM agent to `draft the next story`.
|
||||
6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
|
||||
7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
|
||||
8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
|
||||
|
||||
With this work flow, there is only 1 story in progress at a time, worked sequentially.
|
||||
==================== END: data#bmad-kb ====================
|
||||
|
||||
==================== START: utils#workflow-management ====================
|
||||
@@ -4182,6 +4194,467 @@ so that {{benefit}}.
|
||||
<</REPEAT>>
|
||||
==================== END: templates#brownfield-prd-tmpl ====================
|
||||
|
||||
==================== START: templates#simple-project-prd-tmpl ====================
|
||||
# {{Project Name}} Product Requirements Document (PRD)
|
||||
|
||||
[[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
|
||||
|
||||
## Goals and Background Context
|
||||
|
||||
[[LLM: Populate the 2 child sections based on what we have received from user description or the provided brief. Allow user to review the 2 sections and offer changes before proceeding]]
|
||||
|
||||
### Goals
|
||||
|
||||
[[LLM: Bullet list of 1 line desired outcomes the PRD will deliver if successful - user and project desires]]
|
||||
|
||||
### Background Context
|
||||
|
||||
[[LLM: 1-2 short paragraphs summarizing the background context, such as what we learned in the brief without being redundant with the goals, what and why this solves a problem, what the current landscape or need is etc...]]
|
||||
|
||||
### Change Log
|
||||
|
||||
[[LLM: Track document versions and changes]]
|
||||
|
||||
| Date | Version | Description | Author |
|
||||
| :--- | :------ | :---------- | :----- |
|
||||
|
||||
## Requirements
|
||||
|
||||
[[LLM: Draft the list of functional and non functional requirements under the two child sections, and immediately execute tasks#advanced-elicitation display]]
|
||||
|
||||
### Functional
|
||||
|
||||
[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with FR`.]]
|
||||
@{example: - FR6: The Todo List uses AI to detect and warn against adding potentially duplicate todo items that are worded differently.}
|
||||
|
||||
### Non Functional
|
||||
|
||||
[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR`.]]
|
||||
@{example: - NFR1: AWS service usage **must** aim to stay within free-tier limits where feasible.}
|
||||
|
||||
^^CONDITION: has_ui^^
|
||||
|
||||
## User Interface Design Goals
|
||||
|
||||
[[LLM: Capture high-level UI/UX vision to inform story creation and also generate a prompt for Lovable or V0 if the user would like either. Steps:
|
||||
|
||||
1. Pre-fill all subsections with educated guesses based on project context
|
||||
2. Present the complete rendered section to user
|
||||
3. Clearly let the user know where assumptions were made
|
||||
4. Ask targeted questions for unclear/missing elements or areas needing more specification
|
||||
5. This is NOT detailed UI spec - focus on product vision and user goals
|
||||
6. After section completion, immediately apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### Overall UX Vision
|
||||
|
||||
### Key Interaction Paradigms
|
||||
|
||||
### Core Screens and Views
|
||||
|
||||
[[LLM: From a product perspective, what are the most critical screens or views necessary to deliver the the PRD values and goals? This is meant to be Conceptual High Level to Drive Rough Epic or User Stories]]
|
||||
|
||||
@{example}
|
||||
|
||||
- Login Screen
|
||||
- Main Dashboard
|
||||
- Item Detail Page
|
||||
- Settings Page
|
||||
@{/example}
|
||||
|
||||
### Accessibility: { None, WCAG, etc }
|
||||
|
||||
### Branding
|
||||
|
||||
[[LLM: Any known branding elements or style guides that must be incorporated?]]
|
||||
|
||||
@{example}
|
||||
|
||||
- Replicate the look and feel of early 1900s black and white cinema, including animated effects replicating film damage or projector glitches during page or state transitions.
|
||||
- Attached is the full color pallet and tokens for our corporate branding.
|
||||
@{/example}
|
||||
|
||||
### Target Device and Platforms
|
||||
|
||||
@{example}
|
||||
"Web Responsive, and all mobile platforms", "IPhone Only", "ASCII Windows Desktop"
|
||||
@{/example}
|
||||
|
||||
^^/CONDITION: has_ui^^
|
||||
|
||||
## Technical Assumptions
|
||||
|
||||
[[LLM: Gather technical decisions that will be used for this simple technical PRD that includes architecture decisions. Steps:
|
||||
|
||||
1. Check if `data#technical-preferences` file exists - use it to pre-populate choices
|
||||
2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
|
||||
3. For unknowns, offer guidance based on project goals and MVP scope
|
||||
4. Document ALL technical choices with rationale (why this choice fits the project)
|
||||
5. These become constraints for the Architect - be specific and complete
|
||||
6. After section completion, apply `tasks#advanced-elicitation` protocol.]]
|
||||
|
||||
### Repository Structure: { Monorepo, Polyrepo, etc...}
|
||||
|
||||
### Service Architecture
|
||||
|
||||
[[LLM: CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).]]
|
||||
|
||||
## Testing requirements
|
||||
|
||||
[[LLM: CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).]]
|
||||
|
||||
### Additional Technical Assumptions and Requests
|
||||
|
||||
[[LLM: Throughout the entire process of drafting this document, if any other technical assumptions are raised or discovered appropriate for the architect, add them here as additional bulleted items]]
|
||||
|
||||
## Data Models
|
||||
|
||||
[[LLM: Define the core data models/entities that will be used in the front end (if there is one), core application or back end, and if both, shared between frontend and backend:
|
||||
|
||||
1. Review PRD requirements and identify key business entities
|
||||
2. For each model, explain its purpose and relationships
|
||||
3. Include key attributes and data types
|
||||
4. Show relationships between models
|
||||
5. Create TypeScript interfaces that can be shared
|
||||
6. Discuss design decisions with user
|
||||
|
||||
Create a clear conceptual model before moving to database schema.
|
||||
|
||||
After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: data_model>>
|
||||
|
||||
### {{model_name}}
|
||||
|
||||
**Purpose:** {{model_purpose}}
|
||||
|
||||
**Key Attributes:**
|
||||
|
||||
- {{attribute_1}}: {{type_1}} - {{description_1}}
|
||||
- {{attribute_2}}: {{type_2}} - {{description_2}}
|
||||
|
||||
**TypeScript Interface:**
|
||||
|
||||
```typescript
|
||||
{
|
||||
{
|
||||
model_interface;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**Relationships:**
|
||||
|
||||
- {{relationship_1}}
|
||||
- {{relationship_2}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: data_model}
|
||||
|
||||
### User
|
||||
|
||||
**Purpose:** Represents authenticated users in the system
|
||||
|
||||
**Key Attributes:**
|
||||
|
||||
- id: string - Unique identifier
|
||||
- email: string - User's email address
|
||||
- name: string - Display name
|
||||
- role: enum - User permission level
|
||||
- timestamps: Date - Created and updated times
|
||||
|
||||
**TypeScript Interface:**
|
||||
|
||||
```typescript
|
||||
interface User {
|
||||
id: string;
|
||||
email: string;
|
||||
name: string;
|
||||
role: "admin" | "user" | "guest";
|
||||
createdAt: Date;
|
||||
updatedAt: Date;
|
||||
profile?: UserProfile;
|
||||
}
|
||||
|
||||
interface UserProfile {
|
||||
avatarUrl?: string;
|
||||
bio?: string;
|
||||
preferences: Record<string, any>;
|
||||
}
|
||||
```
|
||||
|
||||
**Relationships:**
|
||||
|
||||
- Has many Posts (1:n)
|
||||
- Has one Profile (1:1)
|
||||
@{/example}
|
||||
|
||||
## REST API Spec
|
||||
|
||||
[[LLM: Based on the chosen API style from Tech Stack:
|
||||
|
||||
1. If REST API, create an OpenAPI 3.0 specification
|
||||
2. If GraphQL, provide the GraphQL schema
|
||||
3. If tRPC, show router definitions
|
||||
4. Include all endpoints from epics/stories
|
||||
5. Define request/response schemas based on data models
|
||||
6. Document authentication requirements
|
||||
7. Include example requests/responses
|
||||
|
||||
Use appropriate format for the chosen API style. If no API (e.g., static site), skip this section.]]
|
||||
|
||||
^^CONDITION: has_rest_api^^
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.0
|
||||
info:
|
||||
title: { { api_title } }
|
||||
version: { { api_version } }
|
||||
description: { { api_description } }
|
||||
|
||||
servers:
|
||||
- url: { { api_base_url } }
|
||||
description: { { environment } }
|
||||
# ... OpenAPI specification continues
|
||||
```
|
||||
|
||||
^^/CONDITION: has_rest_api^^
|
||||
|
||||
^^CONDITION: has_graphql_api^^
|
||||
|
||||
```graphql
|
||||
# GraphQL Schema
|
||||
{{graphql_schema}}
|
||||
```
|
||||
|
||||
^^/CONDITION: has_graphql_api^^
|
||||
|
||||
^^CONDITION: has_trpc_api^^
|
||||
|
||||
```typescript
|
||||
// tRPC Router Definitions
|
||||
{
|
||||
{
|
||||
trpc_routers;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
^^/CONDITION: has_trpc_api^^
|
||||
|
||||
[[LLM: After presenting the API spec (or noting its absence if not applicable), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Components
|
||||
|
||||
[[LLM: Based on the architectural patterns, tech stack, and data models from above:
|
||||
|
||||
1. Identify major logical components/services across the fullstack
|
||||
2. Consider both frontend and backend components
|
||||
3. Define clear boundaries and interfaces between components
|
||||
4. For each component, specify:
|
||||
|
||||
- Primary responsibility
|
||||
- Key interfaces/APIs exposed
|
||||
- Dependencies on other components
|
||||
- Technology specifics based on tech stack choices
|
||||
|
||||
5. Create component diagrams where helpful
|
||||
6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: component>>
|
||||
|
||||
### {{component_name}}
|
||||
|
||||
**Responsibility:** {{component_description}}
|
||||
|
||||
**Key Interfaces:**
|
||||
|
||||
- {{interface_1}}
|
||||
- {{interface_2}}
|
||||
|
||||
**Dependencies:** {{dependencies}}
|
||||
|
||||
**Technology Stack:** {{component_tech_details}}
|
||||
<</REPEAT>>
|
||||
|
||||
### Component Diagrams
|
||||
|
||||
[[LLM: Create Mermaid diagrams to visualize component relationships. Options:
|
||||
|
||||
- C4 Container diagram for high-level view
|
||||
- Component diagram for detailed internal structure
|
||||
- Sequence diagrams for complex interactions
|
||||
Choose the most appropriate for clarity
|
||||
|
||||
After presenting the diagrams, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## External APIs
|
||||
|
||||
[[LLM: For each external service integration:
|
||||
|
||||
1. Identify APIs needed based on PRD requirements and component design
|
||||
2. If documentation URLs are unknown, ask user for specifics
|
||||
3. Document authentication methods and security considerations
|
||||
4. List specific endpoints that will be used
|
||||
5. Note any rate limits or usage constraints
|
||||
|
||||
If no external APIs are needed, state this explicitly and skip to next section.]]
|
||||
|
||||
^^CONDITION: has_external_apis^^
|
||||
|
||||
<<REPEAT: external_api>>
|
||||
|
||||
### {{api_name}} API
|
||||
|
||||
- **Purpose:** {{api_purpose}}
|
||||
- **Documentation:** {{api_docs_url}}
|
||||
- **Base URL(s):** {{api_base_url}}
|
||||
- **Authentication:** {{auth_method}}
|
||||
- **Rate Limits:** {{rate_limits}}
|
||||
|
||||
**Key Endpoints Used:**
|
||||
<<REPEAT: endpoint>>
|
||||
|
||||
- `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
|
||||
<</REPEAT>>
|
||||
|
||||
**Integration Notes:** {{integration_considerations}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: external_api}
|
||||
|
||||
### Stripe API
|
||||
|
||||
- **Purpose:** Payment processing and subscription management
|
||||
- **Documentation:** https://stripe.com/docs/api
|
||||
- **Base URL(s):** `https://api.stripe.com/v1`
|
||||
- **Authentication:** Bearer token with secret key
|
||||
- **Rate Limits:** 100 requests per second
|
||||
|
||||
**Key Endpoints Used:**
|
||||
|
||||
- `POST /customers` - Create customer profiles
|
||||
- `POST /payment_intents` - Process payments
|
||||
- `POST /subscriptions` - Manage subscriptions
|
||||
@{/example}
|
||||
|
||||
^^/CONDITION: has_external_apis^^
|
||||
|
||||
[[LLM: After presenting external APIs (or noting their absence), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Coding Standards
|
||||
|
||||
[[LLM: Define MINIMAL but CRITICAL standards for AI agents. Focus only on project-specific rules that prevent common mistakes. These will be used by dev agents.
|
||||
|
||||
After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### Critical Fullstack Rules
|
||||
|
||||
<<REPEAT: critical_rule>>
|
||||
|
||||
- **{{rule_name}}:** {{rule_description}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: critical_rules}
|
||||
|
||||
- **Type Sharing:** Always define types in packages/shared and import from there
|
||||
- **API Calls:** Never make direct HTTP calls - use the service layer
|
||||
- **Environment Variables:** Access only through config objects, never process.env directly
|
||||
- **Error Handling:** All API routes must use the standard error handler
|
||||
- **State Updates:** Never mutate state directly - use proper state management patterns
|
||||
@{/example}
|
||||
|
||||
### Naming Conventions
|
||||
|
||||
| Element | Frontend | Backend | Example |
|
||||
| :-------------- | :------------------- | :--------- | :------------------ |
|
||||
| Components | PascalCase | - | `UserProfile.tsx` |
|
||||
| Hooks | camelCase with 'use' | - | `useAuth.ts` |
|
||||
| API Routes | - | kebab-case | `/api/user-profile` |
|
||||
| Database Tables | - | snake_case | `user_profiles` |
|
||||
|
||||
## Epics
|
||||
|
||||
[[LLM: First, present a high-level list of all epics for user approval, the epic_list and immediately execute tasks#advanced-elicitation display. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.
|
||||
|
||||
CRITICAL: Epics MUST be logically sequential following agile best practices:
|
||||
|
||||
- Each epic should deliver a significant, end-to-end, fully deployable increment of testable functionality
|
||||
- Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page
|
||||
- Each subsequent epic builds upon previous epics' functionality delivering major blocks of functionality that provide tangible value to users or business when deployed
|
||||
- Not every project needs multiple epics, an epic needs to deliver value. For example, an API completed can deliver value even if a UI is not complete and planned for a separate epic.
|
||||
- Err on the side of less epics, but let the user know your rationale and offer options for splitting them if it seems some are too large or focused on disparate things.
|
||||
- Cross Cutting Concerns should flow through epics and stories and not be final stories. For example, adding a logging framework as a last story of an epic, or at the end of a project as a final epic or story would be terrible as we would not have logging from the beginning.]]
|
||||
|
||||
<<REPEAT: epic_list>>
|
||||
|
||||
- Epic{{epic_number}} {{epic_title}}: {{short_goal}}
|
||||
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: epic_list}
|
||||
|
||||
1. Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management
|
||||
2. Core Business Entities: Create and manage primary domain objects with CRUD operations
|
||||
3. User Workflows & Interactions: Enable key user journeys and business processes
|
||||
4. Reporting & Analytics: Provide insights and data visualization for users
|
||||
|
||||
@{/example}
|
||||
|
||||
[[LLM: After the epic list is approved, present each `epic_details` with all its stories and acceptance criteria as a complete review unit and immediately execute tasks#advanced-elicitation display, before moving on to the next epic.]]
|
||||
|
||||
<<REPEAT: epic_details>>
|
||||
|
||||
## Epic {{epic_number}} {{epic_title}}
|
||||
|
||||
{{epic_goal}} [[LLM: Expanded goal - 2-3 sentences describing the objective and value all the stories will achieve]]
|
||||
|
||||
[[LLM: CRITICAL STORY SEQUENCING REQUIREMENTS:
|
||||
|
||||
- Stories within each epic MUST be logically sequential
|
||||
- Each story should be a "vertical slice" delivering complete functionality
|
||||
- No story should depend on work from a later story or epic
|
||||
- Identify and note any direct prerequisite stories
|
||||
- Focus on "what" and "why" not "how" (leave technical implementation to Architect) yet be precise enough to support a logical sequential order of operations from story to story.
|
||||
- Ensure each story delivers clear user or business value, try to avoid enablers and build them into stories that deliver value.
|
||||
- Size stories for AI agent execution: Each story must be completable by a single AI agent in one focused session without context overflow
|
||||
- Think "junior developer working for 2-4 hours" - stories must be small, focused, and self-contained
|
||||
- If a story seems complex, break it down further as long as it can deliver a vertical slice
|
||||
- Each story should result in working, testable code before the agent's context window fills]]
|
||||
|
||||
<<REPEAT: story>>
|
||||
|
||||
### Story {{epic_number}}.{{story_number}} {{story_title}}
|
||||
|
||||
As a {{user_type}},
|
||||
I want {{action}},
|
||||
so that {{benefit}}.
|
||||
|
||||
#### Acceptance Criteria
|
||||
|
||||
[[LLM: Define clear, comprehensive, and testable acceptance criteria that:
|
||||
|
||||
- Precisely define what "done" means from a functional perspective
|
||||
- Are unambiguous and serve as basis for verification
|
||||
- Include any critical non-functional requirements from the PRD
|
||||
- Consider local testability for backend/data components
|
||||
- Specify UI/UX requirements and framework adherence where applicable
|
||||
- Avoid cross-cutting concerns that should be in other stories or PRD sections]]
|
||||
|
||||
<<REPEAT: criteria>>
|
||||
|
||||
- {{criterion number}}: {{criteria}}
|
||||
|
||||
<</REPEAT>>
|
||||
<</REPEAT>>
|
||||
<</REPEAT>>
|
||||
|
||||
## Next Steps
|
||||
|
||||
### Design Architect Prompt
|
||||
|
||||
[[LLM: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input.]]
|
||||
==================== END: templates#simple-project-prd-tmpl ====================
|
||||
|
||||
==================== START: checklists#pm-checklist ====================
|
||||
# Product Manager (PM) Requirements Checklist
|
||||
|
||||
@@ -6704,38 +7177,6 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
## Checklist Results Report
|
||||
|
||||
[[LLM: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the `architect-checklist` and populate results here.]]
|
||||
|
||||
## Next Steps
|
||||
|
||||
[[LLM: Provide specific next steps for implementation.]]
|
||||
|
||||
### Implementation Order
|
||||
|
||||
1. **Environment Setup**
|
||||
|
||||
- Initialize monorepo structure
|
||||
- Configure development environment
|
||||
- Set up version control
|
||||
|
||||
2. **Foundation (Epic 1)**
|
||||
|
||||
- Implement authentication flow
|
||||
- Set up database schema
|
||||
- Create basic API structure
|
||||
- Implement core UI components
|
||||
|
||||
3. **Feature Development**
|
||||
- Follow story sequence from PRD
|
||||
- Maintain type safety across stack
|
||||
- Write tests as you go
|
||||
|
||||
### Developer Handoff Prompts
|
||||
|
||||
**For Scrum Master:**
|
||||
"Create stories for {{Project Name}} using the PRD at docs/prd.md and this fullstack architecture at docs/fullstack-architecture.md. Focus on Epic 1 implementation."
|
||||
|
||||
**For Developer:**
|
||||
"Implement Story 1.1 from docs/stories/epic1/story-1.1.md using the fullstack architecture at docs/fullstack-architecture.md. Follow the coding standards and use the defined tech stack."
|
||||
==================== END: templates#fullstack-architecture-tmpl ====================
|
||||
|
||||
==================== START: templates#brownfield-architecture-tmpl ====================
|
||||
|
||||
@@ -91,10 +91,10 @@ workflow:
|
||||
notes: "Creates focused project brief for simple project. SAVE OUTPUT: Copy final project-brief.md to your project's docs/ folder."
|
||||
|
||||
- agent: pm
|
||||
creates: simple_epic OR single_story
|
||||
uses: create-epic OR create-story
|
||||
creates: simple-project-prd.md
|
||||
uses: create doc simple-project-prd OR create-epic OR create-story
|
||||
requires: project-brief.md
|
||||
notes: "Create simple epic or story instead of full PRD for rapid development. Choose based on scope."
|
||||
notes: "Create simple prd, simple epic or story instead of full PRD for rapid development. Choose based on scope."
|
||||
|
||||
- workflow_end:
|
||||
action: move_to_ide
|
||||
|
||||
@@ -8,25 +8,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
|
||||
|
||||
```yml
|
||||
activation-instructions:
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
agent:
|
||||
name: John
|
||||
id: pm
|
||||
title: Product Manager
|
||||
icon: 📋
|
||||
whenToUse: "Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication"
|
||||
customization:
|
||||
|
||||
whenToUse: Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication
|
||||
customization: null
|
||||
persona:
|
||||
role: Investigative Product Strategist & Market-Savvy PM
|
||||
style: Analytical, inquisitive, data-driven, user-focused, pragmatic
|
||||
identity: Product Manager specialized in document creation and product research
|
||||
focus: Creating PRDs and other product documentation using templates
|
||||
|
||||
core_principles:
|
||||
- Deeply understand "Why" - uncover root causes and motivations
|
||||
- Champion the user - maintain relentless focus on target user value
|
||||
@@ -36,16 +33,13 @@ persona:
|
||||
- Collaborative & iterative approach
|
||||
- Proactive risk identification
|
||||
- Strategic thinking & outcome-oriented
|
||||
|
||||
startup:
|
||||
- Greet the user with your name and role, and inform of the *help command.
|
||||
|
||||
commands:
|
||||
- "*help" - Show: numbered list of the following commands to allow selection
|
||||
- "*chat-mode" - (Default) Deep conversation with advanced-elicitation
|
||||
- "*create-doc {template}" - Create doc (no template = show available templates)
|
||||
- "*exit" - Say goodbye as the PM, and then abandon inhabiting this persona
|
||||
|
||||
- '*help" - Show: numbered list of the following commands to allow selection'
|
||||
- '*chat-mode" - (Default) Deep conversation with advanced-elicitation'
|
||||
- '*create-doc {template}" - Create doc (no template = show available templates)'
|
||||
- '*exit" - Say goodbye as the PM, and then abandon inhabiting this persona'
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-doc
|
||||
@@ -58,6 +52,7 @@ dependencies:
|
||||
templates:
|
||||
- prd-tmpl
|
||||
- brownfield-prd-tmpl
|
||||
- simple-project-prd-tmpl
|
||||
checklists:
|
||||
- pm-checklist
|
||||
- change-checklist
|
||||
|
||||
@@ -18,14 +18,12 @@ agent:
|
||||
id: bmad-master
|
||||
title: BMAD Master Task Executor
|
||||
icon: 🧙
|
||||
whenToUse: "Use when you need comprehensive expertise across all domains or rapid context switching between multiple agent capabilities"
|
||||
|
||||
whenToUse: Use when you need comprehensive expertise across all domains or rapid context switching between multiple agent capabilities
|
||||
persona:
|
||||
role: Master Task Executor & BMAD Method Expert
|
||||
style: Efficient, direct, action-oriented. Executes any BMAD task/template/util/checklist with precision
|
||||
identity: Universal executor of all BMAD-METHOD capabilities, directly runs any resource
|
||||
focus: Direct execution without transformation, load resources only when needed
|
||||
|
||||
core_principles:
|
||||
- Execute any resource directly without persona transformation
|
||||
- Load resources at runtime, never pre-load
|
||||
@@ -33,36 +31,30 @@ persona:
|
||||
- Track execution state and guide multi-step processes
|
||||
- Use numbered lists for choices
|
||||
- Process (*) commands immediately
|
||||
|
||||
startup:
|
||||
- Announce: "I'm BMad Master, your BMAD task executor. I can run any task, template, util, checklist, workflow, or schema. Type *help or tell me what you need."
|
||||
- Announce: I'm BMad Master, your BMAD task executor. I can run any task, template, util, checklist, workflow, or schema. Type *help or tell me what you need.
|
||||
- CRITICAL: Do NOT scan filesystem or load any resources during startup
|
||||
- CRITICAL: Do NOT run discovery tasks automatically
|
||||
- CRITICAL: Do NOT run discovery tasks automatically
|
||||
- Wait for user request before any tool use
|
||||
- Match request to resources, offer numbered options if unclear
|
||||
- Load resources only when explicitly requested
|
||||
|
||||
commands:
|
||||
- "*help" - Show commands
|
||||
- "*chat" - Advanced elicitation + KB mode
|
||||
- "*status" - Current context
|
||||
- "*task/template/util/checklist/workflow {name}" - Execute (list if no name)
|
||||
- "*list {type}" - List resources by type
|
||||
- "*exit" - Exit (confirm)
|
||||
- "*yolo" - Skip confirmations
|
||||
- "*doc-out" - Output full document
|
||||
|
||||
- '*help" - Show commands'
|
||||
- '*chat" - Advanced elicitation + KB mode'
|
||||
- '*status" - Current context'
|
||||
- '*task/template/util/checklist/workflow {name}" - Execute (list if no name)'
|
||||
- '*list {type}" - List resources by type'
|
||||
- '*exit" - Exit (confirm)'
|
||||
- '*yolo" - Skip confirmations'
|
||||
- '*doc-out" - Output full document'
|
||||
fuzzy-matching:
|
||||
- 85% confidence threshold
|
||||
- Show numbered list if unsure
|
||||
|
||||
execution:
|
||||
- NEVER use tools during startup - only announce and wait
|
||||
- Runtime discovery ONLY when user requests specific resources
|
||||
- Workflow: User request → Runtime discovery → Load resource → Execute instructions → Guide inputs → Provide feedback
|
||||
- Suggest related resources after completion
|
||||
|
||||
# Reference list for runtime discovery (DO NOT PRELOAD):
|
||||
dependencies:
|
||||
tasks:
|
||||
- advanced-elicitation
|
||||
|
||||
@@ -64,6 +64,7 @@ dependencies:
|
||||
templates:
|
||||
- prd-tmpl
|
||||
- brownfield-prd-tmpl
|
||||
- simple-project-prd-tmpl
|
||||
checklists:
|
||||
- pm-checklist
|
||||
- change-checklist
|
||||
|
||||
@@ -14,50 +14,44 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
|
||||
|
||||
```yml
|
||||
activation-instructions:
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
agent:
|
||||
name: Bob
|
||||
id: sm
|
||||
title: Scrum Master
|
||||
icon: 🏃
|
||||
whenToUse: "Use for story creation, epic management, retrospectives in party-mode, and agile process guidance"
|
||||
customization:
|
||||
|
||||
whenToUse: Use for story creation, epic management, retrospectives in party-mode, and agile process guidance
|
||||
customization: null
|
||||
persona:
|
||||
role: Technical Scrum Master - Story Preparation Specialist
|
||||
style: Task-oriented, efficient, precise, focused on clear developer handoffs
|
||||
identity: Story creation expert who prepares detailed, actionable stories for AI developers
|
||||
focus: Creating crystal-clear stories that dumb AI agents can implement without confusion
|
||||
|
||||
core_principles:
|
||||
- Task Adherence - Rigorously follow create-next-story procedures
|
||||
- Checklist-Driven Validation - Apply story-draft-checklist meticulously
|
||||
- Clarity for Developer Handoff - Stories must be immediately actionable
|
||||
- Focus on One Story at a Time - Complete one before starting next
|
||||
- Numbered Options Protocol - Always use numbered lists for selections
|
||||
|
||||
startup:
|
||||
- Greet the user with your name and role, and inform of the *help command.
|
||||
- CRITICAL: Do NOT automatically execute create-next-story tasks during startup
|
||||
- CRITICAL: Do NOT create or modify any files during startup
|
||||
- Offer to help with story preparation but wait for explicit user confirmation
|
||||
- Only execute tasks when user explicitly requests them
|
||||
- CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Dev Agent
|
||||
|
||||
- 'CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Dev Agent'
|
||||
commands:
|
||||
- "*help" - Show: numbered list of the following commands to allow selection
|
||||
- "*chat-mode" - Conversational mode with advanced-elicitation for advice
|
||||
- "*create" - Execute all steps in Create Next Story Task document
|
||||
- "*pivot" - Run correct-course task (ensure no story already created first)
|
||||
- "*checklist {checklist}" - Show numbered list of checklists, execute selection
|
||||
- "*doc-shard {PRD|Architecture|Other}" - Execute shard-doc task
|
||||
- "*index-docs" - Update documentation index in /docs/index.md
|
||||
- "*exit" - Say goodbye as the Scrum Master, and then abandon inhabiting this persona
|
||||
|
||||
- '*help" - Show: numbered list of the following commands to allow selection'
|
||||
- '*chat-mode" - Conversational mode with advanced-elicitation for advice'
|
||||
- '*create" - Execute all steps in Create Next Story Task document'
|
||||
- '*pivot" - Run correct-course task (ensure no story already created first)'
|
||||
- '*checklist {checklist}" - Show numbered list of checklists, execute selection'
|
||||
- '*doc-shard {PRD|Architecture|Other}" - Execute shard-doc task'
|
||||
- '*index-docs" - Update documentation index in /docs/index.md'
|
||||
- '*exit" - Say goodbye as the Scrum Master, and then abandon inhabiting this persona'
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-next-story
|
||||
|
||||
@@ -8,25 +8,22 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
|
||||
|
||||
```yml
|
||||
activation-instructions:
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
agent:
|
||||
name: John
|
||||
id: pm
|
||||
title: Product Manager
|
||||
icon: 📋
|
||||
whenToUse: "Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication"
|
||||
customization:
|
||||
|
||||
whenToUse: Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication
|
||||
customization: null
|
||||
persona:
|
||||
role: Investigative Product Strategist & Market-Savvy PM
|
||||
style: Analytical, inquisitive, data-driven, user-focused, pragmatic
|
||||
identity: Product Manager specialized in document creation and product research
|
||||
focus: Creating PRDs and other product documentation using templates
|
||||
|
||||
core_principles:
|
||||
- Deeply understand "Why" - uncover root causes and motivations
|
||||
- Champion the user - maintain relentless focus on target user value
|
||||
@@ -36,16 +33,13 @@ persona:
|
||||
- Collaborative & iterative approach
|
||||
- Proactive risk identification
|
||||
- Strategic thinking & outcome-oriented
|
||||
|
||||
startup:
|
||||
- Greet the user with your name and role, and inform of the *help command.
|
||||
|
||||
commands:
|
||||
- "*help" - Show: numbered list of the following commands to allow selection
|
||||
- "*chat-mode" - (Default) Deep conversation with advanced-elicitation
|
||||
- "*create-doc {template}" - Create doc (no template = show available templates)
|
||||
- "*exit" - Say goodbye as the PM, and then abandon inhabiting this persona
|
||||
|
||||
- '*help" - Show: numbered list of the following commands to allow selection'
|
||||
- '*chat-mode" - (Default) Deep conversation with advanced-elicitation'
|
||||
- '*create-doc {template}" - Create doc (no template = show available templates)'
|
||||
- '*exit" - Say goodbye as the PM, and then abandon inhabiting this persona'
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-doc
|
||||
@@ -58,6 +52,7 @@ dependencies:
|
||||
templates:
|
||||
- prd-tmpl
|
||||
- brownfield-prd-tmpl
|
||||
- simple-project-prd-tmpl
|
||||
checklists:
|
||||
- pm-checklist
|
||||
- change-checklist
|
||||
|
||||
42
docs/sample-output/simple-fullstack-greenfield/prd.md
Normal file
42
docs/sample-output/simple-fullstack-greenfield/prd.md
Normal file
@@ -0,0 +1,42 @@
|
||||
# PRD
|
||||
|
||||
## Epic 1: Core To-Do Functionality
|
||||
|
||||
**Goal:** To deliver a functional, single-user to-do application with user authentication and full CRUD (Create, Read, Update, Delete) capabilities for tasks.
|
||||
|
||||
**Stories:**
|
||||
|
||||
**Story 1.1: User Authentication**
|
||||
|
||||
- **As a** user,
|
||||
- **I want** to be able to sign up, log in, and log out,
|
||||
- **so that** I can securely manage my personal to-do list.
|
||||
- **Acceptance Criteria:**
|
||||
1. The application uses the Supabase Auth UI for login and sign-up forms.
|
||||
2. A user can create an account and will be automatically logged in.
|
||||
3. A logged-in user can log out, which redirects them to the login page.
|
||||
4. The main to-do list page is protected and only visible to authenticated users.
|
||||
|
||||
**Story 1.2: Create and View To-Dos**
|
||||
|
||||
- **As an** authenticated user,
|
||||
- **I want** to enter a task into an input field and see it appear on my to-do list,
|
||||
- **so that** I can keep track of my tasks.
|
||||
- **Acceptance Criteria:**
|
||||
1. There is a text input field and a "Create" button on the main page.
|
||||
2. Submitting a new task adds it to the database and displays it in the list of to-dos without a page refresh.
|
||||
3. The to-do list is fetched from the Supabase database when the page loads.
|
||||
4. The input field is cleared after a to-do is successfully created.
|
||||
|
||||
**Story 1.3: Update and Delete To-Dos**
|
||||
|
||||
- **As an** authenticated user,
|
||||
- **I want** to be able to mark a to-do as complete and delete it,
|
||||
- **so that** I can manage my task list effectively.
|
||||
- **Acceptance Criteria:**
|
||||
1. Each to-do item has a checkbox or button to toggle its "completed" status.
|
||||
2. Changing the status updates the item in the database and visually (e.g., with a strikethrough).
|
||||
3. Each to-do item has a "Delete" button.
|
||||
4. Clicking "Delete" removes the to-do from the UI and the database.
|
||||
|
||||
With this epic, the planning phase is complete. All the requirements are clearly defined and structured for development.
|
||||
Reference in New Issue
Block a user