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

feat: improve docs, technical preference usage

Browse Source
This commit is contained in:
Brian Madison
2025-06-15 21:27:37 -05:00
parent ac291c8dbe
commit 764e7702b3
3 changed files with 15 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
.bmad-core/templates/architecture-tmpl.md
View File

@@ -136,7 +136,7 @@ Common patterns to consider:
[[LLM: This is the DEFINITIVE technology selection section. Work with the user to make specific choices: [[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 2. For each category, present 2-3 viable options with pros/cons
3. Make a clear recommendation based on project needs 3. Make a clear recommendation based on project needs
4. Get explicit user approval for each selection 4. Get explicit user approval for each selection
@@ -344,15 +344,18 @@ Use YAML format for better readability. If no REST API, skip this section.]]
```yaml ```yaml
openapi: 3.0.0 openapi: 3.0.0
info: info:
title: { { api_title } } title:
version: { { api_version } } '[object Object]': null
description: { { api_description } } version:
'[object Object]': null
description:
'[object Object]': null
servers: servers:
- url: { { api_base_url } } - url:
description: { { environment } } '[object Object]': null
# ... OpenAPI specification continues description:
``` '[object Object]': null
```text
^^/CONDITION: has_rest_api^^ ^^/CONDITION: has_rest_api^^
@@ -463,7 +466,7 @@ Get user input on deployment preferences and CI/CD tool choices.]]
### Environment Promotion Flow ### Environment Promotion Flow
``` ```text
{{promotion_flow_diagram}} {{promotion_flow_diagram}}
``` ```

2
.bmad-core/templates/prd-tmpl.md
View File

@@ -88,7 +88,7 @@
[[LLM: Gather technical decisions that will guide the Architect. Steps: [[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 2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
3. For unknowns, offer guidance based on project goals and MVP scope 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) 4. Document ALL technical choices with rationale (why this choice fits the project)

2
.bmad-core/templates/simple-project-prd-tmpl.md
View File

@@ -88,7 +88,7 @@
[[LLM: Gather technical decisions that will be used for this simple technical PRD that includes architecture decisions. Steps: [[LLM: Gather technical decisions that will be used for this simple technical PRD that includes architecture decisions. Steps:
1. Check if `data#technical-preferences` file exists - use it to pre-populate choices 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 2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
3. For unknowns, offer guidance based on project goals and MVP scope 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) 4. Document ALL technical choices with rationale (why this choice fits the project)