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

style: apply formatting fixes and yaml standardization

Browse Source 
- Auto-formatting applied by prettier and yaml-format tools
- Standardized YAML code blocks to use 'yaml' instead of 'yml'
- Fixed quote escaping in YAML strings

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Brian Madison
2025-06-15 14:23:33 -05:00
parent ba1e5ceb36
commit 49e34f41b6
14 changed files with 386 additions and 364 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
.bmad-core/tasks/doc-migration-task.md
View File

@@ -68,7 +68,7 @@ The epic numbering starts at 1 and increments for each epic found.
### Before (PRD):
````markdown
`````markdown
# Product Requirements Document
## 1. Executive Summary
@@ -136,4 +136,8 @@ Content...
## Technical Stack Tools
Content...
````
````
`````
```text
```

5
.bmad-core/tasks/index-docs.md
View File

@@ -56,7 +56,7 @@ You are now operating as a Documentation Indexer. Your goal is to ensure all doc
The index should be organized as follows:
````markdown
`````markdown
# Documentation Index
## Root Documents
@@ -100,6 +100,8 @@ Each entry should follow this format:
Brief description of the document's purpose and contents.
````
`````
````
### Rules of Operation
@@ -178,3 +180,4 @@ Please provide:
5. Whether to include hidden files/folders (starting with `.`)
Would you like to proceed with documentation indexing? Please provide the required input above.
````

14
.bmad-core/templates/fullstack-architecture-tmpl.md
View File

@@ -467,7 +467,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Component Organization:**
```text
`````text
{{component_structure}}
```text
@@ -493,7 +493,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
state_structure;
}
}
````
`````
**State Management Patterns:**
@@ -508,7 +508,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```text
{{route_structure}}
```
```text
**Protected Route Pattern:**
@@ -578,7 +578,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
^^CONDITION: traditional_server^^
**Controller/Route Organization:**
```text
`````text
{{controller_structure}}
```text
@@ -602,7 +602,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```sql
{{database_schema}}
````
`````
**Data Access Layer:**
@@ -855,7 +855,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
{{frontend_test_structure}}
```text
````text
**Backend Tests:**
@@ -867,7 +867,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**E2E Tests:**
```
````
{{e2e_test_structure}}

34
.bmad-core/web-bundles/agents/analyst.txt
View File

@@ -43,27 +43,24 @@ These references map directly to bundle sections:
CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
```yml
```yaml
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: Mary
id: analyst
title: Business Analyst
icon: 📊
whenToUse: "Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery"
customization:
whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery
customization: null
persona:
role: Insightful Analyst & Strategic Ideation Partner
style: Analytical, inquisitive, creative, facilitative, objective, data-informed
identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
focus: Research planning, ideation facilitation, strategic analysis, actionable insights
core_principles:
- Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
- Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
@@ -76,19 +73,16 @@ persona:
- Maintaining a Broad Perspective - Stay aware of market trends and dynamics
- Integrity of Information - Ensure accurate sourcing and representation
- Numbered Options Protocol - Always use numbered lists for selections
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) Strategic analysis consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*brainstorm {topic}" - Facilitate structured brainstorming session
- "*research {topic}" - Generate deep research prompt for investigation
- "*elicit" - Run advanced elicitation to clarify requirements
- "*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*brainstorm {topic}" - Facilitate structured brainstorming session'
- '*research {topic}" - Generate deep research prompt for investigation'
- '*elicit" - Run advanced elicitation to clarify requirements'
- '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
dependencies:
tasks:
- brainstorming-techniques

89
.bmad-core/web-bundles/agents/architect.txt
View File

