bmad-method 4.2.0 → 4.4.1

package/{.bmad-core → bmad-core}/tasks/index-docs.md

@@ -56,7 +56,7 @@ You are now operating as a Documentation Indexer. Your goal is to ensure all doc
 
 The index should be organized as follows:
 
-```markdown
+`````markdown
 # Documentation Index
 
 ## Root Documents
@@ -88,7 +88,8 @@ Documents within the `another-folder/` directory:
 ### [Nested Document](./another-folder/document.md)
 
 Description of nested document.
-```text
+
+````text
 
 ### Index Entry Format
 
@@ -98,7 +99,10 @@ Each entry should follow this format:
 ### [Document Title](relative/path/to/file.md)
 
 Brief description of the document's purpose and contents.
-```
+````
+`````
+
+````
 
 ### Rules of Operation
 
@@ -176,3 +180,4 @@ Please provide:
 5. Whether to include hidden files/folders (starting with `.`)
 
 Would you like to proceed with documentation indexing? Please provide the required input above.
+````

package/{.bmad-core → bmad-core}/tasks/shard-doc.md

@@ -101,7 +101,7 @@ Create an `index.md` file in the sharded folder that:
 1. Contains the original level 1 heading and any content before the first level 2 section
 2. Lists all the sharded files with links:
 
-```markdown
+````markdown
 # Original Document Title
 
 [Original introduction content if any]
@@ -112,7 +112,8 @@ Create an `index.md` file in the sharded folder that:
 - [Section Name 2](./section-name-2.md)
 - [Section Name 3](./section-name-3.md)
   ...
-```
+
+````text
 
 ### 5. Preserve Special Content
 
@@ -122,7 +123,8 @@ Create an `index.md` file in the sharded folder that:
 
    ```language
    content
-   ```
+````
+````
 
 2. **Mermaid diagrams**: Preserve complete syntax:
 

package/{.bmad-core → bmad-core}/templates/architecture-tmpl.md

@@ -136,7 +136,7 @@ Common patterns to consider:
 
 [[LLM: This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
 
-1. Review PRD technical assumptions and any preferences from `data#technical-preferences`
+1. Review PRD technical assumptions and any preferences from `data#technical-preferences` or an attached `technical-preferences`
 2. For each category, present 2-3 viable options with pros/cons
 3. Make a clear recommendation based on project needs
 4. Get explicit user approval for each selection
@@ -341,18 +341,21 @@ Use YAML format for better readability. If no REST API, skip this section.]]
 
 ^^CONDITION: has_rest_api^^
 
-```yaml
+````yaml
 openapi: 3.0.0
 info:
-  title: { { api_title } }
-  version: { { api_version } }
-  description: { { api_description } }
-
+  title:
+    '[object Object]': null
+  version:
+    '[object Object]': null
+  description:
+    '[object Object]': null
 servers:
-  - url: { { api_base_url } }
-    description: { { environment } }
-# ... OpenAPI specification continues
-```
+  - url:
+      '[object Object]': null
+    description:
+      '[object Object]': null
+```text
 
 ^^/CONDITION: has_rest_api^^
 
@@ -415,7 +418,7 @@ After presenting the structure, apply `tasks#advanced-elicitation` protocol to r
 ├── {{package-manifest}}        # Dependencies manifest
 ├── {{config-files}}            # Language/framework configs
 └── README.md                   # Project documentation
-```
+```text
 
 @{example: monorepo-structure}
 project-root/
@@ -463,9 +466,9 @@ Get user input on deployment preferences and CI/CD tool choices.]]
 
 ### Environment Promotion Flow
 
-```
+```text
 {{promotion_flow_diagram}}
-```
+````
 
 ### Rollback Strategy
 

package/{.bmad-core → bmad-core}/templates/brownfield-architecture-tmpl.md

@@ -222,9 +222,9 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]
 
 [[LLM: Create Mermaid diagram showing how new components interact with existing ones]]
 
-```mermaid
+````mermaid
 {{component_interaction_diagram}}
-```
+```text
 
 ## API Design and Integration
 
@@ -258,13 +258,13 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]
 
 ```json
 {{request_schema}}
-```
+````
 
 **Response:**
 
-```json
+````json
 {{response_schema}}
-```
+```text
 
 <</REPEAT>>
 
@@ -313,7 +313,7 @@ Present integration plan and apply `tasks#advanced-elicitation` protocol]]
 
 ```plaintext
 {{existing_structure_relevant_parts}}
-```
+````
 
 ### New File Organization
 

package/{.bmad-core → bmad-core}/templates/front-end-spec-tmpl.md

@@ -74,9 +74,9 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ### Site Map / Screen Inventory
 
