From 38e23b1db57675244f7ea44816faea0843fec54e Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Sun, 17 Aug 2025 02:06:45 +0000 Subject: [PATCH] release: bump to v5.0.1 --- dist/agents/analyst.txt | 234 ++--- dist/agents/architect.txt | 286 +++--- dist/agents/bmad-master.txt | 672 +++++++------- dist/agents/pm.txt | 80 +- dist/agents/po.txt | 4 +- dist/agents/qa.txt | 18 +- dist/agents/sm.txt | 4 +- dist/agents/ux-expert.txt | 114 +-- .../agents/game-designer.txt | 64 +- .../agents/game-developer.txt | 12 +- .../agents/game-sm.txt | 38 +- .../teams/phaser-2d-nodejs-game-team.txt | 464 +++++----- .../agents/game-architect.txt | 40 +- .../agents/game-designer.txt | 126 +-- .../bmad-2d-unity-game-dev/agents/game-sm.txt | 18 +- .../teams/unity-2d-game-team.txt | 604 ++++++------ .../agents/infra-devops-platform.txt | 40 +- dist/teams/team-all.txt | 858 +++++++++--------- dist/teams/team-fullstack.txt | 842 ++++++++--------- dist/teams/team-ide-minimal.txt | 18 +- dist/teams/team-no-ui.txt | 640 ++++++------- package.json | 2 +- tools/installer/package.json | 2 +- 23 files changed, 2590 insertions(+), 2590 deletions(-) diff --git a/dist/agents/analyst.txt b/dist/agents/analyst.txt index 28120eb8..6f24d041 100644 --- a/dist/agents/analyst.txt +++ b/dist/agents/analyst.txt @@ -1101,24 +1101,24 @@ template: output: format: markdown filename: docs/brief.md - title: 'Project Brief: {{project_name}}' + title: "Project Brief: {{project_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Project Brief Elicitation Actions' + title: "Project Brief Elicitation Actions" options: - - 'Expand section with more specific details' - - 'Validate against similar successful products' - - 'Stress test assumptions with edge cases' - - 'Explore alternative solution approaches' - - 'Analyze resource/constraint trade-offs' - - 'Generate risk mitigation strategies' - - 'Challenge scope from MVP minimalist view' - - 'Brainstorm creative feature possibilities' - - 'If only we had [resource/capability/time]...' - - 'Proceed to next section' + - "Expand section with more specific details" + - "Validate against similar successful products" + - "Stress test assumptions with edge cases" + - "Explore alternative solution approaches" + - "Analyze resource/constraint trade-offs" + - "Generate risk mitigation strategies" + - "Challenge scope from MVP minimalist view" + - "Brainstorm creative feature possibilities" + - "If only we had [resource/capability/time]..." + - "Proceed to next section" sections: - id: introduction @@ -1140,7 +1140,7 @@ sections: - Primary problem being solved - Target market identification - Key value proposition - template: '{{executive_summary_content}}' + template: "{{executive_summary_content}}" - id: problem-statement title: Problem Statement @@ -1150,7 +1150,7 @@ sections: - Impact of the problem (quantify if possible) - Why existing solutions fall short - Urgency and importance of solving this now - template: '{{detailed_problem_description}}' + template: "{{detailed_problem_description}}" - id: proposed-solution title: Proposed Solution @@ -1160,7 +1160,7 @@ sections: - Key differentiators from existing solutions - Why this solution will succeed where others haven't - High-level vision for the product - template: '{{solution_description}}' + template: "{{solution_description}}" - id: target-users title: Target Users @@ -1172,12 +1172,12 @@ sections: - Goals they're trying to achieve sections: - id: primary-segment - title: 'Primary User Segment: {{segment_name}}' - template: '{{primary_user_description}}' + title: "Primary User Segment: {{segment_name}}" + template: "{{primary_user_description}}" - id: secondary-segment - title: 'Secondary User Segment: {{segment_name}}' + title: "Secondary User Segment: {{segment_name}}" condition: Has secondary user segment - template: '{{secondary_user_description}}' + template: "{{secondary_user_description}}" - id: goals-metrics title: Goals & Success Metrics @@ -1186,15 +1186,15 @@ sections: - id: business-objectives title: Business Objectives type: bullet-list - template: '- {{objective_with_metric}}' + template: "- {{objective_with_metric}}" - id: user-success-metrics title: User Success Metrics type: bullet-list - template: '- {{user_metric}}' + template: "- {{user_metric}}" - id: kpis title: Key Performance Indicators (KPIs) type: bullet-list - template: '- {{kpi}}: {{definition_and_target}}' + template: "- {{kpi}}: {{definition_and_target}}" - id: mvp-scope title: MVP Scope @@ -1203,14 +1203,14 @@ sections: - id: core-features title: Core Features (Must Have) type: bullet-list - template: '- **{{feature}}:** {{description_and_rationale}}' + template: "- **{{feature}}:** {{description_and_rationale}}" - id: out-of-scope title: Out of Scope for MVP type: bullet-list - template: '- {{feature_or_capability}}' + template: "- {{feature_or_capability}}" - id: mvp-success-criteria title: MVP Success Criteria - template: '{{mvp_success_definition}}' + template: "{{mvp_success_definition}}" - id: post-mvp-vision title: Post-MVP Vision @@ -1218,13 +1218,13 @@ sections: sections: - id: phase-2-features title: Phase 2 Features - template: '{{next_priority_features}}' + template: "{{next_priority_features}}" - id: long-term-vision title: Long-term Vision - template: '{{one_two_year_vision}}' + template: "{{one_two_year_vision}}" - id: expansion-opportunities title: Expansion Opportunities - template: '{{potential_expansions}}' + template: "{{potential_expansions}}" - id: technical-considerations title: Technical Considerations @@ -1265,7 +1265,7 @@ sections: - id: key-assumptions title: Key Assumptions type: bullet-list - template: '- {{assumption}}' + template: "- {{assumption}}" - id: risks-questions title: Risks & Open Questions @@ -1274,15 +1274,15 @@ sections: - id: key-risks title: Key Risks type: bullet-list - template: '- **{{risk}}:** {{description_and_impact}}' + template: "- **{{risk}}:** {{description_and_impact}}" - id: open-questions title: Open Questions type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: research-areas title: Areas Needing Further Research type: bullet-list - template: '- {{research_topic}}' + template: "- {{research_topic}}" - id: appendices title: Appendices @@ -1299,10 +1299,10 @@ sections: - id: stakeholder-input title: B. Stakeholder Input condition: Has stakeholder feedback - template: '{{stakeholder_feedback}}' + template: "{{stakeholder_feedback}}" - id: references title: C. References - template: '{{relevant_links_and_docs}}' + template: "{{relevant_links_and_docs}}" - id: next-steps title: Next Steps @@ -1310,7 +1310,7 @@ sections: - id: immediate-actions title: Immediate Actions type: numbered-list - template: '{{action_item}}' + template: "{{action_item}}" - id: pm-handoff title: PM Handoff content: | @@ -1325,24 +1325,24 @@ template: output: format: markdown filename: docs/market-research.md - title: 'Market Research Report: {{project_product_name}}' + title: "Market Research Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Market Research Elicitation Actions' + title: "Market Research Elicitation Actions" options: - - 'Expand market sizing calculations with sensitivity analysis' - - 'Deep dive into a specific customer segment' - - 'Analyze an emerging market trend in detail' - - 'Compare this market to an analogous market' - - 'Stress test market assumptions' - - 'Explore adjacent market opportunities' - - 'Challenge market definition and boundaries' - - 'Generate strategic scenarios (best/base/worst case)' - - 'If only we had considered [X market factor]...' - - 'Proceed to next section' + - "Expand market sizing calculations with sensitivity analysis" + - "Deep dive into a specific customer segment" + - "Analyze an emerging market trend in detail" + - "Compare this market to an analogous market" + - "Stress test market assumptions" + - "Explore adjacent market opportunities" + - "Challenge market definition and boundaries" + - "Generate strategic scenarios (best/base/worst case)" + - "If only we had considered [X market factor]..." + - "Proceed to next section" sections: - id: executive-summary @@ -1424,7 +1424,7 @@ sections: repeatable: true sections: - id: segment - title: 'Segment {{segment_number}}: {{segment_name}}' + title: "Segment {{segment_number}}: {{segment_name}}" template: | - **Description:** {{brief_overview}} - **Size:** {{number_of_customers_market_value}} @@ -1493,20 +1493,20 @@ sections: instruction: Analyze each force with specific evidence and implications sections: - id: supplier-power - title: 'Supplier Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Supplier Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: buyer-power - title: 'Buyer Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Buyer Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: competitive-rivalry - title: 'Competitive Rivalry: {{intensity_level}}' - template: '{{analysis_and_implications}}' + title: "Competitive Rivalry: {{intensity_level}}" + template: "{{analysis_and_implications}}" - id: threat-new-entry - title: 'Threat of New Entry: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of New Entry: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: threat-substitutes - title: 'Threat of Substitutes: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of Substitutes: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: adoption-lifecycle title: Technology Adoption Lifecycle Stage instruction: | @@ -1524,7 +1524,7 @@ sections: repeatable: true sections: - id: opportunity - title: 'Opportunity {{opportunity_number}}: {{name}}' + title: "Opportunity {{opportunity_number}}: {{name}}" template: | - **Description:** {{what_is_the_opportunity}} - **Size/Potential:** {{quantified_potential}} @@ -1580,24 +1580,24 @@ template: output: format: markdown filename: docs/competitor-analysis.md - title: 'Competitive Analysis Report: {{project_product_name}}' + title: "Competitive Analysis Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Competitive Analysis Elicitation Actions' + title: "Competitive Analysis Elicitation Actions" options: - "Deep dive on a specific competitor's strategy" - - 'Analyze competitive dynamics in a specific segment' - - 'War game competitive responses to your moves' - - 'Explore partnership vs. competition scenarios' - - 'Stress test differentiation claims' - - 'Analyze disruption potential (yours or theirs)' - - 'Compare to competition in adjacent markets' - - 'Generate win/loss analysis insights' + - "Analyze competitive dynamics in a specific segment" + - "War game competitive responses to your moves" + - "Explore partnership vs. competition scenarios" + - "Stress test differentiation claims" + - "Analyze disruption potential (yours or theirs)" + - "Compare to competition in adjacent markets" + - "Generate win/loss analysis insights" - "If only we had known about [competitor X's plan]..." - - 'Proceed to next section' + - "Proceed to next section" sections: - id: executive-summary @@ -1664,7 +1664,7 @@ sections: repeatable: true sections: - id: competitor - title: '{{competitor_name}} - Priority {{priority_level}}' + title: "{{competitor_name}} - Priority {{priority_level}}" sections: - id: company-overview title: Company Overview @@ -1696,11 +1696,11 @@ sections: - id: strengths title: Strengths type: bullet-list - template: '- {{strength}}' + template: "- {{strength}}" - id: weaknesses title: Weaknesses type: bullet-list - template: '- {{weakness}}' + template: "- {{weakness}}" - id: market-position title: Market Position & Performance template: | @@ -1718,35 +1718,35 @@ sections: type: table columns: [ - 'Feature Category', - '{{your_company}}', - '{{competitor_1}}', - '{{competitor_2}}', - '{{competitor_3}}', + "Feature Category", + "{{your_company}}", + "{{competitor_1}}", + "{{competitor_2}}", + "{{competitor_3}}", ] rows: - - category: 'Core Functionality' + - category: "Core Functionality" items: - - ['Feature A', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - ['Feature B', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - category: 'User Experience' + - ["Feature A", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - ["Feature B", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - category: "User Experience" items: - - ['Mobile App', '{{rating}}', '{{rating}}', '{{rating}}', '{{rating}}'] - - ['Onboarding Time', '{{time}}', '{{time}}', '{{time}}', '{{time}}'] - - category: 'Integration & Ecosystem' + - ["Mobile App", "{{rating}}", "{{rating}}", "{{rating}}", "{{rating}}"] + - ["Onboarding Time", "{{time}}", "{{time}}", "{{time}}", "{{time}}"] + - category: "Integration & Ecosystem" items: - [ - 'API Availability', - '{{availability}}', - '{{availability}}', - '{{availability}}', - '{{availability}}', + "API Availability", + "{{availability}}", + "{{availability}}", + "{{availability}}", + "{{availability}}", ] - - ['Third-party Integrations', '{{number}}', '{{number}}', '{{number}}', '{{number}}'] - - category: 'Pricing & Plans' + - ["Third-party Integrations", "{{number}}", "{{number}}", "{{number}}", "{{number}}"] + - category: "Pricing & Plans" items: - - ['Starting Price', '{{price}}', '{{price}}', '{{price}}', '{{price}}'] - - ['Free Tier', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}'] + - ["Starting Price", "{{price}}", "{{price}}", "{{price}}", "{{price}}"] + - ["Free Tier", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}"] - id: swot-comparison title: SWOT Comparison instruction: Create SWOT analysis for your solution vs. top competitors @@ -1759,7 +1759,7 @@ sections: - **Opportunities:** {{opportunities}} - **Threats:** {{threats}} - id: vs-competitor - title: 'vs. {{main_competitor}}' + title: "vs. {{main_competitor}}" template: | - **Competitive Advantages:** {{your_advantages}} - **Competitive Disadvantages:** {{their_advantages}} @@ -1889,7 +1889,7 @@ template: output: format: markdown filename: docs/brainstorming-session-results.md - title: 'Brainstorming Session Results' + title: "Brainstorming Session Results" workflow: mode: non-interactive @@ -1914,38 +1914,38 @@ sections: **Total Ideas Generated:** {{total_ideas}} - id: key-themes - title: 'Key Themes Identified:' + title: "Key Themes Identified:" type: bullet-list - template: '- {{theme}}' + template: "- {{theme}}" - id: technique-sessions title: Technique Sessions repeatable: true sections: - id: technique - title: '{{technique_name}} - {{duration}}' + title: "{{technique_name}} - {{duration}}" sections: - id: description - template: '**Description:** {{technique_description}}' + template: "**Description:** {{technique_description}}" - id: ideas-generated - title: 'Ideas Generated:' + title: "Ideas Generated:" type: numbered-list - template: '{{idea}}' + template: "{{idea}}" - id: insights - title: 'Insights Discovered:' + title: "Insights Discovered:" type: bullet-list - template: '- {{insight}}' + template: "- {{insight}}" - id: connections - title: 'Notable Connections:' + title: "Notable Connections:" type: bullet-list - template: '- {{connection}}' + template: "- {{connection}}" - id: idea-categorization title: Idea Categorization sections: - id: immediate-opportunities title: Immediate Opportunities - content: '*Ideas ready to implement now*' + content: "*Ideas ready to implement now*" repeatable: true type: numbered-list template: | @@ -1955,7 +1955,7 @@ sections: - Resources needed: {{requirements}} - id: future-innovations title: Future Innovations - content: '*Ideas requiring development/research*' + content: "*Ideas requiring development/research*" repeatable: true type: numbered-list template: | @@ -1965,7 +1965,7 @@ sections: - Timeline estimate: {{timeline}} - id: moonshots title: Moonshots - content: '*Ambitious, transformative concepts*' + content: "*Ambitious, transformative concepts*" repeatable: true type: numbered-list template: | @@ -1975,9 +1975,9 @@ sections: - Challenges to overcome: {{challenges}} - id: insights-learnings title: Insights & Learnings - content: '*Key realizations from the session*' + content: "*Key realizations from the session*" type: bullet-list - template: '- {{insight}}: {{description_and_implications}}' + template: "- {{insight}}: {{description_and_implications}}" - id: action-planning title: Action Planning @@ -1986,21 +1986,21 @@ sections: title: Top 3 Priority Ideas sections: - id: priority-1 - title: '#1 Priority: {{idea_name}}' + title: "#1 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-2 - title: '#2 Priority: {{idea_name}}' + title: "#2 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-3 - title: '#3 Priority: {{idea_name}}' + title: "#3 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} @@ -2013,19 +2013,19 @@ sections: - id: what-worked title: What Worked Well type: bullet-list - template: '- {{aspect}}' + template: "- {{aspect}}" - id: areas-exploration title: Areas for Further Exploration type: bullet-list - template: '- {{area}}: {{reason}}' + template: "- {{area}}: {{reason}}" - id: recommended-techniques title: Recommended Follow-up Techniques type: bullet-list - template: '- {{technique}}: {{reason}}' + template: "- {{technique}}: {{reason}}" - id: questions-emerged title: Questions That Emerged type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: next-session title: Next Session Planning template: | diff --git a/dist/agents/architect.txt b/dist/agents/architect.txt index 7bf3a8ef..d50c89b7 100644 --- a/dist/agents/architect.txt +++ b/dist/agents/architect.txt @@ -933,7 +933,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Architecture Document' + title: "{{project_name}} Architecture Document" workflow: mode: interactive @@ -1044,11 +1044,11 @@ sections: - Code organization patterns (Dependency Injection, Repository, Module, Factory) - Data patterns (Event Sourcing, Saga, Database per Service) - Communication patterns (REST, GraphQL, Message Queue, Pub/Sub) - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - - '**Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling' - - '**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility' - - '**Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience' + - "**Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling" + - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility" + - "**Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience" - id: tech-stack title: Tech Stack @@ -1086,9 +1086,9 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Populate the technology stack table with all relevant technologies examples: - - '| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |' - - '| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |' - - '| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |' + - "| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |" + - "| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |" + - "| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |" - id: data-models title: Data Models @@ -1106,7 +1106,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -1137,7 +1137,7 @@ sections: sections: - id: component-list repeatable: true - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} @@ -1175,7 +1175,7 @@ sections: repeatable: true sections: - id: api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -1300,12 +1300,12 @@ sections: - id: environments title: Environments repeatable: true - template: '- **{{env_name}}:** {{env_purpose}} - {{env_details}}' + template: "- **{{env_name}}:** {{env_purpose}} - {{env_details}}" - id: promotion-flow title: Environment Promotion Flow type: code language: text - template: '{{promotion_flow_diagram}}' + template: "{{promotion_flow_diagram}}" - id: rollback-strategy title: Rollback Strategy template: | @@ -1401,16 +1401,16 @@ sections: Avoid obvious rules like "use SOLID principles" or "write clean code" repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" - id: language-specifics title: Language-Specific Guidelines condition: Critical language-specific rules needed instruction: Add ONLY if critical for preventing AI mistakes. Most teams don't need this section. sections: - id: language-rules - title: '{{language_name}} Specifics' + title: "{{language_name}} Specifics" repeatable: true - template: '- **{{rule_topic}}:** {{rule_detail}}' + template: "- **{{rule_topic}}:** {{rule_detail}}" - id: test-strategy title: Test Strategy and Standards @@ -1458,9 +1458,9 @@ sections: - **Test Infrastructure:** - **{{dependency_name}}:** {{test_approach}} ({{test_tool}}) examples: - - '**Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration' - - '**Message Queue:** Embedded Kafka for tests' - - '**External APIs:** WireMock for stubbing' + - "**Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration" + - "**Message Queue:** Embedded Kafka for tests" + - "**External APIs:** WireMock for stubbing" - id: e2e-tests title: End-to-End Tests template: | @@ -1586,7 +1586,7 @@ template: output: format: markdown filename: docs/ui-architecture.md - title: '{{project_name}} Frontend Architecture Document' + title: "{{project_name}} Frontend Architecture Document" workflow: mode: interactive @@ -1654,29 +1654,29 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Fill in appropriate technology choices based on the selected framework and project requirements. rows: - - ['Framework', '{{framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['UI Library', '{{ui_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Framework", "{{framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["UI Library", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'State Management', - '{{state_management}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "State Management", + "{{state_management}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['Routing', '{{routing_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Build Tool', '{{build_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Styling', '{{styling_solution}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Testing', '{{test_framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Routing", "{{routing_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Styling", "{{styling_solution}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Testing", "{{test_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Component Library', - '{{component_lib}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Component Library", + "{{component_lib}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['Form Handling', '{{form_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Animation', '{{animation_lib}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Dev Tools', '{{dev_tools}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Form Handling", "{{form_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Animation", "{{animation_lib}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Dev Tools", "{{dev_tools}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - id: project-structure title: Project Structure @@ -1770,12 +1770,12 @@ sections: title: Testing Best Practices type: numbered-list items: - - '**Unit Tests**: Test individual components in isolation' - - '**Integration Tests**: Test component interactions' - - '**E2E Tests**: Test critical user flows (using Cypress/Playwright)' - - '**Coverage Goals**: Aim for 80% code coverage' - - '**Test Structure**: Arrange-Act-Assert pattern' - - '**Mock External Dependencies**: API calls, routing, state management' + - "**Unit Tests**: Test individual components in isolation" + - "**Integration Tests**: Test component interactions" + - "**E2E Tests**: Test critical user flows (using Cypress/Playwright)" + - "**Coverage Goals**: Aim for 80% code coverage" + - "**Test Structure**: Arrange-Act-Assert pattern" + - "**Mock External Dependencies**: API calls, routing, state management" - id: environment-configuration title: Environment Configuration @@ -1807,7 +1807,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Fullstack Architecture Document' + title: "{{project_name}} Fullstack Architecture Document" workflow: mode: interactive @@ -1928,12 +1928,12 @@ sections: For each pattern, provide recommendation and rationale. repeatable: true - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - - '**Jamstack Architecture:** Static site generation with serverless APIs - _Rationale:_ Optimal performance and scalability for content-heavy applications' - - '**Component-Based UI:** Reusable React components with TypeScript - _Rationale:_ Maintainability and type safety across large codebases' - - '**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility' - - '**API Gateway Pattern:** Single entry point for all API calls - _Rationale:_ Centralized auth, rate limiting, and monitoring' + - "**Jamstack Architecture:** Static site generation with serverless APIs - _Rationale:_ Optimal performance and scalability for content-heavy applications" + - "**Component-Based UI:** Reusable React components with TypeScript - _Rationale:_ Maintainability and type safety across large codebases" + - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility" + - "**API Gateway Pattern:** Single entry point for all API calls - _Rationale:_ Centralized auth, rate limiting, and monitoring" - id: tech-stack title: Tech Stack @@ -1957,45 +1957,45 @@ sections: type: table columns: [Category, Technology, Version, Purpose, Rationale] rows: - - ['Frontend Language', '{{fe_language}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Frontend Language", "{{fe_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Frontend Framework', - '{{fe_framework}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Frontend Framework", + "{{fe_framework}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - [ - 'UI Component Library', - '{{ui_library}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "UI Component Library", + "{{ui_library}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['State Management', '{{state_mgmt}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Backend Language', '{{be_language}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["State Management", "{{state_mgmt}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Backend Language", "{{be_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Backend Framework', - '{{be_framework}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Backend Framework", + "{{be_framework}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['API Style', '{{api_style}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Database', '{{database}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Cache', '{{cache}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['File Storage', '{{storage}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Authentication', '{{auth}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Frontend Testing', '{{fe_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Backend Testing', '{{be_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['E2E Testing', '{{e2e_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Build Tool', '{{build_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Bundler', '{{bundler}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['IaC Tool', '{{iac_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['CI/CD', '{{cicd}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Monitoring', '{{monitoring}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Logging', '{{logging}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['CSS Framework', '{{css_framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["API Style", "{{api_style}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Database", "{{database}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Cache", "{{cache}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["File Storage", "{{storage}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Authentication", "{{auth}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Frontend Testing", "{{fe_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Backend Testing", "{{be_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["E2E Testing", "{{e2e_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Bundler", "{{bundler}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["IaC Tool", "{{iac_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["CI/CD", "{{cicd}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Monitoring", "{{monitoring}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Logging", "{{logging}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["CSS Framework", "{{css_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - id: data-models title: Data Models @@ -2014,7 +2014,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -2026,11 +2026,11 @@ sections: title: TypeScript Interface type: code language: typescript - template: '{{model_interface}}' + template: "{{model_interface}}" - id: relationships title: Relationships type: bullet-list - template: '- {{relationship}}' + template: "- {{relationship}}" - id: api-spec title: API Specification @@ -2067,13 +2067,13 @@ sections: condition: API style is GraphQL type: code language: graphql - template: '{{graphql_schema}}' + template: "{{graphql_schema}}" - id: trpc-api title: tRPC Router Definitions condition: API style is tRPC type: code language: typescript - template: '{{trpc_routers}}' + template: "{{trpc_routers}}" - id: components title: Components @@ -2094,7 +2094,7 @@ sections: sections: - id: component-list repeatable: true - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} @@ -2132,7 +2132,7 @@ sections: repeatable: true sections: - id: api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -2189,12 +2189,12 @@ sections: title: Component Organization type: code language: text - template: '{{component_structure}}' + template: "{{component_structure}}" - id: component-template title: Component Template type: code language: typescript - template: '{{component_template}}' + template: "{{component_template}}" - id: state-management title: State Management Architecture instruction: Detail state management approach based on chosen solution. @@ -2203,11 +2203,11 @@ sections: title: State Structure type: code language: typescript - template: '{{state_structure}}' + template: "{{state_structure}}" - id: state-patterns title: State Management Patterns type: bullet-list - template: '- {{pattern}}' + template: "- {{pattern}}" - id: routing-architecture title: Routing Architecture instruction: Define routing structure based on framework choice. @@ -2216,12 +2216,12 @@ sections: title: Route Organization type: code language: text - template: '{{route_structure}}' + template: "{{route_structure}}" - id: protected-routes title: Protected Route Pattern type: code language: typescript - template: '{{protected_route_example}}' + template: "{{protected_route_example}}" - id: frontend-services title: Frontend Services Layer instruction: Define how frontend communicates with backend. @@ -2230,12 +2230,12 @@ sections: title: API Client Setup type: code language: typescript - template: '{{api_client_setup}}' + template: "{{api_client_setup}}" - id: service-example title: Service Example type: code language: typescript - template: '{{service_example}}' + template: "{{service_example}}" - id: backend-architecture title: Backend Architecture @@ -2253,12 +2253,12 @@ sections: title: Function Organization type: code language: text - template: '{{function_structure}}' + template: "{{function_structure}}" - id: function-template title: Function Template type: code language: typescript - template: '{{function_template}}' + template: "{{function_template}}" - id: traditional-server condition: Traditional server architecture chosen sections: @@ -2266,12 +2266,12 @@ sections: title: Controller/Route Organization type: code language: text - template: '{{controller_structure}}' + template: "{{controller_structure}}" - id: controller-template title: Controller Template type: code language: typescript - template: '{{controller_template}}' + template: "{{controller_template}}" - id: database-architecture title: Database Architecture instruction: Define database schema and access patterns. @@ -2280,12 +2280,12 @@ sections: title: Schema Design type: code language: sql - template: '{{database_schema}}' + template: "{{database_schema}}" - id: data-access-layer title: Data Access Layer type: code language: typescript - template: '{{repository_pattern}}' + template: "{{repository_pattern}}" - id: auth-architecture title: Authentication and Authorization instruction: Define auth implementation details. @@ -2294,12 +2294,12 @@ sections: title: Auth Flow type: mermaid mermaid_type: sequence - template: '{{auth_flow_diagram}}' + template: "{{auth_flow_diagram}}" - id: auth-middleware title: Middleware/Guards type: code language: typescript - template: '{{auth_middleware}}' + template: "{{auth_middleware}}" - id: unified-project-structure title: Unified Project Structure @@ -2375,12 +2375,12 @@ sections: title: Prerequisites type: code language: bash - template: '{{prerequisites_commands}}' + template: "{{prerequisites_commands}}" - id: initial-setup title: Initial Setup type: code language: bash - template: '{{setup_commands}}' + template: "{{setup_commands}}" - id: dev-commands title: Development Commands type: code @@ -2436,15 +2436,15 @@ sections: title: CI/CD Pipeline type: code language: yaml - template: '{{cicd_pipeline_config}}' + template: "{{cicd_pipeline_config}}" - id: environments title: Environments type: table columns: [Environment, Frontend URL, Backend URL, Purpose] rows: - - ['Development', '{{dev_fe_url}}', '{{dev_be_url}}', 'Local development'] - - ['Staging', '{{staging_fe_url}}', '{{staging_be_url}}', 'Pre-production testing'] - - ['Production', '{{prod_fe_url}}', '{{prod_be_url}}', 'Live environment'] + - ["Development", "{{dev_fe_url}}", "{{dev_be_url}}", "Local development"] + - ["Staging", "{{staging_fe_url}}", "{{staging_be_url}}", "Pre-production testing"] + - ["Production", "{{prod_fe_url}}", "{{prod_be_url}}", "Live environment"] - id: security-performance title: Security and Performance @@ -2503,17 +2503,17 @@ sections: title: Frontend Tests type: code language: text - template: '{{frontend_test_structure}}' + template: "{{frontend_test_structure}}" - id: backend-tests title: Backend Tests type: code language: text - template: '{{backend_test_structure}}' + template: "{{backend_test_structure}}" - id: e2e-tests title: E2E Tests type: code language: text - template: '{{e2e_test_structure}}' + template: "{{e2e_test_structure}}" - id: test-examples title: Test Examples sections: @@ -2521,17 +2521,17 @@ sections: title: Frontend Component Test type: code language: typescript - template: '{{frontend_test_example}}' + template: "{{frontend_test_example}}" - id: backend-test title: Backend API Test type: code language: typescript - template: '{{backend_test_example}}' + template: "{{backend_test_example}}" - id: e2e-test title: E2E Test type: code language: typescript - template: '{{e2e_test_example}}' + template: "{{e2e_test_example}}" - id: coding-standards title: Coding Standards @@ -2541,22 +2541,22 @@ sections: - id: critical-rules title: Critical Fullstack Rules repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" examples: - - '**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' + - "**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" - id: naming-conventions title: Naming Conventions type: table columns: [Element, Frontend, Backend, Example] rows: - - ['Components', 'PascalCase', '-', '`UserProfile.tsx`'] - - ['Hooks', "camelCase with 'use'", '-', '`useAuth.ts`'] - - ['API Routes', '-', 'kebab-case', '`/api/user-profile`'] - - ['Database Tables', '-', 'snake_case', '`user_profiles`'] + - ["Components", "PascalCase", "-", "`UserProfile.tsx`"] + - ["Hooks", "camelCase with 'use'", "-", "`useAuth.ts`"] + - ["API Routes", "-", "kebab-case", "`/api/user-profile`"] + - ["Database Tables", "-", "snake_case", "`user_profiles`"] - id: error-handling title: Error Handling Strategy @@ -2567,7 +2567,7 @@ sections: title: Error Flow type: mermaid mermaid_type: sequence - template: '{{error_flow_diagram}}' + template: "{{error_flow_diagram}}" - id: error-format title: Error Response Format type: code @@ -2586,12 +2586,12 @@ sections: title: Frontend Error Handling type: code language: typescript - template: '{{frontend_error_handler}}' + template: "{{frontend_error_handler}}" - id: backend-error-handling title: Backend Error Handling type: code language: typescript - template: '{{backend_error_handler}}' + template: "{{backend_error_handler}}" - id: monitoring title: Monitoring and Observability @@ -2633,7 +2633,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Brownfield Enhancement Architecture' + title: "{{project_name}} Brownfield Enhancement Architecture" workflow: mode: interactive @@ -2691,11 +2691,11 @@ sections: - id: available-docs title: Available Documentation type: bullet-list - template: '- {{existing_docs_summary}}' + template: "- {{existing_docs_summary}}" - id: constraints title: Identified Constraints type: bullet-list - template: '- {{constraint}}' + template: "- {{constraint}}" - id: changelog title: Change Log type: table @@ -2775,7 +2775,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} **Integration:** {{integration_with_existing}} @@ -2818,7 +2818,7 @@ sections: repeatable: true sections: - id: component - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} **Integration Points:** {{integration_points}} @@ -2861,7 +2861,7 @@ sections: repeatable: true sections: - id: endpoint - title: '{{endpoint_name}}' + title: "{{endpoint_name}}" template: | - **Method:** {{http_method}} - **Endpoint:** {{endpoint_path}} @@ -2872,12 +2872,12 @@ sections: title: Request type: code language: json - template: '{{request_schema}}' + template: "{{request_schema}}" - id: response title: Response type: code language: json - template: '{{response_schema}}' + template: "{{response_schema}}" - id: external-api-integration title: External API Integration @@ -2886,7 +2886,7 @@ sections: repeatable: true sections: - id: external-api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -2915,7 +2915,7 @@ sections: type: code language: plaintext instruction: Document relevant parts of current structure - template: '{{existing_structure_relevant_parts}}' + template: "{{existing_structure_relevant_parts}}" - id: new-file-organization title: New File Organization type: code @@ -2990,7 +2990,7 @@ sections: title: Enhancement-Specific Standards condition: New patterns needed for enhancement repeatable: true - template: '- **{{standard_name}}:** {{standard_description}}' + template: "- **{{standard_name}}:** {{standard_description}}" - id: integration-rules title: Critical Integration Rules template: | diff --git a/dist/agents/bmad-master.txt b/dist/agents/bmad-master.txt index 159444c1..0e1b5b28 100644 --- a/dist/agents/bmad-master.txt +++ b/dist/agents/bmad-master.txt @@ -2131,7 +2131,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Architecture Document' + title: "{{project_name}} Architecture Document" workflow: mode: interactive @@ -2242,11 +2242,11 @@ sections: - Code organization patterns (Dependency Injection, Repository, Module, Factory) - Data patterns (Event Sourcing, Saga, Database per Service) - Communication patterns (REST, GraphQL, Message Queue, Pub/Sub) - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - - '**Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling' - - '**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility' - - '**Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience' + - "**Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling" + - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility" + - "**Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience" - id: tech-stack title: Tech Stack @@ -2284,9 +2284,9 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Populate the technology stack table with all relevant technologies examples: - - '| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |' - - '| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |' - - '| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |' + - "| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |" + - "| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |" + - "| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |" - id: data-models title: Data Models @@ -2304,7 +2304,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -2335,7 +2335,7 @@ sections: sections: - id: component-list repeatable: true - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} @@ -2373,7 +2373,7 @@ sections: repeatable: true sections: - id: api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -2498,12 +2498,12 @@ sections: - id: environments title: Environments repeatable: true - template: '- **{{env_name}}:** {{env_purpose}} - {{env_details}}' + template: "- **{{env_name}}:** {{env_purpose}} - {{env_details}}" - id: promotion-flow title: Environment Promotion Flow type: code language: text - template: '{{promotion_flow_diagram}}' + template: "{{promotion_flow_diagram}}" - id: rollback-strategy title: Rollback Strategy template: | @@ -2599,16 +2599,16 @@ sections: Avoid obvious rules like "use SOLID principles" or "write clean code" repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" - id: language-specifics title: Language-Specific Guidelines condition: Critical language-specific rules needed instruction: Add ONLY if critical for preventing AI mistakes. Most teams don't need this section. sections: - id: language-rules - title: '{{language_name}} Specifics' + title: "{{language_name}} Specifics" repeatable: true - template: '- **{{rule_topic}}:** {{rule_detail}}' + template: "- **{{rule_topic}}:** {{rule_detail}}" - id: test-strategy title: Test Strategy and Standards @@ -2656,9 +2656,9 @@ sections: - **Test Infrastructure:** - **{{dependency_name}}:** {{test_approach}} ({{test_tool}}) examples: - - '**Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration' - - '**Message Queue:** Embedded Kafka for tests' - - '**External APIs:** WireMock for stubbing' + - "**Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration" + - "**Message Queue:** Embedded Kafka for tests" + - "**External APIs:** WireMock for stubbing" - id: e2e-tests title: End-to-End Tests template: | @@ -2784,7 +2784,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Brownfield Enhancement Architecture' + title: "{{project_name}} Brownfield Enhancement Architecture" workflow: mode: interactive @@ -2842,11 +2842,11 @@ sections: - id: available-docs title: Available Documentation type: bullet-list - template: '- {{existing_docs_summary}}' + template: "- {{existing_docs_summary}}" - id: constraints title: Identified Constraints type: bullet-list - template: '- {{constraint}}' + template: "- {{constraint}}" - id: changelog title: Change Log type: table @@ -2926,7 +2926,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} **Integration:** {{integration_with_existing}} @@ -2969,7 +2969,7 @@ sections: repeatable: true sections: - id: component - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} **Integration Points:** {{integration_points}} @@ -3012,7 +3012,7 @@ sections: repeatable: true sections: - id: endpoint - title: '{{endpoint_name}}' + title: "{{endpoint_name}}" template: | - **Method:** {{http_method}} - **Endpoint:** {{endpoint_path}} @@ -3023,12 +3023,12 @@ sections: title: Request type: code language: json - template: '{{request_schema}}' + template: "{{request_schema}}" - id: response title: Response type: code language: json - template: '{{response_schema}}' + template: "{{response_schema}}" - id: external-api-integration title: External API Integration @@ -3037,7 +3037,7 @@ sections: repeatable: true sections: - id: external-api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -3066,7 +3066,7 @@ sections: type: code language: plaintext instruction: Document relevant parts of current structure - template: '{{existing_structure_relevant_parts}}' + template: "{{existing_structure_relevant_parts}}" - id: new-file-organization title: New File Organization type: code @@ -3141,7 +3141,7 @@ sections: title: Enhancement-Specific Standards condition: New patterns needed for enhancement repeatable: true - template: '- **{{standard_name}}:** {{standard_description}}' + template: "- **{{standard_name}}:** {{standard_description}}" - id: integration-rules title: Critical Integration Rules template: | @@ -3263,7 +3263,7 @@ template: output: format: markdown filename: docs/prd.md - title: '{{project_name}} Brownfield Enhancement PRD' + title: "{{project_name}} Brownfield Enhancement PRD" workflow: mode: interactive @@ -3326,7 +3326,7 @@ sections: - External API Documentation [[LLM: If from document-project, check ✓]] - UX/UI Guidelines [[LLM: May not be in document-project]] - Technical Debt Documentation [[LLM: If from document-project, check ✓]] - - 'Other: {{other_docs}}' + - "Other: {{other_docs}}" instruction: | - If document-project was already run: "Using existing project analysis from document-project output." - If critical documentation is missing and no document-project: "I recommend running the document-project task first..." @@ -3346,7 +3346,7 @@ sections: - UI/UX Overhaul - Technology Stack Upgrade - Bug Fix and Stability Improvements - - 'Other: {{other_type}}' + - "Other: {{other_type}}" - id: enhancement-description title: Enhancement Description instruction: 2-3 sentences describing what the user wants to add or change @@ -3387,29 +3387,29 @@ sections: prefix: FR instruction: Each Requirement will be a bullet markdown with identifier starting with FR examples: - - 'FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality.' + - "FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality." - id: non-functional title: Non Functional type: numbered-list prefix: NFR instruction: Each Requirement will be a bullet markdown with identifier starting with NFR. Include constraints from existing system examples: - - 'NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%.' + - "NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%." - id: compatibility title: Compatibility Requirements instruction: Critical for brownfield - what must remain compatible type: numbered-list prefix: CR - template: '{{requirement}}: {{description}}' + template: "{{requirement}}: {{description}}" items: - id: cr1 - template: 'CR1: {{existing_api_compatibility}}' + template: "CR1: {{existing_api_compatibility}}" - id: cr2 - template: 'CR2: {{database_schema_compatibility}}' + template: "CR2: {{database_schema_compatibility}}" - id: cr3 - template: 'CR3: {{ui_ux_consistency}}' + template: "CR3: {{ui_ux_consistency}}" - id: cr4 - template: 'CR4: {{integration_compatibility}}' + template: "CR4: {{integration_compatibility}}" - id: ui-enhancement-goals title: User Interface Enhancement Goals @@ -3492,10 +3492,10 @@ sections: - id: epic-approach title: Epic Approach instruction: Explain the rationale for epic structure - typically single epic for brownfield unless multiple unrelated features - template: '**Epic Structure Decision**: {{epic_decision}} with rationale' + template: "**Epic Structure Decision**: {{epic_decision}} with rationale" - id: epic-details - title: 'Epic 1: {{enhancement_title}}' + title: "Epic 1: {{enhancement_title}}" instruction: | Comprehensive epic that delivers the brownfield enhancement while maintaining existing functionality @@ -3515,7 +3515,7 @@ sections: **Integration Requirements**: {{integration_requirements}} sections: - id: story - title: 'Story 1.{{story_number}} {{story_title}}' + title: "Story 1.{{story_number}} {{story_title}}" repeatable: true template: | As a {{user_type}}, @@ -3526,16 +3526,16 @@ sections: title: Acceptance Criteria type: numbered-list instruction: Define criteria that include both new functionality and existing system integrity - item_template: '{{criterion_number}}: {{criteria}}' + item_template: "{{criterion_number}}: {{criteria}}" - id: integration-verification title: Integration Verification instruction: Specific verification steps to ensure existing functionality remains intact type: numbered-list prefix: IV items: - - template: 'IV1: {{existing_functionality_verification}}' - - template: 'IV2: {{integration_point_verification}}' - - template: 'IV3: {{performance_impact_verification}}' + - template: "IV1: {{existing_functionality_verification}}" + - template: "IV2: {{integration_point_verification}}" + - template: "IV3: {{performance_impact_verification}}" ==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ==================== ==================== START: .bmad-core/templates/competitor-analysis-tmpl.yaml ==================== @@ -3546,24 +3546,24 @@ template: output: format: markdown filename: docs/competitor-analysis.md - title: 'Competitive Analysis Report: {{project_product_name}}' + title: "Competitive Analysis Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Competitive Analysis Elicitation Actions' + title: "Competitive Analysis Elicitation Actions" options: - "Deep dive on a specific competitor's strategy" - - 'Analyze competitive dynamics in a specific segment' - - 'War game competitive responses to your moves' - - 'Explore partnership vs. competition scenarios' - - 'Stress test differentiation claims' - - 'Analyze disruption potential (yours or theirs)' - - 'Compare to competition in adjacent markets' - - 'Generate win/loss analysis insights' + - "Analyze competitive dynamics in a specific segment" + - "War game competitive responses to your moves" + - "Explore partnership vs. competition scenarios" + - "Stress test differentiation claims" + - "Analyze disruption potential (yours or theirs)" + - "Compare to competition in adjacent markets" + - "Generate win/loss analysis insights" - "If only we had known about [competitor X's plan]..." - - 'Proceed to next section' + - "Proceed to next section" sections: - id: executive-summary @@ -3630,7 +3630,7 @@ sections: repeatable: true sections: - id: competitor - title: '{{competitor_name}} - Priority {{priority_level}}' + title: "{{competitor_name}} - Priority {{priority_level}}" sections: - id: company-overview title: Company Overview @@ -3662,11 +3662,11 @@ sections: - id: strengths title: Strengths type: bullet-list - template: '- {{strength}}' + template: "- {{strength}}" - id: weaknesses title: Weaknesses type: bullet-list - template: '- {{weakness}}' + template: "- {{weakness}}" - id: market-position title: Market Position & Performance template: | @@ -3684,35 +3684,35 @@ sections: type: table columns: [ - 'Feature Category', - '{{your_company}}', - '{{competitor_1}}', - '{{competitor_2}}', - '{{competitor_3}}', + "Feature Category", + "{{your_company}}", + "{{competitor_1}}", + "{{competitor_2}}", + "{{competitor_3}}", ] rows: - - category: 'Core Functionality' + - category: "Core Functionality" items: - - ['Feature A', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - ['Feature B', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - category: 'User Experience' + - ["Feature A", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - ["Feature B", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - category: "User Experience" items: - - ['Mobile App', '{{rating}}', '{{rating}}', '{{rating}}', '{{rating}}'] - - ['Onboarding Time', '{{time}}', '{{time}}', '{{time}}', '{{time}}'] - - category: 'Integration & Ecosystem' + - ["Mobile App", "{{rating}}", "{{rating}}", "{{rating}}", "{{rating}}"] + - ["Onboarding Time", "{{time}}", "{{time}}", "{{time}}", "{{time}}"] + - category: "Integration & Ecosystem" items: - [ - 'API Availability', - '{{availability}}', - '{{availability}}', - '{{availability}}', - '{{availability}}', + "API Availability", + "{{availability}}", + "{{availability}}", + "{{availability}}", + "{{availability}}", ] - - ['Third-party Integrations', '{{number}}', '{{number}}', '{{number}}', '{{number}}'] - - category: 'Pricing & Plans' + - ["Third-party Integrations", "{{number}}", "{{number}}", "{{number}}", "{{number}}"] + - category: "Pricing & Plans" items: - - ['Starting Price', '{{price}}', '{{price}}', '{{price}}', '{{price}}'] - - ['Free Tier', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}'] + - ["Starting Price", "{{price}}", "{{price}}", "{{price}}", "{{price}}"] + - ["Free Tier", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}"] - id: swot-comparison title: SWOT Comparison instruction: Create SWOT analysis for your solution vs. top competitors @@ -3725,7 +3725,7 @@ sections: - **Opportunities:** {{opportunities}} - **Threats:** {{threats}} - id: vs-competitor - title: 'vs. {{main_competitor}}' + title: "vs. {{main_competitor}}" template: | - **Competitive Advantages:** {{your_advantages}} - **Competitive Disadvantages:** {{their_advantages}} @@ -3855,7 +3855,7 @@ template: output: format: markdown filename: docs/ui-architecture.md - title: '{{project_name}} Frontend Architecture Document' + title: "{{project_name}} Frontend Architecture Document" workflow: mode: interactive @@ -3923,29 +3923,29 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Fill in appropriate technology choices based on the selected framework and project requirements. rows: - - ['Framework', '{{framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['UI Library', '{{ui_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Framework", "{{framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["UI Library", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'State Management', - '{{state_management}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "State Management", + "{{state_management}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['Routing', '{{routing_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Build Tool', '{{build_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Styling', '{{styling_solution}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Testing', '{{test_framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Routing", "{{routing_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Styling", "{{styling_solution}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Testing", "{{test_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Component Library', - '{{component_lib}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Component Library", + "{{component_lib}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['Form Handling', '{{form_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Animation', '{{animation_lib}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Dev Tools', '{{dev_tools}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Form Handling", "{{form_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Animation", "{{animation_lib}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Dev Tools", "{{dev_tools}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - id: project-structure title: Project Structure @@ -4039,12 +4039,12 @@ sections: title: Testing Best Practices type: numbered-list items: - - '**Unit Tests**: Test individual components in isolation' - - '**Integration Tests**: Test component interactions' - - '**E2E Tests**: Test critical user flows (using Cypress/Playwright)' - - '**Coverage Goals**: Aim for 80% code coverage' - - '**Test Structure**: Arrange-Act-Assert pattern' - - '**Mock External Dependencies**: API calls, routing, state management' + - "**Unit Tests**: Test individual components in isolation" + - "**Integration Tests**: Test component interactions" + - "**E2E Tests**: Test critical user flows (using Cypress/Playwright)" + - "**Coverage Goals**: Aim for 80% code coverage" + - "**Test Structure**: Arrange-Act-Assert pattern" + - "**Mock External Dependencies**: API calls, routing, state management" - id: environment-configuration title: Environment Configuration @@ -4076,7 +4076,7 @@ template: output: format: markdown filename: docs/front-end-spec.md - title: '{{project_name}} UI/UX Specification' + title: "{{project_name}} UI/UX Specification" workflow: mode: interactive @@ -4104,29 +4104,29 @@ sections: sections: - id: user-personas title: Target User Personas - template: '{{persona_descriptions}}' + template: "{{persona_descriptions}}" examples: - - '**Power User:** Technical professionals who need advanced features and efficiency' - - '**Casual User:** Occasional users who prioritize ease of use and clear guidance' - - '**Administrator:** System managers who need control and oversight capabilities' + - "**Power User:** Technical professionals who need advanced features and efficiency" + - "**Casual User:** Occasional users who prioritize ease of use and clear guidance" + - "**Administrator:** System managers who need control and oversight capabilities" - id: usability-goals title: Usability Goals - template: '{{usability_goals}}' + template: "{{usability_goals}}" examples: - - 'Ease of learning: New users can complete core tasks within 5 minutes' - - 'Efficiency of use: Power users can complete frequent tasks with minimal clicks' - - 'Error prevention: Clear validation and confirmation for destructive actions' - - 'Memorability: Infrequent users can return without relearning' + - "Ease of learning: New users can complete core tasks within 5 minutes" + - "Efficiency of use: Power users can complete frequent tasks with minimal clicks" + - "Error prevention: Clear validation and confirmation for destructive actions" + - "Memorability: Infrequent users can return without relearning" - id: design-principles title: Design Principles - template: '{{design_principles}}' + template: "{{design_principles}}" type: numbered-list examples: - - '**Clarity over cleverness** - Prioritize clear communication over aesthetic innovation' + - "**Clarity over cleverness** - Prioritize clear communication over aesthetic innovation" - "**Progressive disclosure** - Show only what's needed, when it's needed" - - '**Consistent patterns** - Use familiar UI patterns throughout the application' - - '**Immediate feedback** - Every action should have a clear, immediate response' - - '**Accessible by default** - Design for all users from the start' + - "**Consistent patterns** - Use familiar UI patterns throughout the application" + - "**Immediate feedback** - Every action should have a clear, immediate response" + - "**Accessible by default** - Design for all users from the start" - id: changelog title: Change Log type: table @@ -4148,7 +4148,7 @@ sections: title: Site Map / Screen Inventory type: mermaid mermaid_type: graph - template: '{{sitemap_diagram}}' + template: "{{sitemap_diagram}}" examples: - | graph TD @@ -4188,7 +4188,7 @@ sections: repeatable: true sections: - id: flow - title: '{{flow_name}}' + title: "{{flow_name}}" template: | **User Goal:** {{flow_goal}} @@ -4200,13 +4200,13 @@ sections: title: Flow Diagram type: mermaid mermaid_type: graph - template: '{{flow_diagram}}' + template: "{{flow_diagram}}" - id: edge-cases - title: 'Edge Cases & Error Handling:' + title: "Edge Cases & Error Handling:" type: bullet-list - template: '- {{edge_case}}' + template: "- {{edge_case}}" - id: notes - template: '**Notes:** {{flow_notes}}' + template: "**Notes:** {{flow_notes}}" - id: wireframes-mockups title: Wireframes & Mockups @@ -4215,13 +4215,13 @@ sections: elicit: true sections: - id: design-files - template: '**Primary Design Files:** {{design_tool_link}}' + template: "**Primary Design Files:** {{design_tool_link}}" - id: key-screen-layouts title: Key Screen Layouts repeatable: true sections: - id: screen - title: '{{screen_name}}' + title: "{{screen_name}}" template: | **Purpose:** {{screen_purpose}} @@ -4241,13 +4241,13 @@ sections: elicit: true sections: - id: design-system-approach - template: '**Design System Approach:** {{design_system_approach}}' + template: "**Design System Approach:** {{design_system_approach}}" - id: core-components title: Core Components repeatable: true sections: - id: component - title: '{{component_name}}' + title: "{{component_name}}" template: | **Purpose:** {{component_purpose}} @@ -4264,19 +4264,19 @@ sections: sections: - id: visual-identity title: Visual Identity - template: '**Brand Guidelines:** {{brand_guidelines_link}}' + template: "**Brand Guidelines:** {{brand_guidelines_link}}" - id: color-palette title: Color Palette type: table - columns: ['Color Type', 'Hex Code', 'Usage'] + columns: ["Color Type", "Hex Code", "Usage"] rows: - - ['Primary', '{{primary_color}}', '{{primary_usage}}'] - - ['Secondary', '{{secondary_color}}', '{{secondary_usage}}'] - - ['Accent', '{{accent_color}}', '{{accent_usage}}'] - - ['Success', '{{success_color}}', 'Positive feedback, confirmations'] - - ['Warning', '{{warning_color}}', 'Cautions, important notices'] - - ['Error', '{{error_color}}', 'Errors, destructive actions'] - - ['Neutral', '{{neutral_colors}}', 'Text, borders, backgrounds'] + - ["Primary", "{{primary_color}}", "{{primary_usage}}"] + - ["Secondary", "{{secondary_color}}", "{{secondary_usage}}"] + - ["Accent", "{{accent_color}}", "{{accent_usage}}"] + - ["Success", "{{success_color}}", "Positive feedback, confirmations"] + - ["Warning", "{{warning_color}}", "Cautions, important notices"] + - ["Error", "{{error_color}}", "Errors, destructive actions"] + - ["Neutral", "{{neutral_colors}}", "Text, borders, backgrounds"] - id: typography title: Typography sections: @@ -4289,13 +4289,13 @@ sections: - id: type-scale title: Type Scale type: table - columns: ['Element', 'Size', 'Weight', 'Line Height'] + columns: ["Element", "Size", "Weight", "Line Height"] rows: - - ['H1', '{{h1_size}}', '{{h1_weight}}', '{{h1_line}}'] - - ['H2', '{{h2_size}}', '{{h2_weight}}', '{{h2_line}}'] - - ['H3', '{{h3_size}}', '{{h3_weight}}', '{{h3_line}}'] - - ['Body', '{{body_size}}', '{{body_weight}}', '{{body_line}}'] - - ['Small', '{{small_size}}', '{{small_weight}}', '{{small_line}}'] + - ["H1", "{{h1_size}}", "{{h1_weight}}", "{{h1_line}}"] + - ["H2", "{{h2_size}}", "{{h2_weight}}", "{{h2_line}}"] + - ["H3", "{{h3_size}}", "{{h3_weight}}", "{{h3_line}}"] + - ["Body", "{{body_size}}", "{{body_weight}}", "{{body_line}}"] + - ["Small", "{{small_size}}", "{{small_weight}}", "{{small_line}}"] - id: iconography title: Iconography template: | @@ -4316,7 +4316,7 @@ sections: sections: - id: compliance-target title: Compliance Target - template: '**Standard:** {{compliance_standard}}' + template: "**Standard:** {{compliance_standard}}" - id: key-requirements title: Key Requirements template: | @@ -4336,7 +4336,7 @@ sections: - Form labels: {{form_requirements}} - id: testing-strategy title: Testing Strategy - template: '{{accessibility_testing}}' + template: "{{accessibility_testing}}" - id: responsiveness title: Responsiveness Strategy @@ -4346,12 +4346,12 @@ sections: - id: breakpoints title: Breakpoints type: table - columns: ['Breakpoint', 'Min Width', 'Max Width', 'Target Devices'] + columns: ["Breakpoint", "Min Width", "Max Width", "Target Devices"] rows: - - ['Mobile', '{{mobile_min}}', '{{mobile_max}}', '{{mobile_devices}}'] - - ['Tablet', '{{tablet_min}}', '{{tablet_max}}', '{{tablet_devices}}'] - - ['Desktop', '{{desktop_min}}', '{{desktop_max}}', '{{desktop_devices}}'] - - ['Wide', '{{wide_min}}', '-', '{{wide_devices}}'] + - ["Mobile", "{{mobile_min}}", "{{mobile_max}}", "{{mobile_devices}}"] + - ["Tablet", "{{tablet_min}}", "{{tablet_max}}", "{{tablet_devices}}"] + - ["Desktop", "{{desktop_min}}", "{{desktop_max}}", "{{desktop_devices}}"] + - ["Wide", "{{wide_min}}", "-", "{{wide_devices}}"] - id: adaptation-patterns title: Adaptation Patterns template: | @@ -4370,11 +4370,11 @@ sections: sections: - id: motion-principles title: Motion Principles - template: '{{motion_principles}}' + template: "{{motion_principles}}" - id: key-animations title: Key Animations repeatable: true - template: '- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})' + template: "- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})" - id: performance title: Performance Considerations @@ -4388,7 +4388,7 @@ sections: - **Animation FPS:** {{animation_goal}} - id: design-strategies title: Design Strategies - template: '{{performance_strategies}}' + template: "{{performance_strategies}}" - id: next-steps title: Next Steps @@ -4403,17 +4403,17 @@ sections: - id: immediate-actions title: Immediate Actions type: numbered-list - template: '{{action}}' + template: "{{action}}" - id: design-handoff-checklist title: Design Handoff Checklist type: checklist items: - - 'All user flows documented' - - 'Component inventory complete' - - 'Accessibility requirements defined' - - 'Responsive strategy clear' - - 'Brand guidelines incorporated' - - 'Performance goals established' + - "All user flows documented" + - "Component inventory complete" + - "Accessibility requirements defined" + - "Responsive strategy clear" + - "Brand guidelines incorporated" + - "Performance goals established" - id: checklist-results title: Checklist Results @@ -4428,7 +4428,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Fullstack Architecture Document' + title: "{{project_name}} Fullstack Architecture Document" workflow: mode: interactive @@ -4549,12 +4549,12 @@ sections: For each pattern, provide recommendation and rationale. repeatable: true - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - - '**Jamstack Architecture:** Static site generation with serverless APIs - _Rationale:_ Optimal performance and scalability for content-heavy applications' - - '**Component-Based UI:** Reusable React components with TypeScript - _Rationale:_ Maintainability and type safety across large codebases' - - '**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility' - - '**API Gateway Pattern:** Single entry point for all API calls - _Rationale:_ Centralized auth, rate limiting, and monitoring' + - "**Jamstack Architecture:** Static site generation with serverless APIs - _Rationale:_ Optimal performance and scalability for content-heavy applications" + - "**Component-Based UI:** Reusable React components with TypeScript - _Rationale:_ Maintainability and type safety across large codebases" + - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility" + - "**API Gateway Pattern:** Single entry point for all API calls - _Rationale:_ Centralized auth, rate limiting, and monitoring" - id: tech-stack title: Tech Stack @@ -4578,45 +4578,45 @@ sections: type: table columns: [Category, Technology, Version, Purpose, Rationale] rows: - - ['Frontend Language', '{{fe_language}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Frontend Language", "{{fe_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Frontend Framework', - '{{fe_framework}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Frontend Framework", + "{{fe_framework}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - [ - 'UI Component Library', - '{{ui_library}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "UI Component Library", + "{{ui_library}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['State Management', '{{state_mgmt}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Backend Language', '{{be_language}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["State Management", "{{state_mgmt}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Backend Language", "{{be_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Backend Framework', - '{{be_framework}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Backend Framework", + "{{be_framework}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['API Style', '{{api_style}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Database', '{{database}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Cache', '{{cache}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['File Storage', '{{storage}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Authentication', '{{auth}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Frontend Testing', '{{fe_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Backend Testing', '{{be_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['E2E Testing', '{{e2e_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Build Tool', '{{build_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Bundler', '{{bundler}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['IaC Tool', '{{iac_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['CI/CD', '{{cicd}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Monitoring', '{{monitoring}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Logging', '{{logging}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['CSS Framework', '{{css_framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["API Style", "{{api_style}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Database", "{{database}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Cache", "{{cache}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["File Storage", "{{storage}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Authentication", "{{auth}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Frontend Testing", "{{fe_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Backend Testing", "{{be_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["E2E Testing", "{{e2e_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Bundler", "{{bundler}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["IaC Tool", "{{iac_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["CI/CD", "{{cicd}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Monitoring", "{{monitoring}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Logging", "{{logging}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["CSS Framework", "{{css_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - id: data-models title: Data Models @@ -4635,7 +4635,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -4647,11 +4647,11 @@ sections: title: TypeScript Interface type: code language: typescript - template: '{{model_interface}}' + template: "{{model_interface}}" - id: relationships title: Relationships type: bullet-list - template: '- {{relationship}}' + template: "- {{relationship}}" - id: api-spec title: API Specification @@ -4688,13 +4688,13 @@ sections: condition: API style is GraphQL type: code language: graphql - template: '{{graphql_schema}}' + template: "{{graphql_schema}}" - id: trpc-api title: tRPC Router Definitions condition: API style is tRPC type: code language: typescript - template: '{{trpc_routers}}' + template: "{{trpc_routers}}" - id: components title: Components @@ -4715,7 +4715,7 @@ sections: sections: - id: component-list repeatable: true - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} @@ -4753,7 +4753,7 @@ sections: repeatable: true sections: - id: api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -4810,12 +4810,12 @@ sections: title: Component Organization type: code language: text - template: '{{component_structure}}' + template: "{{component_structure}}" - id: component-template title: Component Template type: code language: typescript - template: '{{component_template}}' + template: "{{component_template}}" - id: state-management title: State Management Architecture instruction: Detail state management approach based on chosen solution. @@ -4824,11 +4824,11 @@ sections: title: State Structure type: code language: typescript - template: '{{state_structure}}' + template: "{{state_structure}}" - id: state-patterns title: State Management Patterns type: bullet-list - template: '- {{pattern}}' + template: "- {{pattern}}" - id: routing-architecture title: Routing Architecture instruction: Define routing structure based on framework choice. @@ -4837,12 +4837,12 @@ sections: title: Route Organization type: code language: text - template: '{{route_structure}}' + template: "{{route_structure}}" - id: protected-routes title: Protected Route Pattern type: code language: typescript - template: '{{protected_route_example}}' + template: "{{protected_route_example}}" - id: frontend-services title: Frontend Services Layer instruction: Define how frontend communicates with backend. @@ -4851,12 +4851,12 @@ sections: title: API Client Setup type: code language: typescript - template: '{{api_client_setup}}' + template: "{{api_client_setup}}" - id: service-example title: Service Example type: code language: typescript - template: '{{service_example}}' + template: "{{service_example}}" - id: backend-architecture title: Backend Architecture @@ -4874,12 +4874,12 @@ sections: title: Function Organization type: code language: text - template: '{{function_structure}}' + template: "{{function_structure}}" - id: function-template title: Function Template type: code language: typescript - template: '{{function_template}}' + template: "{{function_template}}" - id: traditional-server condition: Traditional server architecture chosen sections: @@ -4887,12 +4887,12 @@ sections: title: Controller/Route Organization type: code language: text - template: '{{controller_structure}}' + template: "{{controller_structure}}" - id: controller-template title: Controller Template type: code language: typescript - template: '{{controller_template}}' + template: "{{controller_template}}" - id: database-architecture title: Database Architecture instruction: Define database schema and access patterns. @@ -4901,12 +4901,12 @@ sections: title: Schema Design type: code language: sql - template: '{{database_schema}}' + template: "{{database_schema}}" - id: data-access-layer title: Data Access Layer type: code language: typescript - template: '{{repository_pattern}}' + template: "{{repository_pattern}}" - id: auth-architecture title: Authentication and Authorization instruction: Define auth implementation details. @@ -4915,12 +4915,12 @@ sections: title: Auth Flow type: mermaid mermaid_type: sequence - template: '{{auth_flow_diagram}}' + template: "{{auth_flow_diagram}}" - id: auth-middleware title: Middleware/Guards type: code language: typescript - template: '{{auth_middleware}}' + template: "{{auth_middleware}}" - id: unified-project-structure title: Unified Project Structure @@ -4996,12 +4996,12 @@ sections: title: Prerequisites type: code language: bash - template: '{{prerequisites_commands}}' + template: "{{prerequisites_commands}}" - id: initial-setup title: Initial Setup type: code language: bash - template: '{{setup_commands}}' + template: "{{setup_commands}}" - id: dev-commands title: Development Commands type: code @@ -5057,15 +5057,15 @@ sections: title: CI/CD Pipeline type: code language: yaml - template: '{{cicd_pipeline_config}}' + template: "{{cicd_pipeline_config}}" - id: environments title: Environments type: table columns: [Environment, Frontend URL, Backend URL, Purpose] rows: - - ['Development', '{{dev_fe_url}}', '{{dev_be_url}}', 'Local development'] - - ['Staging', '{{staging_fe_url}}', '{{staging_be_url}}', 'Pre-production testing'] - - ['Production', '{{prod_fe_url}}', '{{prod_be_url}}', 'Live environment'] + - ["Development", "{{dev_fe_url}}", "{{dev_be_url}}", "Local development"] + - ["Staging", "{{staging_fe_url}}", "{{staging_be_url}}", "Pre-production testing"] + - ["Production", "{{prod_fe_url}}", "{{prod_be_url}}", "Live environment"] - id: security-performance title: Security and Performance @@ -5124,17 +5124,17 @@ sections: title: Frontend Tests type: code language: text - template: '{{frontend_test_structure}}' + template: "{{frontend_test_structure}}" - id: backend-tests title: Backend Tests type: code language: text - template: '{{backend_test_structure}}' + template: "{{backend_test_structure}}" - id: e2e-tests title: E2E Tests type: code language: text - template: '{{e2e_test_structure}}' + template: "{{e2e_test_structure}}" - id: test-examples title: Test Examples sections: @@ -5142,17 +5142,17 @@ sections: title: Frontend Component Test type: code language: typescript - template: '{{frontend_test_example}}' + template: "{{frontend_test_example}}" - id: backend-test title: Backend API Test type: code language: typescript - template: '{{backend_test_example}}' + template: "{{backend_test_example}}" - id: e2e-test title: E2E Test type: code language: typescript - template: '{{e2e_test_example}}' + template: "{{e2e_test_example}}" - id: coding-standards title: Coding Standards @@ -5162,22 +5162,22 @@ sections: - id: critical-rules title: Critical Fullstack Rules repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" examples: - - '**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' + - "**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" - id: naming-conventions title: Naming Conventions type: table columns: [Element, Frontend, Backend, Example] rows: - - ['Components', 'PascalCase', '-', '`UserProfile.tsx`'] - - ['Hooks', "camelCase with 'use'", '-', '`useAuth.ts`'] - - ['API Routes', '-', 'kebab-case', '`/api/user-profile`'] - - ['Database Tables', '-', 'snake_case', '`user_profiles`'] + - ["Components", "PascalCase", "-", "`UserProfile.tsx`"] + - ["Hooks", "camelCase with 'use'", "-", "`useAuth.ts`"] + - ["API Routes", "-", "kebab-case", "`/api/user-profile`"] + - ["Database Tables", "-", "snake_case", "`user_profiles`"] - id: error-handling title: Error Handling Strategy @@ -5188,7 +5188,7 @@ sections: title: Error Flow type: mermaid mermaid_type: sequence - template: '{{error_flow_diagram}}' + template: "{{error_flow_diagram}}" - id: error-format title: Error Response Format type: code @@ -5207,12 +5207,12 @@ sections: title: Frontend Error Handling type: code language: typescript - template: '{{frontend_error_handler}}' + template: "{{frontend_error_handler}}" - id: backend-error-handling title: Backend Error Handling type: code language: typescript - template: '{{backend_error_handler}}' + template: "{{backend_error_handler}}" - id: monitoring title: Monitoring and Observability @@ -5254,24 +5254,24 @@ template: output: format: markdown filename: docs/market-research.md - title: 'Market Research Report: {{project_product_name}}' + title: "Market Research Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Market Research Elicitation Actions' + title: "Market Research Elicitation Actions" options: - - 'Expand market sizing calculations with sensitivity analysis' - - 'Deep dive into a specific customer segment' - - 'Analyze an emerging market trend in detail' - - 'Compare this market to an analogous market' - - 'Stress test market assumptions' - - 'Explore adjacent market opportunities' - - 'Challenge market definition and boundaries' - - 'Generate strategic scenarios (best/base/worst case)' - - 'If only we had considered [X market factor]...' - - 'Proceed to next section' + - "Expand market sizing calculations with sensitivity analysis" + - "Deep dive into a specific customer segment" + - "Analyze an emerging market trend in detail" + - "Compare this market to an analogous market" + - "Stress test market assumptions" + - "Explore adjacent market opportunities" + - "Challenge market definition and boundaries" + - "Generate strategic scenarios (best/base/worst case)" + - "If only we had considered [X market factor]..." + - "Proceed to next section" sections: - id: executive-summary @@ -5353,7 +5353,7 @@ sections: repeatable: true sections: - id: segment - title: 'Segment {{segment_number}}: {{segment_name}}' + title: "Segment {{segment_number}}: {{segment_name}}" template: | - **Description:** {{brief_overview}} - **Size:** {{number_of_customers_market_value}} @@ -5422,20 +5422,20 @@ sections: instruction: Analyze each force with specific evidence and implications sections: - id: supplier-power - title: 'Supplier Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Supplier Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: buyer-power - title: 'Buyer Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Buyer Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: competitive-rivalry - title: 'Competitive Rivalry: {{intensity_level}}' - template: '{{analysis_and_implications}}' + title: "Competitive Rivalry: {{intensity_level}}" + template: "{{analysis_and_implications}}" - id: threat-new-entry - title: 'Threat of New Entry: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of New Entry: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: threat-substitutes - title: 'Threat of Substitutes: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of Substitutes: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: adoption-lifecycle title: Technology Adoption Lifecycle Stage instruction: | @@ -5453,7 +5453,7 @@ sections: repeatable: true sections: - id: opportunity - title: 'Opportunity {{opportunity_number}}: {{name}}' + title: "Opportunity {{opportunity_number}}: {{name}}" template: | - **Description:** {{what_is_the_opportunity}} - **Size/Potential:** {{quantified_potential}} @@ -5509,7 +5509,7 @@ template: output: format: markdown filename: docs/prd.md - title: '{{project_name}} Product Requirements Document (PRD)' + title: "{{project_name}} Product Requirements Document (PRD)" workflow: mode: interactive @@ -5546,14 +5546,14 @@ sections: prefix: FR instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with FR examples: - - 'FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently.' + - "FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently." - id: non-functional title: Non Functional type: numbered-list prefix: NFR instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR examples: - - 'NFR1: AWS service usage must aim to stay within free-tier limits where feasible.' + - "NFR1: AWS service usage must aim to stay within free-tier limits where feasible." - id: ui-goals title: User Interface Design Goals @@ -5579,24 +5579,24 @@ sections: title: Core Screens and Views instruction: 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 examples: - - 'Login Screen' - - 'Main Dashboard' - - 'Item Detail Page' - - 'Settings Page' + - "Login Screen" + - "Main Dashboard" + - "Item Detail Page" + - "Settings Page" - id: accessibility - title: 'Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}' + title: "Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}" - id: branding title: Branding instruction: Any known branding elements or style guides that must be incorporated? examples: - - '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.' + - "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." - id: target-platforms - title: 'Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}' + title: "Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}" examples: - - 'Web Responsive, and all mobile platforms' - - 'iPhone Only' - - 'ASCII Windows Desktop' + - "Web Responsive, and all mobile platforms" + - "iPhone Only" + - "ASCII Windows Desktop" - id: technical-assumptions title: Technical Assumptions @@ -5615,13 +5615,13 @@ sections: testing: [Unit Only, Unit + Integration, Full Testing Pyramid] sections: - id: repository-structure - title: 'Repository Structure: {Monorepo|Polyrepo|Multi-repo}' + title: "Repository Structure: {Monorepo|Polyrepo|Multi-repo}" - id: service-architecture title: Service Architecture - instruction: 'CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).' + instruction: "CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo)." - id: testing-requirements title: Testing Requirements - instruction: 'CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).' + instruction: "CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods)." - id: additional-assumptions title: Additional Technical Assumptions and Requests instruction: 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 @@ -5641,10 +5641,10 @@ sections: - 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. elicit: true examples: - - 'Epic 1: Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management' - - 'Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations' - - 'Epic 3: User Workflows & Interactions: Enable key user journeys and business processes' - - 'Epic 4: Reporting & Analytics: Provide insights and data visualization for users' + - "Epic 1: Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management" + - "Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations" + - "Epic 3: User Workflows & Interactions: Enable key user journeys and business processes" + - "Epic 4: Reporting & Analytics: Provide insights and data visualization for users" - id: epic-details title: Epic {{epic_number}} {{epic_title}} @@ -5666,7 +5666,7 @@ sections: - 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 elicit: true - template: '{{epic_goal}}' + template: "{{epic_goal}}" sections: - id: story title: Story {{epic_number}}.{{story_number}} {{story_title}} @@ -5679,7 +5679,7 @@ sections: - id: acceptance-criteria title: Acceptance Criteria type: numbered-list - item_template: '{{criterion_number}}: {{criteria}}' + item_template: "{{criterion_number}}: {{criteria}}" repeatable: true instruction: | Define clear, comprehensive, and testable acceptance criteria that: @@ -5714,24 +5714,24 @@ template: output: format: markdown filename: docs/brief.md - title: 'Project Brief: {{project_name}}' + title: "Project Brief: {{project_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Project Brief Elicitation Actions' + title: "Project Brief Elicitation Actions" options: - - 'Expand section with more specific details' - - 'Validate against similar successful products' - - 'Stress test assumptions with edge cases' - - 'Explore alternative solution approaches' - - 'Analyze resource/constraint trade-offs' - - 'Generate risk mitigation strategies' - - 'Challenge scope from MVP minimalist view' - - 'Brainstorm creative feature possibilities' - - 'If only we had [resource/capability/time]...' - - 'Proceed to next section' + - "Expand section with more specific details" + - "Validate against similar successful products" + - "Stress test assumptions with edge cases" + - "Explore alternative solution approaches" + - "Analyze resource/constraint trade-offs" + - "Generate risk mitigation strategies" + - "Challenge scope from MVP minimalist view" + - "Brainstorm creative feature possibilities" + - "If only we had [resource/capability/time]..." + - "Proceed to next section" sections: - id: introduction @@ -5753,7 +5753,7 @@ sections: - Primary problem being solved - Target market identification - Key value proposition - template: '{{executive_summary_content}}' + template: "{{executive_summary_content}}" - id: problem-statement title: Problem Statement @@ -5763,7 +5763,7 @@ sections: - Impact of the problem (quantify if possible) - Why existing solutions fall short - Urgency and importance of solving this now - template: '{{detailed_problem_description}}' + template: "{{detailed_problem_description}}" - id: proposed-solution title: Proposed Solution @@ -5773,7 +5773,7 @@ sections: - Key differentiators from existing solutions - Why this solution will succeed where others haven't - High-level vision for the product - template: '{{solution_description}}' + template: "{{solution_description}}" - id: target-users title: Target Users @@ -5785,12 +5785,12 @@ sections: - Goals they're trying to achieve sections: - id: primary-segment - title: 'Primary User Segment: {{segment_name}}' - template: '{{primary_user_description}}' + title: "Primary User Segment: {{segment_name}}" + template: "{{primary_user_description}}" - id: secondary-segment - title: 'Secondary User Segment: {{segment_name}}' + title: "Secondary User Segment: {{segment_name}}" condition: Has secondary user segment - template: '{{secondary_user_description}}' + template: "{{secondary_user_description}}" - id: goals-metrics title: Goals & Success Metrics @@ -5799,15 +5799,15 @@ sections: - id: business-objectives title: Business Objectives type: bullet-list - template: '- {{objective_with_metric}}' + template: "- {{objective_with_metric}}" - id: user-success-metrics title: User Success Metrics type: bullet-list - template: '- {{user_metric}}' + template: "- {{user_metric}}" - id: kpis title: Key Performance Indicators (KPIs) type: bullet-list - template: '- {{kpi}}: {{definition_and_target}}' + template: "- {{kpi}}: {{definition_and_target}}" - id: mvp-scope title: MVP Scope @@ -5816,14 +5816,14 @@ sections: - id: core-features title: Core Features (Must Have) type: bullet-list - template: '- **{{feature}}:** {{description_and_rationale}}' + template: "- **{{feature}}:** {{description_and_rationale}}" - id: out-of-scope title: Out of Scope for MVP type: bullet-list - template: '- {{feature_or_capability}}' + template: "- {{feature_or_capability}}" - id: mvp-success-criteria title: MVP Success Criteria - template: '{{mvp_success_definition}}' + template: "{{mvp_success_definition}}" - id: post-mvp-vision title: Post-MVP Vision @@ -5831,13 +5831,13 @@ sections: sections: - id: phase-2-features title: Phase 2 Features - template: '{{next_priority_features}}' + template: "{{next_priority_features}}" - id: long-term-vision title: Long-term Vision - template: '{{one_two_year_vision}}' + template: "{{one_two_year_vision}}" - id: expansion-opportunities title: Expansion Opportunities - template: '{{potential_expansions}}' + template: "{{potential_expansions}}" - id: technical-considerations title: Technical Considerations @@ -5878,7 +5878,7 @@ sections: - id: key-assumptions title: Key Assumptions type: bullet-list - template: '- {{assumption}}' + template: "- {{assumption}}" - id: risks-questions title: Risks & Open Questions @@ -5887,15 +5887,15 @@ sections: - id: key-risks title: Key Risks type: bullet-list - template: '- **{{risk}}:** {{description_and_impact}}' + template: "- **{{risk}}:** {{description_and_impact}}" - id: open-questions title: Open Questions type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: research-areas title: Areas Needing Further Research type: bullet-list - template: '- {{research_topic}}' + template: "- {{research_topic}}" - id: appendices title: Appendices @@ -5912,10 +5912,10 @@ sections: - id: stakeholder-input title: B. Stakeholder Input condition: Has stakeholder feedback - template: '{{stakeholder_feedback}}' + template: "{{stakeholder_feedback}}" - id: references title: C. References - template: '{{relevant_links_and_docs}}' + template: "{{relevant_links_and_docs}}" - id: next-steps title: Next Steps @@ -5923,7 +5923,7 @@ sections: - id: immediate-actions title: Immediate Actions type: numbered-list - template: '{{action_item}}' + template: "{{action_item}}" - id: pm-handoff title: PM Handoff content: | @@ -5938,7 +5938,7 @@ template: output: format: markdown filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md - title: 'Story {{epic_num}}.{{story_num}}: {{story_title_short}}' + title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}" workflow: mode: interactive @@ -6040,7 +6040,7 @@ sections: sections: - id: agent-model title: Agent Model Used - template: '{{agent_model_name_version}}' + template: "{{agent_model_name_version}}" instruction: Record the specific AI agent model and version used for development owner: dev-agent editors: [dev-agent] diff --git a/dist/agents/pm.txt b/dist/agents/pm.txt index 503cb8d4..1248cacd 100644 --- a/dist/agents/pm.txt +++ b/dist/agents/pm.txt @@ -1159,7 +1159,7 @@ template: output: format: markdown filename: docs/prd.md - title: '{{project_name}} Product Requirements Document (PRD)' + title: "{{project_name}} Product Requirements Document (PRD)" workflow: mode: interactive @@ -1196,14 +1196,14 @@ sections: prefix: FR instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with FR examples: - - 'FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently.' + - "FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently." - id: non-functional title: Non Functional type: numbered-list prefix: NFR instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR examples: - - 'NFR1: AWS service usage must aim to stay within free-tier limits where feasible.' + - "NFR1: AWS service usage must aim to stay within free-tier limits where feasible." - id: ui-goals title: User Interface Design Goals @@ -1229,24 +1229,24 @@ sections: title: Core Screens and Views instruction: 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 examples: - - 'Login Screen' - - 'Main Dashboard' - - 'Item Detail Page' - - 'Settings Page' + - "Login Screen" + - "Main Dashboard" + - "Item Detail Page" + - "Settings Page" - id: accessibility - title: 'Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}' + title: "Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}" - id: branding title: Branding instruction: Any known branding elements or style guides that must be incorporated? examples: - - '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.' + - "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." - id: target-platforms - title: 'Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}' + title: "Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}" examples: - - 'Web Responsive, and all mobile platforms' - - 'iPhone Only' - - 'ASCII Windows Desktop' + - "Web Responsive, and all mobile platforms" + - "iPhone Only" + - "ASCII Windows Desktop" - id: technical-assumptions title: Technical Assumptions @@ -1265,13 +1265,13 @@ sections: testing: [Unit Only, Unit + Integration, Full Testing Pyramid] sections: - id: repository-structure - title: 'Repository Structure: {Monorepo|Polyrepo|Multi-repo}' + title: "Repository Structure: {Monorepo|Polyrepo|Multi-repo}" - id: service-architecture title: Service Architecture - instruction: 'CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).' + instruction: "CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo)." - id: testing-requirements title: Testing Requirements - instruction: 'CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).' + instruction: "CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods)." - id: additional-assumptions title: Additional Technical Assumptions and Requests instruction: 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 @@ -1291,10 +1291,10 @@ sections: - 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. elicit: true examples: - - 'Epic 1: Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management' - - 'Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations' - - 'Epic 3: User Workflows & Interactions: Enable key user journeys and business processes' - - 'Epic 4: Reporting & Analytics: Provide insights and data visualization for users' + - "Epic 1: Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management" + - "Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations" + - "Epic 3: User Workflows & Interactions: Enable key user journeys and business processes" + - "Epic 4: Reporting & Analytics: Provide insights and data visualization for users" - id: epic-details title: Epic {{epic_number}} {{epic_title}} @@ -1316,7 +1316,7 @@ sections: - 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 elicit: true - template: '{{epic_goal}}' + template: "{{epic_goal}}" sections: - id: story title: Story {{epic_number}}.{{story_number}} {{story_title}} @@ -1329,7 +1329,7 @@ sections: - id: acceptance-criteria title: Acceptance Criteria type: numbered-list - item_template: '{{criterion_number}}: {{criteria}}' + item_template: "{{criterion_number}}: {{criteria}}" repeatable: true instruction: | Define clear, comprehensive, and testable acceptance criteria that: @@ -1364,7 +1364,7 @@ template: output: format: markdown filename: docs/prd.md - title: '{{project_name}} Brownfield Enhancement PRD' + title: "{{project_name}} Brownfield Enhancement PRD" workflow: mode: interactive @@ -1427,7 +1427,7 @@ sections: - External API Documentation [[LLM: If from document-project, check ✓]] - UX/UI Guidelines [[LLM: May not be in document-project]] - Technical Debt Documentation [[LLM: If from document-project, check ✓]] - - 'Other: {{other_docs}}' + - "Other: {{other_docs}}" instruction: | - If document-project was already run: "Using existing project analysis from document-project output." - If critical documentation is missing and no document-project: "I recommend running the document-project task first..." @@ -1447,7 +1447,7 @@ sections: - UI/UX Overhaul - Technology Stack Upgrade - Bug Fix and Stability Improvements - - 'Other: {{other_type}}' + - "Other: {{other_type}}" - id: enhancement-description title: Enhancement Description instruction: 2-3 sentences describing what the user wants to add or change @@ -1488,29 +1488,29 @@ sections: prefix: FR instruction: Each Requirement will be a bullet markdown with identifier starting with FR examples: - - 'FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality.' + - "FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality." - id: non-functional title: Non Functional type: numbered-list prefix: NFR instruction: Each Requirement will be a bullet markdown with identifier starting with NFR. Include constraints from existing system examples: - - 'NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%.' + - "NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%." - id: compatibility title: Compatibility Requirements instruction: Critical for brownfield - what must remain compatible type: numbered-list prefix: CR - template: '{{requirement}}: {{description}}' + template: "{{requirement}}: {{description}}" items: - id: cr1 - template: 'CR1: {{existing_api_compatibility}}' + template: "CR1: {{existing_api_compatibility}}" - id: cr2 - template: 'CR2: {{database_schema_compatibility}}' + template: "CR2: {{database_schema_compatibility}}" - id: cr3 - template: 'CR3: {{ui_ux_consistency}}' + template: "CR3: {{ui_ux_consistency}}" - id: cr4 - template: 'CR4: {{integration_compatibility}}' + template: "CR4: {{integration_compatibility}}" - id: ui-enhancement-goals title: User Interface Enhancement Goals @@ -1593,10 +1593,10 @@ sections: - id: epic-approach title: Epic Approach instruction: Explain the rationale for epic structure - typically single epic for brownfield unless multiple unrelated features - template: '**Epic Structure Decision**: {{epic_decision}} with rationale' + template: "**Epic Structure Decision**: {{epic_decision}} with rationale" - id: epic-details - title: 'Epic 1: {{enhancement_title}}' + title: "Epic 1: {{enhancement_title}}" instruction: | Comprehensive epic that delivers the brownfield enhancement while maintaining existing functionality @@ -1616,7 +1616,7 @@ sections: **Integration Requirements**: {{integration_requirements}} sections: - id: story - title: 'Story 1.{{story_number}} {{story_title}}' + title: "Story 1.{{story_number}} {{story_title}}" repeatable: true template: | As a {{user_type}}, @@ -1627,16 +1627,16 @@ sections: title: Acceptance Criteria type: numbered-list instruction: Define criteria that include both new functionality and existing system integrity - item_template: '{{criterion_number}}: {{criteria}}' + item_template: "{{criterion_number}}: {{criteria}}" - id: integration-verification title: Integration Verification instruction: Specific verification steps to ensure existing functionality remains intact type: numbered-list prefix: IV items: - - template: 'IV1: {{existing_functionality_verification}}' - - template: 'IV2: {{integration_point_verification}}' - - template: 'IV3: {{performance_impact_verification}}' + - template: "IV1: {{existing_functionality_verification}}" + - template: "IV2: {{integration_point_verification}}" + - template: "IV3: {{performance_impact_verification}}" ==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ==================== ==================== START: .bmad-core/checklists/pm-checklist.md ==================== diff --git a/dist/agents/po.txt b/dist/agents/po.txt index 846e2594..dd7ea0b4 100644 --- a/dist/agents/po.txt +++ b/dist/agents/po.txt @@ -593,7 +593,7 @@ template: output: format: markdown filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md - title: 'Story {{epic_num}}.{{story_num}}: {{story_title_short}}' + title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}" workflow: mode: interactive @@ -695,7 +695,7 @@ sections: sections: - id: agent-model title: Agent Model Used - template: '{{agent_model_name_version}}' + template: "{{agent_model_name_version}}" instruction: Record the specific AI agent model and version used for development owner: dev-agent editors: [dev-agent] diff --git a/dist/agents/qa.txt b/dist/agents/qa.txt index b6bbb22e..909d98cc 100644 --- a/dist/agents/qa.txt +++ b/dist/agents/qa.txt @@ -1743,7 +1743,7 @@ template: output: format: markdown filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md - title: 'Story {{epic_num}}.{{story_num}}: {{story_title_short}}' + title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}" workflow: mode: interactive @@ -1845,7 +1845,7 @@ sections: sections: - id: agent-model title: Agent Model Used - template: '{{agent_model_name_version}}' + template: "{{agent_model_name_version}}" instruction: Record the specific AI agent model and version used for development owner: dev-agent editors: [dev-agent] @@ -1883,16 +1883,16 @@ template: output: format: yaml filename: docs/qa/gates/{{epic_num}}.{{story_num}}-{{story_slug}}.yml - title: 'Quality Gate: {{epic_num}}.{{story_num}}' + title: "Quality Gate: {{epic_num}}.{{story_num}}" # Required fields (keep these first) schema: 1 -story: '{{epic_num}}.{{story_num}}' -story_title: '{{story_title}}' -gate: '{{gate_status}}' # PASS|CONCERNS|FAIL|WAIVED -status_reason: '{{status_reason}}' # 1-2 sentence summary of why this gate decision -reviewer: 'Quinn (Test Architect)' -updated: '{{iso_timestamp}}' +story: "{{epic_num}}.{{story_num}}" +story_title: "{{story_title}}" +gate: "{{gate_status}}" # PASS|CONCERNS|FAIL|WAIVED +status_reason: "{{status_reason}}" # 1-2 sentence summary of why this gate decision +reviewer: "Quinn (Test Architect)" +updated: "{{iso_timestamp}}" # Always present but only active when WAIVED waiver: { active: false } diff --git a/dist/agents/sm.txt b/dist/agents/sm.txt index 10e3a925..e0fbe32b 100644 --- a/dist/agents/sm.txt +++ b/dist/agents/sm.txt @@ -369,7 +369,7 @@ template: output: format: markdown filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md - title: 'Story {{epic_num}}.{{story_num}}: {{story_title_short}}' + title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}" workflow: mode: interactive @@ -471,7 +471,7 @@ sections: sections: - id: agent-model title: Agent Model Used - template: '{{agent_model_name_version}}' + template: "{{agent_model_name_version}}" instruction: Record the specific AI agent model and version used for development owner: dev-agent editors: [dev-agent] diff --git a/dist/agents/ux-expert.txt b/dist/agents/ux-expert.txt index 1b0fbc3e..e1855b09 100644 --- a/dist/agents/ux-expert.txt +++ b/dist/agents/ux-expert.txt @@ -343,7 +343,7 @@ template: output: format: markdown filename: docs/front-end-spec.md - title: '{{project_name}} UI/UX Specification' + title: "{{project_name}} UI/UX Specification" workflow: mode: interactive @@ -371,29 +371,29 @@ sections: sections: - id: user-personas title: Target User Personas - template: '{{persona_descriptions}}' + template: "{{persona_descriptions}}" examples: - - '**Power User:** Technical professionals who need advanced features and efficiency' - - '**Casual User:** Occasional users who prioritize ease of use and clear guidance' - - '**Administrator:** System managers who need control and oversight capabilities' + - "**Power User:** Technical professionals who need advanced features and efficiency" + - "**Casual User:** Occasional users who prioritize ease of use and clear guidance" + - "**Administrator:** System managers who need control and oversight capabilities" - id: usability-goals title: Usability Goals - template: '{{usability_goals}}' + template: "{{usability_goals}}" examples: - - 'Ease of learning: New users can complete core tasks within 5 minutes' - - 'Efficiency of use: Power users can complete frequent tasks with minimal clicks' - - 'Error prevention: Clear validation and confirmation for destructive actions' - - 'Memorability: Infrequent users can return without relearning' + - "Ease of learning: New users can complete core tasks within 5 minutes" + - "Efficiency of use: Power users can complete frequent tasks with minimal clicks" + - "Error prevention: Clear validation and confirmation for destructive actions" + - "Memorability: Infrequent users can return without relearning" - id: design-principles title: Design Principles - template: '{{design_principles}}' + template: "{{design_principles}}" type: numbered-list examples: - - '**Clarity over cleverness** - Prioritize clear communication over aesthetic innovation' + - "**Clarity over cleverness** - Prioritize clear communication over aesthetic innovation" - "**Progressive disclosure** - Show only what's needed, when it's needed" - - '**Consistent patterns** - Use familiar UI patterns throughout the application' - - '**Immediate feedback** - Every action should have a clear, immediate response' - - '**Accessible by default** - Design for all users from the start' + - "**Consistent patterns** - Use familiar UI patterns throughout the application" + - "**Immediate feedback** - Every action should have a clear, immediate response" + - "**Accessible by default** - Design for all users from the start" - id: changelog title: Change Log type: table @@ -415,7 +415,7 @@ sections: title: Site Map / Screen Inventory type: mermaid mermaid_type: graph - template: '{{sitemap_diagram}}' + template: "{{sitemap_diagram}}" examples: - | graph TD @@ -455,7 +455,7 @@ sections: repeatable: true sections: - id: flow - title: '{{flow_name}}' + title: "{{flow_name}}" template: | **User Goal:** {{flow_goal}} @@ -467,13 +467,13 @@ sections: title: Flow Diagram type: mermaid mermaid_type: graph - template: '{{flow_diagram}}' + template: "{{flow_diagram}}" - id: edge-cases - title: 'Edge Cases & Error Handling:' + title: "Edge Cases & Error Handling:" type: bullet-list - template: '- {{edge_case}}' + template: "- {{edge_case}}" - id: notes - template: '**Notes:** {{flow_notes}}' + template: "**Notes:** {{flow_notes}}" - id: wireframes-mockups title: Wireframes & Mockups @@ -482,13 +482,13 @@ sections: elicit: true sections: - id: design-files - template: '**Primary Design Files:** {{design_tool_link}}' + template: "**Primary Design Files:** {{design_tool_link}}" - id: key-screen-layouts title: Key Screen Layouts repeatable: true sections: - id: screen - title: '{{screen_name}}' + title: "{{screen_name}}" template: | **Purpose:** {{screen_purpose}} @@ -508,13 +508,13 @@ sections: elicit: true sections: - id: design-system-approach - template: '**Design System Approach:** {{design_system_approach}}' + template: "**Design System Approach:** {{design_system_approach}}" - id: core-components title: Core Components repeatable: true sections: - id: component - title: '{{component_name}}' + title: "{{component_name}}" template: | **Purpose:** {{component_purpose}} @@ -531,19 +531,19 @@ sections: sections: - id: visual-identity title: Visual Identity - template: '**Brand Guidelines:** {{brand_guidelines_link}}' + template: "**Brand Guidelines:** {{brand_guidelines_link}}" - id: color-palette title: Color Palette type: table - columns: ['Color Type', 'Hex Code', 'Usage'] + columns: ["Color Type", "Hex Code", "Usage"] rows: - - ['Primary', '{{primary_color}}', '{{primary_usage}}'] - - ['Secondary', '{{secondary_color}}', '{{secondary_usage}}'] - - ['Accent', '{{accent_color}}', '{{accent_usage}}'] - - ['Success', '{{success_color}}', 'Positive feedback, confirmations'] - - ['Warning', '{{warning_color}}', 'Cautions, important notices'] - - ['Error', '{{error_color}}', 'Errors, destructive actions'] - - ['Neutral', '{{neutral_colors}}', 'Text, borders, backgrounds'] + - ["Primary", "{{primary_color}}", "{{primary_usage}}"] + - ["Secondary", "{{secondary_color}}", "{{secondary_usage}}"] + - ["Accent", "{{accent_color}}", "{{accent_usage}}"] + - ["Success", "{{success_color}}", "Positive feedback, confirmations"] + - ["Warning", "{{warning_color}}", "Cautions, important notices"] + - ["Error", "{{error_color}}", "Errors, destructive actions"] + - ["Neutral", "{{neutral_colors}}", "Text, borders, backgrounds"] - id: typography title: Typography sections: @@ -556,13 +556,13 @@ sections: - id: type-scale title: Type Scale type: table - columns: ['Element', 'Size', 'Weight', 'Line Height'] + columns: ["Element", "Size", "Weight", "Line Height"] rows: - - ['H1', '{{h1_size}}', '{{h1_weight}}', '{{h1_line}}'] - - ['H2', '{{h2_size}}', '{{h2_weight}}', '{{h2_line}}'] - - ['H3', '{{h3_size}}', '{{h3_weight}}', '{{h3_line}}'] - - ['Body', '{{body_size}}', '{{body_weight}}', '{{body_line}}'] - - ['Small', '{{small_size}}', '{{small_weight}}', '{{small_line}}'] + - ["H1", "{{h1_size}}", "{{h1_weight}}", "{{h1_line}}"] + - ["H2", "{{h2_size}}", "{{h2_weight}}", "{{h2_line}}"] + - ["H3", "{{h3_size}}", "{{h3_weight}}", "{{h3_line}}"] + - ["Body", "{{body_size}}", "{{body_weight}}", "{{body_line}}"] + - ["Small", "{{small_size}}", "{{small_weight}}", "{{small_line}}"] - id: iconography title: Iconography template: | @@ -583,7 +583,7 @@ sections: sections: - id: compliance-target title: Compliance Target - template: '**Standard:** {{compliance_standard}}' + template: "**Standard:** {{compliance_standard}}" - id: key-requirements title: Key Requirements template: | @@ -603,7 +603,7 @@ sections: - Form labels: {{form_requirements}} - id: testing-strategy title: Testing Strategy - template: '{{accessibility_testing}}' + template: "{{accessibility_testing}}" - id: responsiveness title: Responsiveness Strategy @@ -613,12 +613,12 @@ sections: - id: breakpoints title: Breakpoints type: table - columns: ['Breakpoint', 'Min Width', 'Max Width', 'Target Devices'] + columns: ["Breakpoint", "Min Width", "Max Width", "Target Devices"] rows: - - ['Mobile', '{{mobile_min}}', '{{mobile_max}}', '{{mobile_devices}}'] - - ['Tablet', '{{tablet_min}}', '{{tablet_max}}', '{{tablet_devices}}'] - - ['Desktop', '{{desktop_min}}', '{{desktop_max}}', '{{desktop_devices}}'] - - ['Wide', '{{wide_min}}', '-', '{{wide_devices}}'] + - ["Mobile", "{{mobile_min}}", "{{mobile_max}}", "{{mobile_devices}}"] + - ["Tablet", "{{tablet_min}}", "{{tablet_max}}", "{{tablet_devices}}"] + - ["Desktop", "{{desktop_min}}", "{{desktop_max}}", "{{desktop_devices}}"] + - ["Wide", "{{wide_min}}", "-", "{{wide_devices}}"] - id: adaptation-patterns title: Adaptation Patterns template: | @@ -637,11 +637,11 @@ sections: sections: - id: motion-principles title: Motion Principles - template: '{{motion_principles}}' + template: "{{motion_principles}}" - id: key-animations title: Key Animations repeatable: true - template: '- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})' + template: "- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})" - id: performance title: Performance Considerations @@ -655,7 +655,7 @@ sections: - **Animation FPS:** {{animation_goal}} - id: design-strategies title: Design Strategies - template: '{{performance_strategies}}' + template: "{{performance_strategies}}" - id: next-steps title: Next Steps @@ -670,17 +670,17 @@ sections: - id: immediate-actions title: Immediate Actions type: numbered-list - template: '{{action}}' + template: "{{action}}" - id: design-handoff-checklist title: Design Handoff Checklist type: checklist items: - - 'All user flows documented' - - 'Component inventory complete' - - 'Accessibility requirements defined' - - 'Responsive strategy clear' - - 'Brand guidelines incorporated' - - 'Performance goals established' + - "All user flows documented" + - "Component inventory complete" + - "Accessibility requirements defined" + - "Responsive strategy clear" + - "Brand guidelines incorporated" + - "Performance goals established" - id: checklist-results title: Checklist Results diff --git a/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt b/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt index de4250fd..b5fa9723 100644 --- a/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt +++ b/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt @@ -981,8 +981,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-game-design-document.md' - title: '{{game_title}} Game Design Document (GDD)' + filename: "docs/{{game_name}}-game-design-document.md" + title: "{{game_title}} Game Design Document (GDD)" workflow: mode: interactive @@ -1019,7 +1019,7 @@ sections: title: Unique Selling Points instruction: List 3-5 key features that differentiate this game from competitors type: numbered-list - template: '{{usp}}' + template: "{{usp}}" - id: core-gameplay title: Core Gameplay @@ -1064,7 +1064,7 @@ sections: repeatable: true sections: - id: mechanic - title: '{{mechanic_name}}' + title: "{{mechanic_name}}" template: | **Description:** {{detailed_description}} @@ -1129,7 +1129,7 @@ sections: repeatable: true sections: - id: level-type - title: '{{level_type_name}}' + title: "{{level_type_name}}" template: | **Purpose:** {{gameplay_purpose}} **Duration:** {{target_time}} @@ -1230,10 +1230,10 @@ sections: instruction: Break down the development into phases that can be converted to epics sections: - id: phase-1-core-systems - title: 'Phase 1: Core Systems ({{duration}})' + title: "Phase 1: Core Systems ({{duration}})" sections: - id: foundation-epic - title: 'Epic: Foundation' + title: "Epic: Foundation" type: bullet-list template: | - Engine setup and configuration @@ -1241,41 +1241,41 @@ sections: - Core input handling - Asset loading pipeline - id: core-mechanics-epic - title: 'Epic: Core Mechanics' + title: "Epic: Core Mechanics" type: bullet-list template: | - {{primary_mechanic}} implementation - Basic physics and collision - Player controller - id: phase-2-gameplay-features - title: 'Phase 2: Gameplay Features ({{duration}})' + title: "Phase 2: Gameplay Features ({{duration}})" sections: - id: game-systems-epic - title: 'Epic: Game Systems' + title: "Epic: Game Systems" type: bullet-list template: | - {{mechanic_2}} implementation - {{mechanic_3}} implementation - Game state management - id: content-creation-epic - title: 'Epic: Content Creation' + title: "Epic: Content Creation" type: bullet-list template: | - Level loading system - First playable levels - Basic UI implementation - id: phase-3-polish-optimization - title: 'Phase 3: Polish & Optimization ({{duration}})' + title: "Phase 3: Polish & Optimization ({{duration}})" sections: - id: performance-epic - title: 'Epic: Performance' + title: "Epic: Performance" type: bullet-list template: | - Optimization and profiling - Mobile platform testing - Memory management - id: user-experience-epic - title: 'Epic: User Experience' + title: "Epic: User Experience" type: bullet-list template: | - Audio implementation @@ -1317,7 +1317,7 @@ sections: title: References instruction: List any competitive analysis, inspiration, or research sources type: bullet-list - template: '{{reference}}' + template: "{{reference}}" ==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ==================== ==================== START: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ==================== @@ -1327,8 +1327,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-level-design-document.md' - title: '{{game_title}} Level Design Document' + filename: "docs/{{game_name}}-level-design-document.md" + title: "{{game_title}} Level Design Document" workflow: mode: interactive @@ -1389,7 +1389,7 @@ sections: repeatable: true sections: - id: level-category - title: '{{category_name}} Levels' + title: "{{category_name}} Levels" template: | **Purpose:** {{gameplay_purpose}} @@ -1694,19 +1694,19 @@ sections: title: Playtesting Checklist type: checklist items: - - 'Level completes within target time range' - - 'All mechanics function correctly' - - 'Difficulty feels appropriate for level category' - - 'Player guidance is clear and effective' - - 'No exploits or sequence breaks (unless intended)' + - "Level completes within target time range" + - "All mechanics function correctly" + - "Difficulty feels appropriate for level category" + - "Player guidance is clear and effective" + - "No exploits or sequence breaks (unless intended)" - id: player-experience-testing title: Player Experience Testing type: checklist items: - - 'Tutorial levels teach effectively' - - 'Challenge feels fair and rewarding' - - 'Flow and pacing maintain engagement' - - 'Audio and visual feedback support gameplay' + - "Tutorial levels teach effectively" + - "Challenge feels fair and rewarding" + - "Flow and pacing maintain engagement" + - "Audio and visual feedback support gameplay" - id: balance-validation title: Balance Validation template: | @@ -1814,8 +1814,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-game-brief.md' - title: '{{game_title}} Game Brief' + filename: "docs/{{game_name}}-game-brief.md" + title: "{{game_title}} Game Brief" workflow: mode: interactive @@ -2101,21 +2101,21 @@ sections: title: Development Roadmap sections: - id: phase-1-preproduction - title: 'Phase 1: Pre-Production ({{duration}})' + title: "Phase 1: Pre-Production ({{duration}})" type: bullet-list template: | - Detailed Game Design Document creation - Technical architecture planning - Art style exploration and pipeline setup - id: phase-2-prototype - title: 'Phase 2: Prototype ({{duration}})' + title: "Phase 2: Prototype ({{duration}})" type: bullet-list template: | - Core mechanic implementation - Technical proof of concept - Initial playtesting and iteration - id: phase-3-production - title: 'Phase 3: Production ({{duration}})' + title: "Phase 3: Production ({{duration}})" type: bullet-list template: | - Full feature development diff --git a/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt b/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt index 7adc27b3..e8b10de4 100644 --- a/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt +++ b/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt @@ -197,8 +197,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-game-architecture.md' - title: '{{game_title}} Game Architecture Document' + filename: "docs/{{game_name}}-game-architecture.md" + title: "{{game_title}} Game Architecture Document" workflow: mode: interactive @@ -422,7 +422,7 @@ sections: repeatable: true sections: - id: mechanic-system - title: '{{mechanic_name}} System' + title: "{{mechanic_name}} System" template: | **Purpose:** {{system_purpose}} @@ -719,7 +719,7 @@ sections: instruction: Break down the architecture implementation into phases that align with the GDD development phases sections: - id: phase-1-foundation - title: 'Phase 1: Foundation ({{duration}})' + title: "Phase 1: Foundation ({{duration}})" sections: - id: phase-1-core title: Core Systems @@ -737,7 +737,7 @@ sections: - "Basic Scene Management System" - "Asset Loading Foundation" - id: phase-2-game-systems - title: 'Phase 2: Game Systems ({{duration}})' + title: "Phase 2: Game Systems ({{duration}})" sections: - id: phase-2-gameplay title: Gameplay Systems @@ -755,7 +755,7 @@ sections: - "Physics and Collision Framework" - "Game State Management System" - id: phase-3-content-polish - title: 'Phase 3: Content & Polish ({{duration}})' + title: "Phase 3: Content & Polish ({{duration}})" sections: - id: phase-3-content title: Content Systems diff --git a/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt b/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt index 87c970ee..c38591de 100644 --- a/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt +++ b/dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt @@ -402,8 +402,8 @@ template: version: 2.0 output: format: markdown - filename: 'stories/{{epic_name}}/{{story_id}}-{{story_name}}.md' - title: 'Story: {{story_title}}' + filename: "stories/{{epic_name}}/{{story_id}}-{{story_name}}.md" + title: "Story: {{story_title}}" workflow: mode: interactive @@ -432,7 +432,7 @@ sections: - id: description title: Description instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature. - template: '{{clear_description_of_what_needs_to_be_implemented}}' + template: "{{clear_description_of_what_needs_to_be_implemented}}" - id: acceptance-criteria title: Acceptance Criteria @@ -442,22 +442,22 @@ sections: title: Functional Requirements type: checklist items: - - '{{specific_functional_requirement}}' + - "{{specific_functional_requirement}}" - id: technical-requirements title: Technical Requirements type: checklist items: - - 'Code follows TypeScript strict mode standards' - - 'Maintains 60 FPS on target devices' - - 'No memory leaks or performance degradation' - - '{{specific_technical_requirement}}' + - "Code follows TypeScript strict mode standards" + - "Maintains 60 FPS on target devices" + - "No memory leaks or performance degradation" + - "{{specific_technical_requirement}}" - id: game-design-requirements title: Game Design Requirements type: checklist items: - - '{{gameplay_requirement_from_gdd}}' - - '{{balance_requirement_if_applicable}}' - - '{{player_experience_requirement}}' + - "{{gameplay_requirement_from_gdd}}" + - "{{balance_requirement_if_applicable}}" + - "{{player_experience_requirement}}" - id: technical-specifications title: Technical Specifications @@ -622,14 +622,14 @@ sections: instruction: Checklist that must be completed before the story is considered finished type: checklist items: - - 'All acceptance criteria met' - - 'Code reviewed and approved' - - 'Unit tests written and passing' - - 'Integration tests passing' - - 'Performance targets met' - - 'No linting errors' - - 'Documentation updated' - - '{{game_specific_dod_item}}' + - "All acceptance criteria met" + - "Code reviewed and approved" + - "Unit tests written and passing" + - "Integration tests passing" + - "Performance targets met" + - "No linting errors" + - "Documentation updated" + - "{{game_specific_dod_item}}" - id: notes title: Notes diff --git a/dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt b/dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt index 7ca15973..2f275ee6 100644 --- a/dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt +++ b/dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt @@ -1408,24 +1408,24 @@ template: output: format: markdown filename: docs/brief.md - title: 'Project Brief: {{project_name}}' + title: "Project Brief: {{project_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Project Brief Elicitation Actions' + title: "Project Brief Elicitation Actions" options: - - 'Expand section with more specific details' - - 'Validate against similar successful products' - - 'Stress test assumptions with edge cases' - - 'Explore alternative solution approaches' - - 'Analyze resource/constraint trade-offs' - - 'Generate risk mitigation strategies' - - 'Challenge scope from MVP minimalist view' - - 'Brainstorm creative feature possibilities' - - 'If only we had [resource/capability/time]...' - - 'Proceed to next section' + - "Expand section with more specific details" + - "Validate against similar successful products" + - "Stress test assumptions with edge cases" + - "Explore alternative solution approaches" + - "Analyze resource/constraint trade-offs" + - "Generate risk mitigation strategies" + - "Challenge scope from MVP minimalist view" + - "Brainstorm creative feature possibilities" + - "If only we had [resource/capability/time]..." + - "Proceed to next section" sections: - id: introduction @@ -1447,7 +1447,7 @@ sections: - Primary problem being solved - Target market identification - Key value proposition - template: '{{executive_summary_content}}' + template: "{{executive_summary_content}}" - id: problem-statement title: Problem Statement @@ -1457,7 +1457,7 @@ sections: - Impact of the problem (quantify if possible) - Why existing solutions fall short - Urgency and importance of solving this now - template: '{{detailed_problem_description}}' + template: "{{detailed_problem_description}}" - id: proposed-solution title: Proposed Solution @@ -1467,7 +1467,7 @@ sections: - Key differentiators from existing solutions - Why this solution will succeed where others haven't - High-level vision for the product - template: '{{solution_description}}' + template: "{{solution_description}}" - id: target-users title: Target Users @@ -1479,12 +1479,12 @@ sections: - Goals they're trying to achieve sections: - id: primary-segment - title: 'Primary User Segment: {{segment_name}}' - template: '{{primary_user_description}}' + title: "Primary User Segment: {{segment_name}}" + template: "{{primary_user_description}}" - id: secondary-segment - title: 'Secondary User Segment: {{segment_name}}' + title: "Secondary User Segment: {{segment_name}}" condition: Has secondary user segment - template: '{{secondary_user_description}}' + template: "{{secondary_user_description}}" - id: goals-metrics title: Goals & Success Metrics @@ -1493,15 +1493,15 @@ sections: - id: business-objectives title: Business Objectives type: bullet-list - template: '- {{objective_with_metric}}' + template: "- {{objective_with_metric}}" - id: user-success-metrics title: User Success Metrics type: bullet-list - template: '- {{user_metric}}' + template: "- {{user_metric}}" - id: kpis title: Key Performance Indicators (KPIs) type: bullet-list - template: '- {{kpi}}: {{definition_and_target}}' + template: "- {{kpi}}: {{definition_and_target}}" - id: mvp-scope title: MVP Scope @@ -1510,14 +1510,14 @@ sections: - id: core-features title: Core Features (Must Have) type: bullet-list - template: '- **{{feature}}:** {{description_and_rationale}}' + template: "- **{{feature}}:** {{description_and_rationale}}" - id: out-of-scope title: Out of Scope for MVP type: bullet-list - template: '- {{feature_or_capability}}' + template: "- {{feature_or_capability}}" - id: mvp-success-criteria title: MVP Success Criteria - template: '{{mvp_success_definition}}' + template: "{{mvp_success_definition}}" - id: post-mvp-vision title: Post-MVP Vision @@ -1525,13 +1525,13 @@ sections: sections: - id: phase-2-features title: Phase 2 Features - template: '{{next_priority_features}}' + template: "{{next_priority_features}}" - id: long-term-vision title: Long-term Vision - template: '{{one_two_year_vision}}' + template: "{{one_two_year_vision}}" - id: expansion-opportunities title: Expansion Opportunities - template: '{{potential_expansions}}' + template: "{{potential_expansions}}" - id: technical-considerations title: Technical Considerations @@ -1572,7 +1572,7 @@ sections: - id: key-assumptions title: Key Assumptions type: bullet-list - template: '- {{assumption}}' + template: "- {{assumption}}" - id: risks-questions title: Risks & Open Questions @@ -1581,15 +1581,15 @@ sections: - id: key-risks title: Key Risks type: bullet-list - template: '- **{{risk}}:** {{description_and_impact}}' + template: "- **{{risk}}:** {{description_and_impact}}" - id: open-questions title: Open Questions type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: research-areas title: Areas Needing Further Research type: bullet-list - template: '- {{research_topic}}' + template: "- {{research_topic}}" - id: appendices title: Appendices @@ -1606,10 +1606,10 @@ sections: - id: stakeholder-input title: B. Stakeholder Input condition: Has stakeholder feedback - template: '{{stakeholder_feedback}}' + template: "{{stakeholder_feedback}}" - id: references title: C. References - template: '{{relevant_links_and_docs}}' + template: "{{relevant_links_and_docs}}" - id: next-steps title: Next Steps @@ -1617,7 +1617,7 @@ sections: - id: immediate-actions title: Immediate Actions type: numbered-list - template: '{{action_item}}' + template: "{{action_item}}" - id: pm-handoff title: PM Handoff content: | @@ -1632,24 +1632,24 @@ template: output: format: markdown filename: docs/market-research.md - title: 'Market Research Report: {{project_product_name}}' + title: "Market Research Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Market Research Elicitation Actions' + title: "Market Research Elicitation Actions" options: - - 'Expand market sizing calculations with sensitivity analysis' - - 'Deep dive into a specific customer segment' - - 'Analyze an emerging market trend in detail' - - 'Compare this market to an analogous market' - - 'Stress test market assumptions' - - 'Explore adjacent market opportunities' - - 'Challenge market definition and boundaries' - - 'Generate strategic scenarios (best/base/worst case)' - - 'If only we had considered [X market factor]...' - - 'Proceed to next section' + - "Expand market sizing calculations with sensitivity analysis" + - "Deep dive into a specific customer segment" + - "Analyze an emerging market trend in detail" + - "Compare this market to an analogous market" + - "Stress test market assumptions" + - "Explore adjacent market opportunities" + - "Challenge market definition and boundaries" + - "Generate strategic scenarios (best/base/worst case)" + - "If only we had considered [X market factor]..." + - "Proceed to next section" sections: - id: executive-summary @@ -1731,7 +1731,7 @@ sections: repeatable: true sections: - id: segment - title: 'Segment {{segment_number}}: {{segment_name}}' + title: "Segment {{segment_number}}: {{segment_name}}" template: | - **Description:** {{brief_overview}} - **Size:** {{number_of_customers_market_value}} @@ -1800,20 +1800,20 @@ sections: instruction: Analyze each force with specific evidence and implications sections: - id: supplier-power - title: 'Supplier Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Supplier Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: buyer-power - title: 'Buyer Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Buyer Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: competitive-rivalry - title: 'Competitive Rivalry: {{intensity_level}}' - template: '{{analysis_and_implications}}' + title: "Competitive Rivalry: {{intensity_level}}" + template: "{{analysis_and_implications}}" - id: threat-new-entry - title: 'Threat of New Entry: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of New Entry: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: threat-substitutes - title: 'Threat of Substitutes: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of Substitutes: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: adoption-lifecycle title: Technology Adoption Lifecycle Stage instruction: | @@ -1831,7 +1831,7 @@ sections: repeatable: true sections: - id: opportunity - title: 'Opportunity {{opportunity_number}}: {{name}}' + title: "Opportunity {{opportunity_number}}: {{name}}" template: | - **Description:** {{what_is_the_opportunity}} - **Size/Potential:** {{quantified_potential}} @@ -1887,24 +1887,24 @@ template: output: format: markdown filename: docs/competitor-analysis.md - title: 'Competitive Analysis Report: {{project_product_name}}' + title: "Competitive Analysis Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Competitive Analysis Elicitation Actions' + title: "Competitive Analysis Elicitation Actions" options: - "Deep dive on a specific competitor's strategy" - - 'Analyze competitive dynamics in a specific segment' - - 'War game competitive responses to your moves' - - 'Explore partnership vs. competition scenarios' - - 'Stress test differentiation claims' - - 'Analyze disruption potential (yours or theirs)' - - 'Compare to competition in adjacent markets' - - 'Generate win/loss analysis insights' + - "Analyze competitive dynamics in a specific segment" + - "War game competitive responses to your moves" + - "Explore partnership vs. competition scenarios" + - "Stress test differentiation claims" + - "Analyze disruption potential (yours or theirs)" + - "Compare to competition in adjacent markets" + - "Generate win/loss analysis insights" - "If only we had known about [competitor X's plan]..." - - 'Proceed to next section' + - "Proceed to next section" sections: - id: executive-summary @@ -1971,7 +1971,7 @@ sections: repeatable: true sections: - id: competitor - title: '{{competitor_name}} - Priority {{priority_level}}' + title: "{{competitor_name}} - Priority {{priority_level}}" sections: - id: company-overview title: Company Overview @@ -2003,11 +2003,11 @@ sections: - id: strengths title: Strengths type: bullet-list - template: '- {{strength}}' + template: "- {{strength}}" - id: weaknesses title: Weaknesses type: bullet-list - template: '- {{weakness}}' + template: "- {{weakness}}" - id: market-position title: Market Position & Performance template: | @@ -2025,35 +2025,35 @@ sections: type: table columns: [ - 'Feature Category', - '{{your_company}}', - '{{competitor_1}}', - '{{competitor_2}}', - '{{competitor_3}}', + "Feature Category", + "{{your_company}}", + "{{competitor_1}}", + "{{competitor_2}}", + "{{competitor_3}}", ] rows: - - category: 'Core Functionality' + - category: "Core Functionality" items: - - ['Feature A', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - ['Feature B', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - category: 'User Experience' + - ["Feature A", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - ["Feature B", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - category: "User Experience" items: - - ['Mobile App', '{{rating}}', '{{rating}}', '{{rating}}', '{{rating}}'] - - ['Onboarding Time', '{{time}}', '{{time}}', '{{time}}', '{{time}}'] - - category: 'Integration & Ecosystem' + - ["Mobile App", "{{rating}}", "{{rating}}", "{{rating}}", "{{rating}}"] + - ["Onboarding Time", "{{time}}", "{{time}}", "{{time}}", "{{time}}"] + - category: "Integration & Ecosystem" items: - [ - 'API Availability', - '{{availability}}', - '{{availability}}', - '{{availability}}', - '{{availability}}', + "API Availability", + "{{availability}}", + "{{availability}}", + "{{availability}}", + "{{availability}}", ] - - ['Third-party Integrations', '{{number}}', '{{number}}', '{{number}}', '{{number}}'] - - category: 'Pricing & Plans' + - ["Third-party Integrations", "{{number}}", "{{number}}", "{{number}}", "{{number}}"] + - category: "Pricing & Plans" items: - - ['Starting Price', '{{price}}', '{{price}}', '{{price}}', '{{price}}'] - - ['Free Tier', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}'] + - ["Starting Price", "{{price}}", "{{price}}", "{{price}}", "{{price}}"] + - ["Free Tier", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}"] - id: swot-comparison title: SWOT Comparison instruction: Create SWOT analysis for your solution vs. top competitors @@ -2066,7 +2066,7 @@ sections: - **Opportunities:** {{opportunities}} - **Threats:** {{threats}} - id: vs-competitor - title: 'vs. {{main_competitor}}' + title: "vs. {{main_competitor}}" template: | - **Competitive Advantages:** {{your_advantages}} - **Competitive Disadvantages:** {{their_advantages}} @@ -2196,7 +2196,7 @@ template: output: format: markdown filename: docs/brainstorming-session-results.md - title: 'Brainstorming Session Results' + title: "Brainstorming Session Results" workflow: mode: non-interactive @@ -2221,38 +2221,38 @@ sections: **Total Ideas Generated:** {{total_ideas}} - id: key-themes - title: 'Key Themes Identified:' + title: "Key Themes Identified:" type: bullet-list - template: '- {{theme}}' + template: "- {{theme}}" - id: technique-sessions title: Technique Sessions repeatable: true sections: - id: technique - title: '{{technique_name}} - {{duration}}' + title: "{{technique_name}} - {{duration}}" sections: - id: description - template: '**Description:** {{technique_description}}' + template: "**Description:** {{technique_description}}" - id: ideas-generated - title: 'Ideas Generated:' + title: "Ideas Generated:" type: numbered-list - template: '{{idea}}' + template: "{{idea}}" - id: insights - title: 'Insights Discovered:' + title: "Insights Discovered:" type: bullet-list - template: '- {{insight}}' + template: "- {{insight}}" - id: connections - title: 'Notable Connections:' + title: "Notable Connections:" type: bullet-list - template: '- {{connection}}' + template: "- {{connection}}" - id: idea-categorization title: Idea Categorization sections: - id: immediate-opportunities title: Immediate Opportunities - content: '*Ideas ready to implement now*' + content: "*Ideas ready to implement now*" repeatable: true type: numbered-list template: | @@ -2262,7 +2262,7 @@ sections: - Resources needed: {{requirements}} - id: future-innovations title: Future Innovations - content: '*Ideas requiring development/research*' + content: "*Ideas requiring development/research*" repeatable: true type: numbered-list template: | @@ -2272,7 +2272,7 @@ sections: - Timeline estimate: {{timeline}} - id: moonshots title: Moonshots - content: '*Ambitious, transformative concepts*' + content: "*Ambitious, transformative concepts*" repeatable: true type: numbered-list template: | @@ -2282,9 +2282,9 @@ sections: - Challenges to overcome: {{challenges}} - id: insights-learnings title: Insights & Learnings - content: '*Key realizations from the session*' + content: "*Key realizations from the session*" type: bullet-list - template: '- {{insight}}: {{description_and_implications}}' + template: "- {{insight}}: {{description_and_implications}}" - id: action-planning title: Action Planning @@ -2293,21 +2293,21 @@ sections: title: Top 3 Priority Ideas sections: - id: priority-1 - title: '#1 Priority: {{idea_name}}' + title: "#1 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-2 - title: '#2 Priority: {{idea_name}}' + title: "#2 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-3 - title: '#3 Priority: {{idea_name}}' + title: "#3 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} @@ -2320,19 +2320,19 @@ sections: - id: what-worked title: What Worked Well type: bullet-list - template: '- {{aspect}}' + template: "- {{aspect}}" - id: areas-exploration title: Areas for Further Exploration type: bullet-list - template: '- {{area}}: {{reason}}' + template: "- {{area}}: {{reason}}" - id: recommended-techniques title: Recommended Follow-up Techniques type: bullet-list - template: '- {{technique}}: {{reason}}' + template: "- {{technique}}: {{reason}}" - id: questions-emerged title: Questions That Emerged type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: next-session title: Next Session Planning template: | @@ -3335,8 +3335,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-game-design-document.md' - title: '{{game_title}} Game Design Document (GDD)' + filename: "docs/{{game_name}}-game-design-document.md" + title: "{{game_title}} Game Design Document (GDD)" workflow: mode: interactive @@ -3373,7 +3373,7 @@ sections: title: Unique Selling Points instruction: List 3-5 key features that differentiate this game from competitors type: numbered-list - template: '{{usp}}' + template: "{{usp}}" - id: core-gameplay title: Core Gameplay @@ -3418,7 +3418,7 @@ sections: repeatable: true sections: - id: mechanic - title: '{{mechanic_name}}' + title: "{{mechanic_name}}" template: | **Description:** {{detailed_description}} @@ -3483,7 +3483,7 @@ sections: repeatable: true sections: - id: level-type - title: '{{level_type_name}}' + title: "{{level_type_name}}" template: | **Purpose:** {{gameplay_purpose}} **Duration:** {{target_time}} @@ -3584,10 +3584,10 @@ sections: instruction: Break down the development into phases that can be converted to epics sections: - id: phase-1-core-systems - title: 'Phase 1: Core Systems ({{duration}})' + title: "Phase 1: Core Systems ({{duration}})" sections: - id: foundation-epic - title: 'Epic: Foundation' + title: "Epic: Foundation" type: bullet-list template: | - Engine setup and configuration @@ -3595,41 +3595,41 @@ sections: - Core input handling - Asset loading pipeline - id: core-mechanics-epic - title: 'Epic: Core Mechanics' + title: "Epic: Core Mechanics" type: bullet-list template: | - {{primary_mechanic}} implementation - Basic physics and collision - Player controller - id: phase-2-gameplay-features - title: 'Phase 2: Gameplay Features ({{duration}})' + title: "Phase 2: Gameplay Features ({{duration}})" sections: - id: game-systems-epic - title: 'Epic: Game Systems' + title: "Epic: Game Systems" type: bullet-list template: | - {{mechanic_2}} implementation - {{mechanic_3}} implementation - Game state management - id: content-creation-epic - title: 'Epic: Content Creation' + title: "Epic: Content Creation" type: bullet-list template: | - Level loading system - First playable levels - Basic UI implementation - id: phase-3-polish-optimization - title: 'Phase 3: Polish & Optimization ({{duration}})' + title: "Phase 3: Polish & Optimization ({{duration}})" sections: - id: performance-epic - title: 'Epic: Performance' + title: "Epic: Performance" type: bullet-list template: | - Optimization and profiling - Mobile platform testing - Memory management - id: user-experience-epic - title: 'Epic: User Experience' + title: "Epic: User Experience" type: bullet-list template: | - Audio implementation @@ -3671,7 +3671,7 @@ sections: title: References instruction: List any competitive analysis, inspiration, or research sources type: bullet-list - template: '{{reference}}' + template: "{{reference}}" ==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ==================== ==================== START: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ==================== @@ -3681,8 +3681,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-level-design-document.md' - title: '{{game_title}} Level Design Document' + filename: "docs/{{game_name}}-level-design-document.md" + title: "{{game_title}} Level Design Document" workflow: mode: interactive @@ -3743,7 +3743,7 @@ sections: repeatable: true sections: - id: level-category - title: '{{category_name}} Levels' + title: "{{category_name}} Levels" template: | **Purpose:** {{gameplay_purpose}} @@ -4048,19 +4048,19 @@ sections: title: Playtesting Checklist type: checklist items: - - 'Level completes within target time range' - - 'All mechanics function correctly' - - 'Difficulty feels appropriate for level category' - - 'Player guidance is clear and effective' - - 'No exploits or sequence breaks (unless intended)' + - "Level completes within target time range" + - "All mechanics function correctly" + - "Difficulty feels appropriate for level category" + - "Player guidance is clear and effective" + - "No exploits or sequence breaks (unless intended)" - id: player-experience-testing title: Player Experience Testing type: checklist items: - - 'Tutorial levels teach effectively' - - 'Challenge feels fair and rewarding' - - 'Flow and pacing maintain engagement' - - 'Audio and visual feedback support gameplay' + - "Tutorial levels teach effectively" + - "Challenge feels fair and rewarding" + - "Flow and pacing maintain engagement" + - "Audio and visual feedback support gameplay" - id: balance-validation title: Balance Validation template: | @@ -4168,8 +4168,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-game-brief.md' - title: '{{game_title}} Game Brief' + filename: "docs/{{game_name}}-game-brief.md" + title: "{{game_title}} Game Brief" workflow: mode: interactive @@ -4455,21 +4455,21 @@ sections: title: Development Roadmap sections: - id: phase-1-preproduction - title: 'Phase 1: Pre-Production ({{duration}})' + title: "Phase 1: Pre-Production ({{duration}})" type: bullet-list template: | - Detailed Game Design Document creation - Technical architecture planning - Art style exploration and pipeline setup - id: phase-2-prototype - title: 'Phase 2: Prototype ({{duration}})' + title: "Phase 2: Prototype ({{duration}})" type: bullet-list template: | - Core mechanic implementation - Technical proof of concept - Initial playtesting and iteration - id: phase-3-production - title: 'Phase 3: Production ({{duration}})' + title: "Phase 3: Production ({{duration}})" type: bullet-list template: | - Full feature development @@ -4731,8 +4731,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-game-architecture.md' - title: '{{game_title}} Game Architecture Document' + filename: "docs/{{game_name}}-game-architecture.md" + title: "{{game_title}} Game Architecture Document" workflow: mode: interactive @@ -4956,7 +4956,7 @@ sections: repeatable: true sections: - id: mechanic-system - title: '{{mechanic_name}} System' + title: "{{mechanic_name}} System" template: | **Purpose:** {{system_purpose}} @@ -5253,7 +5253,7 @@ sections: instruction: Break down the architecture implementation into phases that align with the GDD development phases sections: - id: phase-1-foundation - title: 'Phase 1: Foundation ({{duration}})' + title: "Phase 1: Foundation ({{duration}})" sections: - id: phase-1-core title: Core Systems @@ -5271,7 +5271,7 @@ sections: - "Basic Scene Management System" - "Asset Loading Foundation" - id: phase-2-game-systems - title: 'Phase 2: Game Systems ({{duration}})' + title: "Phase 2: Game Systems ({{duration}})" sections: - id: phase-2-gameplay title: Gameplay Systems @@ -5289,7 +5289,7 @@ sections: - "Physics and Collision Framework" - "Game State Management System" - id: phase-3-content-polish - title: 'Phase 3: Content & Polish ({{duration}})' + title: "Phase 3: Content & Polish ({{duration}})" sections: - id: phase-3-content title: Content Systems @@ -6379,8 +6379,8 @@ template: version: 2.0 output: format: markdown - filename: 'stories/{{epic_name}}/{{story_id}}-{{story_name}}.md' - title: 'Story: {{story_title}}' + filename: "stories/{{epic_name}}/{{story_id}}-{{story_name}}.md" + title: "Story: {{story_title}}" workflow: mode: interactive @@ -6409,7 +6409,7 @@ sections: - id: description title: Description instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature. - template: '{{clear_description_of_what_needs_to_be_implemented}}' + template: "{{clear_description_of_what_needs_to_be_implemented}}" - id: acceptance-criteria title: Acceptance Criteria @@ -6419,22 +6419,22 @@ sections: title: Functional Requirements type: checklist items: - - '{{specific_functional_requirement}}' + - "{{specific_functional_requirement}}" - id: technical-requirements title: Technical Requirements type: checklist items: - - 'Code follows TypeScript strict mode standards' - - 'Maintains 60 FPS on target devices' - - 'No memory leaks or performance degradation' - - '{{specific_technical_requirement}}' + - "Code follows TypeScript strict mode standards" + - "Maintains 60 FPS on target devices" + - "No memory leaks or performance degradation" + - "{{specific_technical_requirement}}" - id: game-design-requirements title: Game Design Requirements type: checklist items: - - '{{gameplay_requirement_from_gdd}}' - - '{{balance_requirement_if_applicable}}' - - '{{player_experience_requirement}}' + - "{{gameplay_requirement_from_gdd}}" + - "{{balance_requirement_if_applicable}}" + - "{{player_experience_requirement}}" - id: technical-specifications title: Technical Specifications @@ -6599,14 +6599,14 @@ sections: instruction: Checklist that must be completed before the story is considered finished type: checklist items: - - 'All acceptance criteria met' - - 'Code reviewed and approved' - - 'Unit tests written and passing' - - 'Integration tests passing' - - 'Performance targets met' - - 'No linting errors' - - 'Documentation updated' - - '{{game_specific_dod_item}}' + - "All acceptance criteria met" + - "Code reviewed and approved" + - "Unit tests written and passing" + - "Integration tests passing" + - "Performance targets met" + - "No linting errors" + - "Documentation updated" + - "{{game_specific_dod_item}}" - id: notes title: Notes @@ -6635,8 +6635,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-game-architecture.md' - title: '{{game_title}} Game Architecture Document' + filename: "docs/{{game_name}}-game-architecture.md" + title: "{{game_title}} Game Architecture Document" workflow: mode: interactive @@ -6860,7 +6860,7 @@ sections: repeatable: true sections: - id: mechanic-system - title: '{{mechanic_name}} System' + title: "{{mechanic_name}} System" template: | **Purpose:** {{system_purpose}} @@ -7157,7 +7157,7 @@ sections: instruction: Break down the architecture implementation into phases that align with the GDD development phases sections: - id: phase-1-foundation - title: 'Phase 1: Foundation ({{duration}})' + title: "Phase 1: Foundation ({{duration}})" sections: - id: phase-1-core title: Core Systems @@ -7175,7 +7175,7 @@ sections: - "Basic Scene Management System" - "Asset Loading Foundation" - id: phase-2-game-systems - title: 'Phase 2: Game Systems ({{duration}})' + title: "Phase 2: Game Systems ({{duration}})" sections: - id: phase-2-gameplay title: Gameplay Systems @@ -7193,7 +7193,7 @@ sections: - "Physics and Collision Framework" - "Game State Management System" - id: phase-3-content-polish - title: 'Phase 3: Content & Polish ({{duration}})' + title: "Phase 3: Content & Polish ({{duration}})" sections: - id: phase-3-content title: Content Systems @@ -7251,8 +7251,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-game-brief.md' - title: '{{game_title}} Game Brief' + filename: "docs/{{game_name}}-game-brief.md" + title: "{{game_title}} Game Brief" workflow: mode: interactive @@ -7538,21 +7538,21 @@ sections: title: Development Roadmap sections: - id: phase-1-preproduction - title: 'Phase 1: Pre-Production ({{duration}})' + title: "Phase 1: Pre-Production ({{duration}})" type: bullet-list template: | - Detailed Game Design Document creation - Technical architecture planning - Art style exploration and pipeline setup - id: phase-2-prototype - title: 'Phase 2: Prototype ({{duration}})' + title: "Phase 2: Prototype ({{duration}})" type: bullet-list template: | - Core mechanic implementation - Technical proof of concept - Initial playtesting and iteration - id: phase-3-production - title: 'Phase 3: Production ({{duration}})' + title: "Phase 3: Production ({{duration}})" type: bullet-list template: | - Full feature development @@ -7610,8 +7610,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-game-design-document.md' - title: '{{game_title}} Game Design Document (GDD)' + filename: "docs/{{game_name}}-game-design-document.md" + title: "{{game_title}} Game Design Document (GDD)" workflow: mode: interactive @@ -7648,7 +7648,7 @@ sections: title: Unique Selling Points instruction: List 3-5 key features that differentiate this game from competitors type: numbered-list - template: '{{usp}}' + template: "{{usp}}" - id: core-gameplay title: Core Gameplay @@ -7693,7 +7693,7 @@ sections: repeatable: true sections: - id: mechanic - title: '{{mechanic_name}}' + title: "{{mechanic_name}}" template: | **Description:** {{detailed_description}} @@ -7758,7 +7758,7 @@ sections: repeatable: true sections: - id: level-type - title: '{{level_type_name}}' + title: "{{level_type_name}}" template: | **Purpose:** {{gameplay_purpose}} **Duration:** {{target_time}} @@ -7859,10 +7859,10 @@ sections: instruction: Break down the development into phases that can be converted to epics sections: - id: phase-1-core-systems - title: 'Phase 1: Core Systems ({{duration}})' + title: "Phase 1: Core Systems ({{duration}})" sections: - id: foundation-epic - title: 'Epic: Foundation' + title: "Epic: Foundation" type: bullet-list template: | - Engine setup and configuration @@ -7870,41 +7870,41 @@ sections: - Core input handling - Asset loading pipeline - id: core-mechanics-epic - title: 'Epic: Core Mechanics' + title: "Epic: Core Mechanics" type: bullet-list template: | - {{primary_mechanic}} implementation - Basic physics and collision - Player controller - id: phase-2-gameplay-features - title: 'Phase 2: Gameplay Features ({{duration}})' + title: "Phase 2: Gameplay Features ({{duration}})" sections: - id: game-systems-epic - title: 'Epic: Game Systems' + title: "Epic: Game Systems" type: bullet-list template: | - {{mechanic_2}} implementation - {{mechanic_3}} implementation - Game state management - id: content-creation-epic - title: 'Epic: Content Creation' + title: "Epic: Content Creation" type: bullet-list template: | - Level loading system - First playable levels - Basic UI implementation - id: phase-3-polish-optimization - title: 'Phase 3: Polish & Optimization ({{duration}})' + title: "Phase 3: Polish & Optimization ({{duration}})" sections: - id: performance-epic - title: 'Epic: Performance' + title: "Epic: Performance" type: bullet-list template: | - Optimization and profiling - Mobile platform testing - Memory management - id: user-experience-epic - title: 'Epic: User Experience' + title: "Epic: User Experience" type: bullet-list template: | - Audio implementation @@ -7946,7 +7946,7 @@ sections: title: References instruction: List any competitive analysis, inspiration, or research sources type: bullet-list - template: '{{reference}}' + template: "{{reference}}" ==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ==================== ==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ==================== @@ -7956,8 +7956,8 @@ template: version: 2.0 output: format: markdown - filename: 'stories/{{epic_name}}/{{story_id}}-{{story_name}}.md' - title: 'Story: {{story_title}}' + filename: "stories/{{epic_name}}/{{story_id}}-{{story_name}}.md" + title: "Story: {{story_title}}" workflow: mode: interactive @@ -7986,7 +7986,7 @@ sections: - id: description title: Description instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature. - template: '{{clear_description_of_what_needs_to_be_implemented}}' + template: "{{clear_description_of_what_needs_to_be_implemented}}" - id: acceptance-criteria title: Acceptance Criteria @@ -7996,22 +7996,22 @@ sections: title: Functional Requirements type: checklist items: - - '{{specific_functional_requirement}}' + - "{{specific_functional_requirement}}" - id: technical-requirements title: Technical Requirements type: checklist items: - - 'Code follows TypeScript strict mode standards' - - 'Maintains 60 FPS on target devices' - - 'No memory leaks or performance degradation' - - '{{specific_technical_requirement}}' + - "Code follows TypeScript strict mode standards" + - "Maintains 60 FPS on target devices" + - "No memory leaks or performance degradation" + - "{{specific_technical_requirement}}" - id: game-design-requirements title: Game Design Requirements type: checklist items: - - '{{gameplay_requirement_from_gdd}}' - - '{{balance_requirement_if_applicable}}' - - '{{player_experience_requirement}}' + - "{{gameplay_requirement_from_gdd}}" + - "{{balance_requirement_if_applicable}}" + - "{{player_experience_requirement}}" - id: technical-specifications title: Technical Specifications @@ -8176,14 +8176,14 @@ sections: instruction: Checklist that must be completed before the story is considered finished type: checklist items: - - 'All acceptance criteria met' - - 'Code reviewed and approved' - - 'Unit tests written and passing' - - 'Integration tests passing' - - 'Performance targets met' - - 'No linting errors' - - 'Documentation updated' - - '{{game_specific_dod_item}}' + - "All acceptance criteria met" + - "Code reviewed and approved" + - "Unit tests written and passing" + - "Integration tests passing" + - "Performance targets met" + - "No linting errors" + - "Documentation updated" + - "{{game_specific_dod_item}}" - id: notes title: Notes @@ -8212,8 +8212,8 @@ template: version: 2.0 output: format: markdown - filename: 'docs/{{game_name}}-level-design-document.md' - title: '{{game_title}} Level Design Document' + filename: "docs/{{game_name}}-level-design-document.md" + title: "{{game_title}} Level Design Document" workflow: mode: interactive @@ -8274,7 +8274,7 @@ sections: repeatable: true sections: - id: level-category - title: '{{category_name}} Levels' + title: "{{category_name}} Levels" template: | **Purpose:** {{gameplay_purpose}} @@ -8579,19 +8579,19 @@ sections: title: Playtesting Checklist type: checklist items: - - 'Level completes within target time range' - - 'All mechanics function correctly' - - 'Difficulty feels appropriate for level category' - - 'Player guidance is clear and effective' - - 'No exploits or sequence breaks (unless intended)' + - "Level completes within target time range" + - "All mechanics function correctly" + - "Difficulty feels appropriate for level category" + - "Player guidance is clear and effective" + - "No exploits or sequence breaks (unless intended)" - id: player-experience-testing title: Player Experience Testing type: checklist items: - - 'Tutorial levels teach effectively' - - 'Challenge feels fair and rewarding' - - 'Flow and pacing maintain engagement' - - 'Audio and visual feedback support gameplay' + - "Tutorial levels teach effectively" + - "Challenge feels fair and rewarding" + - "Flow and pacing maintain engagement" + - "Audio and visual feedback support gameplay" - id: balance-validation title: Balance Validation template: | @@ -9917,7 +9917,7 @@ workflow: notes: Implement stories in priority order. Test frequently and adjust design based on what feels fun. Document discoveries. workflow_end: action: prototype_evaluation - notes: 'Prototype complete. Evaluate core mechanics, gather feedback, and decide next steps: iterate, expand, or archive.' + notes: "Prototype complete. Evaluate core mechanics, gather feedback, and decide next steps: iterate, expand, or archive." game_jam_sequence: - step: jam_concept agent: game-designer diff --git a/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-architect.txt b/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-architect.txt index bcb9d36a..7cabad1e 100644 --- a/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-architect.txt +++ b/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-architect.txt @@ -1231,7 +1231,7 @@ template: output: format: markdown filename: docs/game-architecture.md - title: '{{project_name}} Game Architecture Document' + title: "{{project_name}} Game Architecture Document" workflow: mode: interactive @@ -1341,11 +1341,11 @@ sections: - Game management patterns (Singleton managers, Event systems, State machines) - Data patterns (ScriptableObject configuration, Save/Load systems) - Unity-specific patterns (Object pooling, Coroutines, Unity Events) - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - "**Component-Based Architecture:** Using MonoBehaviour components for game logic - _Rationale:_ Aligns with Unity's design philosophy and enables reusable, testable game systems" - - '**ScriptableObject Data:** Using ScriptableObjects for game configuration - _Rationale:_ Enables data-driven design and easy balancing without code changes' - - '**Event-Driven Communication:** Using Unity Events and C# events for system decoupling - _Rationale:_ Supports modular architecture and easier testing' + - "**ScriptableObject Data:** Using ScriptableObjects for game configuration - _Rationale:_ Enables data-driven design and easy balancing without code changes" + - "**Event-Driven Communication:** Using Unity Events and C# events for system decoupling - _Rationale:_ Supports modular architecture and easier testing" - id: tech-stack title: Tech Stack @@ -1384,13 +1384,13 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Populate the technology stack table with all relevant Unity technologies examples: - - '| **Game Engine** | Unity | 2022.3.21f1 | Core game development platform | Latest LTS version, stable 2D tooling, comprehensive package ecosystem |' + - "| **Game Engine** | Unity | 2022.3.21f1 | Core game development platform | Latest LTS version, stable 2D tooling, comprehensive package ecosystem |" - "| **Language** | C# | 10.0 | Primary scripting language | Unity's native language, strong typing, excellent tooling |" - - '| **Render Pipeline** | Universal Render Pipeline (URP) | 14.0.10 | 2D/3D rendering | Optimized for mobile, excellent 2D features, future-proof |' - - '| **Input System** | Unity Input System | 1.7.0 | Cross-platform input handling | Modern input system, supports multiple devices, rebindable controls |' - - '| **Physics** | Unity 2D Physics | Built-in | 2D collision and physics | Integrated Box2D, optimized for 2D games |' - - '| **Audio** | Unity Audio | Built-in | Audio playback and mixing | Built-in audio system with mixer support |' - - '| **Testing** | Unity Test Framework | 1.1.33 | Unit and integration testing | Built-in testing framework based on NUnit |' + - "| **Render Pipeline** | Universal Render Pipeline (URP) | 14.0.10 | 2D/3D rendering | Optimized for mobile, excellent 2D features, future-proof |" + - "| **Input System** | Unity Input System | 1.7.0 | Cross-platform input handling | Modern input system, supports multiple devices, rebindable controls |" + - "| **Physics** | Unity 2D Physics | Built-in | 2D collision and physics | Integrated Box2D, optimized for 2D games |" + - "| **Audio** | Unity Audio | Built-in | Audio playback and mixing | Built-in audio system with mixer support |" + - "| **Testing** | Unity Test Framework | 1.1.33 | Unit and integration testing | Built-in testing framework based on NUnit |" - id: data-models title: Game Data Models @@ -1408,7 +1408,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -1443,7 +1443,7 @@ sections: sections: - id: system-list repeatable: true - title: '{{system_name}} System' + title: "{{system_name}} System" template: | **Responsibility:** {{system_description}} @@ -1967,7 +1967,7 @@ sections: repeatable: true sections: - id: integration - title: '{{service_name}} Integration' + title: "{{service_name}} Integration" template: | - **Purpose:** {{service_purpose}} - **Documentation:** {{service_docs_url}} @@ -2079,12 +2079,12 @@ sections: - id: environments title: Build Environments repeatable: true - template: '- **{{env_name}}:** {{env_purpose}} - {{platform_settings}}' + template: "- **{{env_name}}:** {{env_purpose}} - {{platform_settings}}" - id: platform-specific-builds title: Platform-Specific Build Settings type: code language: text - template: '{{platform_build_configurations}}' + template: "{{platform_build_configurations}}" - id: coding-standards title: Coding Standards @@ -2113,9 +2113,9 @@ sections: columns: [Element, Convention, Example] instruction: Only include if deviating from Unity defaults examples: - - '| MonoBehaviour | PascalCase + Component suffix | PlayerController, HealthSystem |' - - '| ScriptableObject | PascalCase + Data/Config suffix | PlayerData, GameConfig |' - - '| Prefab | PascalCase descriptive | PlayerCharacter, EnvironmentTile |' + - "| MonoBehaviour | PascalCase + Component suffix | PlayerController, HealthSystem |" + - "| ScriptableObject | PascalCase + Data/Config suffix | PlayerData, GameConfig |" + - "| Prefab | PascalCase descriptive | PlayerCharacter, EnvironmentTile |" - id: critical-rules title: Critical Unity Rules instruction: | @@ -2127,7 +2127,7 @@ sections: Avoid obvious rules like "follow SOLID principles" or "optimize performance" repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" - id: unity-specifics title: Unity-Specific Guidelines condition: Critical Unity-specific rules needed @@ -2136,7 +2136,7 @@ sections: - id: unity-lifecycle title: Unity Lifecycle Rules repeatable: true - template: '- **{{lifecycle_method}}:** {{usage_rule}}' + template: "- **{{lifecycle_method}}:** {{usage_rule}}" - id: test-strategy title: Test Strategy and Standards diff --git a/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-designer.txt b/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-designer.txt index 208c76f3..275f881e 100644 --- a/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-designer.txt +++ b/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-designer.txt @@ -1175,7 +1175,7 @@ template: output: format: markdown filename: docs/game-design-document.md - title: '{{game_title}} Game Design Document (GDD)' + title: "{{game_title}} Game Design Document (GDD)" workflow: mode: interactive @@ -1223,8 +1223,8 @@ sections: **Primary:** {{age_range}}, {{player_type}}, {{platform_preference}} **Secondary:** {{secondary_audience}} examples: - - 'Primary: Ages 8-16, casual mobile gamers, prefer short play sessions' - - 'Secondary: Adult puzzle enthusiasts, educators looking for teaching tools' + - "Primary: Ages 8-16, casual mobile gamers, prefer short play sessions" + - "Secondary: Adult puzzle enthusiasts, educators looking for teaching tools" - id: platform-technical title: Platform & Technical Requirements instruction: Based on the technical preferences or user input, define the target platforms and Unity-specific requirements @@ -1235,7 +1235,7 @@ sections: **Screen Support:** {{resolution_range}} **Build Targets:** {{build_targets}} examples: - - 'Primary Platform: Mobile (iOS/Android), Engine: Unity 2022.3 LTS & C#, Performance: 60 FPS on iPhone 8/Galaxy S8' + - "Primary Platform: Mobile (iOS/Android), Engine: Unity 2022.3 LTS & C#, Performance: 60 FPS on iPhone 8/Galaxy S8" - id: unique-selling-points title: Unique Selling Points instruction: List 3-5 key features that differentiate this game from competitors @@ -1286,8 +1286,8 @@ sections: - {{loss_condition_1}} - Trigger: {{unity_trigger}} - {{loss_condition_2}} - Trigger: {{unity_trigger}} examples: - - 'Victory: Player reaches exit portal - Unity Event: OnTriggerEnter2D with Portal tag' - - 'Failure: Health reaches zero - Trigger: Health component value <= 0' + - "Victory: Player reaches exit portal - Unity Event: OnTriggerEnter2D with Portal tag" + - "Failure: Health reaches zero - Trigger: Health component value <= 0" - id: game-mechanics title: Game Mechanics @@ -1299,7 +1299,7 @@ sections: repeatable: true sections: - id: mechanic - title: '{{mechanic_name}}' + title: "{{mechanic_name}}" template: | **Description:** {{detailed_description}} @@ -1321,8 +1321,8 @@ sections: - {{script_name}}.cs - {{responsibility}} - {{manager_script}}.cs - {{management_role}} examples: - - 'Components Needed: Rigidbody2D, BoxCollider2D, PlayerMovement script' - - 'Physics Requirements: 2D Physics material for ground friction, Gravity scale 3' + - "Components Needed: Rigidbody2D, BoxCollider2D, PlayerMovement script" + - "Physics Requirements: 2D Physics material for ground friction, Gravity scale 3" - id: controls title: Controls instruction: Define all input methods for different platforms using Unity's Input System @@ -1377,7 +1377,7 @@ sections: **Late Game:** {{duration}} - {{difficulty_description}} - Unity Config: {{scriptable_object_values}} examples: - - 'enemy speed: 2.0f, jump height: 4.5f, obstacle density: 0.3f' + - "enemy speed: 2.0f, jump height: 4.5f, obstacle density: 0.3f" - id: economy-resources title: Economy & Resources condition: has_economy @@ -1400,7 +1400,7 @@ sections: repeatable: true sections: - id: level-type - title: '{{level_type_name}}' + title: "{{level_type_name}}" template: | **Purpose:** {{gameplay_purpose}} **Target Duration:** {{target_time}} @@ -1424,7 +1424,7 @@ sections: - {{prefab_name}} - {{prefab_purpose}} examples: - - 'Environment: TilemapRenderer with Platform tileset, Lighting: 2D Global Light + Point Lights' + - "Environment: TilemapRenderer with Platform tileset, Lighting: 2D Global Light + Point Lights" - id: level-progression title: Level Progression template: | @@ -1439,7 +1439,7 @@ sections: - Addressable Assets: {{addressable_groups}} - Loading Screens: {{loading_implementation}} examples: - - 'Scene Naming: World{X}_Level{Y}_Name, Addressable Groups: Levels_World1, World_Environments' + - "Scene Naming: World{X}_Level{Y}_Name, Addressable Groups: Levels_World1, World_Environments" - id: technical-specifications title: Technical Specifications @@ -1471,7 +1471,7 @@ sections: - Physics Settings: {{physics_config}} examples: - com.unity.addressables 1.20.5 - Asset loading and memory management - - 'Color Space: Linear, Quality: Mobile/Desktop presets, Gravity: -20' + - "Color Space: Linear, Quality: Mobile/Desktop presets, Gravity: -20" - id: performance-requirements title: Performance Requirements template: | @@ -1487,7 +1487,7 @@ sections: - GC Allocs: <{{gc_limit}}KB per frame - Draw Calls: <{{draw_calls}} per frame examples: - - '60 FPS (minimum 30), CPU: <16.67ms, GPU: <16.67ms, GC: <4KB, Draws: <50' + - "60 FPS (minimum 30), CPU: <16.67ms, GPU: <16.67ms, GC: <4KB, Draws: <50" - id: platform-specific title: Platform Specific Requirements template: | @@ -1510,7 +1510,7 @@ sections: - Browser Support: {{browser_list}} - Compression: {{compression_format}} examples: - - 'Resolution: 1280x720 - 4K, Gamepad: Xbox/PlayStation controllers via Input System' + - "Resolution: 1280x720 - 4K, Gamepad: Xbox/PlayStation controllers via Input System" - id: asset-requirements title: Asset Requirements instruction: Define asset specifications for Unity pipeline optimization @@ -1536,7 +1536,7 @@ sections: - Font: {{font_requirements}} - Icon Sizes: {{icon_specifications}} examples: - - 'Sprites: 32x32 to 256x256 at 16 PPU, Format: RGBA32 for quality/RGBA16 for performance' + - "Sprites: 32x32 to 256x256 at 16 PPU, Format: RGBA32 for quality/RGBA16 for performance" - id: technical-architecture-requirements title: Technical Architecture Requirements @@ -1578,8 +1578,8 @@ sections: - Prefabs: {{prefab_naming}} - Scenes: {{scene_naming}} examples: - - 'Architecture: Component-Based with ScriptableObject data containers' - - 'Scripts: PascalCase (PlayerController), Prefabs: Player_Prefab, Scenes: Level_01_Forest' + - "Architecture: Component-Based with ScriptableObject data containers" + - "Scripts: PascalCase (PlayerController), Prefabs: Player_Prefab, Scenes: Level_01_Forest" - id: unity-systems-integration title: Unity Systems Integration template: | @@ -1601,8 +1601,8 @@ sections: - **Memory Management:** {{memory_strategy}} - **Build Pipeline:** {{build_automation}} examples: - - 'Input System: Action Maps for Menu/Gameplay contexts with device switching' - - 'DOTween: Smooth UI transitions and gameplay animations' + - "Input System: Action Maps for Menu/Gameplay contexts with device switching" + - "DOTween: Smooth UI transitions and gameplay animations" - id: data-management title: Data Management template: | @@ -1625,8 +1625,8 @@ sections: - **Memory Pools:** {{pooling_objects}} - **Asset References:** {{asset_reference_system}} examples: - - 'Save Data: JSON format with AES encryption, stored in persistent data path' - - 'ScriptableObjects: Game settings, level configurations, character data' + - "Save Data: JSON format with AES encryption, stored in persistent data path" + - "ScriptableObjects: Game settings, level configurations, character data" - id: development-phases title: Development Phases & Epic Planning @@ -1638,15 +1638,15 @@ sections: instruction: Present a high-level list of all phases for user approval. Each phase's design should deliver significant Unity functionality. type: numbered-list examples: - - 'Phase 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management' - - 'Phase 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop' - - 'Phase 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression' - - 'Phase 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment' + - "Phase 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management" + - "Phase 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop" + - "Phase 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression" + - "Phase 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment" - id: phase-1-foundation - title: 'Phase 1: Unity Foundation & Core Systems ({{duration}})' + title: "Phase 1: Unity Foundation & Core Systems ({{duration}})" sections: - id: foundation-design - title: 'Design: Unity Project Foundation' + title: "Design: Unity Project Foundation" type: bullet-list template: | - Unity project setup with proper folder structure and naming conventions @@ -1656,9 +1656,9 @@ sections: - Development tools setup (debugging, profiling integration) - Initial build pipeline and platform configuration examples: - - 'Input System: Configure PlayerInput component with Action Maps for movement and UI' + - "Input System: Configure PlayerInput component with Action Maps for movement and UI" - id: core-systems-design - title: 'Design: Essential Game Systems' + title: "Design: Essential Game Systems" type: bullet-list template: | - Save/Load system implementation with {{save_format}} format @@ -1668,10 +1668,10 @@ sections: - Basic UI framework and canvas configuration - Settings and configuration management with ScriptableObjects - id: phase-2-gameplay - title: 'Phase 2: Core Gameplay Implementation ({{duration}})' + title: "Phase 2: Core Gameplay Implementation ({{duration}})" sections: - id: gameplay-mechanics-design - title: 'Design: Primary Game Mechanics' + title: "Design: Primary Game Mechanics" type: bullet-list template: | - Player controller with {{movement_type}} movement system @@ -1681,7 +1681,7 @@ sections: - Basic collision detection and response systems - Animation system integration with Animator controllers - id: level-systems-design - title: 'Design: Level & Content Systems' + title: "Design: Level & Content Systems" type: bullet-list template: | - Scene loading and transition system @@ -1691,10 +1691,10 @@ sections: - Collectibles and pickup systems - Victory/defeat condition implementation - id: phase-3-polish - title: 'Phase 3: Polish & Optimization ({{duration}})' + title: "Phase 3: Polish & Optimization ({{duration}})" sections: - id: performance-design - title: 'Design: Performance & Platform Optimization' + title: "Design: Performance & Platform Optimization" type: bullet-list template: | - Unity Profiler analysis and optimization passes @@ -1704,7 +1704,7 @@ sections: - Build size optimization and asset bundling - Quality settings configuration for different device tiers - id: user-experience-design - title: 'Design: User Experience & Polish' + title: "Design: User Experience & Polish" type: bullet-list template: | - Complete UI/UX implementation with responsive design @@ -1729,10 +1729,10 @@ sections: - 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. elicit: true examples: - - 'Epic 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management' - - 'Epic 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop' - - 'Epic 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression' - - 'Epic 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment' + - "Epic 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management" + - "Epic 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop" + - "Epic 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression" + - "Epic 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment" - id: epic-details title: Epic {{epic_number}} {{epic_title}} @@ -1754,13 +1754,13 @@ sections: - 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 elicit: true - template: '{{epic_goal}}' + template: "{{epic_goal}}" sections: - id: story title: Story {{epic_number}}.{{story_number}} {{story_title}} repeatable: true instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature and reference the gamearchitecture section for additional implementation and integration specifics. - template: '{{clear_description_of_what_needs_to_be_implemented}}' + template: "{{clear_description_of_what_needs_to_be_implemented}}" sections: - id: acceptance-criteria title: Acceptance Criteria @@ -1770,7 +1770,7 @@ sections: title: Functional Requirements type: checklist items: - - '{{specific_functional_requirement}}' + - "{{specific_functional_requirement}}" - id: technical-requirements title: Technical Requirements type: checklist @@ -1778,14 +1778,14 @@ sections: - Code follows C# best practices - Maintains stable frame rate on target devices - No memory leaks or performance degradation - - '{{specific_technical_requirement}}' + - "{{specific_technical_requirement}}" - id: game-design-requirements title: Game Design Requirements type: checklist items: - - '{{gameplay_requirement_from_gdd}}' - - '{{balance_requirement_if_applicable}}' - - '{{player_experience_requirement}}' + - "{{gameplay_requirement_from_gdd}}" + - "{{balance_requirement_if_applicable}}" + - "{{player_experience_requirement}}" - id: success-metrics title: Success Metrics & Quality Assurance @@ -1803,8 +1803,8 @@ sections: - **Build Size:** Final build <{{size_limit}}MB for mobile, <{{desktop_limit}}MB for desktop - **Battery Life:** Mobile gameplay sessions >{{battery_target}} hours on average device examples: - - 'Frame Rate: Consistent 60 FPS with <5% drops below 45 FPS on target hardware' - - 'Crash Rate: <0.5% across iOS/Android, <0.1% on desktop platforms' + - "Frame Rate: Consistent 60 FPS with <5% drops below 45 FPS on target hardware" + - "Crash Rate: <0.5% across iOS/Android, <0.1% on desktop platforms" - id: gameplay-metrics title: Gameplay & User Engagement Metrics type: bullet-list @@ -1816,8 +1816,8 @@ sections: - **Gameplay Completion:** {{completion_rate}}% complete main game content - **Control Responsiveness:** Input lag <{{input_lag}}ms on all platforms examples: - - 'Tutorial Completion: 85% of players complete movement and basic mechanics tutorial' - - 'Session Duration: Average 15-20 minutes per session for mobile, 30-45 minutes for desktop' + - "Tutorial Completion: 85% of players complete movement and basic mechanics tutorial" + - "Session Duration: Average 15-20 minutes per session for mobile, 30-45 minutes for desktop" - id: platform-specific-metrics title: Platform-Specific Quality Metrics type: table @@ -1862,17 +1862,17 @@ sections: - Consider cross-platform testing requirements - Account for Unity build and deployment steps examples: - - 'Foundation stories: Individual Unity systems (Input, Audio, Scene Management) - 1-2 days each' - - 'Feature stories: Complete gameplay mechanics with UI and feedback - 2-4 days each' + - "Foundation stories: Individual Unity systems (Input, Audio, Scene Management) - 1-2 days each" + - "Feature stories: Complete gameplay mechanics with UI and feedback - 2-4 days each" - id: recommended-agents title: Recommended BMad Agent Sequence type: numbered-list template: | 1. **{{agent_name}}**: {{agent_responsibility}} examples: - - 'Unity Architect: Create detailed technical architecture document with specific Unity implementation patterns' - - 'Unity Developer: Implement core systems and gameplay mechanics according to architecture' - - 'QA Tester: Validate performance metrics and cross-platform functionality' + - "Unity Architect: Create detailed technical architecture document with specific Unity implementation patterns" + - "Unity Developer: Implement core systems and gameplay mechanics according to architecture" + - "QA Tester: Validate performance metrics and cross-platform functionality" ==================== END: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ==================== ==================== START: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ==================== @@ -1883,7 +1883,7 @@ template: output: format: markdown filename: docs/level-design-document.md - title: '{{game_title}} Level Design Document' + title: "{{game_title}} Level Design Document" workflow: mode: interactive @@ -1944,7 +1944,7 @@ sections: repeatable: true sections: - id: level-category - title: '{{category_name}} Levels' + title: "{{category_name}} Levels" template: | **Purpose:** {{gameplay_purpose}} @@ -2370,7 +2370,7 @@ template: output: format: markdown filename: docs/game-brief.md - title: '{{game_title}} Game Brief' + title: "{{game_title}} Game Brief" workflow: mode: interactive @@ -2656,21 +2656,21 @@ sections: title: Development Roadmap sections: - id: phase-1-preproduction - title: 'Phase 1: Pre-Production ({{duration}})' + title: "Phase 1: Pre-Production ({{duration}})" type: bullet-list template: | - Detailed Game Design Document creation - Technical architecture planning - Art style exploration and pipeline setup - id: phase-2-prototype - title: 'Phase 2: Prototype ({{duration}})' + title: "Phase 2: Prototype ({{duration}})" type: bullet-list template: | - Core mechanic implementation - Technical proof of concept - Initial playtesting and iteration - id: phase-3-production - title: 'Phase 3: Production ({{duration}})' + title: "Phase 3: Production ({{duration}})" type: bullet-list template: | - Full feature development diff --git a/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-sm.txt b/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-sm.txt index 2452b85d..6637e712 100644 --- a/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-sm.txt +++ b/dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-sm.txt @@ -514,8 +514,8 @@ template: version: 3.0 output: format: markdown - filename: 'stories/{{epic_name}}/{{story_id}}-{{story_name}}.md' - title: 'Story: {{story_title}}' + filename: "stories/{{epic_name}}/{{story_id}}-{{story_name}}.md" + title: "Story: {{story_title}}" workflow: mode: interactive @@ -544,7 +544,7 @@ sections: - id: description title: Description instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature. - template: '{{clear_description_of_what_needs_to_be_implemented}}' + template: "{{clear_description_of_what_needs_to_be_implemented}}" - id: acceptance-criteria title: Acceptance Criteria @@ -554,7 +554,7 @@ sections: title: Functional Requirements type: checklist items: - - '{{specific_functional_requirement}}' + - "{{specific_functional_requirement}}" - id: technical-requirements title: Technical Requirements type: checklist @@ -562,14 +562,14 @@ sections: - Code follows C# best practices - Maintains stable frame rate on target devices - No memory leaks or performance degradation - - '{{specific_technical_requirement}}' + - "{{specific_technical_requirement}}" - id: game-design-requirements title: Game Design Requirements type: checklist items: - - '{{gameplay_requirement_from_gdd}}' - - '{{balance_requirement_if_applicable}}' - - '{{player_experience_requirement}}' + - "{{gameplay_requirement_from_gdd}}" + - "{{balance_requirement_if_applicable}}" + - "{{player_experience_requirement}}" - id: technical-specifications title: Technical Specifications @@ -744,7 +744,7 @@ sections: - Performance targets met - No C# compiler errors or warnings - Documentation updated - - '{{game_specific_dod_item}}' + - "{{game_specific_dod_item}}" - id: notes title: Notes diff --git a/dist/expansion-packs/bmad-2d-unity-game-dev/teams/unity-2d-game-team.txt b/dist/expansion-packs/bmad-2d-unity-game-dev/teams/unity-2d-game-team.txt index fa7e3bd6..4e45a0e2 100644 --- a/dist/expansion-packs/bmad-2d-unity-game-dev/teams/unity-2d-game-team.txt +++ b/dist/expansion-packs/bmad-2d-unity-game-dev/teams/unity-2d-game-team.txt @@ -1472,24 +1472,24 @@ template: output: format: markdown filename: docs/brief.md - title: 'Project Brief: {{project_name}}' + title: "Project Brief: {{project_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Project Brief Elicitation Actions' + title: "Project Brief Elicitation Actions" options: - - 'Expand section with more specific details' - - 'Validate against similar successful products' - - 'Stress test assumptions with edge cases' - - 'Explore alternative solution approaches' - - 'Analyze resource/constraint trade-offs' - - 'Generate risk mitigation strategies' - - 'Challenge scope from MVP minimalist view' - - 'Brainstorm creative feature possibilities' - - 'If only we had [resource/capability/time]...' - - 'Proceed to next section' + - "Expand section with more specific details" + - "Validate against similar successful products" + - "Stress test assumptions with edge cases" + - "Explore alternative solution approaches" + - "Analyze resource/constraint trade-offs" + - "Generate risk mitigation strategies" + - "Challenge scope from MVP minimalist view" + - "Brainstorm creative feature possibilities" + - "If only we had [resource/capability/time]..." + - "Proceed to next section" sections: - id: introduction @@ -1511,7 +1511,7 @@ sections: - Primary problem being solved - Target market identification - Key value proposition - template: '{{executive_summary_content}}' + template: "{{executive_summary_content}}" - id: problem-statement title: Problem Statement @@ -1521,7 +1521,7 @@ sections: - Impact of the problem (quantify if possible) - Why existing solutions fall short - Urgency and importance of solving this now - template: '{{detailed_problem_description}}' + template: "{{detailed_problem_description}}" - id: proposed-solution title: Proposed Solution @@ -1531,7 +1531,7 @@ sections: - Key differentiators from existing solutions - Why this solution will succeed where others haven't - High-level vision for the product - template: '{{solution_description}}' + template: "{{solution_description}}" - id: target-users title: Target Users @@ -1543,12 +1543,12 @@ sections: - Goals they're trying to achieve sections: - id: primary-segment - title: 'Primary User Segment: {{segment_name}}' - template: '{{primary_user_description}}' + title: "Primary User Segment: {{segment_name}}" + template: "{{primary_user_description}}" - id: secondary-segment - title: 'Secondary User Segment: {{segment_name}}' + title: "Secondary User Segment: {{segment_name}}" condition: Has secondary user segment - template: '{{secondary_user_description}}' + template: "{{secondary_user_description}}" - id: goals-metrics title: Goals & Success Metrics @@ -1557,15 +1557,15 @@ sections: - id: business-objectives title: Business Objectives type: bullet-list - template: '- {{objective_with_metric}}' + template: "- {{objective_with_metric}}" - id: user-success-metrics title: User Success Metrics type: bullet-list - template: '- {{user_metric}}' + template: "- {{user_metric}}" - id: kpis title: Key Performance Indicators (KPIs) type: bullet-list - template: '- {{kpi}}: {{definition_and_target}}' + template: "- {{kpi}}: {{definition_and_target}}" - id: mvp-scope title: MVP Scope @@ -1574,14 +1574,14 @@ sections: - id: core-features title: Core Features (Must Have) type: bullet-list - template: '- **{{feature}}:** {{description_and_rationale}}' + template: "- **{{feature}}:** {{description_and_rationale}}" - id: out-of-scope title: Out of Scope for MVP type: bullet-list - template: '- {{feature_or_capability}}' + template: "- {{feature_or_capability}}" - id: mvp-success-criteria title: MVP Success Criteria - template: '{{mvp_success_definition}}' + template: "{{mvp_success_definition}}" - id: post-mvp-vision title: Post-MVP Vision @@ -1589,13 +1589,13 @@ sections: sections: - id: phase-2-features title: Phase 2 Features - template: '{{next_priority_features}}' + template: "{{next_priority_features}}" - id: long-term-vision title: Long-term Vision - template: '{{one_two_year_vision}}' + template: "{{one_two_year_vision}}" - id: expansion-opportunities title: Expansion Opportunities - template: '{{potential_expansions}}' + template: "{{potential_expansions}}" - id: technical-considerations title: Technical Considerations @@ -1636,7 +1636,7 @@ sections: - id: key-assumptions title: Key Assumptions type: bullet-list - template: '- {{assumption}}' + template: "- {{assumption}}" - id: risks-questions title: Risks & Open Questions @@ -1645,15 +1645,15 @@ sections: - id: key-risks title: Key Risks type: bullet-list - template: '- **{{risk}}:** {{description_and_impact}}' + template: "- **{{risk}}:** {{description_and_impact}}" - id: open-questions title: Open Questions type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: research-areas title: Areas Needing Further Research type: bullet-list - template: '- {{research_topic}}' + template: "- {{research_topic}}" - id: appendices title: Appendices @@ -1670,10 +1670,10 @@ sections: - id: stakeholder-input title: B. Stakeholder Input condition: Has stakeholder feedback - template: '{{stakeholder_feedback}}' + template: "{{stakeholder_feedback}}" - id: references title: C. References - template: '{{relevant_links_and_docs}}' + template: "{{relevant_links_and_docs}}" - id: next-steps title: Next Steps @@ -1681,7 +1681,7 @@ sections: - id: immediate-actions title: Immediate Actions type: numbered-list - template: '{{action_item}}' + template: "{{action_item}}" - id: pm-handoff title: PM Handoff content: | @@ -1696,24 +1696,24 @@ template: output: format: markdown filename: docs/market-research.md - title: 'Market Research Report: {{project_product_name}}' + title: "Market Research Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Market Research Elicitation Actions' + title: "Market Research Elicitation Actions" options: - - 'Expand market sizing calculations with sensitivity analysis' - - 'Deep dive into a specific customer segment' - - 'Analyze an emerging market trend in detail' - - 'Compare this market to an analogous market' - - 'Stress test market assumptions' - - 'Explore adjacent market opportunities' - - 'Challenge market definition and boundaries' - - 'Generate strategic scenarios (best/base/worst case)' - - 'If only we had considered [X market factor]...' - - 'Proceed to next section' + - "Expand market sizing calculations with sensitivity analysis" + - "Deep dive into a specific customer segment" + - "Analyze an emerging market trend in detail" + - "Compare this market to an analogous market" + - "Stress test market assumptions" + - "Explore adjacent market opportunities" + - "Challenge market definition and boundaries" + - "Generate strategic scenarios (best/base/worst case)" + - "If only we had considered [X market factor]..." + - "Proceed to next section" sections: - id: executive-summary @@ -1795,7 +1795,7 @@ sections: repeatable: true sections: - id: segment - title: 'Segment {{segment_number}}: {{segment_name}}' + title: "Segment {{segment_number}}: {{segment_name}}" template: | - **Description:** {{brief_overview}} - **Size:** {{number_of_customers_market_value}} @@ -1864,20 +1864,20 @@ sections: instruction: Analyze each force with specific evidence and implications sections: - id: supplier-power - title: 'Supplier Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Supplier Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: buyer-power - title: 'Buyer Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Buyer Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: competitive-rivalry - title: 'Competitive Rivalry: {{intensity_level}}' - template: '{{analysis_and_implications}}' + title: "Competitive Rivalry: {{intensity_level}}" + template: "{{analysis_and_implications}}" - id: threat-new-entry - title: 'Threat of New Entry: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of New Entry: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: threat-substitutes - title: 'Threat of Substitutes: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of Substitutes: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: adoption-lifecycle title: Technology Adoption Lifecycle Stage instruction: | @@ -1895,7 +1895,7 @@ sections: repeatable: true sections: - id: opportunity - title: 'Opportunity {{opportunity_number}}: {{name}}' + title: "Opportunity {{opportunity_number}}: {{name}}" template: | - **Description:** {{what_is_the_opportunity}} - **Size/Potential:** {{quantified_potential}} @@ -1951,24 +1951,24 @@ template: output: format: markdown filename: docs/competitor-analysis.md - title: 'Competitive Analysis Report: {{project_product_name}}' + title: "Competitive Analysis Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Competitive Analysis Elicitation Actions' + title: "Competitive Analysis Elicitation Actions" options: - "Deep dive on a specific competitor's strategy" - - 'Analyze competitive dynamics in a specific segment' - - 'War game competitive responses to your moves' - - 'Explore partnership vs. competition scenarios' - - 'Stress test differentiation claims' - - 'Analyze disruption potential (yours or theirs)' - - 'Compare to competition in adjacent markets' - - 'Generate win/loss analysis insights' + - "Analyze competitive dynamics in a specific segment" + - "War game competitive responses to your moves" + - "Explore partnership vs. competition scenarios" + - "Stress test differentiation claims" + - "Analyze disruption potential (yours or theirs)" + - "Compare to competition in adjacent markets" + - "Generate win/loss analysis insights" - "If only we had known about [competitor X's plan]..." - - 'Proceed to next section' + - "Proceed to next section" sections: - id: executive-summary @@ -2035,7 +2035,7 @@ sections: repeatable: true sections: - id: competitor - title: '{{competitor_name}} - Priority {{priority_level}}' + title: "{{competitor_name}} - Priority {{priority_level}}" sections: - id: company-overview title: Company Overview @@ -2067,11 +2067,11 @@ sections: - id: strengths title: Strengths type: bullet-list - template: '- {{strength}}' + template: "- {{strength}}" - id: weaknesses title: Weaknesses type: bullet-list - template: '- {{weakness}}' + template: "- {{weakness}}" - id: market-position title: Market Position & Performance template: | @@ -2089,35 +2089,35 @@ sections: type: table columns: [ - 'Feature Category', - '{{your_company}}', - '{{competitor_1}}', - '{{competitor_2}}', - '{{competitor_3}}', + "Feature Category", + "{{your_company}}", + "{{competitor_1}}", + "{{competitor_2}}", + "{{competitor_3}}", ] rows: - - category: 'Core Functionality' + - category: "Core Functionality" items: - - ['Feature A', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - ['Feature B', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - category: 'User Experience' + - ["Feature A", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - ["Feature B", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - category: "User Experience" items: - - ['Mobile App', '{{rating}}', '{{rating}}', '{{rating}}', '{{rating}}'] - - ['Onboarding Time', '{{time}}', '{{time}}', '{{time}}', '{{time}}'] - - category: 'Integration & Ecosystem' + - ["Mobile App", "{{rating}}", "{{rating}}", "{{rating}}", "{{rating}}"] + - ["Onboarding Time", "{{time}}", "{{time}}", "{{time}}", "{{time}}"] + - category: "Integration & Ecosystem" items: - [ - 'API Availability', - '{{availability}}', - '{{availability}}', - '{{availability}}', - '{{availability}}', + "API Availability", + "{{availability}}", + "{{availability}}", + "{{availability}}", + "{{availability}}", ] - - ['Third-party Integrations', '{{number}}', '{{number}}', '{{number}}', '{{number}}'] - - category: 'Pricing & Plans' + - ["Third-party Integrations", "{{number}}", "{{number}}", "{{number}}", "{{number}}"] + - category: "Pricing & Plans" items: - - ['Starting Price', '{{price}}', '{{price}}', '{{price}}', '{{price}}'] - - ['Free Tier', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}'] + - ["Starting Price", "{{price}}", "{{price}}", "{{price}}", "{{price}}"] + - ["Free Tier", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}"] - id: swot-comparison title: SWOT Comparison instruction: Create SWOT analysis for your solution vs. top competitors @@ -2130,7 +2130,7 @@ sections: - **Opportunities:** {{opportunities}} - **Threats:** {{threats}} - id: vs-competitor - title: 'vs. {{main_competitor}}' + title: "vs. {{main_competitor}}" template: | - **Competitive Advantages:** {{your_advantages}} - **Competitive Disadvantages:** {{their_advantages}} @@ -2260,7 +2260,7 @@ template: output: format: markdown filename: docs/brainstorming-session-results.md - title: 'Brainstorming Session Results' + title: "Brainstorming Session Results" workflow: mode: non-interactive @@ -2285,38 +2285,38 @@ sections: **Total Ideas Generated:** {{total_ideas}} - id: key-themes - title: 'Key Themes Identified:' + title: "Key Themes Identified:" type: bullet-list - template: '- {{theme}}' + template: "- {{theme}}" - id: technique-sessions title: Technique Sessions repeatable: true sections: - id: technique - title: '{{technique_name}} - {{duration}}' + title: "{{technique_name}} - {{duration}}" sections: - id: description - template: '**Description:** {{technique_description}}' + template: "**Description:** {{technique_description}}" - id: ideas-generated - title: 'Ideas Generated:' + title: "Ideas Generated:" type: numbered-list - template: '{{idea}}' + template: "{{idea}}" - id: insights - title: 'Insights Discovered:' + title: "Insights Discovered:" type: bullet-list - template: '- {{insight}}' + template: "- {{insight}}" - id: connections - title: 'Notable Connections:' + title: "Notable Connections:" type: bullet-list - template: '- {{connection}}' + template: "- {{connection}}" - id: idea-categorization title: Idea Categorization sections: - id: immediate-opportunities title: Immediate Opportunities - content: '*Ideas ready to implement now*' + content: "*Ideas ready to implement now*" repeatable: true type: numbered-list template: | @@ -2326,7 +2326,7 @@ sections: - Resources needed: {{requirements}} - id: future-innovations title: Future Innovations - content: '*Ideas requiring development/research*' + content: "*Ideas requiring development/research*" repeatable: true type: numbered-list template: | @@ -2336,7 +2336,7 @@ sections: - Timeline estimate: {{timeline}} - id: moonshots title: Moonshots - content: '*Ambitious, transformative concepts*' + content: "*Ambitious, transformative concepts*" repeatable: true type: numbered-list template: | @@ -2346,9 +2346,9 @@ sections: - Challenges to overcome: {{challenges}} - id: insights-learnings title: Insights & Learnings - content: '*Key realizations from the session*' + content: "*Key realizations from the session*" type: bullet-list - template: '- {{insight}}: {{description_and_implications}}' + template: "- {{insight}}: {{description_and_implications}}" - id: action-planning title: Action Planning @@ -2357,21 +2357,21 @@ sections: title: Top 3 Priority Ideas sections: - id: priority-1 - title: '#1 Priority: {{idea_name}}' + title: "#1 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-2 - title: '#2 Priority: {{idea_name}}' + title: "#2 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-3 - title: '#3 Priority: {{idea_name}}' + title: "#3 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} @@ -2384,19 +2384,19 @@ sections: - id: what-worked title: What Worked Well type: bullet-list - template: '- {{aspect}}' + template: "- {{aspect}}" - id: areas-exploration title: Areas for Further Exploration type: bullet-list - template: '- {{area}}: {{reason}}' + template: "- {{area}}: {{reason}}" - id: recommended-techniques title: Recommended Follow-up Techniques type: bullet-list - template: '- {{technique}}: {{reason}}' + template: "- {{technique}}: {{reason}}" - id: questions-emerged title: Questions That Emerged type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: next-session title: Next Session Planning template: | @@ -4107,7 +4107,7 @@ template: output: format: markdown filename: docs/game-design-document.md - title: '{{game_title}} Game Design Document (GDD)' + title: "{{game_title}} Game Design Document (GDD)" workflow: mode: interactive @@ -4155,8 +4155,8 @@ sections: **Primary:** {{age_range}}, {{player_type}}, {{platform_preference}} **Secondary:** {{secondary_audience}} examples: - - 'Primary: Ages 8-16, casual mobile gamers, prefer short play sessions' - - 'Secondary: Adult puzzle enthusiasts, educators looking for teaching tools' + - "Primary: Ages 8-16, casual mobile gamers, prefer short play sessions" + - "Secondary: Adult puzzle enthusiasts, educators looking for teaching tools" - id: platform-technical title: Platform & Technical Requirements instruction: Based on the technical preferences or user input, define the target platforms and Unity-specific requirements @@ -4167,7 +4167,7 @@ sections: **Screen Support:** {{resolution_range}} **Build Targets:** {{build_targets}} examples: - - 'Primary Platform: Mobile (iOS/Android), Engine: Unity 2022.3 LTS & C#, Performance: 60 FPS on iPhone 8/Galaxy S8' + - "Primary Platform: Mobile (iOS/Android), Engine: Unity 2022.3 LTS & C#, Performance: 60 FPS on iPhone 8/Galaxy S8" - id: unique-selling-points title: Unique Selling Points instruction: List 3-5 key features that differentiate this game from competitors @@ -4218,8 +4218,8 @@ sections: - {{loss_condition_1}} - Trigger: {{unity_trigger}} - {{loss_condition_2}} - Trigger: {{unity_trigger}} examples: - - 'Victory: Player reaches exit portal - Unity Event: OnTriggerEnter2D with Portal tag' - - 'Failure: Health reaches zero - Trigger: Health component value <= 0' + - "Victory: Player reaches exit portal - Unity Event: OnTriggerEnter2D with Portal tag" + - "Failure: Health reaches zero - Trigger: Health component value <= 0" - id: game-mechanics title: Game Mechanics @@ -4231,7 +4231,7 @@ sections: repeatable: true sections: - id: mechanic - title: '{{mechanic_name}}' + title: "{{mechanic_name}}" template: | **Description:** {{detailed_description}} @@ -4253,8 +4253,8 @@ sections: - {{script_name}}.cs - {{responsibility}} - {{manager_script}}.cs - {{management_role}} examples: - - 'Components Needed: Rigidbody2D, BoxCollider2D, PlayerMovement script' - - 'Physics Requirements: 2D Physics material for ground friction, Gravity scale 3' + - "Components Needed: Rigidbody2D, BoxCollider2D, PlayerMovement script" + - "Physics Requirements: 2D Physics material for ground friction, Gravity scale 3" - id: controls title: Controls instruction: Define all input methods for different platforms using Unity's Input System @@ -4309,7 +4309,7 @@ sections: **Late Game:** {{duration}} - {{difficulty_description}} - Unity Config: {{scriptable_object_values}} examples: - - 'enemy speed: 2.0f, jump height: 4.5f, obstacle density: 0.3f' + - "enemy speed: 2.0f, jump height: 4.5f, obstacle density: 0.3f" - id: economy-resources title: Economy & Resources condition: has_economy @@ -4332,7 +4332,7 @@ sections: repeatable: true sections: - id: level-type - title: '{{level_type_name}}' + title: "{{level_type_name}}" template: | **Purpose:** {{gameplay_purpose}} **Target Duration:** {{target_time}} @@ -4356,7 +4356,7 @@ sections: - {{prefab_name}} - {{prefab_purpose}} examples: - - 'Environment: TilemapRenderer with Platform tileset, Lighting: 2D Global Light + Point Lights' + - "Environment: TilemapRenderer with Platform tileset, Lighting: 2D Global Light + Point Lights" - id: level-progression title: Level Progression template: | @@ -4371,7 +4371,7 @@ sections: - Addressable Assets: {{addressable_groups}} - Loading Screens: {{loading_implementation}} examples: - - 'Scene Naming: World{X}_Level{Y}_Name, Addressable Groups: Levels_World1, World_Environments' + - "Scene Naming: World{X}_Level{Y}_Name, Addressable Groups: Levels_World1, World_Environments" - id: technical-specifications title: Technical Specifications @@ -4403,7 +4403,7 @@ sections: - Physics Settings: {{physics_config}} examples: - com.unity.addressables 1.20.5 - Asset loading and memory management - - 'Color Space: Linear, Quality: Mobile/Desktop presets, Gravity: -20' + - "Color Space: Linear, Quality: Mobile/Desktop presets, Gravity: -20" - id: performance-requirements title: Performance Requirements template: | @@ -4419,7 +4419,7 @@ sections: - GC Allocs: <{{gc_limit}}KB per frame - Draw Calls: <{{draw_calls}} per frame examples: - - '60 FPS (minimum 30), CPU: <16.67ms, GPU: <16.67ms, GC: <4KB, Draws: <50' + - "60 FPS (minimum 30), CPU: <16.67ms, GPU: <16.67ms, GC: <4KB, Draws: <50" - id: platform-specific title: Platform Specific Requirements template: | @@ -4442,7 +4442,7 @@ sections: - Browser Support: {{browser_list}} - Compression: {{compression_format}} examples: - - 'Resolution: 1280x720 - 4K, Gamepad: Xbox/PlayStation controllers via Input System' + - "Resolution: 1280x720 - 4K, Gamepad: Xbox/PlayStation controllers via Input System" - id: asset-requirements title: Asset Requirements instruction: Define asset specifications for Unity pipeline optimization @@ -4468,7 +4468,7 @@ sections: - Font: {{font_requirements}} - Icon Sizes: {{icon_specifications}} examples: - - 'Sprites: 32x32 to 256x256 at 16 PPU, Format: RGBA32 for quality/RGBA16 for performance' + - "Sprites: 32x32 to 256x256 at 16 PPU, Format: RGBA32 for quality/RGBA16 for performance" - id: technical-architecture-requirements title: Technical Architecture Requirements @@ -4510,8 +4510,8 @@ sections: - Prefabs: {{prefab_naming}} - Scenes: {{scene_naming}} examples: - - 'Architecture: Component-Based with ScriptableObject data containers' - - 'Scripts: PascalCase (PlayerController), Prefabs: Player_Prefab, Scenes: Level_01_Forest' + - "Architecture: Component-Based with ScriptableObject data containers" + - "Scripts: PascalCase (PlayerController), Prefabs: Player_Prefab, Scenes: Level_01_Forest" - id: unity-systems-integration title: Unity Systems Integration template: | @@ -4533,8 +4533,8 @@ sections: - **Memory Management:** {{memory_strategy}} - **Build Pipeline:** {{build_automation}} examples: - - 'Input System: Action Maps for Menu/Gameplay contexts with device switching' - - 'DOTween: Smooth UI transitions and gameplay animations' + - "Input System: Action Maps for Menu/Gameplay contexts with device switching" + - "DOTween: Smooth UI transitions and gameplay animations" - id: data-management title: Data Management template: | @@ -4557,8 +4557,8 @@ sections: - **Memory Pools:** {{pooling_objects}} - **Asset References:** {{asset_reference_system}} examples: - - 'Save Data: JSON format with AES encryption, stored in persistent data path' - - 'ScriptableObjects: Game settings, level configurations, character data' + - "Save Data: JSON format with AES encryption, stored in persistent data path" + - "ScriptableObjects: Game settings, level configurations, character data" - id: development-phases title: Development Phases & Epic Planning @@ -4570,15 +4570,15 @@ sections: instruction: Present a high-level list of all phases for user approval. Each phase's design should deliver significant Unity functionality. type: numbered-list examples: - - 'Phase 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management' - - 'Phase 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop' - - 'Phase 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression' - - 'Phase 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment' + - "Phase 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management" + - "Phase 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop" + - "Phase 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression" + - "Phase 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment" - id: phase-1-foundation - title: 'Phase 1: Unity Foundation & Core Systems ({{duration}})' + title: "Phase 1: Unity Foundation & Core Systems ({{duration}})" sections: - id: foundation-design - title: 'Design: Unity Project Foundation' + title: "Design: Unity Project Foundation" type: bullet-list template: | - Unity project setup with proper folder structure and naming conventions @@ -4588,9 +4588,9 @@ sections: - Development tools setup (debugging, profiling integration) - Initial build pipeline and platform configuration examples: - - 'Input System: Configure PlayerInput component with Action Maps for movement and UI' + - "Input System: Configure PlayerInput component with Action Maps for movement and UI" - id: core-systems-design - title: 'Design: Essential Game Systems' + title: "Design: Essential Game Systems" type: bullet-list template: | - Save/Load system implementation with {{save_format}} format @@ -4600,10 +4600,10 @@ sections: - Basic UI framework and canvas configuration - Settings and configuration management with ScriptableObjects - id: phase-2-gameplay - title: 'Phase 2: Core Gameplay Implementation ({{duration}})' + title: "Phase 2: Core Gameplay Implementation ({{duration}})" sections: - id: gameplay-mechanics-design - title: 'Design: Primary Game Mechanics' + title: "Design: Primary Game Mechanics" type: bullet-list template: | - Player controller with {{movement_type}} movement system @@ -4613,7 +4613,7 @@ sections: - Basic collision detection and response systems - Animation system integration with Animator controllers - id: level-systems-design - title: 'Design: Level & Content Systems' + title: "Design: Level & Content Systems" type: bullet-list template: | - Scene loading and transition system @@ -4623,10 +4623,10 @@ sections: - Collectibles and pickup systems - Victory/defeat condition implementation - id: phase-3-polish - title: 'Phase 3: Polish & Optimization ({{duration}})' + title: "Phase 3: Polish & Optimization ({{duration}})" sections: - id: performance-design - title: 'Design: Performance & Platform Optimization' + title: "Design: Performance & Platform Optimization" type: bullet-list template: | - Unity Profiler analysis and optimization passes @@ -4636,7 +4636,7 @@ sections: - Build size optimization and asset bundling - Quality settings configuration for different device tiers - id: user-experience-design - title: 'Design: User Experience & Polish' + title: "Design: User Experience & Polish" type: bullet-list template: | - Complete UI/UX implementation with responsive design @@ -4661,10 +4661,10 @@ sections: - 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. elicit: true examples: - - 'Epic 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management' - - 'Epic 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop' - - 'Epic 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression' - - 'Epic 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment' + - "Epic 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management" + - "Epic 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop" + - "Epic 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression" + - "Epic 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment" - id: epic-details title: Epic {{epic_number}} {{epic_title}} @@ -4686,13 +4686,13 @@ sections: - 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 elicit: true - template: '{{epic_goal}}' + template: "{{epic_goal}}" sections: - id: story title: Story {{epic_number}}.{{story_number}} {{story_title}} repeatable: true instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature and reference the gamearchitecture section for additional implementation and integration specifics. - template: '{{clear_description_of_what_needs_to_be_implemented}}' + template: "{{clear_description_of_what_needs_to_be_implemented}}" sections: - id: acceptance-criteria title: Acceptance Criteria @@ -4702,7 +4702,7 @@ sections: title: Functional Requirements type: checklist items: - - '{{specific_functional_requirement}}' + - "{{specific_functional_requirement}}" - id: technical-requirements title: Technical Requirements type: checklist @@ -4710,14 +4710,14 @@ sections: - Code follows C# best practices - Maintains stable frame rate on target devices - No memory leaks or performance degradation - - '{{specific_technical_requirement}}' + - "{{specific_technical_requirement}}" - id: game-design-requirements title: Game Design Requirements type: checklist items: - - '{{gameplay_requirement_from_gdd}}' - - '{{balance_requirement_if_applicable}}' - - '{{player_experience_requirement}}' + - "{{gameplay_requirement_from_gdd}}" + - "{{balance_requirement_if_applicable}}" + - "{{player_experience_requirement}}" - id: success-metrics title: Success Metrics & Quality Assurance @@ -4735,8 +4735,8 @@ sections: - **Build Size:** Final build <{{size_limit}}MB for mobile, <{{desktop_limit}}MB for desktop - **Battery Life:** Mobile gameplay sessions >{{battery_target}} hours on average device examples: - - 'Frame Rate: Consistent 60 FPS with <5% drops below 45 FPS on target hardware' - - 'Crash Rate: <0.5% across iOS/Android, <0.1% on desktop platforms' + - "Frame Rate: Consistent 60 FPS with <5% drops below 45 FPS on target hardware" + - "Crash Rate: <0.5% across iOS/Android, <0.1% on desktop platforms" - id: gameplay-metrics title: Gameplay & User Engagement Metrics type: bullet-list @@ -4748,8 +4748,8 @@ sections: - **Gameplay Completion:** {{completion_rate}}% complete main game content - **Control Responsiveness:** Input lag <{{input_lag}}ms on all platforms examples: - - 'Tutorial Completion: 85% of players complete movement and basic mechanics tutorial' - - 'Session Duration: Average 15-20 minutes per session for mobile, 30-45 minutes for desktop' + - "Tutorial Completion: 85% of players complete movement and basic mechanics tutorial" + - "Session Duration: Average 15-20 minutes per session for mobile, 30-45 minutes for desktop" - id: platform-specific-metrics title: Platform-Specific Quality Metrics type: table @@ -4794,17 +4794,17 @@ sections: - Consider cross-platform testing requirements - Account for Unity build and deployment steps examples: - - 'Foundation stories: Individual Unity systems (Input, Audio, Scene Management) - 1-2 days each' - - 'Feature stories: Complete gameplay mechanics with UI and feedback - 2-4 days each' + - "Foundation stories: Individual Unity systems (Input, Audio, Scene Management) - 1-2 days each" + - "Feature stories: Complete gameplay mechanics with UI and feedback - 2-4 days each" - id: recommended-agents title: Recommended BMad Agent Sequence type: numbered-list template: | 1. **{{agent_name}}**: {{agent_responsibility}} examples: - - 'Unity Architect: Create detailed technical architecture document with specific Unity implementation patterns' - - 'Unity Developer: Implement core systems and gameplay mechanics according to architecture' - - 'QA Tester: Validate performance metrics and cross-platform functionality' + - "Unity Architect: Create detailed technical architecture document with specific Unity implementation patterns" + - "Unity Developer: Implement core systems and gameplay mechanics according to architecture" + - "QA Tester: Validate performance metrics and cross-platform functionality" ==================== END: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ==================== ==================== START: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ==================== @@ -4815,7 +4815,7 @@ template: output: format: markdown filename: docs/level-design-document.md - title: '{{game_title}} Level Design Document' + title: "{{game_title}} Level Design Document" workflow: mode: interactive @@ -4876,7 +4876,7 @@ sections: repeatable: true sections: - id: level-category - title: '{{category_name}} Levels' + title: "{{category_name}} Levels" template: | **Purpose:** {{gameplay_purpose}} @@ -5302,7 +5302,7 @@ template: output: format: markdown filename: docs/game-brief.md - title: '{{game_title}} Game Brief' + title: "{{game_title}} Game Brief" workflow: mode: interactive @@ -5588,21 +5588,21 @@ sections: title: Development Roadmap sections: - id: phase-1-preproduction - title: 'Phase 1: Pre-Production ({{duration}})' + title: "Phase 1: Pre-Production ({{duration}})" type: bullet-list template: | - Detailed Game Design Document creation - Technical architecture planning - Art style exploration and pipeline setup - id: phase-2-prototype - title: 'Phase 2: Prototype ({{duration}})' + title: "Phase 2: Prototype ({{duration}})" type: bullet-list template: | - Core mechanic implementation - Technical proof of concept - Initial playtesting and iteration - id: phase-3-production - title: 'Phase 3: Production ({{duration}})' + title: "Phase 3: Production ({{duration}})" type: bullet-list template: | - Full feature development @@ -5865,7 +5865,7 @@ template: output: format: markdown filename: docs/game-architecture.md - title: '{{project_name}} Game Architecture Document' + title: "{{project_name}} Game Architecture Document" workflow: mode: interactive @@ -5975,11 +5975,11 @@ sections: - Game management patterns (Singleton managers, Event systems, State machines) - Data patterns (ScriptableObject configuration, Save/Load systems) - Unity-specific patterns (Object pooling, Coroutines, Unity Events) - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - "**Component-Based Architecture:** Using MonoBehaviour components for game logic - _Rationale:_ Aligns with Unity's design philosophy and enables reusable, testable game systems" - - '**ScriptableObject Data:** Using ScriptableObjects for game configuration - _Rationale:_ Enables data-driven design and easy balancing without code changes' - - '**Event-Driven Communication:** Using Unity Events and C# events for system decoupling - _Rationale:_ Supports modular architecture and easier testing' + - "**ScriptableObject Data:** Using ScriptableObjects for game configuration - _Rationale:_ Enables data-driven design and easy balancing without code changes" + - "**Event-Driven Communication:** Using Unity Events and C# events for system decoupling - _Rationale:_ Supports modular architecture and easier testing" - id: tech-stack title: Tech Stack @@ -6018,13 +6018,13 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Populate the technology stack table with all relevant Unity technologies examples: - - '| **Game Engine** | Unity | 2022.3.21f1 | Core game development platform | Latest LTS version, stable 2D tooling, comprehensive package ecosystem |' + - "| **Game Engine** | Unity | 2022.3.21f1 | Core game development platform | Latest LTS version, stable 2D tooling, comprehensive package ecosystem |" - "| **Language** | C# | 10.0 | Primary scripting language | Unity's native language, strong typing, excellent tooling |" - - '| **Render Pipeline** | Universal Render Pipeline (URP) | 14.0.10 | 2D/3D rendering | Optimized for mobile, excellent 2D features, future-proof |' - - '| **Input System** | Unity Input System | 1.7.0 | Cross-platform input handling | Modern input system, supports multiple devices, rebindable controls |' - - '| **Physics** | Unity 2D Physics | Built-in | 2D collision and physics | Integrated Box2D, optimized for 2D games |' - - '| **Audio** | Unity Audio | Built-in | Audio playback and mixing | Built-in audio system with mixer support |' - - '| **Testing** | Unity Test Framework | 1.1.33 | Unit and integration testing | Built-in testing framework based on NUnit |' + - "| **Render Pipeline** | Universal Render Pipeline (URP) | 14.0.10 | 2D/3D rendering | Optimized for mobile, excellent 2D features, future-proof |" + - "| **Input System** | Unity Input System | 1.7.0 | Cross-platform input handling | Modern input system, supports multiple devices, rebindable controls |" + - "| **Physics** | Unity 2D Physics | Built-in | 2D collision and physics | Integrated Box2D, optimized for 2D games |" + - "| **Audio** | Unity Audio | Built-in | Audio playback and mixing | Built-in audio system with mixer support |" + - "| **Testing** | Unity Test Framework | 1.1.33 | Unit and integration testing | Built-in testing framework based on NUnit |" - id: data-models title: Game Data Models @@ -6042,7 +6042,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -6077,7 +6077,7 @@ sections: sections: - id: system-list repeatable: true - title: '{{system_name}} System' + title: "{{system_name}} System" template: | **Responsibility:** {{system_description}} @@ -6601,7 +6601,7 @@ sections: repeatable: true sections: - id: integration - title: '{{service_name}} Integration' + title: "{{service_name}} Integration" template: | - **Purpose:** {{service_purpose}} - **Documentation:** {{service_docs_url}} @@ -6713,12 +6713,12 @@ sections: - id: environments title: Build Environments repeatable: true - template: '- **{{env_name}}:** {{env_purpose}} - {{platform_settings}}' + template: "- **{{env_name}}:** {{env_purpose}} - {{platform_settings}}" - id: platform-specific-builds title: Platform-Specific Build Settings type: code language: text - template: '{{platform_build_configurations}}' + template: "{{platform_build_configurations}}" - id: coding-standards title: Coding Standards @@ -6747,9 +6747,9 @@ sections: columns: [Element, Convention, Example] instruction: Only include if deviating from Unity defaults examples: - - '| MonoBehaviour | PascalCase + Component suffix | PlayerController, HealthSystem |' - - '| ScriptableObject | PascalCase + Data/Config suffix | PlayerData, GameConfig |' - - '| Prefab | PascalCase descriptive | PlayerCharacter, EnvironmentTile |' + - "| MonoBehaviour | PascalCase + Component suffix | PlayerController, HealthSystem |" + - "| ScriptableObject | PascalCase + Data/Config suffix | PlayerData, GameConfig |" + - "| Prefab | PascalCase descriptive | PlayerCharacter, EnvironmentTile |" - id: critical-rules title: Critical Unity Rules instruction: | @@ -6761,7 +6761,7 @@ sections: Avoid obvious rules like "follow SOLID principles" or "optimize performance" repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" - id: unity-specifics title: Unity-Specific Guidelines condition: Critical Unity-specific rules needed @@ -6770,7 +6770,7 @@ sections: - id: unity-lifecycle title: Unity Lifecycle Rules repeatable: true - template: '- **{{lifecycle_method}}:** {{usage_rule}}' + template: "- **{{lifecycle_method}}:** {{usage_rule}}" - id: test-strategy title: Test Strategy and Standards @@ -8475,8 +8475,8 @@ template: version: 3.0 output: format: markdown - filename: 'stories/{{epic_name}}/{{story_id}}-{{story_name}}.md' - title: 'Story: {{story_title}}' + filename: "stories/{{epic_name}}/{{story_id}}-{{story_name}}.md" + title: "Story: {{story_title}}" workflow: mode: interactive @@ -8505,7 +8505,7 @@ sections: - id: description title: Description instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature. - template: '{{clear_description_of_what_needs_to_be_implemented}}' + template: "{{clear_description_of_what_needs_to_be_implemented}}" - id: acceptance-criteria title: Acceptance Criteria @@ -8515,7 +8515,7 @@ sections: title: Functional Requirements type: checklist items: - - '{{specific_functional_requirement}}' + - "{{specific_functional_requirement}}" - id: technical-requirements title: Technical Requirements type: checklist @@ -8523,14 +8523,14 @@ sections: - Code follows C# best practices - Maintains stable frame rate on target devices - No memory leaks or performance degradation - - '{{specific_technical_requirement}}' + - "{{specific_technical_requirement}}" - id: game-design-requirements title: Game Design Requirements type: checklist items: - - '{{gameplay_requirement_from_gdd}}' - - '{{balance_requirement_if_applicable}}' - - '{{player_experience_requirement}}' + - "{{gameplay_requirement_from_gdd}}" + - "{{balance_requirement_if_applicable}}" + - "{{player_experience_requirement}}" - id: technical-specifications title: Technical Specifications @@ -8705,7 +8705,7 @@ sections: - Performance targets met - No C# compiler errors or warnings - Documentation updated - - '{{game_specific_dod_item}}' + - "{{game_specific_dod_item}}" - id: notes title: Notes @@ -8941,7 +8941,7 @@ template: output: format: markdown filename: docs/game-architecture.md - title: '{{project_name}} Game Architecture Document' + title: "{{project_name}} Game Architecture Document" workflow: mode: interactive @@ -9051,11 +9051,11 @@ sections: - Game management patterns (Singleton managers, Event systems, State machines) - Data patterns (ScriptableObject configuration, Save/Load systems) - Unity-specific patterns (Object pooling, Coroutines, Unity Events) - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - "**Component-Based Architecture:** Using MonoBehaviour components for game logic - _Rationale:_ Aligns with Unity's design philosophy and enables reusable, testable game systems" - - '**ScriptableObject Data:** Using ScriptableObjects for game configuration - _Rationale:_ Enables data-driven design and easy balancing without code changes' - - '**Event-Driven Communication:** Using Unity Events and C# events for system decoupling - _Rationale:_ Supports modular architecture and easier testing' + - "**ScriptableObject Data:** Using ScriptableObjects for game configuration - _Rationale:_ Enables data-driven design and easy balancing without code changes" + - "**Event-Driven Communication:** Using Unity Events and C# events for system decoupling - _Rationale:_ Supports modular architecture and easier testing" - id: tech-stack title: Tech Stack @@ -9094,13 +9094,13 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Populate the technology stack table with all relevant Unity technologies examples: - - '| **Game Engine** | Unity | 2022.3.21f1 | Core game development platform | Latest LTS version, stable 2D tooling, comprehensive package ecosystem |' + - "| **Game Engine** | Unity | 2022.3.21f1 | Core game development platform | Latest LTS version, stable 2D tooling, comprehensive package ecosystem |" - "| **Language** | C# | 10.0 | Primary scripting language | Unity's native language, strong typing, excellent tooling |" - - '| **Render Pipeline** | Universal Render Pipeline (URP) | 14.0.10 | 2D/3D rendering | Optimized for mobile, excellent 2D features, future-proof |' - - '| **Input System** | Unity Input System | 1.7.0 | Cross-platform input handling | Modern input system, supports multiple devices, rebindable controls |' - - '| **Physics** | Unity 2D Physics | Built-in | 2D collision and physics | Integrated Box2D, optimized for 2D games |' - - '| **Audio** | Unity Audio | Built-in | Audio playback and mixing | Built-in audio system with mixer support |' - - '| **Testing** | Unity Test Framework | 1.1.33 | Unit and integration testing | Built-in testing framework based on NUnit |' + - "| **Render Pipeline** | Universal Render Pipeline (URP) | 14.0.10 | 2D/3D rendering | Optimized for mobile, excellent 2D features, future-proof |" + - "| **Input System** | Unity Input System | 1.7.0 | Cross-platform input handling | Modern input system, supports multiple devices, rebindable controls |" + - "| **Physics** | Unity 2D Physics | Built-in | 2D collision and physics | Integrated Box2D, optimized for 2D games |" + - "| **Audio** | Unity Audio | Built-in | Audio playback and mixing | Built-in audio system with mixer support |" + - "| **Testing** | Unity Test Framework | 1.1.33 | Unit and integration testing | Built-in testing framework based on NUnit |" - id: data-models title: Game Data Models @@ -9118,7 +9118,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -9153,7 +9153,7 @@ sections: sections: - id: system-list repeatable: true - title: '{{system_name}} System' + title: "{{system_name}} System" template: | **Responsibility:** {{system_description}} @@ -9677,7 +9677,7 @@ sections: repeatable: true sections: - id: integration - title: '{{service_name}} Integration' + title: "{{service_name}} Integration" template: | - **Purpose:** {{service_purpose}} - **Documentation:** {{service_docs_url}} @@ -9789,12 +9789,12 @@ sections: - id: environments title: Build Environments repeatable: true - template: '- **{{env_name}}:** {{env_purpose}} - {{platform_settings}}' + template: "- **{{env_name}}:** {{env_purpose}} - {{platform_settings}}" - id: platform-specific-builds title: Platform-Specific Build Settings type: code language: text - template: '{{platform_build_configurations}}' + template: "{{platform_build_configurations}}" - id: coding-standards title: Coding Standards @@ -9823,9 +9823,9 @@ sections: columns: [Element, Convention, Example] instruction: Only include if deviating from Unity defaults examples: - - '| MonoBehaviour | PascalCase + Component suffix | PlayerController, HealthSystem |' - - '| ScriptableObject | PascalCase + Data/Config suffix | PlayerData, GameConfig |' - - '| Prefab | PascalCase descriptive | PlayerCharacter, EnvironmentTile |' + - "| MonoBehaviour | PascalCase + Component suffix | PlayerController, HealthSystem |" + - "| ScriptableObject | PascalCase + Data/Config suffix | PlayerData, GameConfig |" + - "| Prefab | PascalCase descriptive | PlayerCharacter, EnvironmentTile |" - id: critical-rules title: Critical Unity Rules instruction: | @@ -9837,7 +9837,7 @@ sections: Avoid obvious rules like "follow SOLID principles" or "optimize performance" repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" - id: unity-specifics title: Unity-Specific Guidelines condition: Critical Unity-specific rules needed @@ -9846,7 +9846,7 @@ sections: - id: unity-lifecycle title: Unity Lifecycle Rules repeatable: true - template: '- **{{lifecycle_method}}:** {{usage_rule}}' + template: "- **{{lifecycle_method}}:** {{usage_rule}}" - id: test-strategy title: Test Strategy and Standards @@ -9974,7 +9974,7 @@ template: output: format: markdown filename: docs/game-brief.md - title: '{{game_title}} Game Brief' + title: "{{game_title}} Game Brief" workflow: mode: interactive @@ -10260,21 +10260,21 @@ sections: title: Development Roadmap sections: - id: phase-1-preproduction - title: 'Phase 1: Pre-Production ({{duration}})' + title: "Phase 1: Pre-Production ({{duration}})" type: bullet-list template: | - Detailed Game Design Document creation - Technical architecture planning - Art style exploration and pipeline setup - id: phase-2-prototype - title: 'Phase 2: Prototype ({{duration}})' + title: "Phase 2: Prototype ({{duration}})" type: bullet-list template: | - Core mechanic implementation - Technical proof of concept - Initial playtesting and iteration - id: phase-3-production - title: 'Phase 3: Production ({{duration}})' + title: "Phase 3: Production ({{duration}})" type: bullet-list template: | - Full feature development @@ -10333,7 +10333,7 @@ template: output: format: markdown filename: docs/game-design-document.md - title: '{{game_title}} Game Design Document (GDD)' + title: "{{game_title}} Game Design Document (GDD)" workflow: mode: interactive @@ -10381,8 +10381,8 @@ sections: **Primary:** {{age_range}}, {{player_type}}, {{platform_preference}} **Secondary:** {{secondary_audience}} examples: - - 'Primary: Ages 8-16, casual mobile gamers, prefer short play sessions' - - 'Secondary: Adult puzzle enthusiasts, educators looking for teaching tools' + - "Primary: Ages 8-16, casual mobile gamers, prefer short play sessions" + - "Secondary: Adult puzzle enthusiasts, educators looking for teaching tools" - id: platform-technical title: Platform & Technical Requirements instruction: Based on the technical preferences or user input, define the target platforms and Unity-specific requirements @@ -10393,7 +10393,7 @@ sections: **Screen Support:** {{resolution_range}} **Build Targets:** {{build_targets}} examples: - - 'Primary Platform: Mobile (iOS/Android), Engine: Unity 2022.3 LTS & C#, Performance: 60 FPS on iPhone 8/Galaxy S8' + - "Primary Platform: Mobile (iOS/Android), Engine: Unity 2022.3 LTS & C#, Performance: 60 FPS on iPhone 8/Galaxy S8" - id: unique-selling-points title: Unique Selling Points instruction: List 3-5 key features that differentiate this game from competitors @@ -10444,8 +10444,8 @@ sections: - {{loss_condition_1}} - Trigger: {{unity_trigger}} - {{loss_condition_2}} - Trigger: {{unity_trigger}} examples: - - 'Victory: Player reaches exit portal - Unity Event: OnTriggerEnter2D with Portal tag' - - 'Failure: Health reaches zero - Trigger: Health component value <= 0' + - "Victory: Player reaches exit portal - Unity Event: OnTriggerEnter2D with Portal tag" + - "Failure: Health reaches zero - Trigger: Health component value <= 0" - id: game-mechanics title: Game Mechanics @@ -10457,7 +10457,7 @@ sections: repeatable: true sections: - id: mechanic - title: '{{mechanic_name}}' + title: "{{mechanic_name}}" template: | **Description:** {{detailed_description}} @@ -10479,8 +10479,8 @@ sections: - {{script_name}}.cs - {{responsibility}} - {{manager_script}}.cs - {{management_role}} examples: - - 'Components Needed: Rigidbody2D, BoxCollider2D, PlayerMovement script' - - 'Physics Requirements: 2D Physics material for ground friction, Gravity scale 3' + - "Components Needed: Rigidbody2D, BoxCollider2D, PlayerMovement script" + - "Physics Requirements: 2D Physics material for ground friction, Gravity scale 3" - id: controls title: Controls instruction: Define all input methods for different platforms using Unity's Input System @@ -10535,7 +10535,7 @@ sections: **Late Game:** {{duration}} - {{difficulty_description}} - Unity Config: {{scriptable_object_values}} examples: - - 'enemy speed: 2.0f, jump height: 4.5f, obstacle density: 0.3f' + - "enemy speed: 2.0f, jump height: 4.5f, obstacle density: 0.3f" - id: economy-resources title: Economy & Resources condition: has_economy @@ -10558,7 +10558,7 @@ sections: repeatable: true sections: - id: level-type - title: '{{level_type_name}}' + title: "{{level_type_name}}" template: | **Purpose:** {{gameplay_purpose}} **Target Duration:** {{target_time}} @@ -10582,7 +10582,7 @@ sections: - {{prefab_name}} - {{prefab_purpose}} examples: - - 'Environment: TilemapRenderer with Platform tileset, Lighting: 2D Global Light + Point Lights' + - "Environment: TilemapRenderer with Platform tileset, Lighting: 2D Global Light + Point Lights" - id: level-progression title: Level Progression template: | @@ -10597,7 +10597,7 @@ sections: - Addressable Assets: {{addressable_groups}} - Loading Screens: {{loading_implementation}} examples: - - 'Scene Naming: World{X}_Level{Y}_Name, Addressable Groups: Levels_World1, World_Environments' + - "Scene Naming: World{X}_Level{Y}_Name, Addressable Groups: Levels_World1, World_Environments" - id: technical-specifications title: Technical Specifications @@ -10629,7 +10629,7 @@ sections: - Physics Settings: {{physics_config}} examples: - com.unity.addressables 1.20.5 - Asset loading and memory management - - 'Color Space: Linear, Quality: Mobile/Desktop presets, Gravity: -20' + - "Color Space: Linear, Quality: Mobile/Desktop presets, Gravity: -20" - id: performance-requirements title: Performance Requirements template: | @@ -10645,7 +10645,7 @@ sections: - GC Allocs: <{{gc_limit}}KB per frame - Draw Calls: <{{draw_calls}} per frame examples: - - '60 FPS (minimum 30), CPU: <16.67ms, GPU: <16.67ms, GC: <4KB, Draws: <50' + - "60 FPS (minimum 30), CPU: <16.67ms, GPU: <16.67ms, GC: <4KB, Draws: <50" - id: platform-specific title: Platform Specific Requirements template: | @@ -10668,7 +10668,7 @@ sections: - Browser Support: {{browser_list}} - Compression: {{compression_format}} examples: - - 'Resolution: 1280x720 - 4K, Gamepad: Xbox/PlayStation controllers via Input System' + - "Resolution: 1280x720 - 4K, Gamepad: Xbox/PlayStation controllers via Input System" - id: asset-requirements title: Asset Requirements instruction: Define asset specifications for Unity pipeline optimization @@ -10694,7 +10694,7 @@ sections: - Font: {{font_requirements}} - Icon Sizes: {{icon_specifications}} examples: - - 'Sprites: 32x32 to 256x256 at 16 PPU, Format: RGBA32 for quality/RGBA16 for performance' + - "Sprites: 32x32 to 256x256 at 16 PPU, Format: RGBA32 for quality/RGBA16 for performance" - id: technical-architecture-requirements title: Technical Architecture Requirements @@ -10736,8 +10736,8 @@ sections: - Prefabs: {{prefab_naming}} - Scenes: {{scene_naming}} examples: - - 'Architecture: Component-Based with ScriptableObject data containers' - - 'Scripts: PascalCase (PlayerController), Prefabs: Player_Prefab, Scenes: Level_01_Forest' + - "Architecture: Component-Based with ScriptableObject data containers" + - "Scripts: PascalCase (PlayerController), Prefabs: Player_Prefab, Scenes: Level_01_Forest" - id: unity-systems-integration title: Unity Systems Integration template: | @@ -10759,8 +10759,8 @@ sections: - **Memory Management:** {{memory_strategy}} - **Build Pipeline:** {{build_automation}} examples: - - 'Input System: Action Maps for Menu/Gameplay contexts with device switching' - - 'DOTween: Smooth UI transitions and gameplay animations' + - "Input System: Action Maps for Menu/Gameplay contexts with device switching" + - "DOTween: Smooth UI transitions and gameplay animations" - id: data-management title: Data Management template: | @@ -10783,8 +10783,8 @@ sections: - **Memory Pools:** {{pooling_objects}} - **Asset References:** {{asset_reference_system}} examples: - - 'Save Data: JSON format with AES encryption, stored in persistent data path' - - 'ScriptableObjects: Game settings, level configurations, character data' + - "Save Data: JSON format with AES encryption, stored in persistent data path" + - "ScriptableObjects: Game settings, level configurations, character data" - id: development-phases title: Development Phases & Epic Planning @@ -10796,15 +10796,15 @@ sections: instruction: Present a high-level list of all phases for user approval. Each phase's design should deliver significant Unity functionality. type: numbered-list examples: - - 'Phase 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management' - - 'Phase 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop' - - 'Phase 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression' - - 'Phase 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment' + - "Phase 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management" + - "Phase 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop" + - "Phase 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression" + - "Phase 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment" - id: phase-1-foundation - title: 'Phase 1: Unity Foundation & Core Systems ({{duration}})' + title: "Phase 1: Unity Foundation & Core Systems ({{duration}})" sections: - id: foundation-design - title: 'Design: Unity Project Foundation' + title: "Design: Unity Project Foundation" type: bullet-list template: | - Unity project setup with proper folder structure and naming conventions @@ -10814,9 +10814,9 @@ sections: - Development tools setup (debugging, profiling integration) - Initial build pipeline and platform configuration examples: - - 'Input System: Configure PlayerInput component with Action Maps for movement and UI' + - "Input System: Configure PlayerInput component with Action Maps for movement and UI" - id: core-systems-design - title: 'Design: Essential Game Systems' + title: "Design: Essential Game Systems" type: bullet-list template: | - Save/Load system implementation with {{save_format}} format @@ -10826,10 +10826,10 @@ sections: - Basic UI framework and canvas configuration - Settings and configuration management with ScriptableObjects - id: phase-2-gameplay - title: 'Phase 2: Core Gameplay Implementation ({{duration}})' + title: "Phase 2: Core Gameplay Implementation ({{duration}})" sections: - id: gameplay-mechanics-design - title: 'Design: Primary Game Mechanics' + title: "Design: Primary Game Mechanics" type: bullet-list template: | - Player controller with {{movement_type}} movement system @@ -10839,7 +10839,7 @@ sections: - Basic collision detection and response systems - Animation system integration with Animator controllers - id: level-systems-design - title: 'Design: Level & Content Systems' + title: "Design: Level & Content Systems" type: bullet-list template: | - Scene loading and transition system @@ -10849,10 +10849,10 @@ sections: - Collectibles and pickup systems - Victory/defeat condition implementation - id: phase-3-polish - title: 'Phase 3: Polish & Optimization ({{duration}})' + title: "Phase 3: Polish & Optimization ({{duration}})" sections: - id: performance-design - title: 'Design: Performance & Platform Optimization' + title: "Design: Performance & Platform Optimization" type: bullet-list template: | - Unity Profiler analysis and optimization passes @@ -10862,7 +10862,7 @@ sections: - Build size optimization and asset bundling - Quality settings configuration for different device tiers - id: user-experience-design - title: 'Design: User Experience & Polish' + title: "Design: User Experience & Polish" type: bullet-list template: | - Complete UI/UX implementation with responsive design @@ -10887,10 +10887,10 @@ sections: - 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. elicit: true examples: - - 'Epic 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management' - - 'Epic 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop' - - 'Epic 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression' - - 'Epic 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment' + - "Epic 1: Unity Foundation & Core Systems: Project setup, input handling, basic scene management" + - "Epic 2: Core Game Mechanics: Player controller, physics systems, basic gameplay loop" + - "Epic 3: Level Systems & Content Pipeline: Scene loading, prefab systems, level progression" + - "Epic 4: Polish & Platform Optimization: Performance tuning, platform-specific features, deployment" - id: epic-details title: Epic {{epic_number}} {{epic_title}} @@ -10912,13 +10912,13 @@ sections: - 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 elicit: true - template: '{{epic_goal}}' + template: "{{epic_goal}}" sections: - id: story title: Story {{epic_number}}.{{story_number}} {{story_title}} repeatable: true instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature and reference the gamearchitecture section for additional implementation and integration specifics. - template: '{{clear_description_of_what_needs_to_be_implemented}}' + template: "{{clear_description_of_what_needs_to_be_implemented}}" sections: - id: acceptance-criteria title: Acceptance Criteria @@ -10928,7 +10928,7 @@ sections: title: Functional Requirements type: checklist items: - - '{{specific_functional_requirement}}' + - "{{specific_functional_requirement}}" - id: technical-requirements title: Technical Requirements type: checklist @@ -10936,14 +10936,14 @@ sections: - Code follows C# best practices - Maintains stable frame rate on target devices - No memory leaks or performance degradation - - '{{specific_technical_requirement}}' + - "{{specific_technical_requirement}}" - id: game-design-requirements title: Game Design Requirements type: checklist items: - - '{{gameplay_requirement_from_gdd}}' - - '{{balance_requirement_if_applicable}}' - - '{{player_experience_requirement}}' + - "{{gameplay_requirement_from_gdd}}" + - "{{balance_requirement_if_applicable}}" + - "{{player_experience_requirement}}" - id: success-metrics title: Success Metrics & Quality Assurance @@ -10961,8 +10961,8 @@ sections: - **Build Size:** Final build <{{size_limit}}MB for mobile, <{{desktop_limit}}MB for desktop - **Battery Life:** Mobile gameplay sessions >{{battery_target}} hours on average device examples: - - 'Frame Rate: Consistent 60 FPS with <5% drops below 45 FPS on target hardware' - - 'Crash Rate: <0.5% across iOS/Android, <0.1% on desktop platforms' + - "Frame Rate: Consistent 60 FPS with <5% drops below 45 FPS on target hardware" + - "Crash Rate: <0.5% across iOS/Android, <0.1% on desktop platforms" - id: gameplay-metrics title: Gameplay & User Engagement Metrics type: bullet-list @@ -10974,8 +10974,8 @@ sections: - **Gameplay Completion:** {{completion_rate}}% complete main game content - **Control Responsiveness:** Input lag <{{input_lag}}ms on all platforms examples: - - 'Tutorial Completion: 85% of players complete movement and basic mechanics tutorial' - - 'Session Duration: Average 15-20 minutes per session for mobile, 30-45 minutes for desktop' + - "Tutorial Completion: 85% of players complete movement and basic mechanics tutorial" + - "Session Duration: Average 15-20 minutes per session for mobile, 30-45 minutes for desktop" - id: platform-specific-metrics title: Platform-Specific Quality Metrics type: table @@ -11020,17 +11020,17 @@ sections: - Consider cross-platform testing requirements - Account for Unity build and deployment steps examples: - - 'Foundation stories: Individual Unity systems (Input, Audio, Scene Management) - 1-2 days each' - - 'Feature stories: Complete gameplay mechanics with UI and feedback - 2-4 days each' + - "Foundation stories: Individual Unity systems (Input, Audio, Scene Management) - 1-2 days each" + - "Feature stories: Complete gameplay mechanics with UI and feedback - 2-4 days each" - id: recommended-agents title: Recommended BMad Agent Sequence type: numbered-list template: | 1. **{{agent_name}}**: {{agent_responsibility}} examples: - - 'Unity Architect: Create detailed technical architecture document with specific Unity implementation patterns' - - 'Unity Developer: Implement core systems and gameplay mechanics according to architecture' - - 'QA Tester: Validate performance metrics and cross-platform functionality' + - "Unity Architect: Create detailed technical architecture document with specific Unity implementation patterns" + - "Unity Developer: Implement core systems and gameplay mechanics according to architecture" + - "QA Tester: Validate performance metrics and cross-platform functionality" ==================== END: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ==================== ==================== START: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ==================== @@ -11040,8 +11040,8 @@ template: version: 3.0 output: format: markdown - filename: 'stories/{{epic_name}}/{{story_id}}-{{story_name}}.md' - title: 'Story: {{story_title}}' + filename: "stories/{{epic_name}}/{{story_id}}-{{story_name}}.md" + title: "Story: {{story_title}}" workflow: mode: interactive @@ -11070,7 +11070,7 @@ sections: - id: description title: Description instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature. - template: '{{clear_description_of_what_needs_to_be_implemented}}' + template: "{{clear_description_of_what_needs_to_be_implemented}}" - id: acceptance-criteria title: Acceptance Criteria @@ -11080,7 +11080,7 @@ sections: title: Functional Requirements type: checklist items: - - '{{specific_functional_requirement}}' + - "{{specific_functional_requirement}}" - id: technical-requirements title: Technical Requirements type: checklist @@ -11088,14 +11088,14 @@ sections: - Code follows C# best practices - Maintains stable frame rate on target devices - No memory leaks or performance degradation - - '{{specific_technical_requirement}}' + - "{{specific_technical_requirement}}" - id: game-design-requirements title: Game Design Requirements type: checklist items: - - '{{gameplay_requirement_from_gdd}}' - - '{{balance_requirement_if_applicable}}' - - '{{player_experience_requirement}}' + - "{{gameplay_requirement_from_gdd}}" + - "{{balance_requirement_if_applicable}}" + - "{{player_experience_requirement}}" - id: technical-specifications title: Technical Specifications @@ -11270,7 +11270,7 @@ sections: - Performance targets met - No C# compiler errors or warnings - Documentation updated - - '{{game_specific_dod_item}}' + - "{{game_specific_dod_item}}" - id: notes title: Notes @@ -11300,7 +11300,7 @@ template: output: format: markdown filename: docs/level-design-document.md - title: '{{game_title}} Level Design Document' + title: "{{game_title}} Level Design Document" workflow: mode: interactive @@ -11361,7 +11361,7 @@ sections: repeatable: true sections: - id: level-category - title: '{{category_name}} Levels' + title: "{{category_name}} Levels" template: | **Purpose:** {{gameplay_purpose}} @@ -13883,7 +13883,7 @@ workflow: notes: Implement stories in priority order. Test frequently in the Unity Editor and adjust design based on what feels fun. Document discoveries. workflow_end: action: prototype_evaluation - notes: 'Prototype complete. Evaluate core mechanics, gather feedback, and decide next steps: iterate, expand, or archive.' + notes: "Prototype complete. Evaluate core mechanics, gather feedback, and decide next steps: iterate, expand, or archive." game_jam_sequence: - step: jam_concept agent: game-designer diff --git a/dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt b/dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt index d3ffa32d..6dcc915e 100644 --- a/dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt +++ b/dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt @@ -530,23 +530,23 @@ template: output: format: markdown filename: docs/infrastructure-architecture.md - title: '{{project_name}} Infrastructure Architecture' + title: "{{project_name}} Infrastructure Architecture" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Infrastructure Architecture Elicitation Actions' + title: "Infrastructure Architecture Elicitation Actions" sections: - id: infrastructure-overview options: - - 'Multi-Cloud Strategy Analysis - Evaluate cloud provider options and vendor lock-in considerations' - - 'Regional Distribution Planning - Analyze latency requirements and data residency needs' - - 'Environment Isolation Strategy - Design security boundaries and resource segregation' - - 'Scalability Patterns Review - Assess auto-scaling needs and traffic patterns' - - 'Compliance Requirements Analysis - Review regulatory and security compliance needs' - - 'Cost-Benefit Analysis - Compare infrastructure options and TCO' - - 'Proceed to next section' + - "Multi-Cloud Strategy Analysis - Evaluate cloud provider options and vendor lock-in considerations" + - "Regional Distribution Planning - Analyze latency requirements and data residency needs" + - "Environment Isolation Strategy - Design security boundaries and resource segregation" + - "Scalability Patterns Review - Assess auto-scaling needs and traffic patterns" + - "Compliance Requirements Analysis - Review regulatory and security compliance needs" + - "Cost-Benefit Analysis - Compare infrastructure options and TCO" + - "Proceed to next section" sections: - id: initial-setup @@ -606,7 +606,7 @@ sections: sections: - id: environments repeatable: true - title: '{{environment_name}} Environment' + title: "{{environment_name}} Environment" template: | - **Purpose:** {{environment_purpose}} - **Resources:** {{environment_resources}} @@ -957,24 +957,24 @@ template: output: format: markdown filename: docs/platform-infrastructure/platform-implementation.md - title: '{{project_name}} Platform Infrastructure Implementation' + title: "{{project_name}} Platform Infrastructure Implementation" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Platform Implementation Elicitation Actions' + title: "Platform Implementation Elicitation Actions" sections: - id: foundation-infrastructure options: - - 'Platform Layer Security Hardening - Additional security controls and compliance validation' - - 'Performance Optimization - Network and resource optimization' - - 'Operational Excellence Enhancement - Automation and monitoring improvements' - - 'Platform Integration Validation - Verify foundation supports upper layers' - - 'Developer Experience Analysis - Foundation impact on developer workflows' - - 'Disaster Recovery Testing - Foundation resilience validation' - - 'BMAD Workflow Integration - Cross-agent support verification' - - 'Finalize and Proceed to Container Platform' + - "Platform Layer Security Hardening - Additional security controls and compliance validation" + - "Performance Optimization - Network and resource optimization" + - "Operational Excellence Enhancement - Automation and monitoring improvements" + - "Platform Integration Validation - Verify foundation supports upper layers" + - "Developer Experience Analysis - Foundation impact on developer workflows" + - "Disaster Recovery Testing - Foundation resilience validation" + - "BMAD Workflow Integration - Cross-agent support verification" + - "Finalize and Proceed to Container Platform" sections: - id: initial-setup diff --git a/dist/teams/team-all.txt b/dist/teams/team-all.txt index e2cb3c61..17d4ffe9 100644 --- a/dist/teams/team-all.txt +++ b/dist/teams/team-all.txt @@ -46,7 +46,7 @@ bundle: description: Includes every core system agent. agents: - bmad-orchestrator - - '*' + - "*" workflows: - brownfield-fullstack.yaml - brownfield-service.yaml @@ -2772,24 +2772,24 @@ template: output: format: markdown filename: docs/brief.md - title: 'Project Brief: {{project_name}}' + title: "Project Brief: {{project_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Project Brief Elicitation Actions' + title: "Project Brief Elicitation Actions" options: - - 'Expand section with more specific details' - - 'Validate against similar successful products' - - 'Stress test assumptions with edge cases' - - 'Explore alternative solution approaches' - - 'Analyze resource/constraint trade-offs' - - 'Generate risk mitigation strategies' - - 'Challenge scope from MVP minimalist view' - - 'Brainstorm creative feature possibilities' - - 'If only we had [resource/capability/time]...' - - 'Proceed to next section' + - "Expand section with more specific details" + - "Validate against similar successful products" + - "Stress test assumptions with edge cases" + - "Explore alternative solution approaches" + - "Analyze resource/constraint trade-offs" + - "Generate risk mitigation strategies" + - "Challenge scope from MVP minimalist view" + - "Brainstorm creative feature possibilities" + - "If only we had [resource/capability/time]..." + - "Proceed to next section" sections: - id: introduction @@ -2811,7 +2811,7 @@ sections: - Primary problem being solved - Target market identification - Key value proposition - template: '{{executive_summary_content}}' + template: "{{executive_summary_content}}" - id: problem-statement title: Problem Statement @@ -2821,7 +2821,7 @@ sections: - Impact of the problem (quantify if possible) - Why existing solutions fall short - Urgency and importance of solving this now - template: '{{detailed_problem_description}}' + template: "{{detailed_problem_description}}" - id: proposed-solution title: Proposed Solution @@ -2831,7 +2831,7 @@ sections: - Key differentiators from existing solutions - Why this solution will succeed where others haven't - High-level vision for the product - template: '{{solution_description}}' + template: "{{solution_description}}" - id: target-users title: Target Users @@ -2843,12 +2843,12 @@ sections: - Goals they're trying to achieve sections: - id: primary-segment - title: 'Primary User Segment: {{segment_name}}' - template: '{{primary_user_description}}' + title: "Primary User Segment: {{segment_name}}" + template: "{{primary_user_description}}" - id: secondary-segment - title: 'Secondary User Segment: {{segment_name}}' + title: "Secondary User Segment: {{segment_name}}" condition: Has secondary user segment - template: '{{secondary_user_description}}' + template: "{{secondary_user_description}}" - id: goals-metrics title: Goals & Success Metrics @@ -2857,15 +2857,15 @@ sections: - id: business-objectives title: Business Objectives type: bullet-list - template: '- {{objective_with_metric}}' + template: "- {{objective_with_metric}}" - id: user-success-metrics title: User Success Metrics type: bullet-list - template: '- {{user_metric}}' + template: "- {{user_metric}}" - id: kpis title: Key Performance Indicators (KPIs) type: bullet-list - template: '- {{kpi}}: {{definition_and_target}}' + template: "- {{kpi}}: {{definition_and_target}}" - id: mvp-scope title: MVP Scope @@ -2874,14 +2874,14 @@ sections: - id: core-features title: Core Features (Must Have) type: bullet-list - template: '- **{{feature}}:** {{description_and_rationale}}' + template: "- **{{feature}}:** {{description_and_rationale}}" - id: out-of-scope title: Out of Scope for MVP type: bullet-list - template: '- {{feature_or_capability}}' + template: "- {{feature_or_capability}}" - id: mvp-success-criteria title: MVP Success Criteria - template: '{{mvp_success_definition}}' + template: "{{mvp_success_definition}}" - id: post-mvp-vision title: Post-MVP Vision @@ -2889,13 +2889,13 @@ sections: sections: - id: phase-2-features title: Phase 2 Features - template: '{{next_priority_features}}' + template: "{{next_priority_features}}" - id: long-term-vision title: Long-term Vision - template: '{{one_two_year_vision}}' + template: "{{one_two_year_vision}}" - id: expansion-opportunities title: Expansion Opportunities - template: '{{potential_expansions}}' + template: "{{potential_expansions}}" - id: technical-considerations title: Technical Considerations @@ -2936,7 +2936,7 @@ sections: - id: key-assumptions title: Key Assumptions type: bullet-list - template: '- {{assumption}}' + template: "- {{assumption}}" - id: risks-questions title: Risks & Open Questions @@ -2945,15 +2945,15 @@ sections: - id: key-risks title: Key Risks type: bullet-list - template: '- **{{risk}}:** {{description_and_impact}}' + template: "- **{{risk}}:** {{description_and_impact}}" - id: open-questions title: Open Questions type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: research-areas title: Areas Needing Further Research type: bullet-list - template: '- {{research_topic}}' + template: "- {{research_topic}}" - id: appendices title: Appendices @@ -2970,10 +2970,10 @@ sections: - id: stakeholder-input title: B. Stakeholder Input condition: Has stakeholder feedback - template: '{{stakeholder_feedback}}' + template: "{{stakeholder_feedback}}" - id: references title: C. References - template: '{{relevant_links_and_docs}}' + template: "{{relevant_links_and_docs}}" - id: next-steps title: Next Steps @@ -2981,7 +2981,7 @@ sections: - id: immediate-actions title: Immediate Actions type: numbered-list - template: '{{action_item}}' + template: "{{action_item}}" - id: pm-handoff title: PM Handoff content: | @@ -2996,24 +2996,24 @@ template: output: format: markdown filename: docs/market-research.md - title: 'Market Research Report: {{project_product_name}}' + title: "Market Research Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Market Research Elicitation Actions' + title: "Market Research Elicitation Actions" options: - - 'Expand market sizing calculations with sensitivity analysis' - - 'Deep dive into a specific customer segment' - - 'Analyze an emerging market trend in detail' - - 'Compare this market to an analogous market' - - 'Stress test market assumptions' - - 'Explore adjacent market opportunities' - - 'Challenge market definition and boundaries' - - 'Generate strategic scenarios (best/base/worst case)' - - 'If only we had considered [X market factor]...' - - 'Proceed to next section' + - "Expand market sizing calculations with sensitivity analysis" + - "Deep dive into a specific customer segment" + - "Analyze an emerging market trend in detail" + - "Compare this market to an analogous market" + - "Stress test market assumptions" + - "Explore adjacent market opportunities" + - "Challenge market definition and boundaries" + - "Generate strategic scenarios (best/base/worst case)" + - "If only we had considered [X market factor]..." + - "Proceed to next section" sections: - id: executive-summary @@ -3095,7 +3095,7 @@ sections: repeatable: true sections: - id: segment - title: 'Segment {{segment_number}}: {{segment_name}}' + title: "Segment {{segment_number}}: {{segment_name}}" template: | - **Description:** {{brief_overview}} - **Size:** {{number_of_customers_market_value}} @@ -3164,20 +3164,20 @@ sections: instruction: Analyze each force with specific evidence and implications sections: - id: supplier-power - title: 'Supplier Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Supplier Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: buyer-power - title: 'Buyer Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Buyer Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: competitive-rivalry - title: 'Competitive Rivalry: {{intensity_level}}' - template: '{{analysis_and_implications}}' + title: "Competitive Rivalry: {{intensity_level}}" + template: "{{analysis_and_implications}}" - id: threat-new-entry - title: 'Threat of New Entry: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of New Entry: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: threat-substitutes - title: 'Threat of Substitutes: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of Substitutes: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: adoption-lifecycle title: Technology Adoption Lifecycle Stage instruction: | @@ -3195,7 +3195,7 @@ sections: repeatable: true sections: - id: opportunity - title: 'Opportunity {{opportunity_number}}: {{name}}' + title: "Opportunity {{opportunity_number}}: {{name}}" template: | - **Description:** {{what_is_the_opportunity}} - **Size/Potential:** {{quantified_potential}} @@ -3251,24 +3251,24 @@ template: output: format: markdown filename: docs/competitor-analysis.md - title: 'Competitive Analysis Report: {{project_product_name}}' + title: "Competitive Analysis Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Competitive Analysis Elicitation Actions' + title: "Competitive Analysis Elicitation Actions" options: - "Deep dive on a specific competitor's strategy" - - 'Analyze competitive dynamics in a specific segment' - - 'War game competitive responses to your moves' - - 'Explore partnership vs. competition scenarios' - - 'Stress test differentiation claims' - - 'Analyze disruption potential (yours or theirs)' - - 'Compare to competition in adjacent markets' - - 'Generate win/loss analysis insights' + - "Analyze competitive dynamics in a specific segment" + - "War game competitive responses to your moves" + - "Explore partnership vs. competition scenarios" + - "Stress test differentiation claims" + - "Analyze disruption potential (yours or theirs)" + - "Compare to competition in adjacent markets" + - "Generate win/loss analysis insights" - "If only we had known about [competitor X's plan]..." - - 'Proceed to next section' + - "Proceed to next section" sections: - id: executive-summary @@ -3335,7 +3335,7 @@ sections: repeatable: true sections: - id: competitor - title: '{{competitor_name}} - Priority {{priority_level}}' + title: "{{competitor_name}} - Priority {{priority_level}}" sections: - id: company-overview title: Company Overview @@ -3367,11 +3367,11 @@ sections: - id: strengths title: Strengths type: bullet-list - template: '- {{strength}}' + template: "- {{strength}}" - id: weaknesses title: Weaknesses type: bullet-list - template: '- {{weakness}}' + template: "- {{weakness}}" - id: market-position title: Market Position & Performance template: | @@ -3389,35 +3389,35 @@ sections: type: table columns: [ - 'Feature Category', - '{{your_company}}', - '{{competitor_1}}', - '{{competitor_2}}', - '{{competitor_3}}', + "Feature Category", + "{{your_company}}", + "{{competitor_1}}", + "{{competitor_2}}", + "{{competitor_3}}", ] rows: - - category: 'Core Functionality' + - category: "Core Functionality" items: - - ['Feature A', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - ['Feature B', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - category: 'User Experience' + - ["Feature A", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - ["Feature B", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - category: "User Experience" items: - - ['Mobile App', '{{rating}}', '{{rating}}', '{{rating}}', '{{rating}}'] - - ['Onboarding Time', '{{time}}', '{{time}}', '{{time}}', '{{time}}'] - - category: 'Integration & Ecosystem' + - ["Mobile App", "{{rating}}", "{{rating}}", "{{rating}}", "{{rating}}"] + - ["Onboarding Time", "{{time}}", "{{time}}", "{{time}}", "{{time}}"] + - category: "Integration & Ecosystem" items: - [ - 'API Availability', - '{{availability}}', - '{{availability}}', - '{{availability}}', - '{{availability}}', + "API Availability", + "{{availability}}", + "{{availability}}", + "{{availability}}", + "{{availability}}", ] - - ['Third-party Integrations', '{{number}}', '{{number}}', '{{number}}', '{{number}}'] - - category: 'Pricing & Plans' + - ["Third-party Integrations", "{{number}}", "{{number}}", "{{number}}", "{{number}}"] + - category: "Pricing & Plans" items: - - ['Starting Price', '{{price}}', '{{price}}', '{{price}}', '{{price}}'] - - ['Free Tier', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}'] + - ["Starting Price", "{{price}}", "{{price}}", "{{price}}", "{{price}}"] + - ["Free Tier", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}"] - id: swot-comparison title: SWOT Comparison instruction: Create SWOT analysis for your solution vs. top competitors @@ -3430,7 +3430,7 @@ sections: - **Opportunities:** {{opportunities}} - **Threats:** {{threats}} - id: vs-competitor - title: 'vs. {{main_competitor}}' + title: "vs. {{main_competitor}}" template: | - **Competitive Advantages:** {{your_advantages}} - **Competitive Disadvantages:** {{their_advantages}} @@ -3560,7 +3560,7 @@ template: output: format: markdown filename: docs/brainstorming-session-results.md - title: 'Brainstorming Session Results' + title: "Brainstorming Session Results" workflow: mode: non-interactive @@ -3585,38 +3585,38 @@ sections: **Total Ideas Generated:** {{total_ideas}} - id: key-themes - title: 'Key Themes Identified:' + title: "Key Themes Identified:" type: bullet-list - template: '- {{theme}}' + template: "- {{theme}}" - id: technique-sessions title: Technique Sessions repeatable: true sections: - id: technique - title: '{{technique_name}} - {{duration}}' + title: "{{technique_name}} - {{duration}}" sections: - id: description - template: '**Description:** {{technique_description}}' + template: "**Description:** {{technique_description}}" - id: ideas-generated - title: 'Ideas Generated:' + title: "Ideas Generated:" type: numbered-list - template: '{{idea}}' + template: "{{idea}}" - id: insights - title: 'Insights Discovered:' + title: "Insights Discovered:" type: bullet-list - template: '- {{insight}}' + template: "- {{insight}}" - id: connections - title: 'Notable Connections:' + title: "Notable Connections:" type: bullet-list - template: '- {{connection}}' + template: "- {{connection}}" - id: idea-categorization title: Idea Categorization sections: - id: immediate-opportunities title: Immediate Opportunities - content: '*Ideas ready to implement now*' + content: "*Ideas ready to implement now*" repeatable: true type: numbered-list template: | @@ -3626,7 +3626,7 @@ sections: - Resources needed: {{requirements}} - id: future-innovations title: Future Innovations - content: '*Ideas requiring development/research*' + content: "*Ideas requiring development/research*" repeatable: true type: numbered-list template: | @@ -3636,7 +3636,7 @@ sections: - Timeline estimate: {{timeline}} - id: moonshots title: Moonshots - content: '*Ambitious, transformative concepts*' + content: "*Ambitious, transformative concepts*" repeatable: true type: numbered-list template: | @@ -3646,9 +3646,9 @@ sections: - Challenges to overcome: {{challenges}} - id: insights-learnings title: Insights & Learnings - content: '*Key realizations from the session*' + content: "*Key realizations from the session*" type: bullet-list - template: '- {{insight}}: {{description_and_implications}}' + template: "- {{insight}}: {{description_and_implications}}" - id: action-planning title: Action Planning @@ -3657,21 +3657,21 @@ sections: title: Top 3 Priority Ideas sections: - id: priority-1 - title: '#1 Priority: {{idea_name}}' + title: "#1 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-2 - title: '#2 Priority: {{idea_name}}' + title: "#2 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-3 - title: '#3 Priority: {{idea_name}}' + title: "#3 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} @@ -3684,19 +3684,19 @@ sections: - id: what-worked title: What Worked Well type: bullet-list - template: '- {{aspect}}' + template: "- {{aspect}}" - id: areas-exploration title: Areas for Further Exploration type: bullet-list - template: '- {{area}}: {{reason}}' + template: "- {{area}}: {{reason}}" - id: recommended-techniques title: Recommended Follow-up Techniques type: bullet-list - template: '- {{technique}}: {{reason}}' + template: "- {{technique}}: {{reason}}" - id: questions-emerged title: Questions That Emerged type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: next-session title: Next Session Planning template: | @@ -3847,7 +3847,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Architecture Document' + title: "{{project_name}} Architecture Document" workflow: mode: interactive @@ -3958,11 +3958,11 @@ sections: - Code organization patterns (Dependency Injection, Repository, Module, Factory) - Data patterns (Event Sourcing, Saga, Database per Service) - Communication patterns (REST, GraphQL, Message Queue, Pub/Sub) - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - - '**Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling' - - '**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility' - - '**Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience' + - "**Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling" + - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility" + - "**Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience" - id: tech-stack title: Tech Stack @@ -4000,9 +4000,9 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Populate the technology stack table with all relevant technologies examples: - - '| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |' - - '| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |' - - '| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |' + - "| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |" + - "| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |" + - "| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |" - id: data-models title: Data Models @@ -4020,7 +4020,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -4051,7 +4051,7 @@ sections: sections: - id: component-list repeatable: true - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} @@ -4089,7 +4089,7 @@ sections: repeatable: true sections: - id: api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -4214,12 +4214,12 @@ sections: - id: environments title: Environments repeatable: true - template: '- **{{env_name}}:** {{env_purpose}} - {{env_details}}' + template: "- **{{env_name}}:** {{env_purpose}} - {{env_details}}" - id: promotion-flow title: Environment Promotion Flow type: code language: text - template: '{{promotion_flow_diagram}}' + template: "{{promotion_flow_diagram}}" - id: rollback-strategy title: Rollback Strategy template: | @@ -4315,16 +4315,16 @@ sections: Avoid obvious rules like "use SOLID principles" or "write clean code" repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" - id: language-specifics title: Language-Specific Guidelines condition: Critical language-specific rules needed instruction: Add ONLY if critical for preventing AI mistakes. Most teams don't need this section. sections: - id: language-rules - title: '{{language_name}} Specifics' + title: "{{language_name}} Specifics" repeatable: true - template: '- **{{rule_topic}}:** {{rule_detail}}' + template: "- **{{rule_topic}}:** {{rule_detail}}" - id: test-strategy title: Test Strategy and Standards @@ -4372,9 +4372,9 @@ sections: - **Test Infrastructure:** - **{{dependency_name}}:** {{test_approach}} ({{test_tool}}) examples: - - '**Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration' - - '**Message Queue:** Embedded Kafka for tests' - - '**External APIs:** WireMock for stubbing' + - "**Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration" + - "**Message Queue:** Embedded Kafka for tests" + - "**External APIs:** WireMock for stubbing" - id: e2e-tests title: End-to-End Tests template: | @@ -4500,7 +4500,7 @@ template: output: format: markdown filename: docs/ui-architecture.md - title: '{{project_name}} Frontend Architecture Document' + title: "{{project_name}} Frontend Architecture Document" workflow: mode: interactive @@ -4568,29 +4568,29 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Fill in appropriate technology choices based on the selected framework and project requirements. rows: - - ['Framework', '{{framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['UI Library', '{{ui_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Framework", "{{framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["UI Library", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'State Management', - '{{state_management}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "State Management", + "{{state_management}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['Routing', '{{routing_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Build Tool', '{{build_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Styling', '{{styling_solution}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Testing', '{{test_framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Routing", "{{routing_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Styling", "{{styling_solution}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Testing", "{{test_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Component Library', - '{{component_lib}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Component Library", + "{{component_lib}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['Form Handling', '{{form_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Animation', '{{animation_lib}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Dev Tools', '{{dev_tools}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Form Handling", "{{form_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Animation", "{{animation_lib}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Dev Tools", "{{dev_tools}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - id: project-structure title: Project Structure @@ -4684,12 +4684,12 @@ sections: title: Testing Best Practices type: numbered-list items: - - '**Unit Tests**: Test individual components in isolation' - - '**Integration Tests**: Test component interactions' - - '**E2E Tests**: Test critical user flows (using Cypress/Playwright)' - - '**Coverage Goals**: Aim for 80% code coverage' - - '**Test Structure**: Arrange-Act-Assert pattern' - - '**Mock External Dependencies**: API calls, routing, state management' + - "**Unit Tests**: Test individual components in isolation" + - "**Integration Tests**: Test component interactions" + - "**E2E Tests**: Test critical user flows (using Cypress/Playwright)" + - "**Coverage Goals**: Aim for 80% code coverage" + - "**Test Structure**: Arrange-Act-Assert pattern" + - "**Mock External Dependencies**: API calls, routing, state management" - id: environment-configuration title: Environment Configuration @@ -4721,7 +4721,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Fullstack Architecture Document' + title: "{{project_name}} Fullstack Architecture Document" workflow: mode: interactive @@ -4842,12 +4842,12 @@ sections: For each pattern, provide recommendation and rationale. repeatable: true - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - - '**Jamstack Architecture:** Static site generation with serverless APIs - _Rationale:_ Optimal performance and scalability for content-heavy applications' - - '**Component-Based UI:** Reusable React components with TypeScript - _Rationale:_ Maintainability and type safety across large codebases' - - '**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility' - - '**API Gateway Pattern:** Single entry point for all API calls - _Rationale:_ Centralized auth, rate limiting, and monitoring' + - "**Jamstack Architecture:** Static site generation with serverless APIs - _Rationale:_ Optimal performance and scalability for content-heavy applications" + - "**Component-Based UI:** Reusable React components with TypeScript - _Rationale:_ Maintainability and type safety across large codebases" + - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility" + - "**API Gateway Pattern:** Single entry point for all API calls - _Rationale:_ Centralized auth, rate limiting, and monitoring" - id: tech-stack title: Tech Stack @@ -4871,45 +4871,45 @@ sections: type: table columns: [Category, Technology, Version, Purpose, Rationale] rows: - - ['Frontend Language', '{{fe_language}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Frontend Language", "{{fe_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Frontend Framework', - '{{fe_framework}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Frontend Framework", + "{{fe_framework}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - [ - 'UI Component Library', - '{{ui_library}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "UI Component Library", + "{{ui_library}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['State Management', '{{state_mgmt}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Backend Language', '{{be_language}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["State Management", "{{state_mgmt}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Backend Language", "{{be_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Backend Framework', - '{{be_framework}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Backend Framework", + "{{be_framework}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['API Style', '{{api_style}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Database', '{{database}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Cache', '{{cache}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['File Storage', '{{storage}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Authentication', '{{auth}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Frontend Testing', '{{fe_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Backend Testing', '{{be_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['E2E Testing', '{{e2e_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Build Tool', '{{build_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Bundler', '{{bundler}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['IaC Tool', '{{iac_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['CI/CD', '{{cicd}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Monitoring', '{{monitoring}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Logging', '{{logging}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['CSS Framework', '{{css_framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["API Style", "{{api_style}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Database", "{{database}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Cache", "{{cache}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["File Storage", "{{storage}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Authentication", "{{auth}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Frontend Testing", "{{fe_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Backend Testing", "{{be_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["E2E Testing", "{{e2e_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Bundler", "{{bundler}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["IaC Tool", "{{iac_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["CI/CD", "{{cicd}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Monitoring", "{{monitoring}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Logging", "{{logging}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["CSS Framework", "{{css_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - id: data-models title: Data Models @@ -4928,7 +4928,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -4940,11 +4940,11 @@ sections: title: TypeScript Interface type: code language: typescript - template: '{{model_interface}}' + template: "{{model_interface}}" - id: relationships title: Relationships type: bullet-list - template: '- {{relationship}}' + template: "- {{relationship}}" - id: api-spec title: API Specification @@ -4981,13 +4981,13 @@ sections: condition: API style is GraphQL type: code language: graphql - template: '{{graphql_schema}}' + template: "{{graphql_schema}}" - id: trpc-api title: tRPC Router Definitions condition: API style is tRPC type: code language: typescript - template: '{{trpc_routers}}' + template: "{{trpc_routers}}" - id: components title: Components @@ -5008,7 +5008,7 @@ sections: sections: - id: component-list repeatable: true - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} @@ -5046,7 +5046,7 @@ sections: repeatable: true sections: - id: api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -5103,12 +5103,12 @@ sections: title: Component Organization type: code language: text - template: '{{component_structure}}' + template: "{{component_structure}}" - id: component-template title: Component Template type: code language: typescript - template: '{{component_template}}' + template: "{{component_template}}" - id: state-management title: State Management Architecture instruction: Detail state management approach based on chosen solution. @@ -5117,11 +5117,11 @@ sections: title: State Structure type: code language: typescript - template: '{{state_structure}}' + template: "{{state_structure}}" - id: state-patterns title: State Management Patterns type: bullet-list - template: '- {{pattern}}' + template: "- {{pattern}}" - id: routing-architecture title: Routing Architecture instruction: Define routing structure based on framework choice. @@ -5130,12 +5130,12 @@ sections: title: Route Organization type: code language: text - template: '{{route_structure}}' + template: "{{route_structure}}" - id: protected-routes title: Protected Route Pattern type: code language: typescript - template: '{{protected_route_example}}' + template: "{{protected_route_example}}" - id: frontend-services title: Frontend Services Layer instruction: Define how frontend communicates with backend. @@ -5144,12 +5144,12 @@ sections: title: API Client Setup type: code language: typescript - template: '{{api_client_setup}}' + template: "{{api_client_setup}}" - id: service-example title: Service Example type: code language: typescript - template: '{{service_example}}' + template: "{{service_example}}" - id: backend-architecture title: Backend Architecture @@ -5167,12 +5167,12 @@ sections: title: Function Organization type: code language: text - template: '{{function_structure}}' + template: "{{function_structure}}" - id: function-template title: Function Template type: code language: typescript - template: '{{function_template}}' + template: "{{function_template}}" - id: traditional-server condition: Traditional server architecture chosen sections: @@ -5180,12 +5180,12 @@ sections: title: Controller/Route Organization type: code language: text - template: '{{controller_structure}}' + template: "{{controller_structure}}" - id: controller-template title: Controller Template type: code language: typescript - template: '{{controller_template}}' + template: "{{controller_template}}" - id: database-architecture title: Database Architecture instruction: Define database schema and access patterns. @@ -5194,12 +5194,12 @@ sections: title: Schema Design type: code language: sql - template: '{{database_schema}}' + template: "{{database_schema}}" - id: data-access-layer title: Data Access Layer type: code language: typescript - template: '{{repository_pattern}}' + template: "{{repository_pattern}}" - id: auth-architecture title: Authentication and Authorization instruction: Define auth implementation details. @@ -5208,12 +5208,12 @@ sections: title: Auth Flow type: mermaid mermaid_type: sequence - template: '{{auth_flow_diagram}}' + template: "{{auth_flow_diagram}}" - id: auth-middleware title: Middleware/Guards type: code language: typescript - template: '{{auth_middleware}}' + template: "{{auth_middleware}}" - id: unified-project-structure title: Unified Project Structure @@ -5289,12 +5289,12 @@ sections: title: Prerequisites type: code language: bash - template: '{{prerequisites_commands}}' + template: "{{prerequisites_commands}}" - id: initial-setup title: Initial Setup type: code language: bash - template: '{{setup_commands}}' + template: "{{setup_commands}}" - id: dev-commands title: Development Commands type: code @@ -5350,15 +5350,15 @@ sections: title: CI/CD Pipeline type: code language: yaml - template: '{{cicd_pipeline_config}}' + template: "{{cicd_pipeline_config}}" - id: environments title: Environments type: table columns: [Environment, Frontend URL, Backend URL, Purpose] rows: - - ['Development', '{{dev_fe_url}}', '{{dev_be_url}}', 'Local development'] - - ['Staging', '{{staging_fe_url}}', '{{staging_be_url}}', 'Pre-production testing'] - - ['Production', '{{prod_fe_url}}', '{{prod_be_url}}', 'Live environment'] + - ["Development", "{{dev_fe_url}}", "{{dev_be_url}}", "Local development"] + - ["Staging", "{{staging_fe_url}}", "{{staging_be_url}}", "Pre-production testing"] + - ["Production", "{{prod_fe_url}}", "{{prod_be_url}}", "Live environment"] - id: security-performance title: Security and Performance @@ -5417,17 +5417,17 @@ sections: title: Frontend Tests type: code language: text - template: '{{frontend_test_structure}}' + template: "{{frontend_test_structure}}" - id: backend-tests title: Backend Tests type: code language: text - template: '{{backend_test_structure}}' + template: "{{backend_test_structure}}" - id: e2e-tests title: E2E Tests type: code language: text - template: '{{e2e_test_structure}}' + template: "{{e2e_test_structure}}" - id: test-examples title: Test Examples sections: @@ -5435,17 +5435,17 @@ sections: title: Frontend Component Test type: code language: typescript - template: '{{frontend_test_example}}' + template: "{{frontend_test_example}}" - id: backend-test title: Backend API Test type: code language: typescript - template: '{{backend_test_example}}' + template: "{{backend_test_example}}" - id: e2e-test title: E2E Test type: code language: typescript - template: '{{e2e_test_example}}' + template: "{{e2e_test_example}}" - id: coding-standards title: Coding Standards @@ -5455,22 +5455,22 @@ sections: - id: critical-rules title: Critical Fullstack Rules repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" examples: - - '**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' + - "**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" - id: naming-conventions title: Naming Conventions type: table columns: [Element, Frontend, Backend, Example] rows: - - ['Components', 'PascalCase', '-', '`UserProfile.tsx`'] - - ['Hooks', "camelCase with 'use'", '-', '`useAuth.ts`'] - - ['API Routes', '-', 'kebab-case', '`/api/user-profile`'] - - ['Database Tables', '-', 'snake_case', '`user_profiles`'] + - ["Components", "PascalCase", "-", "`UserProfile.tsx`"] + - ["Hooks", "camelCase with 'use'", "-", "`useAuth.ts`"] + - ["API Routes", "-", "kebab-case", "`/api/user-profile`"] + - ["Database Tables", "-", "snake_case", "`user_profiles`"] - id: error-handling title: Error Handling Strategy @@ -5481,7 +5481,7 @@ sections: title: Error Flow type: mermaid mermaid_type: sequence - template: '{{error_flow_diagram}}' + template: "{{error_flow_diagram}}" - id: error-format title: Error Response Format type: code @@ -5500,12 +5500,12 @@ sections: title: Frontend Error Handling type: code language: typescript - template: '{{frontend_error_handler}}' + template: "{{frontend_error_handler}}" - id: backend-error-handling title: Backend Error Handling type: code language: typescript - template: '{{backend_error_handler}}' + template: "{{backend_error_handler}}" - id: monitoring title: Monitoring and Observability @@ -5547,7 +5547,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Brownfield Enhancement Architecture' + title: "{{project_name}} Brownfield Enhancement Architecture" workflow: mode: interactive @@ -5605,11 +5605,11 @@ sections: - id: available-docs title: Available Documentation type: bullet-list - template: '- {{existing_docs_summary}}' + template: "- {{existing_docs_summary}}" - id: constraints title: Identified Constraints type: bullet-list - template: '- {{constraint}}' + template: "- {{constraint}}" - id: changelog title: Change Log type: table @@ -5689,7 +5689,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} **Integration:** {{integration_with_existing}} @@ -5732,7 +5732,7 @@ sections: repeatable: true sections: - id: component - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} **Integration Points:** {{integration_points}} @@ -5775,7 +5775,7 @@ sections: repeatable: true sections: - id: endpoint - title: '{{endpoint_name}}' + title: "{{endpoint_name}}" template: | - **Method:** {{http_method}} - **Endpoint:** {{endpoint_path}} @@ -5786,12 +5786,12 @@ sections: title: Request type: code language: json - template: '{{request_schema}}' + template: "{{request_schema}}" - id: response title: Response type: code language: json - template: '{{response_schema}}' + template: "{{response_schema}}" - id: external-api-integration title: External API Integration @@ -5800,7 +5800,7 @@ sections: repeatable: true sections: - id: external-api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -5829,7 +5829,7 @@ sections: type: code language: plaintext instruction: Document relevant parts of current structure - template: '{{existing_structure_relevant_parts}}' + template: "{{existing_structure_relevant_parts}}" - id: new-file-organization title: New File Organization type: code @@ -5904,7 +5904,7 @@ sections: title: Enhancement-Specific Standards condition: New patterns needed for enhancement repeatable: true - template: '- **{{standard_name}}:** {{standard_description}}' + template: "- **{{standard_name}}:** {{standard_description}}" - id: integration-rules title: Critical Integration Rules template: | @@ -7281,7 +7281,7 @@ template: output: format: markdown filename: docs/prd.md - title: '{{project_name}} Product Requirements Document (PRD)' + title: "{{project_name}} Product Requirements Document (PRD)" workflow: mode: interactive @@ -7318,14 +7318,14 @@ sections: prefix: FR instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with FR examples: - - 'FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently.' + - "FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently." - id: non-functional title: Non Functional type: numbered-list prefix: NFR instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR examples: - - 'NFR1: AWS service usage must aim to stay within free-tier limits where feasible.' + - "NFR1: AWS service usage must aim to stay within free-tier limits where feasible." - id: ui-goals title: User Interface Design Goals @@ -7351,24 +7351,24 @@ sections: title: Core Screens and Views instruction: 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 examples: - - 'Login Screen' - - 'Main Dashboard' - - 'Item Detail Page' - - 'Settings Page' + - "Login Screen" + - "Main Dashboard" + - "Item Detail Page" + - "Settings Page" - id: accessibility - title: 'Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}' + title: "Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}" - id: branding title: Branding instruction: Any known branding elements or style guides that must be incorporated? examples: - - '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.' + - "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." - id: target-platforms - title: 'Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}' + title: "Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}" examples: - - 'Web Responsive, and all mobile platforms' - - 'iPhone Only' - - 'ASCII Windows Desktop' + - "Web Responsive, and all mobile platforms" + - "iPhone Only" + - "ASCII Windows Desktop" - id: technical-assumptions title: Technical Assumptions @@ -7387,13 +7387,13 @@ sections: testing: [Unit Only, Unit + Integration, Full Testing Pyramid] sections: - id: repository-structure - title: 'Repository Structure: {Monorepo|Polyrepo|Multi-repo}' + title: "Repository Structure: {Monorepo|Polyrepo|Multi-repo}" - id: service-architecture title: Service Architecture - instruction: 'CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).' + instruction: "CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo)." - id: testing-requirements title: Testing Requirements - instruction: 'CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).' + instruction: "CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods)." - id: additional-assumptions title: Additional Technical Assumptions and Requests instruction: 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 @@ -7413,10 +7413,10 @@ sections: - 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. elicit: true examples: - - 'Epic 1: Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management' - - 'Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations' - - 'Epic 3: User Workflows & Interactions: Enable key user journeys and business processes' - - 'Epic 4: Reporting & Analytics: Provide insights and data visualization for users' + - "Epic 1: Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management" + - "Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations" + - "Epic 3: User Workflows & Interactions: Enable key user journeys and business processes" + - "Epic 4: Reporting & Analytics: Provide insights and data visualization for users" - id: epic-details title: Epic {{epic_number}} {{epic_title}} @@ -7438,7 +7438,7 @@ sections: - 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 elicit: true - template: '{{epic_goal}}' + template: "{{epic_goal}}" sections: - id: story title: Story {{epic_number}}.{{story_number}} {{story_title}} @@ -7451,7 +7451,7 @@ sections: - id: acceptance-criteria title: Acceptance Criteria type: numbered-list - item_template: '{{criterion_number}}: {{criteria}}' + item_template: "{{criterion_number}}: {{criteria}}" repeatable: true instruction: | Define clear, comprehensive, and testable acceptance criteria that: @@ -7486,7 +7486,7 @@ template: output: format: markdown filename: docs/prd.md - title: '{{project_name}} Brownfield Enhancement PRD' + title: "{{project_name}} Brownfield Enhancement PRD" workflow: mode: interactive @@ -7549,7 +7549,7 @@ sections: - External API Documentation [[LLM: If from document-project, check ✓]] - UX/UI Guidelines [[LLM: May not be in document-project]] - Technical Debt Documentation [[LLM: If from document-project, check ✓]] - - 'Other: {{other_docs}}' + - "Other: {{other_docs}}" instruction: | - If document-project was already run: "Using existing project analysis from document-project output." - If critical documentation is missing and no document-project: "I recommend running the document-project task first..." @@ -7569,7 +7569,7 @@ sections: - UI/UX Overhaul - Technology Stack Upgrade - Bug Fix and Stability Improvements - - 'Other: {{other_type}}' + - "Other: {{other_type}}" - id: enhancement-description title: Enhancement Description instruction: 2-3 sentences describing what the user wants to add or change @@ -7610,29 +7610,29 @@ sections: prefix: FR instruction: Each Requirement will be a bullet markdown with identifier starting with FR examples: - - 'FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality.' + - "FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality." - id: non-functional title: Non Functional type: numbered-list prefix: NFR instruction: Each Requirement will be a bullet markdown with identifier starting with NFR. Include constraints from existing system examples: - - 'NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%.' + - "NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%." - id: compatibility title: Compatibility Requirements instruction: Critical for brownfield - what must remain compatible type: numbered-list prefix: CR - template: '{{requirement}}: {{description}}' + template: "{{requirement}}: {{description}}" items: - id: cr1 - template: 'CR1: {{existing_api_compatibility}}' + template: "CR1: {{existing_api_compatibility}}" - id: cr2 - template: 'CR2: {{database_schema_compatibility}}' + template: "CR2: {{database_schema_compatibility}}" - id: cr3 - template: 'CR3: {{ui_ux_consistency}}' + template: "CR3: {{ui_ux_consistency}}" - id: cr4 - template: 'CR4: {{integration_compatibility}}' + template: "CR4: {{integration_compatibility}}" - id: ui-enhancement-goals title: User Interface Enhancement Goals @@ -7715,10 +7715,10 @@ sections: - id: epic-approach title: Epic Approach instruction: Explain the rationale for epic structure - typically single epic for brownfield unless multiple unrelated features - template: '**Epic Structure Decision**: {{epic_decision}} with rationale' + template: "**Epic Structure Decision**: {{epic_decision}} with rationale" - id: epic-details - title: 'Epic 1: {{enhancement_title}}' + title: "Epic 1: {{enhancement_title}}" instruction: | Comprehensive epic that delivers the brownfield enhancement while maintaining existing functionality @@ -7738,7 +7738,7 @@ sections: **Integration Requirements**: {{integration_requirements}} sections: - id: story - title: 'Story 1.{{story_number}} {{story_title}}' + title: "Story 1.{{story_number}} {{story_title}}" repeatable: true template: | As a {{user_type}}, @@ -7749,16 +7749,16 @@ sections: title: Acceptance Criteria type: numbered-list instruction: Define criteria that include both new functionality and existing system integrity - item_template: '{{criterion_number}}: {{criteria}}' + item_template: "{{criterion_number}}: {{criteria}}" - id: integration-verification title: Integration Verification instruction: Specific verification steps to ensure existing functionality remains intact type: numbered-list prefix: IV items: - - template: 'IV1: {{existing_functionality_verification}}' - - template: 'IV2: {{integration_point_verification}}' - - template: 'IV3: {{performance_impact_verification}}' + - template: "IV1: {{existing_functionality_verification}}" + - template: "IV2: {{integration_point_verification}}" + - template: "IV3: {{performance_impact_verification}}" ==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ==================== ==================== START: .bmad-core/checklists/pm-checklist.md ==================== @@ -8327,7 +8327,7 @@ template: output: format: markdown filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md - title: 'Story {{epic_num}}.{{story_num}}: {{story_title_short}}' + title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}" workflow: mode: interactive @@ -8429,7 +8429,7 @@ sections: sections: - id: agent-model title: Agent Model Used - template: '{{agent_model_name_version}}' + template: "{{agent_model_name_version}}" instruction: Record the specific AI agent model and version used for development owner: dev-agent editors: [dev-agent] @@ -10527,16 +10527,16 @@ template: output: format: yaml filename: docs/qa/gates/{{epic_num}}.{{story_num}}-{{story_slug}}.yml - title: 'Quality Gate: {{epic_num}}.{{story_num}}' + title: "Quality Gate: {{epic_num}}.{{story_num}}" # Required fields (keep these first) schema: 1 -story: '{{epic_num}}.{{story_num}}' -story_title: '{{story_title}}' -gate: '{{gate_status}}' # PASS|CONCERNS|FAIL|WAIVED -status_reason: '{{status_reason}}' # 1-2 sentence summary of why this gate decision -reviewer: 'Quinn (Test Architect)' -updated: '{{iso_timestamp}}' +story: "{{epic_num}}.{{story_num}}" +story_title: "{{story_title}}" +gate: "{{gate_status}}" # PASS|CONCERNS|FAIL|WAIVED +status_reason: "{{status_reason}}" # 1-2 sentence summary of why this gate decision +reviewer: "Quinn (Test Architect)" +updated: "{{iso_timestamp}}" # Always present but only active when WAIVED waiver: { active: false } @@ -10957,7 +10957,7 @@ template: output: format: markdown filename: docs/front-end-spec.md - title: '{{project_name}} UI/UX Specification' + title: "{{project_name}} UI/UX Specification" workflow: mode: interactive @@ -10985,29 +10985,29 @@ sections: sections: - id: user-personas title: Target User Personas - template: '{{persona_descriptions}}' + template: "{{persona_descriptions}}" examples: - - '**Power User:** Technical professionals who need advanced features and efficiency' - - '**Casual User:** Occasional users who prioritize ease of use and clear guidance' - - '**Administrator:** System managers who need control and oversight capabilities' + - "**Power User:** Technical professionals who need advanced features and efficiency" + - "**Casual User:** Occasional users who prioritize ease of use and clear guidance" + - "**Administrator:** System managers who need control and oversight capabilities" - id: usability-goals title: Usability Goals - template: '{{usability_goals}}' + template: "{{usability_goals}}" examples: - - 'Ease of learning: New users can complete core tasks within 5 minutes' - - 'Efficiency of use: Power users can complete frequent tasks with minimal clicks' - - 'Error prevention: Clear validation and confirmation for destructive actions' - - 'Memorability: Infrequent users can return without relearning' + - "Ease of learning: New users can complete core tasks within 5 minutes" + - "Efficiency of use: Power users can complete frequent tasks with minimal clicks" + - "Error prevention: Clear validation and confirmation for destructive actions" + - "Memorability: Infrequent users can return without relearning" - id: design-principles title: Design Principles - template: '{{design_principles}}' + template: "{{design_principles}}" type: numbered-list examples: - - '**Clarity over cleverness** - Prioritize clear communication over aesthetic innovation' + - "**Clarity over cleverness** - Prioritize clear communication over aesthetic innovation" - "**Progressive disclosure** - Show only what's needed, when it's needed" - - '**Consistent patterns** - Use familiar UI patterns throughout the application' - - '**Immediate feedback** - Every action should have a clear, immediate response' - - '**Accessible by default** - Design for all users from the start' + - "**Consistent patterns** - Use familiar UI patterns throughout the application" + - "**Immediate feedback** - Every action should have a clear, immediate response" + - "**Accessible by default** - Design for all users from the start" - id: changelog title: Change Log type: table @@ -11029,7 +11029,7 @@ sections: title: Site Map / Screen Inventory type: mermaid mermaid_type: graph - template: '{{sitemap_diagram}}' + template: "{{sitemap_diagram}}" examples: - | graph TD @@ -11069,7 +11069,7 @@ sections: repeatable: true sections: - id: flow - title: '{{flow_name}}' + title: "{{flow_name}}" template: | **User Goal:** {{flow_goal}} @@ -11081,13 +11081,13 @@ sections: title: Flow Diagram type: mermaid mermaid_type: graph - template: '{{flow_diagram}}' + template: "{{flow_diagram}}" - id: edge-cases - title: 'Edge Cases & Error Handling:' + title: "Edge Cases & Error Handling:" type: bullet-list - template: '- {{edge_case}}' + template: "- {{edge_case}}" - id: notes - template: '**Notes:** {{flow_notes}}' + template: "**Notes:** {{flow_notes}}" - id: wireframes-mockups title: Wireframes & Mockups @@ -11096,13 +11096,13 @@ sections: elicit: true sections: - id: design-files - template: '**Primary Design Files:** {{design_tool_link}}' + template: "**Primary Design Files:** {{design_tool_link}}" - id: key-screen-layouts title: Key Screen Layouts repeatable: true sections: - id: screen - title: '{{screen_name}}' + title: "{{screen_name}}" template: | **Purpose:** {{screen_purpose}} @@ -11122,13 +11122,13 @@ sections: elicit: true sections: - id: design-system-approach - template: '**Design System Approach:** {{design_system_approach}}' + template: "**Design System Approach:** {{design_system_approach}}" - id: core-components title: Core Components repeatable: true sections: - id: component - title: '{{component_name}}' + title: "{{component_name}}" template: | **Purpose:** {{component_purpose}} @@ -11145,19 +11145,19 @@ sections: sections: - id: visual-identity title: Visual Identity - template: '**Brand Guidelines:** {{brand_guidelines_link}}' + template: "**Brand Guidelines:** {{brand_guidelines_link}}" - id: color-palette title: Color Palette type: table - columns: ['Color Type', 'Hex Code', 'Usage'] + columns: ["Color Type", "Hex Code", "Usage"] rows: - - ['Primary', '{{primary_color}}', '{{primary_usage}}'] - - ['Secondary', '{{secondary_color}}', '{{secondary_usage}}'] - - ['Accent', '{{accent_color}}', '{{accent_usage}}'] - - ['Success', '{{success_color}}', 'Positive feedback, confirmations'] - - ['Warning', '{{warning_color}}', 'Cautions, important notices'] - - ['Error', '{{error_color}}', 'Errors, destructive actions'] - - ['Neutral', '{{neutral_colors}}', 'Text, borders, backgrounds'] + - ["Primary", "{{primary_color}}", "{{primary_usage}}"] + - ["Secondary", "{{secondary_color}}", "{{secondary_usage}}"] + - ["Accent", "{{accent_color}}", "{{accent_usage}}"] + - ["Success", "{{success_color}}", "Positive feedback, confirmations"] + - ["Warning", "{{warning_color}}", "Cautions, important notices"] + - ["Error", "{{error_color}}", "Errors, destructive actions"] + - ["Neutral", "{{neutral_colors}}", "Text, borders, backgrounds"] - id: typography title: Typography sections: @@ -11170,13 +11170,13 @@ sections: - id: type-scale title: Type Scale type: table - columns: ['Element', 'Size', 'Weight', 'Line Height'] + columns: ["Element", "Size", "Weight", "Line Height"] rows: - - ['H1', '{{h1_size}}', '{{h1_weight}}', '{{h1_line}}'] - - ['H2', '{{h2_size}}', '{{h2_weight}}', '{{h2_line}}'] - - ['H3', '{{h3_size}}', '{{h3_weight}}', '{{h3_line}}'] - - ['Body', '{{body_size}}', '{{body_weight}}', '{{body_line}}'] - - ['Small', '{{small_size}}', '{{small_weight}}', '{{small_line}}'] + - ["H1", "{{h1_size}}", "{{h1_weight}}", "{{h1_line}}"] + - ["H2", "{{h2_size}}", "{{h2_weight}}", "{{h2_line}}"] + - ["H3", "{{h3_size}}", "{{h3_weight}}", "{{h3_line}}"] + - ["Body", "{{body_size}}", "{{body_weight}}", "{{body_line}}"] + - ["Small", "{{small_size}}", "{{small_weight}}", "{{small_line}}"] - id: iconography title: Iconography template: | @@ -11197,7 +11197,7 @@ sections: sections: - id: compliance-target title: Compliance Target - template: '**Standard:** {{compliance_standard}}' + template: "**Standard:** {{compliance_standard}}" - id: key-requirements title: Key Requirements template: | @@ -11217,7 +11217,7 @@ sections: - Form labels: {{form_requirements}} - id: testing-strategy title: Testing Strategy - template: '{{accessibility_testing}}' + template: "{{accessibility_testing}}" - id: responsiveness title: Responsiveness Strategy @@ -11227,12 +11227,12 @@ sections: - id: breakpoints title: Breakpoints type: table - columns: ['Breakpoint', 'Min Width', 'Max Width', 'Target Devices'] + columns: ["Breakpoint", "Min Width", "Max Width", "Target Devices"] rows: - - ['Mobile', '{{mobile_min}}', '{{mobile_max}}', '{{mobile_devices}}'] - - ['Tablet', '{{tablet_min}}', '{{tablet_max}}', '{{tablet_devices}}'] - - ['Desktop', '{{desktop_min}}', '{{desktop_max}}', '{{desktop_devices}}'] - - ['Wide', '{{wide_min}}', '-', '{{wide_devices}}'] + - ["Mobile", "{{mobile_min}}", "{{mobile_max}}", "{{mobile_devices}}"] + - ["Tablet", "{{tablet_min}}", "{{tablet_max}}", "{{tablet_devices}}"] + - ["Desktop", "{{desktop_min}}", "{{desktop_max}}", "{{desktop_devices}}"] + - ["Wide", "{{wide_min}}", "-", "{{wide_devices}}"] - id: adaptation-patterns title: Adaptation Patterns template: | @@ -11251,11 +11251,11 @@ sections: sections: - id: motion-principles title: Motion Principles - template: '{{motion_principles}}' + template: "{{motion_principles}}" - id: key-animations title: Key Animations repeatable: true - template: '- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})' + template: "- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})" - id: performance title: Performance Considerations @@ -11269,7 +11269,7 @@ sections: - **Animation FPS:** {{animation_goal}} - id: design-strategies title: Design Strategies - template: '{{performance_strategies}}' + template: "{{performance_strategies}}" - id: next-steps title: Next Steps @@ -11284,17 +11284,17 @@ sections: - id: immediate-actions title: Immediate Actions type: numbered-list - template: '{{action}}' + template: "{{action}}" - id: design-handoff-checklist title: Design Handoff Checklist type: checklist items: - - 'All user flows documented' - - 'Component inventory complete' - - 'Accessibility requirements defined' - - 'Responsive strategy clear' - - 'Brand guidelines incorporated' - - 'Performance goals established' + - "All user flows documented" + - "Component inventory complete" + - "Accessibility requirements defined" + - "Responsive strategy clear" + - "Brand guidelines incorporated" + - "Performance goals established" - id: checklist-results title: Checklist Results @@ -11333,14 +11333,14 @@ workflow: single_story: agent: pm uses: brownfield-create-story - notes: 'Create single story for immediate implementation. Exit workflow after story creation.' + notes: "Create single story for immediate implementation. Exit workflow after story creation." small_feature: agent: pm uses: brownfield-create-epic - notes: 'Create focused epic with 1-3 stories. Exit workflow after epic creation.' + notes: "Create focused epic with 1-3 stories. Exit workflow after epic creation." major_enhancement: continue: to_next_step - notes: 'Continue with comprehensive planning workflow below.' + notes: "Continue with comprehensive planning workflow below." - step: documentation_check agent: analyst @@ -11358,7 +11358,7 @@ workflow: action: analyze existing project and use task document-project creates: brownfield-architecture.md (or multiple documents) condition: documentation_inadequate - notes: 'Run document-project to capture current system state, technical debt, and constraints. Pass findings to PRD creation.' + notes: "Run document-project to capture current system state, technical debt, and constraints. Pass findings to PRD creation." - agent: pm creates: prd.md @@ -11390,12 +11390,12 @@ workflow: - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for integration safety and completeness. May require updates to any document.' + notes: "Validates all documents for integration safety and completeness. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - agent: po action: shard_documents @@ -11586,7 +11586,7 @@ workflow: {{if yes}}: Proceeding to create architecture document for: {{specific_changes}} {{if no}}: No architectural changes needed. Proceeding to validation. - architect_to_po: 'Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for integration safety.' + architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for integration safety." po_to_sm: | All artifacts validated. @@ -11598,7 +11598,7 @@ workflow: Creating story from {{documentation_type}}. {{if missing_context}}: May need to gather additional context from user during story creation. - complete: 'All planning artifacts validated and development can begin. Stories will be created based on available documentation format.' + complete: "All planning artifacts validated and development can begin. Stories will be created based on available documentation format." ==================== END: .bmad-core/workflows/brownfield-fullstack.yaml ==================== ==================== START: .bmad-core/workflows/brownfield-service.yaml ==================== @@ -11621,7 +11621,7 @@ workflow: agent: architect action: analyze existing project and use task document-project creates: multiple documents per the document-project template - notes: 'Review existing service documentation, codebase, performance metrics, and identify integration dependencies.' + notes: "Review existing service documentation, codebase, performance metrics, and identify integration dependencies." - agent: pm creates: prd.md @@ -11638,12 +11638,12 @@ workflow: - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for service integration safety and API compatibility. May require updates to any document.' + notes: "Validates all documents for service integration safety and API compatibility. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - agent: po action: shard_documents @@ -11784,11 +11784,11 @@ workflow: - Multiple integration points affected handoff_prompts: - analyst_to_pm: 'Service analysis complete. Create comprehensive PRD with service integration strategy.' - pm_to_architect: 'PRD ready. Save it as docs/prd.md, then create the service architecture.' - architect_to_po: 'Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for service integration safety.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "Service analysis complete. Create comprehensive PRD with service integration strategy." + pm_to_architect: "PRD ready. Save it as docs/prd.md, then create the service architecture." + architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for service integration safety." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/brownfield-service.yaml ==================== ==================== START: .bmad-core/workflows/brownfield-ui.yaml ==================== @@ -11810,7 +11810,7 @@ workflow: agent: architect action: analyze existing project and use task document-project creates: multiple documents per the document-project template - notes: 'Review existing frontend application, user feedback, analytics data, and identify improvement areas.' + notes: "Review existing frontend application, user feedback, analytics data, and identify improvement areas." - agent: pm creates: prd.md @@ -11835,12 +11835,12 @@ workflow: - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for UI integration safety and design consistency. May require updates to any document.' + notes: "Validates all documents for UI integration safety and design consistency. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - agent: po action: shard_documents @@ -11983,12 +11983,12 @@ workflow: - Multiple team members will work on related changes handoff_prompts: - analyst_to_pm: 'UI analysis complete. Create comprehensive PRD with UI integration strategy.' - pm_to_ux: 'PRD ready. Save it as docs/prd.md, then create the UI/UX specification.' - ux_to_architect: 'UI/UX spec complete. Save it as docs/front-end-spec.md, then create the frontend architecture.' - architect_to_po: 'Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for UI integration safety.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "UI analysis complete. Create comprehensive PRD with UI integration strategy." + pm_to_ux: "PRD ready. Save it as docs/prd.md, then create the UI/UX specification." + ux_to_architect: "UI/UX spec complete. Save it as docs/front-end-spec.md, then create the frontend architecture." + architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for UI integration safety." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/brownfield-ui.yaml ==================== ==================== START: .bmad-core/workflows/greenfield-fullstack.yaml ==================== @@ -12030,7 +12030,7 @@ workflow: creates: v0_prompt (optional) requires: front-end-spec.md condition: user_wants_ai_generation - notes: 'OPTIONAL BUT RECOMMENDED: Generate AI UI prompt for tools like v0, Lovable, etc. Use the generate-ai-frontend-prompt task. User can then generate UI in external tool and download project structure.' + notes: "OPTIONAL BUT RECOMMENDED: Generate AI UI prompt for tools like v0, Lovable, etc. Use the generate-ai-frontend-prompt task. User can then generate UI in external tool and download project structure." - agent: architect creates: fullstack-architecture.md @@ -12046,26 +12046,26 @@ workflow: updates: prd.md (if needed) requires: fullstack-architecture.md condition: architecture_suggests_prd_changes - notes: 'If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder.' + notes: "If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder." - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for consistency and completeness. May require updates to any document.' + notes: "Validates all documents for consistency and completeness. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - project_setup_guidance: action: guide_project_structure condition: user_has_generated_ui - notes: 'If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo alongside backend repo. For monorepo, place in apps/web or packages/frontend directory. Review architecture document for specific guidance.' + notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo alongside backend repo. For monorepo, place in apps/web or packages/frontend directory. Review architecture document for specific guidance." - development_order_guidance: action: guide_development_sequence - notes: 'Based on PRD stories: If stories are frontend-heavy, start with frontend project/directory first. If backend-heavy or API-first, start with backend. For tightly coupled features, follow story sequence in monorepo setup. Reference sharded PRD epics for development order.' + notes: "Based on PRD stories: If stories are frontend-heavy, start with frontend project/directory first. If backend-heavy or API-first, start with backend. For tightly coupled features, follow story sequence in monorepo setup. Reference sharded PRD epics for development order." - agent: po action: shard_documents @@ -12224,14 +12224,14 @@ workflow: - Enterprise or customer-facing applications handoff_prompts: - analyst_to_pm: 'Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD.' - pm_to_ux: 'PRD is ready. Save it as docs/prd.md in your project, then create the UI/UX specification.' - ux_to_architect: 'UI/UX spec complete. Save it as docs/front-end-spec.md in your project, then create the fullstack architecture.' - architect_review: 'Architecture complete. Save it as docs/fullstack-architecture.md. Do you suggest any changes to the PRD stories or need new stories added?' - architect_to_pm: 'Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/.' - updated_to_po: 'All documents ready in docs/ folder. Please validate all artifacts for consistency.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD." + pm_to_ux: "PRD is ready. Save it as docs/prd.md in your project, then create the UI/UX specification." + ux_to_architect: "UI/UX spec complete. Save it as docs/front-end-spec.md in your project, then create the fullstack architecture." + architect_review: "Architecture complete. Save it as docs/fullstack-architecture.md. Do you suggest any changes to the PRD stories or need new stories added?" + architect_to_pm: "Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/." + updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/greenfield-fullstack.yaml ==================== ==================== START: .bmad-core/workflows/greenfield-service.yaml ==================== @@ -12274,17 +12274,17 @@ workflow: updates: prd.md (if needed) requires: architecture.md condition: architecture_suggests_prd_changes - notes: 'If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder.' + notes: "If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder." - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for consistency and completeness. May require updates to any document.' + notes: "Validates all documents for consistency and completeness. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - agent: po action: shard_documents @@ -12434,13 +12434,13 @@ workflow: - Enterprise or external-facing APIs handoff_prompts: - analyst_to_pm: 'Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD.' - pm_to_architect: 'PRD is ready. Save it as docs/prd.md in your project, then create the service architecture.' - architect_review: 'Architecture complete. Save it as docs/architecture.md. Do you suggest any changes to the PRD stories or need new stories added?' - architect_to_pm: 'Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/.' - updated_to_po: 'All documents ready in docs/ folder. Please validate all artifacts for consistency.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD." + pm_to_architect: "PRD is ready. Save it as docs/prd.md in your project, then create the service architecture." + architect_review: "Architecture complete. Save it as docs/architecture.md. Do you suggest any changes to the PRD stories or need new stories added?" + architect_to_pm: "Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/." + updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/greenfield-service.yaml ==================== ==================== START: .bmad-core/workflows/greenfield-ui.yaml ==================== @@ -12483,7 +12483,7 @@ workflow: creates: v0_prompt (optional) requires: front-end-spec.md condition: user_wants_ai_generation - notes: 'OPTIONAL BUT RECOMMENDED: Generate AI UI prompt for tools like v0, Lovable, etc. Use the generate-ai-frontend-prompt task. User can then generate UI in external tool and download project structure.' + notes: "OPTIONAL BUT RECOMMENDED: Generate AI UI prompt for tools like v0, Lovable, etc. Use the generate-ai-frontend-prompt task. User can then generate UI in external tool and download project structure." - agent: architect creates: front-end-architecture.md @@ -12497,22 +12497,22 @@ workflow: updates: prd.md (if needed) requires: front-end-architecture.md condition: architecture_suggests_prd_changes - notes: 'If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder.' + notes: "If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder." - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for consistency and completeness. May require updates to any document.' + notes: "Validates all documents for consistency and completeness. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - project_setup_guidance: action: guide_project_structure condition: user_has_generated_ui - notes: 'If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance.' + notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance." - agent: po action: shard_documents @@ -12671,12 +12671,12 @@ workflow: - Customer-facing applications handoff_prompts: - analyst_to_pm: 'Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD.' - pm_to_ux: 'PRD is ready. Save it as docs/prd.md in your project, then create the UI/UX specification.' - ux_to_architect: 'UI/UX spec complete. Save it as docs/front-end-spec.md in your project, then create the frontend architecture.' - architect_review: 'Frontend architecture complete. Save it as docs/front-end-architecture.md. Do you suggest any changes to the PRD stories or need new stories added?' - architect_to_pm: 'Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/.' - updated_to_po: 'All documents ready in docs/ folder. Please validate all artifacts for consistency.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD." + pm_to_ux: "PRD is ready. Save it as docs/prd.md in your project, then create the UI/UX specification." + ux_to_architect: "UI/UX spec complete. Save it as docs/front-end-spec.md in your project, then create the frontend architecture." + architect_review: "Frontend architecture complete. Save it as docs/front-end-architecture.md. Do you suggest any changes to the PRD stories or need new stories added?" + architect_to_pm: "Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/." + updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/greenfield-ui.yaml ==================== diff --git a/dist/teams/team-fullstack.txt b/dist/teams/team-fullstack.txt index b3358831..fef15db1 100644 --- a/dist/teams/team-fullstack.txt +++ b/dist/teams/team-fullstack.txt @@ -2609,24 +2609,24 @@ template: output: format: markdown filename: docs/brief.md - title: 'Project Brief: {{project_name}}' + title: "Project Brief: {{project_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Project Brief Elicitation Actions' + title: "Project Brief Elicitation Actions" options: - - 'Expand section with more specific details' - - 'Validate against similar successful products' - - 'Stress test assumptions with edge cases' - - 'Explore alternative solution approaches' - - 'Analyze resource/constraint trade-offs' - - 'Generate risk mitigation strategies' - - 'Challenge scope from MVP minimalist view' - - 'Brainstorm creative feature possibilities' - - 'If only we had [resource/capability/time]...' - - 'Proceed to next section' + - "Expand section with more specific details" + - "Validate against similar successful products" + - "Stress test assumptions with edge cases" + - "Explore alternative solution approaches" + - "Analyze resource/constraint trade-offs" + - "Generate risk mitigation strategies" + - "Challenge scope from MVP minimalist view" + - "Brainstorm creative feature possibilities" + - "If only we had [resource/capability/time]..." + - "Proceed to next section" sections: - id: introduction @@ -2648,7 +2648,7 @@ sections: - Primary problem being solved - Target market identification - Key value proposition - template: '{{executive_summary_content}}' + template: "{{executive_summary_content}}" - id: problem-statement title: Problem Statement @@ -2658,7 +2658,7 @@ sections: - Impact of the problem (quantify if possible) - Why existing solutions fall short - Urgency and importance of solving this now - template: '{{detailed_problem_description}}' + template: "{{detailed_problem_description}}" - id: proposed-solution title: Proposed Solution @@ -2668,7 +2668,7 @@ sections: - Key differentiators from existing solutions - Why this solution will succeed where others haven't - High-level vision for the product - template: '{{solution_description}}' + template: "{{solution_description}}" - id: target-users title: Target Users @@ -2680,12 +2680,12 @@ sections: - Goals they're trying to achieve sections: - id: primary-segment - title: 'Primary User Segment: {{segment_name}}' - template: '{{primary_user_description}}' + title: "Primary User Segment: {{segment_name}}" + template: "{{primary_user_description}}" - id: secondary-segment - title: 'Secondary User Segment: {{segment_name}}' + title: "Secondary User Segment: {{segment_name}}" condition: Has secondary user segment - template: '{{secondary_user_description}}' + template: "{{secondary_user_description}}" - id: goals-metrics title: Goals & Success Metrics @@ -2694,15 +2694,15 @@ sections: - id: business-objectives title: Business Objectives type: bullet-list - template: '- {{objective_with_metric}}' + template: "- {{objective_with_metric}}" - id: user-success-metrics title: User Success Metrics type: bullet-list - template: '- {{user_metric}}' + template: "- {{user_metric}}" - id: kpis title: Key Performance Indicators (KPIs) type: bullet-list - template: '- {{kpi}}: {{definition_and_target}}' + template: "- {{kpi}}: {{definition_and_target}}" - id: mvp-scope title: MVP Scope @@ -2711,14 +2711,14 @@ sections: - id: core-features title: Core Features (Must Have) type: bullet-list - template: '- **{{feature}}:** {{description_and_rationale}}' + template: "- **{{feature}}:** {{description_and_rationale}}" - id: out-of-scope title: Out of Scope for MVP type: bullet-list - template: '- {{feature_or_capability}}' + template: "- {{feature_or_capability}}" - id: mvp-success-criteria title: MVP Success Criteria - template: '{{mvp_success_definition}}' + template: "{{mvp_success_definition}}" - id: post-mvp-vision title: Post-MVP Vision @@ -2726,13 +2726,13 @@ sections: sections: - id: phase-2-features title: Phase 2 Features - template: '{{next_priority_features}}' + template: "{{next_priority_features}}" - id: long-term-vision title: Long-term Vision - template: '{{one_two_year_vision}}' + template: "{{one_two_year_vision}}" - id: expansion-opportunities title: Expansion Opportunities - template: '{{potential_expansions}}' + template: "{{potential_expansions}}" - id: technical-considerations title: Technical Considerations @@ -2773,7 +2773,7 @@ sections: - id: key-assumptions title: Key Assumptions type: bullet-list - template: '- {{assumption}}' + template: "- {{assumption}}" - id: risks-questions title: Risks & Open Questions @@ -2782,15 +2782,15 @@ sections: - id: key-risks title: Key Risks type: bullet-list - template: '- **{{risk}}:** {{description_and_impact}}' + template: "- **{{risk}}:** {{description_and_impact}}" - id: open-questions title: Open Questions type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: research-areas title: Areas Needing Further Research type: bullet-list - template: '- {{research_topic}}' + template: "- {{research_topic}}" - id: appendices title: Appendices @@ -2807,10 +2807,10 @@ sections: - id: stakeholder-input title: B. Stakeholder Input condition: Has stakeholder feedback - template: '{{stakeholder_feedback}}' + template: "{{stakeholder_feedback}}" - id: references title: C. References - template: '{{relevant_links_and_docs}}' + template: "{{relevant_links_and_docs}}" - id: next-steps title: Next Steps @@ -2818,7 +2818,7 @@ sections: - id: immediate-actions title: Immediate Actions type: numbered-list - template: '{{action_item}}' + template: "{{action_item}}" - id: pm-handoff title: PM Handoff content: | @@ -2833,24 +2833,24 @@ template: output: format: markdown filename: docs/market-research.md - title: 'Market Research Report: {{project_product_name}}' + title: "Market Research Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Market Research Elicitation Actions' + title: "Market Research Elicitation Actions" options: - - 'Expand market sizing calculations with sensitivity analysis' - - 'Deep dive into a specific customer segment' - - 'Analyze an emerging market trend in detail' - - 'Compare this market to an analogous market' - - 'Stress test market assumptions' - - 'Explore adjacent market opportunities' - - 'Challenge market definition and boundaries' - - 'Generate strategic scenarios (best/base/worst case)' - - 'If only we had considered [X market factor]...' - - 'Proceed to next section' + - "Expand market sizing calculations with sensitivity analysis" + - "Deep dive into a specific customer segment" + - "Analyze an emerging market trend in detail" + - "Compare this market to an analogous market" + - "Stress test market assumptions" + - "Explore adjacent market opportunities" + - "Challenge market definition and boundaries" + - "Generate strategic scenarios (best/base/worst case)" + - "If only we had considered [X market factor]..." + - "Proceed to next section" sections: - id: executive-summary @@ -2932,7 +2932,7 @@ sections: repeatable: true sections: - id: segment - title: 'Segment {{segment_number}}: {{segment_name}}' + title: "Segment {{segment_number}}: {{segment_name}}" template: | - **Description:** {{brief_overview}} - **Size:** {{number_of_customers_market_value}} @@ -3001,20 +3001,20 @@ sections: instruction: Analyze each force with specific evidence and implications sections: - id: supplier-power - title: 'Supplier Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Supplier Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: buyer-power - title: 'Buyer Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Buyer Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: competitive-rivalry - title: 'Competitive Rivalry: {{intensity_level}}' - template: '{{analysis_and_implications}}' + title: "Competitive Rivalry: {{intensity_level}}" + template: "{{analysis_and_implications}}" - id: threat-new-entry - title: 'Threat of New Entry: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of New Entry: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: threat-substitutes - title: 'Threat of Substitutes: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of Substitutes: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: adoption-lifecycle title: Technology Adoption Lifecycle Stage instruction: | @@ -3032,7 +3032,7 @@ sections: repeatable: true sections: - id: opportunity - title: 'Opportunity {{opportunity_number}}: {{name}}' + title: "Opportunity {{opportunity_number}}: {{name}}" template: | - **Description:** {{what_is_the_opportunity}} - **Size/Potential:** {{quantified_potential}} @@ -3088,24 +3088,24 @@ template: output: format: markdown filename: docs/competitor-analysis.md - title: 'Competitive Analysis Report: {{project_product_name}}' + title: "Competitive Analysis Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Competitive Analysis Elicitation Actions' + title: "Competitive Analysis Elicitation Actions" options: - "Deep dive on a specific competitor's strategy" - - 'Analyze competitive dynamics in a specific segment' - - 'War game competitive responses to your moves' - - 'Explore partnership vs. competition scenarios' - - 'Stress test differentiation claims' - - 'Analyze disruption potential (yours or theirs)' - - 'Compare to competition in adjacent markets' - - 'Generate win/loss analysis insights' + - "Analyze competitive dynamics in a specific segment" + - "War game competitive responses to your moves" + - "Explore partnership vs. competition scenarios" + - "Stress test differentiation claims" + - "Analyze disruption potential (yours or theirs)" + - "Compare to competition in adjacent markets" + - "Generate win/loss analysis insights" - "If only we had known about [competitor X's plan]..." - - 'Proceed to next section' + - "Proceed to next section" sections: - id: executive-summary @@ -3172,7 +3172,7 @@ sections: repeatable: true sections: - id: competitor - title: '{{competitor_name}} - Priority {{priority_level}}' + title: "{{competitor_name}} - Priority {{priority_level}}" sections: - id: company-overview title: Company Overview @@ -3204,11 +3204,11 @@ sections: - id: strengths title: Strengths type: bullet-list - template: '- {{strength}}' + template: "- {{strength}}" - id: weaknesses title: Weaknesses type: bullet-list - template: '- {{weakness}}' + template: "- {{weakness}}" - id: market-position title: Market Position & Performance template: | @@ -3226,35 +3226,35 @@ sections: type: table columns: [ - 'Feature Category', - '{{your_company}}', - '{{competitor_1}}', - '{{competitor_2}}', - '{{competitor_3}}', + "Feature Category", + "{{your_company}}", + "{{competitor_1}}", + "{{competitor_2}}", + "{{competitor_3}}", ] rows: - - category: 'Core Functionality' + - category: "Core Functionality" items: - - ['Feature A', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - ['Feature B', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - category: 'User Experience' + - ["Feature A", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - ["Feature B", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - category: "User Experience" items: - - ['Mobile App', '{{rating}}', '{{rating}}', '{{rating}}', '{{rating}}'] - - ['Onboarding Time', '{{time}}', '{{time}}', '{{time}}', '{{time}}'] - - category: 'Integration & Ecosystem' + - ["Mobile App", "{{rating}}", "{{rating}}", "{{rating}}", "{{rating}}"] + - ["Onboarding Time", "{{time}}", "{{time}}", "{{time}}", "{{time}}"] + - category: "Integration & Ecosystem" items: - [ - 'API Availability', - '{{availability}}', - '{{availability}}', - '{{availability}}', - '{{availability}}', + "API Availability", + "{{availability}}", + "{{availability}}", + "{{availability}}", + "{{availability}}", ] - - ['Third-party Integrations', '{{number}}', '{{number}}', '{{number}}', '{{number}}'] - - category: 'Pricing & Plans' + - ["Third-party Integrations", "{{number}}", "{{number}}", "{{number}}", "{{number}}"] + - category: "Pricing & Plans" items: - - ['Starting Price', '{{price}}', '{{price}}', '{{price}}', '{{price}}'] - - ['Free Tier', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}'] + - ["Starting Price", "{{price}}", "{{price}}", "{{price}}", "{{price}}"] + - ["Free Tier", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}"] - id: swot-comparison title: SWOT Comparison instruction: Create SWOT analysis for your solution vs. top competitors @@ -3267,7 +3267,7 @@ sections: - **Opportunities:** {{opportunities}} - **Threats:** {{threats}} - id: vs-competitor - title: 'vs. {{main_competitor}}' + title: "vs. {{main_competitor}}" template: | - **Competitive Advantages:** {{your_advantages}} - **Competitive Disadvantages:** {{their_advantages}} @@ -3397,7 +3397,7 @@ template: output: format: markdown filename: docs/brainstorming-session-results.md - title: 'Brainstorming Session Results' + title: "Brainstorming Session Results" workflow: mode: non-interactive @@ -3422,38 +3422,38 @@ sections: **Total Ideas Generated:** {{total_ideas}} - id: key-themes - title: 'Key Themes Identified:' + title: "Key Themes Identified:" type: bullet-list - template: '- {{theme}}' + template: "- {{theme}}" - id: technique-sessions title: Technique Sessions repeatable: true sections: - id: technique - title: '{{technique_name}} - {{duration}}' + title: "{{technique_name}} - {{duration}}" sections: - id: description - template: '**Description:** {{technique_description}}' + template: "**Description:** {{technique_description}}" - id: ideas-generated - title: 'Ideas Generated:' + title: "Ideas Generated:" type: numbered-list - template: '{{idea}}' + template: "{{idea}}" - id: insights - title: 'Insights Discovered:' + title: "Insights Discovered:" type: bullet-list - template: '- {{insight}}' + template: "- {{insight}}" - id: connections - title: 'Notable Connections:' + title: "Notable Connections:" type: bullet-list - template: '- {{connection}}' + template: "- {{connection}}" - id: idea-categorization title: Idea Categorization sections: - id: immediate-opportunities title: Immediate Opportunities - content: '*Ideas ready to implement now*' + content: "*Ideas ready to implement now*" repeatable: true type: numbered-list template: | @@ -3463,7 +3463,7 @@ sections: - Resources needed: {{requirements}} - id: future-innovations title: Future Innovations - content: '*Ideas requiring development/research*' + content: "*Ideas requiring development/research*" repeatable: true type: numbered-list template: | @@ -3473,7 +3473,7 @@ sections: - Timeline estimate: {{timeline}} - id: moonshots title: Moonshots - content: '*Ambitious, transformative concepts*' + content: "*Ambitious, transformative concepts*" repeatable: true type: numbered-list template: | @@ -3483,9 +3483,9 @@ sections: - Challenges to overcome: {{challenges}} - id: insights-learnings title: Insights & Learnings - content: '*Key realizations from the session*' + content: "*Key realizations from the session*" type: bullet-list - template: '- {{insight}}: {{description_and_implications}}' + template: "- {{insight}}: {{description_and_implications}}" - id: action-planning title: Action Planning @@ -3494,21 +3494,21 @@ sections: title: Top 3 Priority Ideas sections: - id: priority-1 - title: '#1 Priority: {{idea_name}}' + title: "#1 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-2 - title: '#2 Priority: {{idea_name}}' + title: "#2 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-3 - title: '#3 Priority: {{idea_name}}' + title: "#3 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} @@ -3521,19 +3521,19 @@ sections: - id: what-worked title: What Worked Well type: bullet-list - template: '- {{aspect}}' + template: "- {{aspect}}" - id: areas-exploration title: Areas for Further Exploration type: bullet-list - template: '- {{area}}: {{reason}}' + template: "- {{area}}: {{reason}}" - id: recommended-techniques title: Recommended Follow-up Techniques type: bullet-list - template: '- {{technique}}: {{reason}}' + template: "- {{technique}}: {{reason}}" - id: questions-emerged title: Questions That Emerged type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: next-session title: Next Session Planning template: | @@ -4258,7 +4258,7 @@ template: output: format: markdown filename: docs/prd.md - title: '{{project_name}} Product Requirements Document (PRD)' + title: "{{project_name}} Product Requirements Document (PRD)" workflow: mode: interactive @@ -4295,14 +4295,14 @@ sections: prefix: FR instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with FR examples: - - 'FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently.' + - "FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently." - id: non-functional title: Non Functional type: numbered-list prefix: NFR instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR examples: - - 'NFR1: AWS service usage must aim to stay within free-tier limits where feasible.' + - "NFR1: AWS service usage must aim to stay within free-tier limits where feasible." - id: ui-goals title: User Interface Design Goals @@ -4328,24 +4328,24 @@ sections: title: Core Screens and Views instruction: 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 examples: - - 'Login Screen' - - 'Main Dashboard' - - 'Item Detail Page' - - 'Settings Page' + - "Login Screen" + - "Main Dashboard" + - "Item Detail Page" + - "Settings Page" - id: accessibility - title: 'Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}' + title: "Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}" - id: branding title: Branding instruction: Any known branding elements or style guides that must be incorporated? examples: - - '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.' + - "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." - id: target-platforms - title: 'Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}' + title: "Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}" examples: - - 'Web Responsive, and all mobile platforms' - - 'iPhone Only' - - 'ASCII Windows Desktop' + - "Web Responsive, and all mobile platforms" + - "iPhone Only" + - "ASCII Windows Desktop" - id: technical-assumptions title: Technical Assumptions @@ -4364,13 +4364,13 @@ sections: testing: [Unit Only, Unit + Integration, Full Testing Pyramid] sections: - id: repository-structure - title: 'Repository Structure: {Monorepo|Polyrepo|Multi-repo}' + title: "Repository Structure: {Monorepo|Polyrepo|Multi-repo}" - id: service-architecture title: Service Architecture - instruction: 'CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).' + instruction: "CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo)." - id: testing-requirements title: Testing Requirements - instruction: 'CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).' + instruction: "CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods)." - id: additional-assumptions title: Additional Technical Assumptions and Requests instruction: 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 @@ -4390,10 +4390,10 @@ sections: - 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. elicit: true examples: - - 'Epic 1: Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management' - - 'Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations' - - 'Epic 3: User Workflows & Interactions: Enable key user journeys and business processes' - - 'Epic 4: Reporting & Analytics: Provide insights and data visualization for users' + - "Epic 1: Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management" + - "Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations" + - "Epic 3: User Workflows & Interactions: Enable key user journeys and business processes" + - "Epic 4: Reporting & Analytics: Provide insights and data visualization for users" - id: epic-details title: Epic {{epic_number}} {{epic_title}} @@ -4415,7 +4415,7 @@ sections: - 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 elicit: true - template: '{{epic_goal}}' + template: "{{epic_goal}}" sections: - id: story title: Story {{epic_number}}.{{story_number}} {{story_title}} @@ -4428,7 +4428,7 @@ sections: - id: acceptance-criteria title: Acceptance Criteria type: numbered-list - item_template: '{{criterion_number}}: {{criteria}}' + item_template: "{{criterion_number}}: {{criteria}}" repeatable: true instruction: | Define clear, comprehensive, and testable acceptance criteria that: @@ -4463,7 +4463,7 @@ template: output: format: markdown filename: docs/prd.md - title: '{{project_name}} Brownfield Enhancement PRD' + title: "{{project_name}} Brownfield Enhancement PRD" workflow: mode: interactive @@ -4526,7 +4526,7 @@ sections: - External API Documentation [[LLM: If from document-project, check ✓]] - UX/UI Guidelines [[LLM: May not be in document-project]] - Technical Debt Documentation [[LLM: If from document-project, check ✓]] - - 'Other: {{other_docs}}' + - "Other: {{other_docs}}" instruction: | - If document-project was already run: "Using existing project analysis from document-project output." - If critical documentation is missing and no document-project: "I recommend running the document-project task first..." @@ -4546,7 +4546,7 @@ sections: - UI/UX Overhaul - Technology Stack Upgrade - Bug Fix and Stability Improvements - - 'Other: {{other_type}}' + - "Other: {{other_type}}" - id: enhancement-description title: Enhancement Description instruction: 2-3 sentences describing what the user wants to add or change @@ -4587,29 +4587,29 @@ sections: prefix: FR instruction: Each Requirement will be a bullet markdown with identifier starting with FR examples: - - 'FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality.' + - "FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality." - id: non-functional title: Non Functional type: numbered-list prefix: NFR instruction: Each Requirement will be a bullet markdown with identifier starting with NFR. Include constraints from existing system examples: - - 'NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%.' + - "NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%." - id: compatibility title: Compatibility Requirements instruction: Critical for brownfield - what must remain compatible type: numbered-list prefix: CR - template: '{{requirement}}: {{description}}' + template: "{{requirement}}: {{description}}" items: - id: cr1 - template: 'CR1: {{existing_api_compatibility}}' + template: "CR1: {{existing_api_compatibility}}" - id: cr2 - template: 'CR2: {{database_schema_compatibility}}' + template: "CR2: {{database_schema_compatibility}}" - id: cr3 - template: 'CR3: {{ui_ux_consistency}}' + template: "CR3: {{ui_ux_consistency}}" - id: cr4 - template: 'CR4: {{integration_compatibility}}' + template: "CR4: {{integration_compatibility}}" - id: ui-enhancement-goals title: User Interface Enhancement Goals @@ -4692,10 +4692,10 @@ sections: - id: epic-approach title: Epic Approach instruction: Explain the rationale for epic structure - typically single epic for brownfield unless multiple unrelated features - template: '**Epic Structure Decision**: {{epic_decision}} with rationale' + template: "**Epic Structure Decision**: {{epic_decision}} with rationale" - id: epic-details - title: 'Epic 1: {{enhancement_title}}' + title: "Epic 1: {{enhancement_title}}" instruction: | Comprehensive epic that delivers the brownfield enhancement while maintaining existing functionality @@ -4715,7 +4715,7 @@ sections: **Integration Requirements**: {{integration_requirements}} sections: - id: story - title: 'Story 1.{{story_number}} {{story_title}}' + title: "Story 1.{{story_number}} {{story_title}}" repeatable: true template: | As a {{user_type}}, @@ -4726,16 +4726,16 @@ sections: title: Acceptance Criteria type: numbered-list instruction: Define criteria that include both new functionality and existing system integrity - item_template: '{{criterion_number}}: {{criteria}}' + item_template: "{{criterion_number}}: {{criteria}}" - id: integration-verification title: Integration Verification instruction: Specific verification steps to ensure existing functionality remains intact type: numbered-list prefix: IV items: - - template: 'IV1: {{existing_functionality_verification}}' - - template: 'IV2: {{integration_point_verification}}' - - template: 'IV3: {{performance_impact_verification}}' + - template: "IV1: {{existing_functionality_verification}}" + - template: "IV2: {{integration_point_verification}}" + - template: "IV3: {{performance_impact_verification}}" ==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ==================== ==================== START: .bmad-core/checklists/pm-checklist.md ==================== @@ -5364,7 +5364,7 @@ template: output: format: markdown filename: docs/front-end-spec.md - title: '{{project_name}} UI/UX Specification' + title: "{{project_name}} UI/UX Specification" workflow: mode: interactive @@ -5392,29 +5392,29 @@ sections: sections: - id: user-personas title: Target User Personas - template: '{{persona_descriptions}}' + template: "{{persona_descriptions}}" examples: - - '**Power User:** Technical professionals who need advanced features and efficiency' - - '**Casual User:** Occasional users who prioritize ease of use and clear guidance' - - '**Administrator:** System managers who need control and oversight capabilities' + - "**Power User:** Technical professionals who need advanced features and efficiency" + - "**Casual User:** Occasional users who prioritize ease of use and clear guidance" + - "**Administrator:** System managers who need control and oversight capabilities" - id: usability-goals title: Usability Goals - template: '{{usability_goals}}' + template: "{{usability_goals}}" examples: - - 'Ease of learning: New users can complete core tasks within 5 minutes' - - 'Efficiency of use: Power users can complete frequent tasks with minimal clicks' - - 'Error prevention: Clear validation and confirmation for destructive actions' - - 'Memorability: Infrequent users can return without relearning' + - "Ease of learning: New users can complete core tasks within 5 minutes" + - "Efficiency of use: Power users can complete frequent tasks with minimal clicks" + - "Error prevention: Clear validation and confirmation for destructive actions" + - "Memorability: Infrequent users can return without relearning" - id: design-principles title: Design Principles - template: '{{design_principles}}' + template: "{{design_principles}}" type: numbered-list examples: - - '**Clarity over cleverness** - Prioritize clear communication over aesthetic innovation' + - "**Clarity over cleverness** - Prioritize clear communication over aesthetic innovation" - "**Progressive disclosure** - Show only what's needed, when it's needed" - - '**Consistent patterns** - Use familiar UI patterns throughout the application' - - '**Immediate feedback** - Every action should have a clear, immediate response' - - '**Accessible by default** - Design for all users from the start' + - "**Consistent patterns** - Use familiar UI patterns throughout the application" + - "**Immediate feedback** - Every action should have a clear, immediate response" + - "**Accessible by default** - Design for all users from the start" - id: changelog title: Change Log type: table @@ -5436,7 +5436,7 @@ sections: title: Site Map / Screen Inventory type: mermaid mermaid_type: graph - template: '{{sitemap_diagram}}' + template: "{{sitemap_diagram}}" examples: - | graph TD @@ -5476,7 +5476,7 @@ sections: repeatable: true sections: - id: flow - title: '{{flow_name}}' + title: "{{flow_name}}" template: | **User Goal:** {{flow_goal}} @@ -5488,13 +5488,13 @@ sections: title: Flow Diagram type: mermaid mermaid_type: graph - template: '{{flow_diagram}}' + template: "{{flow_diagram}}" - id: edge-cases - title: 'Edge Cases & Error Handling:' + title: "Edge Cases & Error Handling:" type: bullet-list - template: '- {{edge_case}}' + template: "- {{edge_case}}" - id: notes - template: '**Notes:** {{flow_notes}}' + template: "**Notes:** {{flow_notes}}" - id: wireframes-mockups title: Wireframes & Mockups @@ -5503,13 +5503,13 @@ sections: elicit: true sections: - id: design-files - template: '**Primary Design Files:** {{design_tool_link}}' + template: "**Primary Design Files:** {{design_tool_link}}" - id: key-screen-layouts title: Key Screen Layouts repeatable: true sections: - id: screen - title: '{{screen_name}}' + title: "{{screen_name}}" template: | **Purpose:** {{screen_purpose}} @@ -5529,13 +5529,13 @@ sections: elicit: true sections: - id: design-system-approach - template: '**Design System Approach:** {{design_system_approach}}' + template: "**Design System Approach:** {{design_system_approach}}" - id: core-components title: Core Components repeatable: true sections: - id: component - title: '{{component_name}}' + title: "{{component_name}}" template: | **Purpose:** {{component_purpose}} @@ -5552,19 +5552,19 @@ sections: sections: - id: visual-identity title: Visual Identity - template: '**Brand Guidelines:** {{brand_guidelines_link}}' + template: "**Brand Guidelines:** {{brand_guidelines_link}}" - id: color-palette title: Color Palette type: table - columns: ['Color Type', 'Hex Code', 'Usage'] + columns: ["Color Type", "Hex Code", "Usage"] rows: - - ['Primary', '{{primary_color}}', '{{primary_usage}}'] - - ['Secondary', '{{secondary_color}}', '{{secondary_usage}}'] - - ['Accent', '{{accent_color}}', '{{accent_usage}}'] - - ['Success', '{{success_color}}', 'Positive feedback, confirmations'] - - ['Warning', '{{warning_color}}', 'Cautions, important notices'] - - ['Error', '{{error_color}}', 'Errors, destructive actions'] - - ['Neutral', '{{neutral_colors}}', 'Text, borders, backgrounds'] + - ["Primary", "{{primary_color}}", "{{primary_usage}}"] + - ["Secondary", "{{secondary_color}}", "{{secondary_usage}}"] + - ["Accent", "{{accent_color}}", "{{accent_usage}}"] + - ["Success", "{{success_color}}", "Positive feedback, confirmations"] + - ["Warning", "{{warning_color}}", "Cautions, important notices"] + - ["Error", "{{error_color}}", "Errors, destructive actions"] + - ["Neutral", "{{neutral_colors}}", "Text, borders, backgrounds"] - id: typography title: Typography sections: @@ -5577,13 +5577,13 @@ sections: - id: type-scale title: Type Scale type: table - columns: ['Element', 'Size', 'Weight', 'Line Height'] + columns: ["Element", "Size", "Weight", "Line Height"] rows: - - ['H1', '{{h1_size}}', '{{h1_weight}}', '{{h1_line}}'] - - ['H2', '{{h2_size}}', '{{h2_weight}}', '{{h2_line}}'] - - ['H3', '{{h3_size}}', '{{h3_weight}}', '{{h3_line}}'] - - ['Body', '{{body_size}}', '{{body_weight}}', '{{body_line}}'] - - ['Small', '{{small_size}}', '{{small_weight}}', '{{small_line}}'] + - ["H1", "{{h1_size}}", "{{h1_weight}}", "{{h1_line}}"] + - ["H2", "{{h2_size}}", "{{h2_weight}}", "{{h2_line}}"] + - ["H3", "{{h3_size}}", "{{h3_weight}}", "{{h3_line}}"] + - ["Body", "{{body_size}}", "{{body_weight}}", "{{body_line}}"] + - ["Small", "{{small_size}}", "{{small_weight}}", "{{small_line}}"] - id: iconography title: Iconography template: | @@ -5604,7 +5604,7 @@ sections: sections: - id: compliance-target title: Compliance Target - template: '**Standard:** {{compliance_standard}}' + template: "**Standard:** {{compliance_standard}}" - id: key-requirements title: Key Requirements template: | @@ -5624,7 +5624,7 @@ sections: - Form labels: {{form_requirements}} - id: testing-strategy title: Testing Strategy - template: '{{accessibility_testing}}' + template: "{{accessibility_testing}}" - id: responsiveness title: Responsiveness Strategy @@ -5634,12 +5634,12 @@ sections: - id: breakpoints title: Breakpoints type: table - columns: ['Breakpoint', 'Min Width', 'Max Width', 'Target Devices'] + columns: ["Breakpoint", "Min Width", "Max Width", "Target Devices"] rows: - - ['Mobile', '{{mobile_min}}', '{{mobile_max}}', '{{mobile_devices}}'] - - ['Tablet', '{{tablet_min}}', '{{tablet_max}}', '{{tablet_devices}}'] - - ['Desktop', '{{desktop_min}}', '{{desktop_max}}', '{{desktop_devices}}'] - - ['Wide', '{{wide_min}}', '-', '{{wide_devices}}'] + - ["Mobile", "{{mobile_min}}", "{{mobile_max}}", "{{mobile_devices}}"] + - ["Tablet", "{{tablet_min}}", "{{tablet_max}}", "{{tablet_devices}}"] + - ["Desktop", "{{desktop_min}}", "{{desktop_max}}", "{{desktop_devices}}"] + - ["Wide", "{{wide_min}}", "-", "{{wide_devices}}"] - id: adaptation-patterns title: Adaptation Patterns template: | @@ -5658,11 +5658,11 @@ sections: sections: - id: motion-principles title: Motion Principles - template: '{{motion_principles}}' + template: "{{motion_principles}}" - id: key-animations title: Key Animations repeatable: true - template: '- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})' + template: "- **{{animation_name}}:** {{animation_description}} (Duration: {{duration}}, Easing: {{easing}})" - id: performance title: Performance Considerations @@ -5676,7 +5676,7 @@ sections: - **Animation FPS:** {{animation_goal}} - id: design-strategies title: Design Strategies - template: '{{performance_strategies}}' + template: "{{performance_strategies}}" - id: next-steps title: Next Steps @@ -5691,17 +5691,17 @@ sections: - id: immediate-actions title: Immediate Actions type: numbered-list - template: '{{action}}' + template: "{{action}}" - id: design-handoff-checklist title: Design Handoff Checklist type: checklist items: - - 'All user flows documented' - - 'Component inventory complete' - - 'Accessibility requirements defined' - - 'Responsive strategy clear' - - 'Brand guidelines incorporated' - - 'Performance goals established' + - "All user flows documented" + - "Component inventory complete" + - "Accessibility requirements defined" + - "Responsive strategy clear" + - "Brand guidelines incorporated" + - "Performance goals established" - id: checklist-results title: Checklist Results @@ -5716,7 +5716,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Architecture Document' + title: "{{project_name}} Architecture Document" workflow: mode: interactive @@ -5827,11 +5827,11 @@ sections: - Code organization patterns (Dependency Injection, Repository, Module, Factory) - Data patterns (Event Sourcing, Saga, Database per Service) - Communication patterns (REST, GraphQL, Message Queue, Pub/Sub) - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - - '**Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling' - - '**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility' - - '**Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience' + - "**Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling" + - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility" + - "**Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience" - id: tech-stack title: Tech Stack @@ -5869,9 +5869,9 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Populate the technology stack table with all relevant technologies examples: - - '| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |' - - '| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |' - - '| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |' + - "| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |" + - "| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |" + - "| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |" - id: data-models title: Data Models @@ -5889,7 +5889,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -5920,7 +5920,7 @@ sections: sections: - id: component-list repeatable: true - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} @@ -5958,7 +5958,7 @@ sections: repeatable: true sections: - id: api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -6083,12 +6083,12 @@ sections: - id: environments title: Environments repeatable: true - template: '- **{{env_name}}:** {{env_purpose}} - {{env_details}}' + template: "- **{{env_name}}:** {{env_purpose}} - {{env_details}}" - id: promotion-flow title: Environment Promotion Flow type: code language: text - template: '{{promotion_flow_diagram}}' + template: "{{promotion_flow_diagram}}" - id: rollback-strategy title: Rollback Strategy template: | @@ -6184,16 +6184,16 @@ sections: Avoid obvious rules like "use SOLID principles" or "write clean code" repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" - id: language-specifics title: Language-Specific Guidelines condition: Critical language-specific rules needed instruction: Add ONLY if critical for preventing AI mistakes. Most teams don't need this section. sections: - id: language-rules - title: '{{language_name}} Specifics' + title: "{{language_name}} Specifics" repeatable: true - template: '- **{{rule_topic}}:** {{rule_detail}}' + template: "- **{{rule_topic}}:** {{rule_detail}}" - id: test-strategy title: Test Strategy and Standards @@ -6241,9 +6241,9 @@ sections: - **Test Infrastructure:** - **{{dependency_name}}:** {{test_approach}} ({{test_tool}}) examples: - - '**Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration' - - '**Message Queue:** Embedded Kafka for tests' - - '**External APIs:** WireMock for stubbing' + - "**Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration" + - "**Message Queue:** Embedded Kafka for tests" + - "**External APIs:** WireMock for stubbing" - id: e2e-tests title: End-to-End Tests template: | @@ -6369,7 +6369,7 @@ template: output: format: markdown filename: docs/ui-architecture.md - title: '{{project_name}} Frontend Architecture Document' + title: "{{project_name}} Frontend Architecture Document" workflow: mode: interactive @@ -6437,29 +6437,29 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Fill in appropriate technology choices based on the selected framework and project requirements. rows: - - ['Framework', '{{framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['UI Library', '{{ui_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Framework", "{{framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["UI Library", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'State Management', - '{{state_management}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "State Management", + "{{state_management}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['Routing', '{{routing_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Build Tool', '{{build_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Styling', '{{styling_solution}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Testing', '{{test_framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Routing", "{{routing_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Styling", "{{styling_solution}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Testing", "{{test_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Component Library', - '{{component_lib}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Component Library", + "{{component_lib}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['Form Handling', '{{form_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Animation', '{{animation_lib}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Dev Tools', '{{dev_tools}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Form Handling", "{{form_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Animation", "{{animation_lib}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Dev Tools", "{{dev_tools}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - id: project-structure title: Project Structure @@ -6553,12 +6553,12 @@ sections: title: Testing Best Practices type: numbered-list items: - - '**Unit Tests**: Test individual components in isolation' - - '**Integration Tests**: Test component interactions' - - '**E2E Tests**: Test critical user flows (using Cypress/Playwright)' - - '**Coverage Goals**: Aim for 80% code coverage' - - '**Test Structure**: Arrange-Act-Assert pattern' - - '**Mock External Dependencies**: API calls, routing, state management' + - "**Unit Tests**: Test individual components in isolation" + - "**Integration Tests**: Test component interactions" + - "**E2E Tests**: Test critical user flows (using Cypress/Playwright)" + - "**Coverage Goals**: Aim for 80% code coverage" + - "**Test Structure**: Arrange-Act-Assert pattern" + - "**Mock External Dependencies**: API calls, routing, state management" - id: environment-configuration title: Environment Configuration @@ -6590,7 +6590,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Fullstack Architecture Document' + title: "{{project_name}} Fullstack Architecture Document" workflow: mode: interactive @@ -6711,12 +6711,12 @@ sections: For each pattern, provide recommendation and rationale. repeatable: true - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - - '**Jamstack Architecture:** Static site generation with serverless APIs - _Rationale:_ Optimal performance and scalability for content-heavy applications' - - '**Component-Based UI:** Reusable React components with TypeScript - _Rationale:_ Maintainability and type safety across large codebases' - - '**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility' - - '**API Gateway Pattern:** Single entry point for all API calls - _Rationale:_ Centralized auth, rate limiting, and monitoring' + - "**Jamstack Architecture:** Static site generation with serverless APIs - _Rationale:_ Optimal performance and scalability for content-heavy applications" + - "**Component-Based UI:** Reusable React components with TypeScript - _Rationale:_ Maintainability and type safety across large codebases" + - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility" + - "**API Gateway Pattern:** Single entry point for all API calls - _Rationale:_ Centralized auth, rate limiting, and monitoring" - id: tech-stack title: Tech Stack @@ -6740,45 +6740,45 @@ sections: type: table columns: [Category, Technology, Version, Purpose, Rationale] rows: - - ['Frontend Language', '{{fe_language}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Frontend Language", "{{fe_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Frontend Framework', - '{{fe_framework}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Frontend Framework", + "{{fe_framework}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - [ - 'UI Component Library', - '{{ui_library}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "UI Component Library", + "{{ui_library}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['State Management', '{{state_mgmt}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Backend Language', '{{be_language}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["State Management", "{{state_mgmt}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Backend Language", "{{be_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Backend Framework', - '{{be_framework}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Backend Framework", + "{{be_framework}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['API Style', '{{api_style}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Database', '{{database}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Cache', '{{cache}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['File Storage', '{{storage}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Authentication', '{{auth}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Frontend Testing', '{{fe_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Backend Testing', '{{be_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['E2E Testing', '{{e2e_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Build Tool', '{{build_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Bundler', '{{bundler}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['IaC Tool', '{{iac_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['CI/CD', '{{cicd}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Monitoring', '{{monitoring}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Logging', '{{logging}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['CSS Framework', '{{css_framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["API Style", "{{api_style}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Database", "{{database}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Cache", "{{cache}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["File Storage", "{{storage}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Authentication", "{{auth}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Frontend Testing", "{{fe_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Backend Testing", "{{be_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["E2E Testing", "{{e2e_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Bundler", "{{bundler}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["IaC Tool", "{{iac_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["CI/CD", "{{cicd}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Monitoring", "{{monitoring}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Logging", "{{logging}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["CSS Framework", "{{css_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - id: data-models title: Data Models @@ -6797,7 +6797,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -6809,11 +6809,11 @@ sections: title: TypeScript Interface type: code language: typescript - template: '{{model_interface}}' + template: "{{model_interface}}" - id: relationships title: Relationships type: bullet-list - template: '- {{relationship}}' + template: "- {{relationship}}" - id: api-spec title: API Specification @@ -6850,13 +6850,13 @@ sections: condition: API style is GraphQL type: code language: graphql - template: '{{graphql_schema}}' + template: "{{graphql_schema}}" - id: trpc-api title: tRPC Router Definitions condition: API style is tRPC type: code language: typescript - template: '{{trpc_routers}}' + template: "{{trpc_routers}}" - id: components title: Components @@ -6877,7 +6877,7 @@ sections: sections: - id: component-list repeatable: true - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} @@ -6915,7 +6915,7 @@ sections: repeatable: true sections: - id: api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -6972,12 +6972,12 @@ sections: title: Component Organization type: code language: text - template: '{{component_structure}}' + template: "{{component_structure}}" - id: component-template title: Component Template type: code language: typescript - template: '{{component_template}}' + template: "{{component_template}}" - id: state-management title: State Management Architecture instruction: Detail state management approach based on chosen solution. @@ -6986,11 +6986,11 @@ sections: title: State Structure type: code language: typescript - template: '{{state_structure}}' + template: "{{state_structure}}" - id: state-patterns title: State Management Patterns type: bullet-list - template: '- {{pattern}}' + template: "- {{pattern}}" - id: routing-architecture title: Routing Architecture instruction: Define routing structure based on framework choice. @@ -6999,12 +6999,12 @@ sections: title: Route Organization type: code language: text - template: '{{route_structure}}' + template: "{{route_structure}}" - id: protected-routes title: Protected Route Pattern type: code language: typescript - template: '{{protected_route_example}}' + template: "{{protected_route_example}}" - id: frontend-services title: Frontend Services Layer instruction: Define how frontend communicates with backend. @@ -7013,12 +7013,12 @@ sections: title: API Client Setup type: code language: typescript - template: '{{api_client_setup}}' + template: "{{api_client_setup}}" - id: service-example title: Service Example type: code language: typescript - template: '{{service_example}}' + template: "{{service_example}}" - id: backend-architecture title: Backend Architecture @@ -7036,12 +7036,12 @@ sections: title: Function Organization type: code language: text - template: '{{function_structure}}' + template: "{{function_structure}}" - id: function-template title: Function Template type: code language: typescript - template: '{{function_template}}' + template: "{{function_template}}" - id: traditional-server condition: Traditional server architecture chosen sections: @@ -7049,12 +7049,12 @@ sections: title: Controller/Route Organization type: code language: text - template: '{{controller_structure}}' + template: "{{controller_structure}}" - id: controller-template title: Controller Template type: code language: typescript - template: '{{controller_template}}' + template: "{{controller_template}}" - id: database-architecture title: Database Architecture instruction: Define database schema and access patterns. @@ -7063,12 +7063,12 @@ sections: title: Schema Design type: code language: sql - template: '{{database_schema}}' + template: "{{database_schema}}" - id: data-access-layer title: Data Access Layer type: code language: typescript - template: '{{repository_pattern}}' + template: "{{repository_pattern}}" - id: auth-architecture title: Authentication and Authorization instruction: Define auth implementation details. @@ -7077,12 +7077,12 @@ sections: title: Auth Flow type: mermaid mermaid_type: sequence - template: '{{auth_flow_diagram}}' + template: "{{auth_flow_diagram}}" - id: auth-middleware title: Middleware/Guards type: code language: typescript - template: '{{auth_middleware}}' + template: "{{auth_middleware}}" - id: unified-project-structure title: Unified Project Structure @@ -7158,12 +7158,12 @@ sections: title: Prerequisites type: code language: bash - template: '{{prerequisites_commands}}' + template: "{{prerequisites_commands}}" - id: initial-setup title: Initial Setup type: code language: bash - template: '{{setup_commands}}' + template: "{{setup_commands}}" - id: dev-commands title: Development Commands type: code @@ -7219,15 +7219,15 @@ sections: title: CI/CD Pipeline type: code language: yaml - template: '{{cicd_pipeline_config}}' + template: "{{cicd_pipeline_config}}" - id: environments title: Environments type: table columns: [Environment, Frontend URL, Backend URL, Purpose] rows: - - ['Development', '{{dev_fe_url}}', '{{dev_be_url}}', 'Local development'] - - ['Staging', '{{staging_fe_url}}', '{{staging_be_url}}', 'Pre-production testing'] - - ['Production', '{{prod_fe_url}}', '{{prod_be_url}}', 'Live environment'] + - ["Development", "{{dev_fe_url}}", "{{dev_be_url}}", "Local development"] + - ["Staging", "{{staging_fe_url}}", "{{staging_be_url}}", "Pre-production testing"] + - ["Production", "{{prod_fe_url}}", "{{prod_be_url}}", "Live environment"] - id: security-performance title: Security and Performance @@ -7286,17 +7286,17 @@ sections: title: Frontend Tests type: code language: text - template: '{{frontend_test_structure}}' + template: "{{frontend_test_structure}}" - id: backend-tests title: Backend Tests type: code language: text - template: '{{backend_test_structure}}' + template: "{{backend_test_structure}}" - id: e2e-tests title: E2E Tests type: code language: text - template: '{{e2e_test_structure}}' + template: "{{e2e_test_structure}}" - id: test-examples title: Test Examples sections: @@ -7304,17 +7304,17 @@ sections: title: Frontend Component Test type: code language: typescript - template: '{{frontend_test_example}}' + template: "{{frontend_test_example}}" - id: backend-test title: Backend API Test type: code language: typescript - template: '{{backend_test_example}}' + template: "{{backend_test_example}}" - id: e2e-test title: E2E Test type: code language: typescript - template: '{{e2e_test_example}}' + template: "{{e2e_test_example}}" - id: coding-standards title: Coding Standards @@ -7324,22 +7324,22 @@ sections: - id: critical-rules title: Critical Fullstack Rules repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" examples: - - '**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' + - "**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" - id: naming-conventions title: Naming Conventions type: table columns: [Element, Frontend, Backend, Example] rows: - - ['Components', 'PascalCase', '-', '`UserProfile.tsx`'] - - ['Hooks', "camelCase with 'use'", '-', '`useAuth.ts`'] - - ['API Routes', '-', 'kebab-case', '`/api/user-profile`'] - - ['Database Tables', '-', 'snake_case', '`user_profiles`'] + - ["Components", "PascalCase", "-", "`UserProfile.tsx`"] + - ["Hooks", "camelCase with 'use'", "-", "`useAuth.ts`"] + - ["API Routes", "-", "kebab-case", "`/api/user-profile`"] + - ["Database Tables", "-", "snake_case", "`user_profiles`"] - id: error-handling title: Error Handling Strategy @@ -7350,7 +7350,7 @@ sections: title: Error Flow type: mermaid mermaid_type: sequence - template: '{{error_flow_diagram}}' + template: "{{error_flow_diagram}}" - id: error-format title: Error Response Format type: code @@ -7369,12 +7369,12 @@ sections: title: Frontend Error Handling type: code language: typescript - template: '{{frontend_error_handler}}' + template: "{{frontend_error_handler}}" - id: backend-error-handling title: Backend Error Handling type: code language: typescript - template: '{{backend_error_handler}}' + template: "{{backend_error_handler}}" - id: monitoring title: Monitoring and Observability @@ -7416,7 +7416,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Brownfield Enhancement Architecture' + title: "{{project_name}} Brownfield Enhancement Architecture" workflow: mode: interactive @@ -7474,11 +7474,11 @@ sections: - id: available-docs title: Available Documentation type: bullet-list - template: '- {{existing_docs_summary}}' + template: "- {{existing_docs_summary}}" - id: constraints title: Identified Constraints type: bullet-list - template: '- {{constraint}}' + template: "- {{constraint}}" - id: changelog title: Change Log type: table @@ -7558,7 +7558,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} **Integration:** {{integration_with_existing}} @@ -7601,7 +7601,7 @@ sections: repeatable: true sections: - id: component - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} **Integration Points:** {{integration_points}} @@ -7644,7 +7644,7 @@ sections: repeatable: true sections: - id: endpoint - title: '{{endpoint_name}}' + title: "{{endpoint_name}}" template: | - **Method:** {{http_method}} - **Endpoint:** {{endpoint_path}} @@ -7655,12 +7655,12 @@ sections: title: Request type: code language: json - template: '{{request_schema}}' + template: "{{request_schema}}" - id: response title: Response type: code language: json - template: '{{response_schema}}' + template: "{{response_schema}}" - id: external-api-integration title: External API Integration @@ -7669,7 +7669,7 @@ sections: repeatable: true sections: - id: external-api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -7698,7 +7698,7 @@ sections: type: code language: plaintext instruction: Document relevant parts of current structure - template: '{{existing_structure_relevant_parts}}' + template: "{{existing_structure_relevant_parts}}" - id: new-file-organization title: New File Organization type: code @@ -7773,7 +7773,7 @@ sections: title: Enhancement-Specific Standards condition: New patterns needed for enhancement repeatable: true - template: '- **{{standard_name}}:** {{standard_description}}' + template: "- **{{standard_name}}:** {{standard_description}}" - id: integration-rules title: Critical Integration Rules template: | @@ -8473,7 +8473,7 @@ template: output: format: markdown filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md - title: 'Story {{epic_num}}.{{story_num}}: {{story_title_short}}' + title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}" workflow: mode: interactive @@ -8575,7 +8575,7 @@ sections: sections: - id: agent-model title: Agent Model Used - template: '{{agent_model_name_version}}' + template: "{{agent_model_name_version}}" instruction: Record the specific AI agent model and version used for development owner: dev-agent editors: [dev-agent] @@ -9072,14 +9072,14 @@ workflow: single_story: agent: pm uses: brownfield-create-story - notes: 'Create single story for immediate implementation. Exit workflow after story creation.' + notes: "Create single story for immediate implementation. Exit workflow after story creation." small_feature: agent: pm uses: brownfield-create-epic - notes: 'Create focused epic with 1-3 stories. Exit workflow after epic creation.' + notes: "Create focused epic with 1-3 stories. Exit workflow after epic creation." major_enhancement: continue: to_next_step - notes: 'Continue with comprehensive planning workflow below.' + notes: "Continue with comprehensive planning workflow below." - step: documentation_check agent: analyst @@ -9097,7 +9097,7 @@ workflow: action: analyze existing project and use task document-project creates: brownfield-architecture.md (or multiple documents) condition: documentation_inadequate - notes: 'Run document-project to capture current system state, technical debt, and constraints. Pass findings to PRD creation.' + notes: "Run document-project to capture current system state, technical debt, and constraints. Pass findings to PRD creation." - agent: pm creates: prd.md @@ -9129,12 +9129,12 @@ workflow: - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for integration safety and completeness. May require updates to any document.' + notes: "Validates all documents for integration safety and completeness. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - agent: po action: shard_documents @@ -9325,7 +9325,7 @@ workflow: {{if yes}}: Proceeding to create architecture document for: {{specific_changes}} {{if no}}: No architectural changes needed. Proceeding to validation. - architect_to_po: 'Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for integration safety.' + architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for integration safety." po_to_sm: | All artifacts validated. @@ -9337,7 +9337,7 @@ workflow: Creating story from {{documentation_type}}. {{if missing_context}}: May need to gather additional context from user during story creation. - complete: 'All planning artifacts validated and development can begin. Stories will be created based on available documentation format.' + complete: "All planning artifacts validated and development can begin. Stories will be created based on available documentation format." ==================== END: .bmad-core/workflows/brownfield-fullstack.yaml ==================== ==================== START: .bmad-core/workflows/brownfield-service.yaml ==================== @@ -9360,7 +9360,7 @@ workflow: agent: architect action: analyze existing project and use task document-project creates: multiple documents per the document-project template - notes: 'Review existing service documentation, codebase, performance metrics, and identify integration dependencies.' + notes: "Review existing service documentation, codebase, performance metrics, and identify integration dependencies." - agent: pm creates: prd.md @@ -9377,12 +9377,12 @@ workflow: - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for service integration safety and API compatibility. May require updates to any document.' + notes: "Validates all documents for service integration safety and API compatibility. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - agent: po action: shard_documents @@ -9523,11 +9523,11 @@ workflow: - Multiple integration points affected handoff_prompts: - analyst_to_pm: 'Service analysis complete. Create comprehensive PRD with service integration strategy.' - pm_to_architect: 'PRD ready. Save it as docs/prd.md, then create the service architecture.' - architect_to_po: 'Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for service integration safety.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "Service analysis complete. Create comprehensive PRD with service integration strategy." + pm_to_architect: "PRD ready. Save it as docs/prd.md, then create the service architecture." + architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for service integration safety." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/brownfield-service.yaml ==================== ==================== START: .bmad-core/workflows/brownfield-ui.yaml ==================== @@ -9549,7 +9549,7 @@ workflow: agent: architect action: analyze existing project and use task document-project creates: multiple documents per the document-project template - notes: 'Review existing frontend application, user feedback, analytics data, and identify improvement areas.' + notes: "Review existing frontend application, user feedback, analytics data, and identify improvement areas." - agent: pm creates: prd.md @@ -9574,12 +9574,12 @@ workflow: - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for UI integration safety and design consistency. May require updates to any document.' + notes: "Validates all documents for UI integration safety and design consistency. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - agent: po action: shard_documents @@ -9722,12 +9722,12 @@ workflow: - Multiple team members will work on related changes handoff_prompts: - analyst_to_pm: 'UI analysis complete. Create comprehensive PRD with UI integration strategy.' - pm_to_ux: 'PRD ready. Save it as docs/prd.md, then create the UI/UX specification.' - ux_to_architect: 'UI/UX spec complete. Save it as docs/front-end-spec.md, then create the frontend architecture.' - architect_to_po: 'Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for UI integration safety.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "UI analysis complete. Create comprehensive PRD with UI integration strategy." + pm_to_ux: "PRD ready. Save it as docs/prd.md, then create the UI/UX specification." + ux_to_architect: "UI/UX spec complete. Save it as docs/front-end-spec.md, then create the frontend architecture." + architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for UI integration safety." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/brownfield-ui.yaml ==================== ==================== START: .bmad-core/workflows/greenfield-fullstack.yaml ==================== @@ -9769,7 +9769,7 @@ workflow: creates: v0_prompt (optional) requires: front-end-spec.md condition: user_wants_ai_generation - notes: 'OPTIONAL BUT RECOMMENDED: Generate AI UI prompt for tools like v0, Lovable, etc. Use the generate-ai-frontend-prompt task. User can then generate UI in external tool and download project structure.' + notes: "OPTIONAL BUT RECOMMENDED: Generate AI UI prompt for tools like v0, Lovable, etc. Use the generate-ai-frontend-prompt task. User can then generate UI in external tool and download project structure." - agent: architect creates: fullstack-architecture.md @@ -9785,26 +9785,26 @@ workflow: updates: prd.md (if needed) requires: fullstack-architecture.md condition: architecture_suggests_prd_changes - notes: 'If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder.' + notes: "If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder." - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for consistency and completeness. May require updates to any document.' + notes: "Validates all documents for consistency and completeness. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - project_setup_guidance: action: guide_project_structure condition: user_has_generated_ui - notes: 'If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo alongside backend repo. For monorepo, place in apps/web or packages/frontend directory. Review architecture document for specific guidance.' + notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo alongside backend repo. For monorepo, place in apps/web or packages/frontend directory. Review architecture document for specific guidance." - development_order_guidance: action: guide_development_sequence - notes: 'Based on PRD stories: If stories are frontend-heavy, start with frontend project/directory first. If backend-heavy or API-first, start with backend. For tightly coupled features, follow story sequence in monorepo setup. Reference sharded PRD epics for development order.' + notes: "Based on PRD stories: If stories are frontend-heavy, start with frontend project/directory first. If backend-heavy or API-first, start with backend. For tightly coupled features, follow story sequence in monorepo setup. Reference sharded PRD epics for development order." - agent: po action: shard_documents @@ -9963,14 +9963,14 @@ workflow: - Enterprise or customer-facing applications handoff_prompts: - analyst_to_pm: 'Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD.' - pm_to_ux: 'PRD is ready. Save it as docs/prd.md in your project, then create the UI/UX specification.' - ux_to_architect: 'UI/UX spec complete. Save it as docs/front-end-spec.md in your project, then create the fullstack architecture.' - architect_review: 'Architecture complete. Save it as docs/fullstack-architecture.md. Do you suggest any changes to the PRD stories or need new stories added?' - architect_to_pm: 'Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/.' - updated_to_po: 'All documents ready in docs/ folder. Please validate all artifacts for consistency.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD." + pm_to_ux: "PRD is ready. Save it as docs/prd.md in your project, then create the UI/UX specification." + ux_to_architect: "UI/UX spec complete. Save it as docs/front-end-spec.md in your project, then create the fullstack architecture." + architect_review: "Architecture complete. Save it as docs/fullstack-architecture.md. Do you suggest any changes to the PRD stories or need new stories added?" + architect_to_pm: "Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/." + updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/greenfield-fullstack.yaml ==================== ==================== START: .bmad-core/workflows/greenfield-service.yaml ==================== @@ -10013,17 +10013,17 @@ workflow: updates: prd.md (if needed) requires: architecture.md condition: architecture_suggests_prd_changes - notes: 'If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder.' + notes: "If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder." - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for consistency and completeness. May require updates to any document.' + notes: "Validates all documents for consistency and completeness. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - agent: po action: shard_documents @@ -10173,13 +10173,13 @@ workflow: - Enterprise or external-facing APIs handoff_prompts: - analyst_to_pm: 'Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD.' - pm_to_architect: 'PRD is ready. Save it as docs/prd.md in your project, then create the service architecture.' - architect_review: 'Architecture complete. Save it as docs/architecture.md. Do you suggest any changes to the PRD stories or need new stories added?' - architect_to_pm: 'Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/.' - updated_to_po: 'All documents ready in docs/ folder. Please validate all artifacts for consistency.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD." + pm_to_architect: "PRD is ready. Save it as docs/prd.md in your project, then create the service architecture." + architect_review: "Architecture complete. Save it as docs/architecture.md. Do you suggest any changes to the PRD stories or need new stories added?" + architect_to_pm: "Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/." + updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/greenfield-service.yaml ==================== ==================== START: .bmad-core/workflows/greenfield-ui.yaml ==================== @@ -10222,7 +10222,7 @@ workflow: creates: v0_prompt (optional) requires: front-end-spec.md condition: user_wants_ai_generation - notes: 'OPTIONAL BUT RECOMMENDED: Generate AI UI prompt for tools like v0, Lovable, etc. Use the generate-ai-frontend-prompt task. User can then generate UI in external tool and download project structure.' + notes: "OPTIONAL BUT RECOMMENDED: Generate AI UI prompt for tools like v0, Lovable, etc. Use the generate-ai-frontend-prompt task. User can then generate UI in external tool and download project structure." - agent: architect creates: front-end-architecture.md @@ -10236,22 +10236,22 @@ workflow: updates: prd.md (if needed) requires: front-end-architecture.md condition: architecture_suggests_prd_changes - notes: 'If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder.' + notes: "If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder." - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for consistency and completeness. May require updates to any document.' + notes: "Validates all documents for consistency and completeness. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - project_setup_guidance: action: guide_project_structure condition: user_has_generated_ui - notes: 'If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance.' + notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance." - agent: po action: shard_documents @@ -10410,12 +10410,12 @@ workflow: - Customer-facing applications handoff_prompts: - analyst_to_pm: 'Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD.' - pm_to_ux: 'PRD is ready. Save it as docs/prd.md in your project, then create the UI/UX specification.' - ux_to_architect: 'UI/UX spec complete. Save it as docs/front-end-spec.md in your project, then create the frontend architecture.' - architect_review: 'Frontend architecture complete. Save it as docs/front-end-architecture.md. Do you suggest any changes to the PRD stories or need new stories added?' - architect_to_pm: 'Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/.' - updated_to_po: 'All documents ready in docs/ folder. Please validate all artifacts for consistency.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD." + pm_to_ux: "PRD is ready. Save it as docs/prd.md in your project, then create the UI/UX specification." + ux_to_architect: "UI/UX spec complete. Save it as docs/front-end-spec.md in your project, then create the frontend architecture." + architect_review: "Frontend architecture complete. Save it as docs/front-end-architecture.md. Do you suggest any changes to the PRD stories or need new stories added?" + architect_to_pm: "Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/." + updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/greenfield-ui.yaml ==================== diff --git a/dist/teams/team-ide-minimal.txt b/dist/teams/team-ide-minimal.txt index f7b0cc87..59f15bc6 100644 --- a/dist/teams/team-ide-minimal.txt +++ b/dist/teams/team-ide-minimal.txt @@ -2246,7 +2246,7 @@ template: output: format: markdown filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md - title: 'Story {{epic_num}}.{{story_num}}: {{story_title_short}}' + title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}" workflow: mode: interactive @@ -2348,7 +2348,7 @@ sections: sections: - id: agent-model title: Agent Model Used - template: '{{agent_model_name_version}}' + template: "{{agent_model_name_version}}" instruction: Record the specific AI agent model and version used for development owner: dev-agent editors: [dev-agent] @@ -4999,16 +4999,16 @@ template: output: format: yaml filename: docs/qa/gates/{{epic_num}}.{{story_num}}-{{story_slug}}.yml - title: 'Quality Gate: {{epic_num}}.{{story_num}}' + title: "Quality Gate: {{epic_num}}.{{story_num}}" # Required fields (keep these first) schema: 1 -story: '{{epic_num}}.{{story_num}}' -story_title: '{{story_title}}' -gate: '{{gate_status}}' # PASS|CONCERNS|FAIL|WAIVED -status_reason: '{{status_reason}}' # 1-2 sentence summary of why this gate decision -reviewer: 'Quinn (Test Architect)' -updated: '{{iso_timestamp}}' +story: "{{epic_num}}.{{story_num}}" +story_title: "{{story_title}}" +gate: "{{gate_status}}" # PASS|CONCERNS|FAIL|WAIVED +status_reason: "{{status_reason}}" # 1-2 sentence summary of why this gate decision +reviewer: "Quinn (Test Architect)" +updated: "{{iso_timestamp}}" # Always present but only active when WAIVED waiver: { active: false } diff --git a/dist/teams/team-no-ui.txt b/dist/teams/team-no-ui.txt index 15717063..11db569e 100644 --- a/dist/teams/team-no-ui.txt +++ b/dist/teams/team-no-ui.txt @@ -2555,24 +2555,24 @@ template: output: format: markdown filename: docs/brief.md - title: 'Project Brief: {{project_name}}' + title: "Project Brief: {{project_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Project Brief Elicitation Actions' + title: "Project Brief Elicitation Actions" options: - - 'Expand section with more specific details' - - 'Validate against similar successful products' - - 'Stress test assumptions with edge cases' - - 'Explore alternative solution approaches' - - 'Analyze resource/constraint trade-offs' - - 'Generate risk mitigation strategies' - - 'Challenge scope from MVP minimalist view' - - 'Brainstorm creative feature possibilities' - - 'If only we had [resource/capability/time]...' - - 'Proceed to next section' + - "Expand section with more specific details" + - "Validate against similar successful products" + - "Stress test assumptions with edge cases" + - "Explore alternative solution approaches" + - "Analyze resource/constraint trade-offs" + - "Generate risk mitigation strategies" + - "Challenge scope from MVP minimalist view" + - "Brainstorm creative feature possibilities" + - "If only we had [resource/capability/time]..." + - "Proceed to next section" sections: - id: introduction @@ -2594,7 +2594,7 @@ sections: - Primary problem being solved - Target market identification - Key value proposition - template: '{{executive_summary_content}}' + template: "{{executive_summary_content}}" - id: problem-statement title: Problem Statement @@ -2604,7 +2604,7 @@ sections: - Impact of the problem (quantify if possible) - Why existing solutions fall short - Urgency and importance of solving this now - template: '{{detailed_problem_description}}' + template: "{{detailed_problem_description}}" - id: proposed-solution title: Proposed Solution @@ -2614,7 +2614,7 @@ sections: - Key differentiators from existing solutions - Why this solution will succeed where others haven't - High-level vision for the product - template: '{{solution_description}}' + template: "{{solution_description}}" - id: target-users title: Target Users @@ -2626,12 +2626,12 @@ sections: - Goals they're trying to achieve sections: - id: primary-segment - title: 'Primary User Segment: {{segment_name}}' - template: '{{primary_user_description}}' + title: "Primary User Segment: {{segment_name}}" + template: "{{primary_user_description}}" - id: secondary-segment - title: 'Secondary User Segment: {{segment_name}}' + title: "Secondary User Segment: {{segment_name}}" condition: Has secondary user segment - template: '{{secondary_user_description}}' + template: "{{secondary_user_description}}" - id: goals-metrics title: Goals & Success Metrics @@ -2640,15 +2640,15 @@ sections: - id: business-objectives title: Business Objectives type: bullet-list - template: '- {{objective_with_metric}}' + template: "- {{objective_with_metric}}" - id: user-success-metrics title: User Success Metrics type: bullet-list - template: '- {{user_metric}}' + template: "- {{user_metric}}" - id: kpis title: Key Performance Indicators (KPIs) type: bullet-list - template: '- {{kpi}}: {{definition_and_target}}' + template: "- {{kpi}}: {{definition_and_target}}" - id: mvp-scope title: MVP Scope @@ -2657,14 +2657,14 @@ sections: - id: core-features title: Core Features (Must Have) type: bullet-list - template: '- **{{feature}}:** {{description_and_rationale}}' + template: "- **{{feature}}:** {{description_and_rationale}}" - id: out-of-scope title: Out of Scope for MVP type: bullet-list - template: '- {{feature_or_capability}}' + template: "- {{feature_or_capability}}" - id: mvp-success-criteria title: MVP Success Criteria - template: '{{mvp_success_definition}}' + template: "{{mvp_success_definition}}" - id: post-mvp-vision title: Post-MVP Vision @@ -2672,13 +2672,13 @@ sections: sections: - id: phase-2-features title: Phase 2 Features - template: '{{next_priority_features}}' + template: "{{next_priority_features}}" - id: long-term-vision title: Long-term Vision - template: '{{one_two_year_vision}}' + template: "{{one_two_year_vision}}" - id: expansion-opportunities title: Expansion Opportunities - template: '{{potential_expansions}}' + template: "{{potential_expansions}}" - id: technical-considerations title: Technical Considerations @@ -2719,7 +2719,7 @@ sections: - id: key-assumptions title: Key Assumptions type: bullet-list - template: '- {{assumption}}' + template: "- {{assumption}}" - id: risks-questions title: Risks & Open Questions @@ -2728,15 +2728,15 @@ sections: - id: key-risks title: Key Risks type: bullet-list - template: '- **{{risk}}:** {{description_and_impact}}' + template: "- **{{risk}}:** {{description_and_impact}}" - id: open-questions title: Open Questions type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: research-areas title: Areas Needing Further Research type: bullet-list - template: '- {{research_topic}}' + template: "- {{research_topic}}" - id: appendices title: Appendices @@ -2753,10 +2753,10 @@ sections: - id: stakeholder-input title: B. Stakeholder Input condition: Has stakeholder feedback - template: '{{stakeholder_feedback}}' + template: "{{stakeholder_feedback}}" - id: references title: C. References - template: '{{relevant_links_and_docs}}' + template: "{{relevant_links_and_docs}}" - id: next-steps title: Next Steps @@ -2764,7 +2764,7 @@ sections: - id: immediate-actions title: Immediate Actions type: numbered-list - template: '{{action_item}}' + template: "{{action_item}}" - id: pm-handoff title: PM Handoff content: | @@ -2779,24 +2779,24 @@ template: output: format: markdown filename: docs/market-research.md - title: 'Market Research Report: {{project_product_name}}' + title: "Market Research Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Market Research Elicitation Actions' + title: "Market Research Elicitation Actions" options: - - 'Expand market sizing calculations with sensitivity analysis' - - 'Deep dive into a specific customer segment' - - 'Analyze an emerging market trend in detail' - - 'Compare this market to an analogous market' - - 'Stress test market assumptions' - - 'Explore adjacent market opportunities' - - 'Challenge market definition and boundaries' - - 'Generate strategic scenarios (best/base/worst case)' - - 'If only we had considered [X market factor]...' - - 'Proceed to next section' + - "Expand market sizing calculations with sensitivity analysis" + - "Deep dive into a specific customer segment" + - "Analyze an emerging market trend in detail" + - "Compare this market to an analogous market" + - "Stress test market assumptions" + - "Explore adjacent market opportunities" + - "Challenge market definition and boundaries" + - "Generate strategic scenarios (best/base/worst case)" + - "If only we had considered [X market factor]..." + - "Proceed to next section" sections: - id: executive-summary @@ -2878,7 +2878,7 @@ sections: repeatable: true sections: - id: segment - title: 'Segment {{segment_number}}: {{segment_name}}' + title: "Segment {{segment_number}}: {{segment_name}}" template: | - **Description:** {{brief_overview}} - **Size:** {{number_of_customers_market_value}} @@ -2947,20 +2947,20 @@ sections: instruction: Analyze each force with specific evidence and implications sections: - id: supplier-power - title: 'Supplier Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Supplier Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: buyer-power - title: 'Buyer Power: {{power_level}}' - template: '{{analysis_and_implications}}' + title: "Buyer Power: {{power_level}}" + template: "{{analysis_and_implications}}" - id: competitive-rivalry - title: 'Competitive Rivalry: {{intensity_level}}' - template: '{{analysis_and_implications}}' + title: "Competitive Rivalry: {{intensity_level}}" + template: "{{analysis_and_implications}}" - id: threat-new-entry - title: 'Threat of New Entry: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of New Entry: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: threat-substitutes - title: 'Threat of Substitutes: {{threat_level}}' - template: '{{analysis_and_implications}}' + title: "Threat of Substitutes: {{threat_level}}" + template: "{{analysis_and_implications}}" - id: adoption-lifecycle title: Technology Adoption Lifecycle Stage instruction: | @@ -2978,7 +2978,7 @@ sections: repeatable: true sections: - id: opportunity - title: 'Opportunity {{opportunity_number}}: {{name}}' + title: "Opportunity {{opportunity_number}}: {{name}}" template: | - **Description:** {{what_is_the_opportunity}} - **Size/Potential:** {{quantified_potential}} @@ -3034,24 +3034,24 @@ template: output: format: markdown filename: docs/competitor-analysis.md - title: 'Competitive Analysis Report: {{project_product_name}}' + title: "Competitive Analysis Report: {{project_product_name}}" workflow: mode: interactive elicitation: advanced-elicitation custom_elicitation: - title: 'Competitive Analysis Elicitation Actions' + title: "Competitive Analysis Elicitation Actions" options: - "Deep dive on a specific competitor's strategy" - - 'Analyze competitive dynamics in a specific segment' - - 'War game competitive responses to your moves' - - 'Explore partnership vs. competition scenarios' - - 'Stress test differentiation claims' - - 'Analyze disruption potential (yours or theirs)' - - 'Compare to competition in adjacent markets' - - 'Generate win/loss analysis insights' + - "Analyze competitive dynamics in a specific segment" + - "War game competitive responses to your moves" + - "Explore partnership vs. competition scenarios" + - "Stress test differentiation claims" + - "Analyze disruption potential (yours or theirs)" + - "Compare to competition in adjacent markets" + - "Generate win/loss analysis insights" - "If only we had known about [competitor X's plan]..." - - 'Proceed to next section' + - "Proceed to next section" sections: - id: executive-summary @@ -3118,7 +3118,7 @@ sections: repeatable: true sections: - id: competitor - title: '{{competitor_name}} - Priority {{priority_level}}' + title: "{{competitor_name}} - Priority {{priority_level}}" sections: - id: company-overview title: Company Overview @@ -3150,11 +3150,11 @@ sections: - id: strengths title: Strengths type: bullet-list - template: '- {{strength}}' + template: "- {{strength}}" - id: weaknesses title: Weaknesses type: bullet-list - template: '- {{weakness}}' + template: "- {{weakness}}" - id: market-position title: Market Position & Performance template: | @@ -3172,35 +3172,35 @@ sections: type: table columns: [ - 'Feature Category', - '{{your_company}}', - '{{competitor_1}}', - '{{competitor_2}}', - '{{competitor_3}}', + "Feature Category", + "{{your_company}}", + "{{competitor_1}}", + "{{competitor_2}}", + "{{competitor_3}}", ] rows: - - category: 'Core Functionality' + - category: "Core Functionality" items: - - ['Feature A', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - ['Feature B', '{{status}}', '{{status}}', '{{status}}', '{{status}}'] - - category: 'User Experience' + - ["Feature A", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - ["Feature B", "{{status}}", "{{status}}", "{{status}}", "{{status}}"] + - category: "User Experience" items: - - ['Mobile App', '{{rating}}', '{{rating}}', '{{rating}}', '{{rating}}'] - - ['Onboarding Time', '{{time}}', '{{time}}', '{{time}}', '{{time}}'] - - category: 'Integration & Ecosystem' + - ["Mobile App", "{{rating}}", "{{rating}}", "{{rating}}", "{{rating}}"] + - ["Onboarding Time", "{{time}}", "{{time}}", "{{time}}", "{{time}}"] + - category: "Integration & Ecosystem" items: - [ - 'API Availability', - '{{availability}}', - '{{availability}}', - '{{availability}}', - '{{availability}}', + "API Availability", + "{{availability}}", + "{{availability}}", + "{{availability}}", + "{{availability}}", ] - - ['Third-party Integrations', '{{number}}', '{{number}}', '{{number}}', '{{number}}'] - - category: 'Pricing & Plans' + - ["Third-party Integrations", "{{number}}", "{{number}}", "{{number}}", "{{number}}"] + - category: "Pricing & Plans" items: - - ['Starting Price', '{{price}}', '{{price}}', '{{price}}', '{{price}}'] - - ['Free Tier', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}', '{{yes_no}}'] + - ["Starting Price", "{{price}}", "{{price}}", "{{price}}", "{{price}}"] + - ["Free Tier", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}"] - id: swot-comparison title: SWOT Comparison instruction: Create SWOT analysis for your solution vs. top competitors @@ -3213,7 +3213,7 @@ sections: - **Opportunities:** {{opportunities}} - **Threats:** {{threats}} - id: vs-competitor - title: 'vs. {{main_competitor}}' + title: "vs. {{main_competitor}}" template: | - **Competitive Advantages:** {{your_advantages}} - **Competitive Disadvantages:** {{their_advantages}} @@ -3343,7 +3343,7 @@ template: output: format: markdown filename: docs/brainstorming-session-results.md - title: 'Brainstorming Session Results' + title: "Brainstorming Session Results" workflow: mode: non-interactive @@ -3368,38 +3368,38 @@ sections: **Total Ideas Generated:** {{total_ideas}} - id: key-themes - title: 'Key Themes Identified:' + title: "Key Themes Identified:" type: bullet-list - template: '- {{theme}}' + template: "- {{theme}}" - id: technique-sessions title: Technique Sessions repeatable: true sections: - id: technique - title: '{{technique_name}} - {{duration}}' + title: "{{technique_name}} - {{duration}}" sections: - id: description - template: '**Description:** {{technique_description}}' + template: "**Description:** {{technique_description}}" - id: ideas-generated - title: 'Ideas Generated:' + title: "Ideas Generated:" type: numbered-list - template: '{{idea}}' + template: "{{idea}}" - id: insights - title: 'Insights Discovered:' + title: "Insights Discovered:" type: bullet-list - template: '- {{insight}}' + template: "- {{insight}}" - id: connections - title: 'Notable Connections:' + title: "Notable Connections:" type: bullet-list - template: '- {{connection}}' + template: "- {{connection}}" - id: idea-categorization title: Idea Categorization sections: - id: immediate-opportunities title: Immediate Opportunities - content: '*Ideas ready to implement now*' + content: "*Ideas ready to implement now*" repeatable: true type: numbered-list template: | @@ -3409,7 +3409,7 @@ sections: - Resources needed: {{requirements}} - id: future-innovations title: Future Innovations - content: '*Ideas requiring development/research*' + content: "*Ideas requiring development/research*" repeatable: true type: numbered-list template: | @@ -3419,7 +3419,7 @@ sections: - Timeline estimate: {{timeline}} - id: moonshots title: Moonshots - content: '*Ambitious, transformative concepts*' + content: "*Ambitious, transformative concepts*" repeatable: true type: numbered-list template: | @@ -3429,9 +3429,9 @@ sections: - Challenges to overcome: {{challenges}} - id: insights-learnings title: Insights & Learnings - content: '*Key realizations from the session*' + content: "*Key realizations from the session*" type: bullet-list - template: '- {{insight}}: {{description_and_implications}}' + template: "- {{insight}}: {{description_and_implications}}" - id: action-planning title: Action Planning @@ -3440,21 +3440,21 @@ sections: title: Top 3 Priority Ideas sections: - id: priority-1 - title: '#1 Priority: {{idea_name}}' + title: "#1 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-2 - title: '#2 Priority: {{idea_name}}' + title: "#2 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} - Resources needed: {{resources}} - Timeline: {{timeline}} - id: priority-3 - title: '#3 Priority: {{idea_name}}' + title: "#3 Priority: {{idea_name}}" template: | - Rationale: {{rationale}} - Next steps: {{next_steps}} @@ -3467,19 +3467,19 @@ sections: - id: what-worked title: What Worked Well type: bullet-list - template: '- {{aspect}}' + template: "- {{aspect}}" - id: areas-exploration title: Areas for Further Exploration type: bullet-list - template: '- {{area}}: {{reason}}' + template: "- {{area}}: {{reason}}" - id: recommended-techniques title: Recommended Follow-up Techniques type: bullet-list - template: '- {{technique}}: {{reason}}' + template: "- {{technique}}: {{reason}}" - id: questions-emerged title: Questions That Emerged type: bullet-list - template: '- {{question}}' + template: "- {{question}}" - id: next-session title: Next Session Planning template: | @@ -4204,7 +4204,7 @@ template: output: format: markdown filename: docs/prd.md - title: '{{project_name}} Product Requirements Document (PRD)' + title: "{{project_name}} Product Requirements Document (PRD)" workflow: mode: interactive @@ -4241,14 +4241,14 @@ sections: prefix: FR instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with FR examples: - - 'FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently.' + - "FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently." - id: non-functional title: Non Functional type: numbered-list prefix: NFR instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR examples: - - 'NFR1: AWS service usage must aim to stay within free-tier limits where feasible.' + - "NFR1: AWS service usage must aim to stay within free-tier limits where feasible." - id: ui-goals title: User Interface Design Goals @@ -4274,24 +4274,24 @@ sections: title: Core Screens and Views instruction: 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 examples: - - 'Login Screen' - - 'Main Dashboard' - - 'Item Detail Page' - - 'Settings Page' + - "Login Screen" + - "Main Dashboard" + - "Item Detail Page" + - "Settings Page" - id: accessibility - title: 'Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}' + title: "Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}" - id: branding title: Branding instruction: Any known branding elements or style guides that must be incorporated? examples: - - '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.' + - "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." - id: target-platforms - title: 'Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}' + title: "Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}" examples: - - 'Web Responsive, and all mobile platforms' - - 'iPhone Only' - - 'ASCII Windows Desktop' + - "Web Responsive, and all mobile platforms" + - "iPhone Only" + - "ASCII Windows Desktop" - id: technical-assumptions title: Technical Assumptions @@ -4310,13 +4310,13 @@ sections: testing: [Unit Only, Unit + Integration, Full Testing Pyramid] sections: - id: repository-structure - title: 'Repository Structure: {Monorepo|Polyrepo|Multi-repo}' + title: "Repository Structure: {Monorepo|Polyrepo|Multi-repo}" - id: service-architecture title: Service Architecture - instruction: 'CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).' + instruction: "CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo)." - id: testing-requirements title: Testing Requirements - instruction: 'CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).' + instruction: "CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods)." - id: additional-assumptions title: Additional Technical Assumptions and Requests instruction: 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 @@ -4336,10 +4336,10 @@ sections: - 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. elicit: true examples: - - 'Epic 1: Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management' - - 'Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations' - - 'Epic 3: User Workflows & Interactions: Enable key user journeys and business processes' - - 'Epic 4: Reporting & Analytics: Provide insights and data visualization for users' + - "Epic 1: Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management" + - "Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations" + - "Epic 3: User Workflows & Interactions: Enable key user journeys and business processes" + - "Epic 4: Reporting & Analytics: Provide insights and data visualization for users" - id: epic-details title: Epic {{epic_number}} {{epic_title}} @@ -4361,7 +4361,7 @@ sections: - 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 elicit: true - template: '{{epic_goal}}' + template: "{{epic_goal}}" sections: - id: story title: Story {{epic_number}}.{{story_number}} {{story_title}} @@ -4374,7 +4374,7 @@ sections: - id: acceptance-criteria title: Acceptance Criteria type: numbered-list - item_template: '{{criterion_number}}: {{criteria}}' + item_template: "{{criterion_number}}: {{criteria}}" repeatable: true instruction: | Define clear, comprehensive, and testable acceptance criteria that: @@ -4409,7 +4409,7 @@ template: output: format: markdown filename: docs/prd.md - title: '{{project_name}} Brownfield Enhancement PRD' + title: "{{project_name}} Brownfield Enhancement PRD" workflow: mode: interactive @@ -4472,7 +4472,7 @@ sections: - External API Documentation [[LLM: If from document-project, check ✓]] - UX/UI Guidelines [[LLM: May not be in document-project]] - Technical Debt Documentation [[LLM: If from document-project, check ✓]] - - 'Other: {{other_docs}}' + - "Other: {{other_docs}}" instruction: | - If document-project was already run: "Using existing project analysis from document-project output." - If critical documentation is missing and no document-project: "I recommend running the document-project task first..." @@ -4492,7 +4492,7 @@ sections: - UI/UX Overhaul - Technology Stack Upgrade - Bug Fix and Stability Improvements - - 'Other: {{other_type}}' + - "Other: {{other_type}}" - id: enhancement-description title: Enhancement Description instruction: 2-3 sentences describing what the user wants to add or change @@ -4533,29 +4533,29 @@ sections: prefix: FR instruction: Each Requirement will be a bullet markdown with identifier starting with FR examples: - - 'FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality.' + - "FR1: The existing Todo List will integrate with the new AI duplicate detection service without breaking current functionality." - id: non-functional title: Non Functional type: numbered-list prefix: NFR instruction: Each Requirement will be a bullet markdown with identifier starting with NFR. Include constraints from existing system examples: - - 'NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%.' + - "NFR1: Enhancement must maintain existing performance characteristics and not exceed current memory usage by more than 20%." - id: compatibility title: Compatibility Requirements instruction: Critical for brownfield - what must remain compatible type: numbered-list prefix: CR - template: '{{requirement}}: {{description}}' + template: "{{requirement}}: {{description}}" items: - id: cr1 - template: 'CR1: {{existing_api_compatibility}}' + template: "CR1: {{existing_api_compatibility}}" - id: cr2 - template: 'CR2: {{database_schema_compatibility}}' + template: "CR2: {{database_schema_compatibility}}" - id: cr3 - template: 'CR3: {{ui_ux_consistency}}' + template: "CR3: {{ui_ux_consistency}}" - id: cr4 - template: 'CR4: {{integration_compatibility}}' + template: "CR4: {{integration_compatibility}}" - id: ui-enhancement-goals title: User Interface Enhancement Goals @@ -4638,10 +4638,10 @@ sections: - id: epic-approach title: Epic Approach instruction: Explain the rationale for epic structure - typically single epic for brownfield unless multiple unrelated features - template: '**Epic Structure Decision**: {{epic_decision}} with rationale' + template: "**Epic Structure Decision**: {{epic_decision}} with rationale" - id: epic-details - title: 'Epic 1: {{enhancement_title}}' + title: "Epic 1: {{enhancement_title}}" instruction: | Comprehensive epic that delivers the brownfield enhancement while maintaining existing functionality @@ -4661,7 +4661,7 @@ sections: **Integration Requirements**: {{integration_requirements}} sections: - id: story - title: 'Story 1.{{story_number}} {{story_title}}' + title: "Story 1.{{story_number}} {{story_title}}" repeatable: true template: | As a {{user_type}}, @@ -4672,16 +4672,16 @@ sections: title: Acceptance Criteria type: numbered-list instruction: Define criteria that include both new functionality and existing system integrity - item_template: '{{criterion_number}}: {{criteria}}' + item_template: "{{criterion_number}}: {{criteria}}" - id: integration-verification title: Integration Verification instruction: Specific verification steps to ensure existing functionality remains intact type: numbered-list prefix: IV items: - - template: 'IV1: {{existing_functionality_verification}}' - - template: 'IV2: {{integration_point_verification}}' - - template: 'IV3: {{performance_impact_verification}}' + - template: "IV1: {{existing_functionality_verification}}" + - template: "IV2: {{integration_point_verification}}" + - template: "IV3: {{performance_impact_verification}}" ==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ==================== ==================== START: .bmad-core/checklists/pm-checklist.md ==================== @@ -5256,7 +5256,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Architecture Document' + title: "{{project_name}} Architecture Document" workflow: mode: interactive @@ -5367,11 +5367,11 @@ sections: - Code organization patterns (Dependency Injection, Repository, Module, Factory) - Data patterns (Event Sourcing, Saga, Database per Service) - Communication patterns (REST, GraphQL, Message Queue, Pub/Sub) - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - - '**Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling' - - '**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility' - - '**Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience' + - "**Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling" + - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility" + - "**Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience" - id: tech-stack title: Tech Stack @@ -5409,9 +5409,9 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Populate the technology stack table with all relevant technologies examples: - - '| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |' - - '| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |' - - '| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |' + - "| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |" + - "| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |" + - "| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |" - id: data-models title: Data Models @@ -5429,7 +5429,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -5460,7 +5460,7 @@ sections: sections: - id: component-list repeatable: true - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} @@ -5498,7 +5498,7 @@ sections: repeatable: true sections: - id: api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -5623,12 +5623,12 @@ sections: - id: environments title: Environments repeatable: true - template: '- **{{env_name}}:** {{env_purpose}} - {{env_details}}' + template: "- **{{env_name}}:** {{env_purpose}} - {{env_details}}" - id: promotion-flow title: Environment Promotion Flow type: code language: text - template: '{{promotion_flow_diagram}}' + template: "{{promotion_flow_diagram}}" - id: rollback-strategy title: Rollback Strategy template: | @@ -5724,16 +5724,16 @@ sections: Avoid obvious rules like "use SOLID principles" or "write clean code" repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" - id: language-specifics title: Language-Specific Guidelines condition: Critical language-specific rules needed instruction: Add ONLY if critical for preventing AI mistakes. Most teams don't need this section. sections: - id: language-rules - title: '{{language_name}} Specifics' + title: "{{language_name}} Specifics" repeatable: true - template: '- **{{rule_topic}}:** {{rule_detail}}' + template: "- **{{rule_topic}}:** {{rule_detail}}" - id: test-strategy title: Test Strategy and Standards @@ -5781,9 +5781,9 @@ sections: - **Test Infrastructure:** - **{{dependency_name}}:** {{test_approach}} ({{test_tool}}) examples: - - '**Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration' - - '**Message Queue:** Embedded Kafka for tests' - - '**External APIs:** WireMock for stubbing' + - "**Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration" + - "**Message Queue:** Embedded Kafka for tests" + - "**External APIs:** WireMock for stubbing" - id: e2e-tests title: End-to-End Tests template: | @@ -5909,7 +5909,7 @@ template: output: format: markdown filename: docs/ui-architecture.md - title: '{{project_name}} Frontend Architecture Document' + title: "{{project_name}} Frontend Architecture Document" workflow: mode: interactive @@ -5977,29 +5977,29 @@ sections: columns: [Category, Technology, Version, Purpose, Rationale] instruction: Fill in appropriate technology choices based on the selected framework and project requirements. rows: - - ['Framework', '{{framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['UI Library', '{{ui_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Framework", "{{framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["UI Library", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'State Management', - '{{state_management}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "State Management", + "{{state_management}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['Routing', '{{routing_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Build Tool', '{{build_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Styling', '{{styling_solution}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Testing', '{{test_framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Routing", "{{routing_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Styling", "{{styling_solution}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Testing", "{{test_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Component Library', - '{{component_lib}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Component Library", + "{{component_lib}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['Form Handling', '{{form_library}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Animation', '{{animation_lib}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Dev Tools', '{{dev_tools}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Form Handling", "{{form_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Animation", "{{animation_lib}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Dev Tools", "{{dev_tools}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - id: project-structure title: Project Structure @@ -6093,12 +6093,12 @@ sections: title: Testing Best Practices type: numbered-list items: - - '**Unit Tests**: Test individual components in isolation' - - '**Integration Tests**: Test component interactions' - - '**E2E Tests**: Test critical user flows (using Cypress/Playwright)' - - '**Coverage Goals**: Aim for 80% code coverage' - - '**Test Structure**: Arrange-Act-Assert pattern' - - '**Mock External Dependencies**: API calls, routing, state management' + - "**Unit Tests**: Test individual components in isolation" + - "**Integration Tests**: Test component interactions" + - "**E2E Tests**: Test critical user flows (using Cypress/Playwright)" + - "**Coverage Goals**: Aim for 80% code coverage" + - "**Test Structure**: Arrange-Act-Assert pattern" + - "**Mock External Dependencies**: API calls, routing, state management" - id: environment-configuration title: Environment Configuration @@ -6130,7 +6130,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Fullstack Architecture Document' + title: "{{project_name}} Fullstack Architecture Document" workflow: mode: interactive @@ -6251,12 +6251,12 @@ sections: For each pattern, provide recommendation and rationale. repeatable: true - template: '- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}' + template: "- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}" examples: - - '**Jamstack Architecture:** Static site generation with serverless APIs - _Rationale:_ Optimal performance and scalability for content-heavy applications' - - '**Component-Based UI:** Reusable React components with TypeScript - _Rationale:_ Maintainability and type safety across large codebases' - - '**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility' - - '**API Gateway Pattern:** Single entry point for all API calls - _Rationale:_ Centralized auth, rate limiting, and monitoring' + - "**Jamstack Architecture:** Static site generation with serverless APIs - _Rationale:_ Optimal performance and scalability for content-heavy applications" + - "**Component-Based UI:** Reusable React components with TypeScript - _Rationale:_ Maintainability and type safety across large codebases" + - "**Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility" + - "**API Gateway Pattern:** Single entry point for all API calls - _Rationale:_ Centralized auth, rate limiting, and monitoring" - id: tech-stack title: Tech Stack @@ -6280,45 +6280,45 @@ sections: type: table columns: [Category, Technology, Version, Purpose, Rationale] rows: - - ['Frontend Language', '{{fe_language}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["Frontend Language", "{{fe_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Frontend Framework', - '{{fe_framework}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Frontend Framework", + "{{fe_framework}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - [ - 'UI Component Library', - '{{ui_library}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "UI Component Library", + "{{ui_library}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['State Management', '{{state_mgmt}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Backend Language', '{{be_language}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["State Management", "{{state_mgmt}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Backend Language", "{{be_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - [ - 'Backend Framework', - '{{be_framework}}', - '{{version}}', - '{{purpose}}', - '{{why_chosen}}', + "Backend Framework", + "{{be_framework}}", + "{{version}}", + "{{purpose}}", + "{{why_chosen}}", ] - - ['API Style', '{{api_style}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Database', '{{database}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Cache', '{{cache}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['File Storage', '{{storage}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Authentication', '{{auth}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Frontend Testing', '{{fe_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Backend Testing', '{{be_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['E2E Testing', '{{e2e_test}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Build Tool', '{{build_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Bundler', '{{bundler}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['IaC Tool', '{{iac_tool}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['CI/CD', '{{cicd}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Monitoring', '{{monitoring}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['Logging', '{{logging}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] - - ['CSS Framework', '{{css_framework}}', '{{version}}', '{{purpose}}', '{{why_chosen}}'] + - ["API Style", "{{api_style}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Database", "{{database}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Cache", "{{cache}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["File Storage", "{{storage}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Authentication", "{{auth}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Frontend Testing", "{{fe_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Backend Testing", "{{be_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["E2E Testing", "{{e2e_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Bundler", "{{bundler}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["IaC Tool", "{{iac_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["CI/CD", "{{cicd}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Monitoring", "{{monitoring}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["Logging", "{{logging}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] + - ["CSS Framework", "{{css_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"] - id: data-models title: Data Models @@ -6337,7 +6337,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} @@ -6349,11 +6349,11 @@ sections: title: TypeScript Interface type: code language: typescript - template: '{{model_interface}}' + template: "{{model_interface}}" - id: relationships title: Relationships type: bullet-list - template: '- {{relationship}}' + template: "- {{relationship}}" - id: api-spec title: API Specification @@ -6390,13 +6390,13 @@ sections: condition: API style is GraphQL type: code language: graphql - template: '{{graphql_schema}}' + template: "{{graphql_schema}}" - id: trpc-api title: tRPC Router Definitions condition: API style is tRPC type: code language: typescript - template: '{{trpc_routers}}' + template: "{{trpc_routers}}" - id: components title: Components @@ -6417,7 +6417,7 @@ sections: sections: - id: component-list repeatable: true - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} @@ -6455,7 +6455,7 @@ sections: repeatable: true sections: - id: api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -6512,12 +6512,12 @@ sections: title: Component Organization type: code language: text - template: '{{component_structure}}' + template: "{{component_structure}}" - id: component-template title: Component Template type: code language: typescript - template: '{{component_template}}' + template: "{{component_template}}" - id: state-management title: State Management Architecture instruction: Detail state management approach based on chosen solution. @@ -6526,11 +6526,11 @@ sections: title: State Structure type: code language: typescript - template: '{{state_structure}}' + template: "{{state_structure}}" - id: state-patterns title: State Management Patterns type: bullet-list - template: '- {{pattern}}' + template: "- {{pattern}}" - id: routing-architecture title: Routing Architecture instruction: Define routing structure based on framework choice. @@ -6539,12 +6539,12 @@ sections: title: Route Organization type: code language: text - template: '{{route_structure}}' + template: "{{route_structure}}" - id: protected-routes title: Protected Route Pattern type: code language: typescript - template: '{{protected_route_example}}' + template: "{{protected_route_example}}" - id: frontend-services title: Frontend Services Layer instruction: Define how frontend communicates with backend. @@ -6553,12 +6553,12 @@ sections: title: API Client Setup type: code language: typescript - template: '{{api_client_setup}}' + template: "{{api_client_setup}}" - id: service-example title: Service Example type: code language: typescript - template: '{{service_example}}' + template: "{{service_example}}" - id: backend-architecture title: Backend Architecture @@ -6576,12 +6576,12 @@ sections: title: Function Organization type: code language: text - template: '{{function_structure}}' + template: "{{function_structure}}" - id: function-template title: Function Template type: code language: typescript - template: '{{function_template}}' + template: "{{function_template}}" - id: traditional-server condition: Traditional server architecture chosen sections: @@ -6589,12 +6589,12 @@ sections: title: Controller/Route Organization type: code language: text - template: '{{controller_structure}}' + template: "{{controller_structure}}" - id: controller-template title: Controller Template type: code language: typescript - template: '{{controller_template}}' + template: "{{controller_template}}" - id: database-architecture title: Database Architecture instruction: Define database schema and access patterns. @@ -6603,12 +6603,12 @@ sections: title: Schema Design type: code language: sql - template: '{{database_schema}}' + template: "{{database_schema}}" - id: data-access-layer title: Data Access Layer type: code language: typescript - template: '{{repository_pattern}}' + template: "{{repository_pattern}}" - id: auth-architecture title: Authentication and Authorization instruction: Define auth implementation details. @@ -6617,12 +6617,12 @@ sections: title: Auth Flow type: mermaid mermaid_type: sequence - template: '{{auth_flow_diagram}}' + template: "{{auth_flow_diagram}}" - id: auth-middleware title: Middleware/Guards type: code language: typescript - template: '{{auth_middleware}}' + template: "{{auth_middleware}}" - id: unified-project-structure title: Unified Project Structure @@ -6698,12 +6698,12 @@ sections: title: Prerequisites type: code language: bash - template: '{{prerequisites_commands}}' + template: "{{prerequisites_commands}}" - id: initial-setup title: Initial Setup type: code language: bash - template: '{{setup_commands}}' + template: "{{setup_commands}}" - id: dev-commands title: Development Commands type: code @@ -6759,15 +6759,15 @@ sections: title: CI/CD Pipeline type: code language: yaml - template: '{{cicd_pipeline_config}}' + template: "{{cicd_pipeline_config}}" - id: environments title: Environments type: table columns: [Environment, Frontend URL, Backend URL, Purpose] rows: - - ['Development', '{{dev_fe_url}}', '{{dev_be_url}}', 'Local development'] - - ['Staging', '{{staging_fe_url}}', '{{staging_be_url}}', 'Pre-production testing'] - - ['Production', '{{prod_fe_url}}', '{{prod_be_url}}', 'Live environment'] + - ["Development", "{{dev_fe_url}}", "{{dev_be_url}}", "Local development"] + - ["Staging", "{{staging_fe_url}}", "{{staging_be_url}}", "Pre-production testing"] + - ["Production", "{{prod_fe_url}}", "{{prod_be_url}}", "Live environment"] - id: security-performance title: Security and Performance @@ -6826,17 +6826,17 @@ sections: title: Frontend Tests type: code language: text - template: '{{frontend_test_structure}}' + template: "{{frontend_test_structure}}" - id: backend-tests title: Backend Tests type: code language: text - template: '{{backend_test_structure}}' + template: "{{backend_test_structure}}" - id: e2e-tests title: E2E Tests type: code language: text - template: '{{e2e_test_structure}}' + template: "{{e2e_test_structure}}" - id: test-examples title: Test Examples sections: @@ -6844,17 +6844,17 @@ sections: title: Frontend Component Test type: code language: typescript - template: '{{frontend_test_example}}' + template: "{{frontend_test_example}}" - id: backend-test title: Backend API Test type: code language: typescript - template: '{{backend_test_example}}' + template: "{{backend_test_example}}" - id: e2e-test title: E2E Test type: code language: typescript - template: '{{e2e_test_example}}' + template: "{{e2e_test_example}}" - id: coding-standards title: Coding Standards @@ -6864,22 +6864,22 @@ sections: - id: critical-rules title: Critical Fullstack Rules repeatable: true - template: '- **{{rule_name}}:** {{rule_description}}' + template: "- **{{rule_name}}:** {{rule_description}}" examples: - - '**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' + - "**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" - id: naming-conventions title: Naming Conventions type: table columns: [Element, Frontend, Backend, Example] rows: - - ['Components', 'PascalCase', '-', '`UserProfile.tsx`'] - - ['Hooks', "camelCase with 'use'", '-', '`useAuth.ts`'] - - ['API Routes', '-', 'kebab-case', '`/api/user-profile`'] - - ['Database Tables', '-', 'snake_case', '`user_profiles`'] + - ["Components", "PascalCase", "-", "`UserProfile.tsx`"] + - ["Hooks", "camelCase with 'use'", "-", "`useAuth.ts`"] + - ["API Routes", "-", "kebab-case", "`/api/user-profile`"] + - ["Database Tables", "-", "snake_case", "`user_profiles`"] - id: error-handling title: Error Handling Strategy @@ -6890,7 +6890,7 @@ sections: title: Error Flow type: mermaid mermaid_type: sequence - template: '{{error_flow_diagram}}' + template: "{{error_flow_diagram}}" - id: error-format title: Error Response Format type: code @@ -6909,12 +6909,12 @@ sections: title: Frontend Error Handling type: code language: typescript - template: '{{frontend_error_handler}}' + template: "{{frontend_error_handler}}" - id: backend-error-handling title: Backend Error Handling type: code language: typescript - template: '{{backend_error_handler}}' + template: "{{backend_error_handler}}" - id: monitoring title: Monitoring and Observability @@ -6956,7 +6956,7 @@ template: output: format: markdown filename: docs/architecture.md - title: '{{project_name}} Brownfield Enhancement Architecture' + title: "{{project_name}} Brownfield Enhancement Architecture" workflow: mode: interactive @@ -7014,11 +7014,11 @@ sections: - id: available-docs title: Available Documentation type: bullet-list - template: '- {{existing_docs_summary}}' + template: "- {{existing_docs_summary}}" - id: constraints title: Identified Constraints type: bullet-list - template: '- {{constraint}}' + template: "- {{constraint}}" - id: changelog title: Change Log type: table @@ -7098,7 +7098,7 @@ sections: repeatable: true sections: - id: model - title: '{{model_name}}' + title: "{{model_name}}" template: | **Purpose:** {{model_purpose}} **Integration:** {{integration_with_existing}} @@ -7141,7 +7141,7 @@ sections: repeatable: true sections: - id: component - title: '{{component_name}}' + title: "{{component_name}}" template: | **Responsibility:** {{component_description}} **Integration Points:** {{integration_points}} @@ -7184,7 +7184,7 @@ sections: repeatable: true sections: - id: endpoint - title: '{{endpoint_name}}' + title: "{{endpoint_name}}" template: | - **Method:** {{http_method}} - **Endpoint:** {{endpoint_path}} @@ -7195,12 +7195,12 @@ sections: title: Request type: code language: json - template: '{{request_schema}}' + template: "{{request_schema}}" - id: response title: Response type: code language: json - template: '{{response_schema}}' + template: "{{response_schema}}" - id: external-api-integration title: External API Integration @@ -7209,7 +7209,7 @@ sections: repeatable: true sections: - id: external-api - title: '{{api_name}} API' + title: "{{api_name}} API" template: | - **Purpose:** {{api_purpose}} - **Documentation:** {{api_docs_url}} @@ -7238,7 +7238,7 @@ sections: type: code language: plaintext instruction: Document relevant parts of current structure - template: '{{existing_structure_relevant_parts}}' + template: "{{existing_structure_relevant_parts}}" - id: new-file-organization title: New File Organization type: code @@ -7313,7 +7313,7 @@ sections: title: Enhancement-Specific Standards condition: New patterns needed for enhancement repeatable: true - template: '- **{{standard_name}}:** {{standard_description}}' + template: "- **{{standard_name}}:** {{standard_description}}" - id: integration-rules title: Critical Integration Rules template: | @@ -8013,7 +8013,7 @@ template: output: format: markdown filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md - title: 'Story {{epic_num}}.{{story_num}}: {{story_title_short}}' + title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}" workflow: mode: interactive @@ -8115,7 +8115,7 @@ sections: sections: - id: agent-model title: Agent Model Used - template: '{{agent_model_name_version}}' + template: "{{agent_model_name_version}}" instruction: Record the specific AI agent model and version used for development owner: dev-agent editors: [dev-agent] @@ -8620,17 +8620,17 @@ workflow: updates: prd.md (if needed) requires: architecture.md condition: architecture_suggests_prd_changes - notes: 'If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder.' + notes: "If architect suggests story changes, update PRD and re-export the complete unredacted prd.md to docs/ folder." - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for consistency and completeness. May require updates to any document.' + notes: "Validates all documents for consistency and completeness. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - agent: po action: shard_documents @@ -8780,13 +8780,13 @@ workflow: - Enterprise or external-facing APIs handoff_prompts: - analyst_to_pm: 'Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD.' - pm_to_architect: 'PRD is ready. Save it as docs/prd.md in your project, then create the service architecture.' - architect_review: 'Architecture complete. Save it as docs/architecture.md. Do you suggest any changes to the PRD stories or need new stories added?' - architect_to_pm: 'Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/.' - updated_to_po: 'All documents ready in docs/ folder. Please validate all artifacts for consistency.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD." + pm_to_architect: "PRD is ready. Save it as docs/prd.md in your project, then create the service architecture." + architect_review: "Architecture complete. Save it as docs/architecture.md. Do you suggest any changes to the PRD stories or need new stories added?" + architect_to_pm: "Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/." + updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/greenfield-service.yaml ==================== ==================== START: .bmad-core/workflows/brownfield-service.yaml ==================== @@ -8809,7 +8809,7 @@ workflow: agent: architect action: analyze existing project and use task document-project creates: multiple documents per the document-project template - notes: 'Review existing service documentation, codebase, performance metrics, and identify integration dependencies.' + notes: "Review existing service documentation, codebase, performance metrics, and identify integration dependencies." - agent: pm creates: prd.md @@ -8826,12 +8826,12 @@ workflow: - agent: po validates: all_artifacts uses: po-master-checklist - notes: 'Validates all documents for service integration safety and API compatibility. May require updates to any document.' + notes: "Validates all documents for service integration safety and API compatibility. May require updates to any document." - agent: various updates: any_flagged_documents condition: po_checklist_issues - notes: 'If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder.' + notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder." - agent: po action: shard_documents @@ -8972,9 +8972,9 @@ workflow: - Multiple integration points affected handoff_prompts: - analyst_to_pm: 'Service analysis complete. Create comprehensive PRD with service integration strategy.' - pm_to_architect: 'PRD ready. Save it as docs/prd.md, then create the service architecture.' - architect_to_po: 'Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for service integration safety.' - po_issues: 'PO found issues with [document]. Please return to [agent] to fix and re-save the updated document.' - complete: 'All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development.' + analyst_to_pm: "Service analysis complete. Create comprehensive PRD with service integration strategy." + pm_to_architect: "PRD ready. Save it as docs/prd.md, then create the service architecture." + architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for service integration safety." + po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document." + complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development." ==================== END: .bmad-core/workflows/brownfield-service.yaml ==================== diff --git a/package.json b/package.json index f078562b..42063f8b 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "bmad-method", - "version": "5.0.0", + "version": "5.0.1", "description": "Breakthrough Method of Agile AI-driven Development", "keywords": [ "agile", diff --git a/tools/installer/package.json b/tools/installer/package.json index 5fa1e4a1..ea92a7bb 100644 --- a/tools/installer/package.json +++ b/tools/installer/package.json @@ -1,6 +1,6 @@ { "name": "bmad-method", - "version": "5.1.0", + "version": "5.0.1", "description": "BMad Method installer - AI-powered Agile development framework", "keywords": [ "bmad",