@@ -1650,7 +1650,7 @@ Document the choice and key services that will be used.]]
Use appropriate diagram type for clarity.]]
```mermaid
````mermaid
{{architecture_diagram}}
```text
@@ -1763,7 +1763,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
model_interface;
}
}
```
````
**Relationships:**
@@ -1787,7 +1787,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
**TypeScript Interface:**
```typescript
````typescript
interface User {
id: string;
email: string;
@@ -1841,13 +1841,13 @@ servers:
'[object Object]': null
description:
'[object Object]': null
```
````
^^/CONDITION: has_rest_api^^
^^CONDITION: has_graphql_api^^
```graphql
````graphql
# GraphQL Schema
{{graphql_schema}}
```text
@@ -1863,7 +1863,7 @@ servers:
trpc_routers;
}
}
```
````
^^/CONDITION: has_trpc_api^^
@@ -2010,11 +2010,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```text
{{component_structure}}
```
```text
**Component Template:**
```typescript
````typescript
{
{
component_template;
@@ -2034,7 +2034,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
state_structure;
}
}
```
````
**State Management Patterns:**
@@ -2053,7 +2053,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Protected Route Pattern:**
```typescript
````typescript
{
{
protected_route_example;
@@ -2073,11 +2073,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
api_client_setup;
}
}
```
````
**Service Example:**
```typescript
````typescript
{
{
service_example;
@@ -2098,9 +2098,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
^^CONDITION: serverless^^
**Function Organization:**
```
````
{{function_structure}}
```text
````text
**Function Template:**
@@ -2110,7 +2112,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
function_template;
}
}
```
````
^^/CONDITION: serverless^^
@@ -2119,11 +2121,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```text
{{controller_structure}}
```
```text
**Controller Template:**
```typescript
````typescript
{
{
controller_template;
@@ -2141,11 +2143,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```sql
{{database_schema}}
```
````
**Data Access Layer:**
```typescript
````typescript
{
{
repository_pattern;
@@ -2161,11 +2163,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```mermaid
{{auth_flow_diagram}}
```
````
**Middleware/Guards:**
```typescript
````typescript
{
{
auth_middleware;
@@ -2231,7 +2233,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
├── package.json # Root package.json
├── {{monorepo_config}} # Monorepo configuration
└── README.md
```
````
@{example: vercel_structure}
apps/
@@ -2253,7 +2255,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Prerequisites:**
```bash
````bash
{{prerequisites_commands}}
```text
@@ -2261,11 +2263,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```bash
{{setup_commands}}
```
````
**Development Commands:**
```bash
````bash
# Start all services
{{start_all_command}}
@@ -2292,7 +2294,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
# Shared
{{shared_env_vars}}
```
````
## Deployment Architecture
@@ -2315,7 +2317,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### CI/CD Pipeline
```yml
````yaml
'[object Object]': null
```text
@@ -2375,12 +2377,15 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### Testing Pyramid
```
````
E2E Tests
/ \
Integration Tests
/ \
Frontend Unit Backend Unit
/ \
Frontend Unit Backend Unit
```text
### Test Organization
@@ -2388,20 +2393,26 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Frontend Tests:**
```
{{frontend_test_structure}}
```text
**Backend Tests:**
```
```text
{{backend_test_structure}}
```text
**E2E Tests:**
```
{{e2e_test_structure}}
```text
````text
### Test Examples
@@ -2413,11 +2424,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
frontend_test_example;
}
}
```
````
**Backend API Test:**
```typescript
````typescript
{
{
backend_test_example;
@@ -2433,7 +2444,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
e2e_test_example;
}
}
```
````
## Coding Standards
@@ -2474,7 +2485,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### Error Flow
```mermaid
````mermaid
{{error_flow_diagram}}
```text
@@ -2490,11 +2501,11 @@ interface ApiError {
requestId: string;
};
}
```
````
### Frontend Error Handling
```typescript
````typescript
{
{
frontend_error_handler;
@@ -2510,7 +2521,7 @@ interface ApiError {
backend_error_handler;
}
}
```
````
## Monitoring and Observability

97
.bmad-core/web-bundles/agents/bmad-master.txt
View File

@@ -2622,7 +2622,7 @@ You are now operating as a Documentation Indexer. Your goal is to ensure all doc
The index should be organized as follows:
```markdown
````markdown
# Documentation Index
## Root Documents
@@ -2654,7 +2654,8 @@ Documents within the `another-folder/` directory:
### [Nested Document](./another-folder/document.md)
Description of nested document.
```text
````text
### Index Entry Format
@@ -2664,7 +2665,8 @@ Each entry should follow this format:
### [Document Title](relative/path/to/file.md)
Brief description of the document's purpose and contents.
```
````
````
### Rules of Operation
@@ -5631,7 +5633,7 @@ Document the choice and key services that will be used.]]
Use appropriate diagram type for clarity.]]
```mermaid
````mermaid
{{architecture_diagram}}
```text
@@ -5744,7 +5746,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
model_interface;
}
}
```
````
**Relationships:**
@@ -5768,7 +5770,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
**TypeScript Interface:**
```typescript
````typescript
interface User {
id: string;
email: string;
@@ -5822,13 +5824,13 @@ servers:
'[object Object]': null
description:
'[object Object]': null
```
````
^^/CONDITION: has_rest_api^^
^^CONDITION: has_graphql_api^^
```graphql
````graphql
# GraphQL Schema
{{graphql_schema}}
```text
@@ -5844,7 +5846,7 @@ servers:
trpc_routers;
}
}
```
````
^^/CONDITION: has_trpc_api^^
@@ -5991,11 +5993,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```text
{{component_structure}}
```
```text
**Component Template:**
```typescript
````typescript
{
{
component_template;
@@ -6015,7 +6017,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
state_structure;
}
}
```
````
**State Management Patterns:**
@@ -6034,7 +6036,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Protected Route Pattern:**
```typescript
````typescript
{
{
protected_route_example;
@@ -6054,11 +6056,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
api_client_setup;
}
}
```
````
**Service Example:**
```typescript
````typescript
{
{
service_example;
@@ -6079,9 +6081,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
^^CONDITION: serverless^^
**Function Organization:**
```
````
{{function_structure}}
```text
````text
**Function Template:**
@@ -6091,7 +6095,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
function_template;
}
}
```
````
^^/CONDITION: serverless^^
@@ -6100,11 +6104,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```text
{{controller_structure}}
```
```text
**Controller Template:**
```typescript
````typescript
{
{
controller_template;
@@ -6122,11 +6126,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```sql
{{database_schema}}
```
````
**Data Access Layer:**
```typescript
````typescript
{
{
repository_pattern;
@@ -6142,11 +6146,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```mermaid
{{auth_flow_diagram}}
```
````
**Middleware/Guards:**
```typescript
````typescript
{
{
auth_middleware;
@@ -6212,7 +6216,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
├── package.json # Root package.json
├── {{monorepo_config}} # Monorepo configuration
└── README.md
```
````
@{example: vercel_structure}
apps/
@@ -6234,7 +6238,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Prerequisites:**
```bash
````bash
{{prerequisites_commands}}
```text
@@ -6242,11 +6246,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```bash
{{setup_commands}}
```
````
**Development Commands:**
```bash
````bash
# Start all services
{{start_all_command}}
@@ -6273,7 +6277,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
# Shared
{{shared_env_vars}}
```
````
## Deployment Architecture
@@ -6296,7 +6300,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### CI/CD Pipeline
```yml
````yaml
'[object Object]': null
```text
@@ -6356,12 +6360,15 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### Testing Pyramid
```
````
E2E Tests
/ \
Integration Tests
/ \
Frontend Unit Backend Unit
/ \
Frontend Unit Backend Unit
```text
### Test Organization
@@ -6369,20 +6376,26 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Frontend Tests:**
```
{{frontend_test_structure}}
```text
**Backend Tests:**
```
```text
{{backend_test_structure}}
```text
**E2E Tests:**
```
{{e2e_test_structure}}
```text
````text
### Test Examples
@@ -6394,11 +6407,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
frontend_test_example;
}
}
```
````
**Backend API Test:**
```typescript
````typescript
{
{
backend_test_example;
@@ -6414,7 +6427,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
e2e_test_example;
}
}
```
````
## Coding Standards
@@ -6455,7 +6468,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### Error Flow
```mermaid
````mermaid
{{error_flow_diagram}}
```text
@@ -6471,11 +6484,11 @@ interface ApiError {
requestId: string;
};
}
```
````
### Frontend Error Handling
```typescript
````typescript
{
{
frontend_error_handler;
@@ -6491,7 +6504,7 @@ interface ApiError {
backend_error_handler;
}
}
```
````
## Monitoring and Observability

8
.bmad-core/web-bundles/agents/pm.txt
View File

@@ -1732,7 +1732,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
**TypeScript Interface:**
```typescript
````typescript
{
{
model_interface;
@@ -1778,7 +1778,7 @@ interface UserProfile {
bio?: string;
preferences: Record<string, any>;
}
```
````
**Relationships:**
@@ -1802,7 +1802,7 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),
^^CONDITION: has_rest_api^^
```yml
````yml
openapi: 3.0.0
info:
title:
@@ -1825,7 +1825,7 @@ servers:
```graphql
# GraphQL Schema
{{graphql_schema}}
```
````
^^/CONDITION: has_graphql_api^^

2
.bmad-core/web-bundles/agents/sm.txt
View File

@@ -43,7 +43,7 @@ These references map directly to bundle sections:
CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
```yml
```yaml
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

133
.bmad-core/web-bundles/teams/team-all.txt
View File

@@ -146,27 +146,24 @@ dependencies:
CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
```yml
```yaml
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: Mary
id: analyst
title: Business Analyst
icon: 📊
whenToUse: "Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery"
customization:
whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery
customization: null
persona:
role: Insightful Analyst & Strategic Ideation Partner
style: Analytical, inquisitive, creative, facilitative, objective, data-informed
identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
focus: Research planning, ideation facilitation, strategic analysis, actionable insights
core_principles:
- Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
- Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
@@ -179,19 +176,16 @@ persona:
- Maintaining a Broad Perspective - Stay aware of market trends and dynamics
- Integrity of Information - Ensure accurate sourcing and representation
- Numbered Options Protocol - Always use numbered lists for selections
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) Strategic analysis consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*brainstorm {topic}" - Facilitate structured brainstorming session
- "*research {topic}" - Generate deep research prompt for investigation
- "*elicit" - Run advanced elicitation to clarify requirements
- "*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*brainstorm {topic}" - Facilitate structured brainstorming session'
- '*research {topic}" - Generate deep research prompt for investigation'
- '*elicit" - Run advanced elicitation to clarify requirements'
- '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
dependencies:
tasks:
- brainstorming-techniques
@@ -536,7 +530,7 @@ dependencies:
CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
```yml
```yaml
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
@@ -4495,7 +4489,7 @@ Document the choice and key services that will be used.]]
Use appropriate diagram type for clarity.]]
```mermaid
````mermaid
{{architecture_diagram}}
```text
@@ -4608,7 +4602,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
model_interface;
}
}
```
````
**Relationships:**
@@ -4632,7 +4626,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
**TypeScript Interface:**
```typescript
````typescript
interface User {
id: string;
email: string;
@@ -4686,13 +4680,13 @@ servers:
'[object Object]': null
description:
'[object Object]': null
```
````
^^/CONDITION: has_rest_api^^
^^CONDITION: has_graphql_api^^
```graphql
````graphql
# GraphQL Schema
{{graphql_schema}}
```text
@@ -4708,7 +4702,7 @@ servers:
trpc_routers;
}
}
```
````
^^/CONDITION: has_trpc_api^^
@@ -4855,11 +4849,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```text
{{component_structure}}
```
```text
**Component Template:**
```typescript
````typescript
{
{
component_template;
@@ -4879,7 +4873,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
state_structure;
}
}
```
````
**State Management Patterns:**
@@ -4898,7 +4892,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Protected Route Pattern:**
```typescript
````typescript
{
{
protected_route_example;
@@ -4918,11 +4912,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
api_client_setup;
}
}
```
````
**Service Example:**
```typescript
````typescript
{
{
service_example;
@@ -4943,9 +4937,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
^^CONDITION: serverless^^
**Function Organization:**
```
````
{{function_structure}}
```text
````text
**Function Template:**
@@ -4955,7 +4951,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
function_template;
}
}
```
````
^^/CONDITION: serverless^^
@@ -4964,11 +4960,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```text
{{controller_structure}}
```
```text
**Controller Template:**
```typescript
````typescript
{
{
controller_template;
@@ -4986,11 +4982,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```sql
{{database_schema}}
```
````
**Data Access Layer:**
```typescript
````typescript
{
{
repository_pattern;
@@ -5006,11 +5002,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```mermaid
{{auth_flow_diagram}}
```
````
**Middleware/Guards:**
```typescript
````typescript
{
{
auth_middleware;
@@ -5076,7 +5072,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
├── package.json # Root package.json
├── {{monorepo_config}} # Monorepo configuration
└── README.md
```
````
@{example: vercel_structure}
apps/
@@ -5098,7 +5094,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Prerequisites:**
```bash
````bash
{{prerequisites_commands}}
```text
@@ -5106,11 +5102,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```bash
{{setup_commands}}
```
````
**Development Commands:**
```bash
````bash
# Start all services
{{start_all_command}}
@@ -5137,7 +5133,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
# Shared
{{shared_env_vars}}
```
````
## Deployment Architecture
@@ -5160,7 +5156,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### CI/CD Pipeline
```yml
````yaml
'[object Object]': null
```text
@@ -5220,12 +5216,15 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### Testing Pyramid
```
````
E2E Tests
/ \
Integration Tests
/ \
Frontend Unit Backend Unit
/ \
Frontend Unit Backend Unit
```text
### Test Organization
@@ -5233,20 +5232,26 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Frontend Tests:**
```
{{frontend_test_structure}}
```text
**Backend Tests:**
```
```text
{{backend_test_structure}}
```text
**E2E Tests:**
```
{{e2e_test_structure}}
```text
````text
### Test Examples
@@ -5258,11 +5263,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
frontend_test_example;
}
}
```
````
**Backend API Test:**
```typescript
````typescript
{
{
backend_test_example;
@@ -5278,7 +5283,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
e2e_test_example;
}
}
```
````
## Coding Standards
@@ -5319,7 +5324,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### Error Flow
```mermaid
````mermaid
{{error_flow_diagram}}
```text
@@ -5335,11 +5340,11 @@ interface ApiError {
requestId: string;
};
}
```
````
### Frontend Error Handling
```typescript
````typescript
{
{
frontend_error_handler;
@@ -5355,7 +5360,7 @@ interface ApiError {
backend_error_handler;
}
}
```
````
## Monitoring and Observability
@@ -7643,7 +7648,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
**TypeScript Interface:**
```typescript
````typescript
{
{
model_interface;
@@ -7689,7 +7694,7 @@ interface UserProfile {
bio?: string;
preferences: Record<string, any>;
}
```
````
**Relationships:**
@@ -7713,7 +7718,7 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),
^^CONDITION: has_rest_api^^
```yml
````yml
openapi: 3.0.0
info:
title:
@@ -7736,7 +7741,7 @@ servers:
```graphql
# GraphQL Schema
{{graphql_schema}}
```
````
^^/CONDITION: has_graphql_api^^

131
.bmad-core/web-bundles/teams/team-fullstack.txt
View File

@@ -156,27 +156,24 @@ dependencies:
CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
```yml
```yaml
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: Mary
id: analyst
title: Business Analyst
icon: 📊
whenToUse: "Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery"
customization:
whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery
customization: null
persona:
role: Insightful Analyst & Strategic Ideation Partner
style: Analytical, inquisitive, creative, facilitative, objective, data-informed
identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
focus: Research planning, ideation facilitation, strategic analysis, actionable insights
core_principles:
- Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
- Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
@@ -189,19 +186,16 @@ persona:
- Maintaining a Broad Perspective - Stay aware of market trends and dynamics
- Integrity of Information - Ensure accurate sourcing and representation
- Numbered Options Protocol - Always use numbered lists for selections
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) Strategic analysis consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*brainstorm {topic}" - Facilitate structured brainstorming session
- "*research {topic}" - Generate deep research prompt for investigation
- "*elicit" - Run advanced elicitation to clarify requirements
- "*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*brainstorm {topic}" - Facilitate structured brainstorming session'
- '*research {topic}" - Generate deep research prompt for investigation'
- '*elicit" - Run advanced elicitation to clarify requirements'
- '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
dependencies:
tasks:
- brainstorming-techniques
@@ -4408,7 +4402,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
**TypeScript Interface:**
```typescript
````typescript
{
{
model_interface;
@@ -4454,7 +4448,7 @@ interface UserProfile {
bio?: string;
preferences: Record<string, any>;
}
```
````
**Relationships:**
@@ -4478,7 +4472,7 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),
^^CONDITION: has_rest_api^^
```yml
````yml
openapi: 3.0.0
info:
title:
@@ -4501,7 +4495,7 @@ servers:
```graphql
# GraphQL Schema
{{graphql_schema}}
```
````
^^/CONDITION: has_graphql_api^^
@@ -6838,7 +6832,7 @@ Document the choice and key services that will be used.]]
Use appropriate diagram type for clarity.]]
```mermaid
````mermaid
{{architecture_diagram}}
```text
@@ -6951,7 +6945,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
model_interface;
}
}
```
````
**Relationships:**
@@ -6975,7 +6969,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
**TypeScript Interface:**
```typescript
````typescript
interface User {
id: string;
email: string;
@@ -7029,13 +7023,13 @@ servers:
'[object Object]': null
description:
'[object Object]': null
```
````
^^/CONDITION: has_rest_api^^
^^CONDITION: has_graphql_api^^
```graphql
````graphql
# GraphQL Schema
{{graphql_schema}}
```text
@@ -7051,7 +7045,7 @@ servers:
trpc_routers;
}
}
```
````
^^/CONDITION: has_trpc_api^^
@@ -7198,11 +7192,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```text
{{component_structure}}
```
```text
**Component Template:**
```typescript
````typescript
{
{
component_template;
@@ -7222,7 +7216,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
state_structure;
}
}
```
````
**State Management Patterns:**
@@ -7241,7 +7235,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Protected Route Pattern:**
```typescript
````typescript
{
{
protected_route_example;
@@ -7261,11 +7255,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
api_client_setup;
}
}
```
````
**Service Example:**
```typescript
````typescript
{
{
service_example;
@@ -7286,9 +7280,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
^^CONDITION: serverless^^
**Function Organization:**
```
````
{{function_structure}}
```text
````text
**Function Template:**
@@ -7298,7 +7294,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
function_template;
}
}
```
````
^^/CONDITION: serverless^^
@@ -7307,11 +7303,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```text
{{controller_structure}}
```
```text
**Controller Template:**
```typescript
````typescript
{
{
controller_template;
@@ -7329,11 +7325,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```sql
{{database_schema}}
```
````
**Data Access Layer:**
```typescript
````typescript
{
{
repository_pattern;
@@ -7349,11 +7345,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```mermaid
{{auth_flow_diagram}}
```
````
**Middleware/Guards:**
```typescript
````typescript
{
{
auth_middleware;
@@ -7419,7 +7415,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
├── package.json # Root package.json
├── {{monorepo_config}} # Monorepo configuration
└── README.md
```
````
@{example: vercel_structure}
apps/
@@ -7441,7 +7437,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Prerequisites:**
```bash
````bash
{{prerequisites_commands}}
```text
@@ -7449,11 +7445,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```bash
{{setup_commands}}
```
````
**Development Commands:**
```bash
````bash
# Start all services
{{start_all_command}}
@@ -7480,7 +7476,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
# Shared
{{shared_env_vars}}
```
````
## Deployment Architecture
@@ -7503,7 +7499,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### CI/CD Pipeline
```yml
````yaml
'[object Object]': null
```text
@@ -7563,12 +7559,15 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### Testing Pyramid
```
````
E2E Tests
/ \
Integration Tests
/ \
Frontend Unit Backend Unit
/ \
Frontend Unit Backend Unit
```text
### Test Organization
@@ -7576,20 +7575,26 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Frontend Tests:**
```
{{frontend_test_structure}}
```text
**Backend Tests:**
```
```text
{{backend_test_structure}}
```text
**E2E Tests:**
```
{{e2e_test_structure}}
```text
````text
### Test Examples
@@ -7601,11 +7606,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
frontend_test_example;
}
}
```
````
**Backend API Test:**
```typescript
````typescript
{
{
backend_test_example;
@@ -7621,7 +7626,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
e2e_test_example;
}
}
```
````
## Coding Standards
@@ -7662,7 +7667,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### Error Flow
```mermaid
````mermaid
{{error_flow_diagram}}
```text
@@ -7678,11 +7683,11 @@ interface ApiError {
requestId: string;
};
}
```
````
### Frontend Error Handling
```typescript
````typescript
{
{
frontend_error_handler;
@@ -7698,7 +7703,7 @@ interface ApiError {
backend_error_handler;
}
}
```
````
## Monitoring and Observability

131
.bmad-core/web-bundles/teams/team-no-ui.txt
View File

@@ -145,27 +145,24 @@ dependencies:
CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
```yml
```yaml
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: Mary
id: analyst
title: Business Analyst
icon: 📊
whenToUse: "Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery"
customization:
whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery
customization: null
persona:
role: Insightful Analyst & Strategic Ideation Partner
style: Analytical, inquisitive, creative, facilitative, objective, data-informed
identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
focus: Research planning, ideation facilitation, strategic analysis, actionable insights
core_principles:
- Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
- Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
@@ -178,19 +175,16 @@ persona:
- Maintaining a Broad Perspective - Stay aware of market trends and dynamics
- Integrity of Information - Ensure accurate sourcing and representation
- Numbered Options Protocol - Always use numbered lists for selections
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) Strategic analysis consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*brainstorm {topic}" - Facilitate structured brainstorming session
- "*research {topic}" - Generate deep research prompt for investigation
- "*elicit" - Run advanced elicitation to clarify requirements
- "*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*brainstorm {topic}" - Facilitate structured brainstorming session'
- '*research {topic}" - Generate deep research prompt for investigation'
- '*elicit" - Run advanced elicitation to clarify requirements'
- '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
dependencies:
tasks:
- brainstorming-techniques
@@ -4328,7 +4322,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
**TypeScript Interface:**
```typescript
````typescript
{
{
model_interface;
@@ -4374,7 +4368,7 @@ interface UserProfile {
bio?: string;
preferences: Record<string, any>;
}
```
````
**Relationships:**
@@ -4398,7 +4392,7 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),
^^CONDITION: has_rest_api^^
```yml
````yml
openapi: 3.0.0
info:
title:
@@ -4421,7 +4415,7 @@ servers:
```graphql
# GraphQL Schema
{{graphql_schema}}
```
````
^^/CONDITION: has_graphql_api^^
@@ -6283,7 +6277,7 @@ Document the choice and key services that will be used.]]
Use appropriate diagram type for clarity.]]
```mermaid
````mermaid
{{architecture_diagram}}
```text
@@ -6396,7 +6390,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
model_interface;
}
}
```
````
**Relationships:**
@@ -6420,7 +6414,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
**TypeScript Interface:**
```typescript
````typescript
interface User {
id: string;
email: string;
@@ -6474,13 +6468,13 @@ servers:
'[object Object]': null
description:
'[object Object]': null
```
````
^^/CONDITION: has_rest_api^^
^^CONDITION: has_graphql_api^^
```graphql
````graphql
# GraphQL Schema
{{graphql_schema}}
```text
@@ -6496,7 +6490,7 @@ servers:
trpc_routers;
}
}
```
````
^^/CONDITION: has_trpc_api^^
@@ -6643,11 +6637,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```text
{{component_structure}}
```
```text
**Component Template:**
```typescript
````typescript
{
{
component_template;
@@ -6667,7 +6661,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
state_structure;
}
}
```
````
**State Management Patterns:**
@@ -6686,7 +6680,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Protected Route Pattern:**
```typescript
````typescript
{
{
protected_route_example;
@@ -6706,11 +6700,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
api_client_setup;
}
}
```
````
**Service Example:**
```typescript
````typescript
{
{
service_example;
@@ -6731,9 +6725,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
^^CONDITION: serverless^^
**Function Organization:**
```
````
{{function_structure}}
```text
````text
**Function Template:**
@@ -6743,7 +6739,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
function_template;
}
}
```
````
^^/CONDITION: serverless^^
@@ -6752,11 +6748,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```text
{{controller_structure}}
```
```text
**Controller Template:**
```typescript
````typescript
{
{
controller_template;
@@ -6774,11 +6770,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```sql
{{database_schema}}
```
````
**Data Access Layer:**
```typescript
````typescript
{
{
repository_pattern;
@@ -6794,11 +6790,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```mermaid
{{auth_flow_diagram}}
```
````
**Middleware/Guards:**
```typescript
````typescript
{
{
auth_middleware;
@@ -6864,7 +6860,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
├── package.json # Root package.json
├── {{monorepo_config}} # Monorepo configuration
└── README.md
```
````
@{example: vercel_structure}
apps/
@@ -6886,7 +6882,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Prerequisites:**
```bash
````bash
{{prerequisites_commands}}
```text
@@ -6894,11 +6890,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
```bash
{{setup_commands}}
```
````
**Development Commands:**
```bash
````bash
# Start all services
{{start_all_command}}
@@ -6925,7 +6921,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
# Shared
{{shared_env_vars}}
```
````
## Deployment Architecture
@@ -6948,7 +6944,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### CI/CD Pipeline
```yml
````yaml
'[object Object]': null
```text
@@ -7008,12 +7004,15 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### Testing Pyramid
```
````
E2E Tests
/ \
Integration Tests
/ \
Frontend Unit Backend Unit
/ \
Frontend Unit Backend Unit
```text
### Test Organization
@@ -7021,20 +7020,26 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
**Frontend Tests:**
```
{{frontend_test_structure}}
```text
**Backend Tests:**
```
```text
{{backend_test_structure}}
```text
**E2E Tests:**
```
{{e2e_test_structure}}
```text
````text
### Test Examples
@@ -7046,11 +7051,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
frontend_test_example;
}
}
```
````
**Backend API Test:**
```typescript
````typescript
{
{
backend_test_example;
@@ -7066,7 +7071,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
e2e_test_example;
}
}
```
````
## Coding Standards
@@ -7107,7 +7112,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
### Error Flow
```mermaid
````mermaid
{{error_flow_diagram}}
```text
@@ -7123,11 +7128,11 @@ interface ApiError {
requestId: string;
};
}
```
````
### Frontend Error Handling
```typescript
````typescript
{
{
frontend_error_handler;
@@ -7143,7 +7148,7 @@ interface ApiError {
backend_error_handler;
}
}
```
````
## Monitoring and Observability

34
.claude/commands/analyst.md
View File

@@ -6,27 +6,24 @@ When this command is used, adopt the following agent persona:
CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
```yml
```yaml
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: Mary
id: analyst
title: Business Analyst
icon: 📊
whenToUse: "Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery"
customization:
whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery
customization: null
persona:
role: Insightful Analyst & Strategic Ideation Partner
style: Analytical, inquisitive, creative, facilitative, objective, data-informed
identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
focus: Research planning, ideation facilitation, strategic analysis, actionable insights
core_principles:
- Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
- Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
@@ -39,19 +36,16 @@ persona:
- Maintaining a Broad Perspective - Stay aware of market trends and dynamics
- Integrity of Information - Ensure accurate sourcing and representation
- Numbered Options Protocol - Always use numbered lists for selections
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) Strategic analysis consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*brainstorm {topic}" - Facilitate structured brainstorming session
- "*research {topic}" - Generate deep research prompt for investigation
- "*elicit" - Run advanced elicitation to clarify requirements
- "*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*brainstorm {topic}" - Facilitate structured brainstorming session'
- '*research {topic}" - Generate deep research prompt for investigation'
- '*elicit" - Run advanced elicitation to clarify requirements'
- '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
dependencies:
tasks:
- brainstorming-techniques

32
.cursor/rules/analyst.mdc
View File

@@ -14,25 +14,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: Mary
id: analyst
title: Business Analyst
icon: 📊
whenToUse: "Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery"
customization:
whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery
customization: null
persona:
role: Insightful Analyst & Strategic Ideation Partner
style: Analytical, inquisitive, creative, facilitative, objective, data-informed
identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
focus: Research planning, ideation facilitation, strategic analysis, actionable insights
core_principles:
- Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
- Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
@@ -45,19 +42,16 @@ persona:
- Maintaining a Broad Perspective - Stay aware of market trends and dynamics
- Integrity of Information - Ensure accurate sourcing and representation
- Numbered Options Protocol - Always use numbered lists for selections
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) Strategic analysis consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*brainstorm {topic}" - Facilitate structured brainstorming session
- "*research {topic}" - Generate deep research prompt for investigation
- "*elicit" - Run advanced elicitation to clarify requirements
- "*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*brainstorm {topic}" - Facilitate structured brainstorming session'
- '*research {topic}" - Generate deep research prompt for investigation'
- '*elicit" - Run advanced elicitation to clarify requirements'
- '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
dependencies:
tasks:
- brainstorming-techniques