-```mermaid
+````mermaid
 {{sitemap_diagram}}
-```
+```text
 
 @{example: sitemap}
 
@@ -93,7 +93,7 @@ graph TD
     D --> D1[Profile]
     D --> D2[Settings]
     D --> D3[Billing]
-```
+````
 
 @{/example}
 
@@ -129,9 +129,9 @@ Create subsections for each major flow. After presenting all flows, apply `tasks
 
 #### Flow Diagram
 
-```mermaid
+````mermaid
 {{flow_diagram}}
-```
+```text
 
 **Edge Cases & Error Handling:**
 
@@ -165,7 +165,7 @@ graph TD
     Validate -->|Yes| Verify[Email Verification]
     Verify --> Complete[Account Created]
     Complete --> Dashboard[Redirect to Dashboard]
-```
+````
 
 **Edge Cases & Error Handling:**
 

package/{.bmad-core → bmad-core}/templates/fullstack-architecture-tmpl.md

@@ -109,9 +109,9 @@ Document the choice and key services that will be used.]]
 
 Use appropriate diagram type for clarity.]]
 
-```mermaid
+````mermaid
 {{architecture_diagram}}
-```
+```text
 
 ### Architectural Patterns
 
@@ -222,7 +222,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
     model_interface;
   }
 }
-```
+````
 
 **Relationships:**
 
@@ -246,7 +246,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
 
 **TypeScript Interface:**
 
-```typescript
+````typescript
 interface User {
   id: string;
   email: string;
@@ -262,7 +262,7 @@ interface UserProfile {
   bio?: string;
   preferences: Record<string, any>;
 }
-```
+```text
 
 **Relationships:**
 
@@ -286,27 +286,30 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),
 
 ^^CONDITION: has_rest_api^^
 
-```yaml
+```yml
 openapi: 3.0.0
 info:
-  title: { { api_title } }
-  version: { { api_version } }
-  description: { { api_description } }
-
+  title:
+    '[object Object]': null
+  version:
+    '[object Object]': null
+  description:
+    '[object Object]': null
 servers:
-  - url: { { api_base_url } }
-    description: { { environment } }
-# ... OpenAPI specification continues
-```
+  - url:
+      '[object Object]': null
+    description:
+      '[object Object]': null
+````
 
 ^^/CONDITION: has_rest_api^^
 
 ^^CONDITION: has_graphql_api^^
 
-```graphql
+````graphql
 # GraphQL Schema
 {{graphql_schema}}
-```
+```text
 
 ^^/CONDITION: has_graphql_api^^
 
@@ -319,7 +322,7 @@ servers:
     trpc_routers;
   }
 }
-```
+````
 
 ^^/CONDITION: has_trpc_api^^
 
@@ -464,19 +467,19 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 **Component Organization:**
 
-```
+`````text
 {{component_structure}}
-```
+```text
 
 **Component Template:**
 
-```typescript
+````typescript
 {
   {
     component_template;
   }
 }
-```
+```text
 
 ### State Management Architecture
 
@@ -490,7 +493,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
     state_structure;
   }
 }
-```
+`````
 
 **State Management Patterns:**
 
@@ -503,19 +506,19 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 **Route Organization:**
 
-```
+`````text
 {{route_structure}}
-```
+```text
 
 **Protected Route Pattern:**
 
-```typescript
+````typescript
 {
   {
     protected_route_example;
   }
 }
-```
+```text
 
 ### Frontend Services Layer
 
@@ -529,17 +532,17 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
     api_client_setup;
   }
 }
-```
+`````
 
 **Service Example:**
 
-```typescript
+````typescript
 {
   {
     service_example;
   }
 }
-```
+```text
 
 ## Backend Architecture
 
@@ -554,9 +557,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 ^^CONDITION: serverless^^
 **Function Organization:**
 
-```
+````
+
 {{function_structure}}
-```
+
+````text
 
 **Function Template:**
 
@@ -566,26 +571,26 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
     function_template;
   }
 }
-```
+````
 
 ^^/CONDITION: serverless^^
 
 ^^CONDITION: traditional_server^^
 **Controller/Route Organization:**
 
-```
+`````text
 {{controller_structure}}
-```
+```text
 
 **Controller Template:**
 
-```typescript
+````typescript
 {
   {
     controller_template;
   }
 }
-```
+```text
 
 ^^/CONDITION: traditional_server^^
 
@@ -597,17 +602,17 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ```sql
 {{database_schema}}
-```
+`````
 
 **Data Access Layer:**
 
-```typescript
+````typescript
 {
   {
     repository_pattern;
   }
 }
-```
+```text
 
 ### Authentication and Authorization
 