32
.windsurf/rules/analyst.md
View File

@@ -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: Mary
id: analyst
title: Business Analyst
icon: 📊
whenToUse: "Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery"
customization:
whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery
customization: null
persona:
role: Insightful Analyst & Strategic Ideation Partner
style: Analytical, inquisitive, creative, facilitative, objective, data-informed
identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
focus: Research planning, ideation facilitation, strategic analysis, actionable insights
core_principles:
- Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
- Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
@@ -39,19 +36,16 @@ persona:
- Maintaining a Broad Perspective - Stay aware of market trends and dynamics
- Integrity of Information - Ensure accurate sourcing and representation
- Numbered Options Protocol - Always use numbered lists for selections
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) Strategic analysis consultation with advanced-elicitation
- "*create-doc {template}" - Create doc (no template = show available templates)
- "*brainstorm {topic}" - Facilitate structured brainstorming session
- "*research {topic}" - Generate deep research prompt for investigation
- "*elicit" - Run advanced elicitation to clarify requirements
- "*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona
- '*help" - Show: numbered list of the following commands to allow selection'
- '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
- '*create-doc {template}" - Create doc (no template = show available templates)'
- '*brainstorm {topic}" - Facilitate structured brainstorming session'
- '*research {topic}" - Generate deep research prompt for investigation'
- '*elicit" - Run advanced elicitation to clarify requirements'
- '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
dependencies:
tasks:
- brainstorming-techniques