@@ -617,17 +622,17 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{auth_flow_diagram}}
-```
+````
 
 **Middleware/Guards:**
 
-```typescript
+````typescript
 {
   {
     auth_middleware;
   }
 }
-```
+```text
 
 ## Unified Project Structure
 
@@ -687,7 +692,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 ├── package.json                # Root package.json
 ├── {{monorepo_config}}         # Monorepo configuration
 └── README.md
-```
+````
 
 @{example: vercel_structure}
 apps/
@@ -709,19 +714,19 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 **Prerequisites:**
 
-```bash
+````bash
 {{prerequisites_commands}}
-```
+```text
 
 **Initial Setup:**
 
 ```bash
 {{setup_commands}}
-```
+````
 
 **Development Commands:**
 
-```bash
+````bash
 # Start all services
 {{start_all_command}}
 
@@ -733,7 +738,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 # Run tests
 {{test_commands}}
-```
+```text
 
 ### Environment Configuration
 
@@ -748,7 +753,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 # Shared
 {{shared_env_vars}}
-```
+````
 
 ## Deployment Architecture
 
@@ -771,9 +776,9 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ### CI/CD Pipeline
 
-```yaml
-{ { cicd_pipeline_config } }
-```
+````yaml
+'[object Object]': null
+```text
 
 ### Environments
 
@@ -831,33 +836,42 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ### Testing Pyramid
 
-```
+````
+
         E2E Tests
        /          \
     Integration Tests
-   /                  \
- Frontend Unit    Backend Unit
-```
+
+/ \
+ Frontend Unit Backend Unit
+
+```text
 
 ### Test Organization
 
 **Frontend Tests:**
 
 ```
+
 {{frontend_test_structure}}
-```
+
+````text
 
 **Backend Tests:**
 
-```
+```text
+
 {{backend_test_structure}}
-```
+
+```text
 
 **E2E Tests:**
 
-```
+````
+
 {{e2e_test_structure}}
-```
+
+````text
 
 ### Test Examples
 
@@ -869,17 +883,17 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
     frontend_test_example;
   }
 }
-```
+````
 
 **Backend API Test:**
 
-```typescript
+````typescript
 {
   {
     backend_test_example;
   }
 }
-```
+```text
 
 **E2E Test:**
 
@@ -889,7 +903,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
     e2e_test_example;
   }
 }
-```
+````
 
 ## Coding Standards
 
@@ -930,9 +944,9 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ### Error Flow
 
-```mermaid
+````mermaid
 {{error_flow_diagram}}
-```
+```text
 
 ### Error Response Format
 
@@ -946,17 +960,17 @@ interface ApiError {
     requestId: string;
   };
 }
-```
+````
 
 ### Frontend Error Handling
 
-```typescript
+````typescript
 {
   {
     frontend_error_handler;
   }
 }
-```
+```text
 
 ### Backend Error Handling
 
@@ -966,7 +980,7 @@ interface ApiError {
     backend_error_handler;
   }
 }
-```
+````
 
 ## Monitoring and Observability
 
@@ -1000,35 +1014,3 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 ## Checklist Results Report
 
 [[LLM: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the `architect-checklist` and populate results here.]]
-
-## Next Steps
-
-[[LLM: Provide specific next steps for implementation.]]
-
-### Implementation Order
-
-1. **Environment Setup**
-
-   - Initialize monorepo structure
-   - Configure development environment
-   - Set up version control
-
-2. **Foundation (Epic 1)**
-
-   - Implement authentication flow
-   - Set up database schema
-   - Create basic API structure
-   - Implement core UI components
-
-3. **Feature Development**
-   - Follow story sequence from PRD
-   - Maintain type safety across stack
-   - Write tests as you go
-
-### Developer Handoff Prompts
-
-**For Scrum Master:**
-"Create stories for {{Project Name}} using the PRD at docs/prd.md and this fullstack architecture at docs/fullstack-architecture.md. Focus on Epic 1 implementation."
-
-**For Developer:**
-"Implement Story 1.1 from docs/stories/epic1/story-1.1.md using the fullstack architecture at docs/fullstack-architecture.md. Follow the coding standards and use the defined tech stack."

package/{.bmad-core → bmad-core}/templates/prd-tmpl.md

@@ -88,7 +88,7 @@
 
 [[LLM: Gather technical decisions that will guide the Architect. Steps:
 
-1. Check if `data#technical-preferences` file exists - use it to pre-populate choices
+1. Check if `data#technical-preferences` or an attached `technical-preferences` file exists - use it to pre-populate choices
 2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
 3. For unknowns, offer guidance based on project goals and MVP scope
 4. Document ALL technical choices with rationale (why this choice fits the project)