diff --git a/bmad-core/agents/bmad-master.md b/bmad-core/agents/bmad-master.md index 6d96d24e..d5ae90ed 100644 --- a/bmad-core/agents/bmad-master.md +++ b/bmad-core/agents/bmad-master.md @@ -93,7 +93,6 @@ dependencies: - technical-preferences.md utils: - plan-management.md - - template-format.md - workflow-management.md workflows: - brownfield-fullstack.md diff --git a/bmad-core/agents/bmad-orchestrator.md b/bmad-core/agents/bmad-orchestrator.md index 805697d1..835ef165 100644 --- a/bmad-core/agents/bmad-orchestrator.md +++ b/bmad-core/agents/bmad-orchestrator.md @@ -137,5 +137,4 @@ dependencies: utils: - plan-management.md - workflow-management.md - - template-format.md ``` diff --git a/bmad-core/data/bmad-kb.md b/bmad-core/data/bmad-kb.md index e96053c7..70a17fbd 100644 --- a/bmad-core/data/bmad-kb.md +++ b/bmad-core/data/bmad-kb.md @@ -403,17 +403,10 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor BMad employs a sophisticated template system with three key components: -1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives -2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction +1. **Template Format** (`utils/bmad-doc-template.md`): Defines markup language for variable substitution and AI processing directives from yaml templates +2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction to transform yaml spec to final markdown output 3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming -**Template Features**: - -- **Self-contained**: Templates embed both output structure and processing instructions -- **Variable Substitution**: `{{placeholders}}` for dynamic content -- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing -- **Interactive Refinement**: Built-in elicitation processes for quality improvement - ### Technical Preferences Integration The `technical-preferences.md` file serves as a persistent technical profile that: diff --git a/common/utils/template-format.md b/common/utils/template-format.md deleted file mode 100644 index 0d986ae9..00000000 --- a/common/utils/template-format.md +++ /dev/null @@ -1,26 +0,0 @@ -# Template Format Conventions - -Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation. - -## Template Markup Elements - -- **{{placeholders}}**: Variables to be replaced with actual content -- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users) -- **REPEAT** sections: Content blocks that may be repeated as needed -- **^^CONDITION^^** blocks: Conditional content included only if criteria are met -- **@{examples}**: Example content for guidance (never output to users) - -## Processing Rules - -- Replace all {{placeholders}} with project-specific content -- Execute all [[LLM: instructions]] internally without showing users -- Process conditional and repeat blocks as specified -- Use examples for guidance but never include them in final output -- Present only clean, formatted content to users - -## Critical Guidelines - -- **NEVER display template markup, LLM instructions, or examples to users** -- Template elements are for AI processing only -- Focus on faithful template execution and clean output -- All template-specific instructions are embedded within templates diff --git a/dist/agents/analyst.txt b/dist/agents/analyst.txt index 8dc53f51..24f187e8 100644 --- a/dist/agents/analyst.txt +++ b/dist/agents/analyst.txt @@ -2409,17 +2409,10 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor BMad employs a sophisticated template system with three key components: -1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives -2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction +1. **Template Format** (`utils/bmad-doc-template.md`): Defines markup language for variable substitution and AI processing directives from yaml templates +2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction to transform yaml spec to final markdown output 3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming -**Template Features**: - -- **Self-contained**: Templates embed both output structure and processing instructions -- **Variable Substitution**: `{{placeholders}}` for dynamic content -- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing -- **Interactive Refinement**: Built-in elicitation processes for quality improvement - ### Technical Preferences Integration The `technical-preferences.md` file serves as a persistent technical profile that: diff --git a/dist/agents/architect.txt b/dist/agents/architect.txt index f6fd6bfc..29e6d359 100644 --- a/dist/agents/architect.txt +++ b/dist/agents/architect.txt @@ -1535,7 +1535,6 @@ sections: After completing the architecture: 1. If project has UI components: - - Recommend engaging Design Architect agent - Use "Frontend Architecture Mode" - Provide this document as input @@ -1546,22 +1545,15 @@ sections: 3. Include specific prompts for next agents if needed sections: - - id: design-architect-prompt - title: Design Architect Prompt + - id: architect-prompt + title: Architect Prompt condition: Project has UI components instruction: | - Create a brief prompt to hand off to Design Architect for Frontend Architecture creation. Include: + Create a brief prompt to hand off to Architect for Frontend Architecture creation. Include: - Reference to this architecture document - Key UI requirements from PRD - Any frontend-specific decisions made here - Request for detailed frontend architecture - - id: developer-handoff - title: Developer Handoff - instruction: | - Create a brief prompt for developers starting implementation. Include: - - Reference to this architecture and coding standards - - First epic/story to implement - - Key technical decisions to follow ==================== END: .bmad-core/templates/architecture-tmpl.yaml ==================== ==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ==================== diff --git a/dist/agents/bmad-master.txt b/dist/agents/bmad-master.txt index f5645a8d..94285183 100644 --- a/dist/agents/bmad-master.txt +++ b/dist/agents/bmad-master.txt @@ -127,7 +127,6 @@ dependencies: - technical-preferences.md utils: - plan-management.md - - template-format.md - workflow-management.md workflows: - brownfield-fullstack.md @@ -3318,7 +3317,6 @@ sections: After completing the architecture: 1. If project has UI components: - - Recommend engaging Design Architect agent - Use "Frontend Architecture Mode" - Provide this document as input @@ -3329,22 +3327,15 @@ sections: 3. Include specific prompts for next agents if needed sections: - - id: design-architect-prompt - title: Design Architect Prompt + - id: architect-prompt + title: Architect Prompt condition: Project has UI components instruction: | - Create a brief prompt to hand off to Design Architect for Frontend Architecture creation. Include: + Create a brief prompt to hand off to Architect for Frontend Architecture creation. Include: - Reference to this architecture document - Key UI requirements from PRD - Any frontend-specific decisions made here - Request for detailed frontend architecture - - id: developer-handoff - title: Developer Handoff - instruction: | - Create a brief prompt for developers starting implementation. Include: - - Reference to this architecture and coding standards - - First epic/story to implement - - Key technical decisions to follow ==================== END: .bmad-core/templates/architecture-tmpl.yaml ==================== ==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ==================== @@ -6226,9 +6217,9 @@ sections: - id: next-steps title: Next Steps sections: - - id: design-architect-prompt - title: Design Architect Prompt - instruction: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input. + - id: ux-expert-prompt + title: UX Expert Prompt + instruction: This section will contain the prompt for the UX Expert, keep it short and to the point to initiate create architecture mode using this document as input. - id: architect-prompt title: Architect Prompt instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input. @@ -8720,17 +8711,10 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor BMad employs a sophisticated template system with three key components: -1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives -2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction +1. **Template Format** (`utils/bmad-doc-template.md`): Defines markup language for variable substitution and AI processing directives from yaml templates +2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction to transform yaml spec to final markdown output 3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming -**Template Features**: - -- **Self-contained**: Templates embed both output structure and processing instructions -- **Variable Substitution**: `{{placeholders}}` for dynamic content -- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing -- **Interactive Refinement**: Built-in elicitation processes for quality improvement - ### Technical Preferences Integration The `technical-preferences.md` file serves as a persistent technical profile that: @@ -9531,35 +9515,6 @@ Would you like to: - Parse errors: Fallback to basic text search ==================== END: .bmad-core/utils/plan-management.md ==================== -==================== START: .bmad-core/utils/template-format.md ==================== -# Template Format Conventions - -Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation. - -## Template Markup Elements - -- **{{placeholders}}**: Variables to be replaced with actual content -- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users) -- **REPEAT** sections: Content blocks that may be repeated as needed -- **^^CONDITION^^** blocks: Conditional content included only if criteria are met -- **@{examples}**: Example content for guidance (never output to users) - -## Processing Rules - -- Replace all {{placeholders}} with project-specific content -- Execute all [[LLM: instructions]] internally without showing users -- Process conditional and repeat blocks as specified -- Use examples for guidance but never include them in final output -- Present only clean, formatted content to users - -## Critical Guidelines - -- **NEVER display template markup, LLM instructions, or examples to users** -- Template elements are for AI processing only -- Focus on faithful template execution and clean output -- All template-specific instructions are embedded within templates -==================== END: .bmad-core/utils/template-format.md ==================== - ==================== START: .bmad-core/utils/workflow-management.md ==================== # Workflow Management diff --git a/dist/agents/bmad-orchestrator.txt b/dist/agents/bmad-orchestrator.txt index a002ab86..19357c46 100644 --- a/dist/agents/bmad-orchestrator.txt +++ b/dist/agents/bmad-orchestrator.txt @@ -173,7 +173,6 @@ dependencies: utils: - plan-management.md - workflow-management.md - - template-format.md ``` ==================== END: .bmad-core/agents/bmad-orchestrator.md ==================== @@ -1401,17 +1400,10 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor BMad employs a sophisticated template system with three key components: -1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives -2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction +1. **Template Format** (`utils/bmad-doc-template.md`): Defines markup language for variable substitution and AI processing directives from yaml templates +2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction to transform yaml spec to final markdown output 3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming -**Template Features**: - -- **Self-contained**: Templates embed both output structure and processing instructions -- **Variable Substitution**: `{{placeholders}}` for dynamic content -- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing -- **Interactive Refinement**: Built-in elicitation processes for quality improvement - ### Technical Preferences Integration The `technical-preferences.md` file serves as a persistent technical profile that: @@ -2238,32 +2230,3 @@ Handle conditional paths by asking clarifying questions when needed. Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs. ==================== END: .bmad-core/utils/workflow-management.md ==================== - -==================== START: .bmad-core/utils/template-format.md ==================== -# Template Format Conventions - -Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation. - -## Template Markup Elements - -- **{{placeholders}}**: Variables to be replaced with actual content -- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users) -- **REPEAT** sections: Content blocks that may be repeated as needed -- **^^CONDITION^^** blocks: Conditional content included only if criteria are met -- **@{examples}**: Example content for guidance (never output to users) - -## Processing Rules - -- Replace all {{placeholders}} with project-specific content -- Execute all [[LLM: instructions]] internally without showing users -- Process conditional and repeat blocks as specified -- Use examples for guidance but never include them in final output -- Present only clean, formatted content to users - -## Critical Guidelines - -- **NEVER display template markup, LLM instructions, or examples to users** -- Template elements are for AI processing only -- Focus on faithful template execution and clean output -- All template-specific instructions are embedded within templates -==================== END: .bmad-core/utils/template-format.md ==================== diff --git a/dist/agents/pm.txt b/dist/agents/pm.txt index ff8a869f..ff59e8ce 100644 --- a/dist/agents/pm.txt +++ b/dist/agents/pm.txt @@ -1360,9 +1360,9 @@ sections: - id: next-steps title: Next Steps sections: - - id: design-architect-prompt - title: Design Architect Prompt - instruction: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input. + - id: ux-expert-prompt + title: UX Expert Prompt + instruction: This section will contain the prompt for the UX Expert, keep it short and to the point to initiate create architecture mode using this document as input. - id: architect-prompt title: Architect Prompt instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input. 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 a641e867..ebc5fbb7 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 @@ -254,7 +254,6 @@ dependencies: utils: - plan-management.md - workflow-management.md - - template-format.md ``` ==================== END: .bmad-2d-phaser-game-dev/agents/bmad-orchestrator.md ==================== @@ -3669,35 +3668,6 @@ Handle conditional paths by asking clarifying questions when needed. Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs. ==================== END: .bmad-2d-phaser-game-dev/utils/workflow-management.md ==================== -==================== START: .bmad-2d-phaser-game-dev/utils/template-format.md ==================== -# Template Format Conventions - -Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation. - -## Template Markup Elements - -- **{{placeholders}}**: Variables to be replaced with actual content -- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users) -- **REPEAT** sections: Content blocks that may be repeated as needed -- **^^CONDITION^^** blocks: Conditional content included only if criteria are met -- **@{examples}**: Example content for guidance (never output to users) - -## Processing Rules - -- Replace all {{placeholders}} with project-specific content -- Execute all [[LLM: instructions]] internally without showing users -- Process conditional and repeat blocks as specified -- Use examples for guidance but never include them in final output -- Present only clean, formatted content to users - -## Critical Guidelines - -- **NEVER display template markup, LLM instructions, or examples to users** -- Template elements are for AI processing only -- Focus on faithful template execution and clean output -- All template-specific instructions are embedded within templates -==================== END: .bmad-2d-phaser-game-dev/utils/template-format.md ==================== - ==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ==================== # Checklist Validation Task diff --git a/dist/teams/team-all.txt b/dist/teams/team-all.txt index 6e25906c..836c88e5 100644 --- a/dist/teams/team-all.txt +++ b/dist/teams/team-all.txt @@ -190,7 +190,6 @@ dependencies: utils: - plan-management.md - workflow-management.md - - template-format.md ``` ==================== END: .bmad-core/agents/bmad-orchestrator.md ==================== @@ -1866,17 +1865,10 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor BMad employs a sophisticated template system with three key components: -1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives -2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction +1. **Template Format** (`utils/bmad-doc-template.md`): Defines markup language for variable substitution and AI processing directives from yaml templates +2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction to transform yaml spec to final markdown output 3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming -**Template Features**: - -- **Self-contained**: Templates embed both output structure and processing instructions -- **Variable Substitution**: `{{placeholders}}` for dynamic content -- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing -- **Interactive Refinement**: Built-in elicitation processes for quality improvement - ### Technical Preferences Integration The `technical-preferences.md` file serves as a persistent technical profile that: @@ -2704,35 +2696,6 @@ Handle conditional paths by asking clarifying questions when needed. Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs. ==================== END: .bmad-core/utils/workflow-management.md ==================== -==================== START: .bmad-core/utils/template-format.md ==================== -# Template Format Conventions - -Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation. - -## Template Markup Elements - -- **{{placeholders}}**: Variables to be replaced with actual content -- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users) -- **REPEAT** sections: Content blocks that may be repeated as needed -- **^^CONDITION^^** blocks: Conditional content included only if criteria are met -- **@{examples}**: Example content for guidance (never output to users) - -## Processing Rules - -- Replace all {{placeholders}} with project-specific content -- Execute all [[LLM: instructions]] internally without showing users -- Process conditional and repeat blocks as specified -- Use examples for guidance but never include them in final output -- Present only clean, formatted content to users - -## Critical Guidelines - -- **NEVER display template markup, LLM instructions, or examples to users** -- Template elements are for AI processing only -- Focus on faithful template execution and clean output -- All template-specific instructions are embedded within templates -==================== END: .bmad-core/utils/template-format.md ==================== - ==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ==================== --- docOutputLocation: docs/brainstorming-session-results.md @@ -5197,7 +5160,6 @@ sections: After completing the architecture: 1. If project has UI components: - - Recommend engaging Design Architect agent - Use "Frontend Architecture Mode" - Provide this document as input @@ -5208,22 +5170,15 @@ sections: 3. Include specific prompts for next agents if needed sections: - - id: design-architect-prompt - title: Design Architect Prompt + - id: architect-prompt + title: Architect Prompt condition: Project has UI components instruction: | - Create a brief prompt to hand off to Design Architect for Frontend Architecture creation. Include: + Create a brief prompt to hand off to Architect for Frontend Architecture creation. Include: - Reference to this architecture document - Key UI requirements from PRD - Any frontend-specific decisions made here - Request for detailed frontend architecture - - id: developer-handoff - title: Developer Handoff - instruction: | - Create a brief prompt for developers starting implementation. Include: - - Reference to this architecture and coding standards - - First epic/story to implement - - Key technical decisions to follow ==================== END: .bmad-core/templates/architecture-tmpl.yaml ==================== ==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ==================== @@ -8195,9 +8150,9 @@ sections: - id: next-steps title: Next Steps sections: - - id: design-architect-prompt - title: Design Architect Prompt - instruction: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input. + - id: ux-expert-prompt + title: UX Expert Prompt + instruction: This section will contain the prompt for the UX Expert, keep it short and to the point to initiate create architecture mode using this document as input. - id: architect-prompt title: Architect Prompt instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input. diff --git a/dist/teams/team-fullstack.txt b/dist/teams/team-fullstack.txt index 559b0734..b80bd31e 100644 --- a/dist/teams/team-fullstack.txt +++ b/dist/teams/team-fullstack.txt @@ -194,7 +194,6 @@ dependencies: utils: - plan-management.md - workflow-management.md - - template-format.md ``` ==================== END: .bmad-core/agents/bmad-orchestrator.md ==================== @@ -1724,17 +1723,10 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor BMad employs a sophisticated template system with three key components: -1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives -2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction +1. **Template Format** (`utils/bmad-doc-template.md`): Defines markup language for variable substitution and AI processing directives from yaml templates +2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction to transform yaml spec to final markdown output 3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming -**Template Features**: - -- **Self-contained**: Templates embed both output structure and processing instructions -- **Variable Substitution**: `{{placeholders}}` for dynamic content -- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing -- **Interactive Refinement**: Built-in elicitation processes for quality improvement - ### Technical Preferences Integration The `technical-preferences.md` file serves as a persistent technical profile that: @@ -2562,35 +2554,6 @@ Handle conditional paths by asking clarifying questions when needed. Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs. ==================== END: .bmad-core/utils/workflow-management.md ==================== -==================== START: .bmad-core/utils/template-format.md ==================== -# Template Format Conventions - -Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation. - -## Template Markup Elements - -- **{{placeholders}}**: Variables to be replaced with actual content -- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users) -- **REPEAT** sections: Content blocks that may be repeated as needed -- **^^CONDITION^^** blocks: Conditional content included only if criteria are met -- **@{examples}**: Example content for guidance (never output to users) - -## Processing Rules - -- Replace all {{placeholders}} with project-specific content -- Execute all [[LLM: instructions]] internally without showing users -- Process conditional and repeat blocks as specified -- Use examples for guidance but never include them in final output -- Present only clean, formatted content to users - -## Critical Guidelines - -- **NEVER display template markup, LLM instructions, or examples to users** -- Template elements are for AI processing only -- Focus on faithful template execution and clean output -- All template-specific instructions are embedded within templates -==================== END: .bmad-core/utils/template-format.md ==================== - ==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ==================== --- docOutputLocation: docs/brainstorming-session-results.md @@ -5203,9 +5166,9 @@ sections: - id: next-steps title: Next Steps sections: - - id: design-architect-prompt - title: Design Architect Prompt - instruction: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input. + - id: ux-expert-prompt + title: UX Expert Prompt + instruction: This section will contain the prompt for the UX Expert, keep it short and to the point to initiate create architecture mode using this document as input. - id: architect-prompt title: Architect Prompt instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input. @@ -7101,7 +7064,6 @@ sections: After completing the architecture: 1. If project has UI components: - - Recommend engaging Design Architect agent - Use "Frontend Architecture Mode" - Provide this document as input @@ -7112,22 +7074,15 @@ sections: 3. Include specific prompts for next agents if needed sections: - - id: design-architect-prompt - title: Design Architect Prompt + - id: architect-prompt + title: Architect Prompt condition: Project has UI components instruction: | - Create a brief prompt to hand off to Design Architect for Frontend Architecture creation. Include: + Create a brief prompt to hand off to Architect for Frontend Architecture creation. Include: - Reference to this architecture document - Key UI requirements from PRD - Any frontend-specific decisions made here - Request for detailed frontend architecture - - id: developer-handoff - title: Developer Handoff - instruction: | - Create a brief prompt for developers starting implementation. Include: - - Reference to this architecture and coding standards - - First epic/story to implement - - Key technical decisions to follow ==================== END: .bmad-core/templates/architecture-tmpl.yaml ==================== ==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ==================== diff --git a/dist/teams/team-ide-minimal.txt b/dist/teams/team-ide-minimal.txt index ac80e9cd..e1687f4f 100644 --- a/dist/teams/team-ide-minimal.txt +++ b/dist/teams/team-ide-minimal.txt @@ -186,7 +186,6 @@ dependencies: utils: - plan-management.md - workflow-management.md - - template-format.md ``` ==================== END: .bmad-core/agents/bmad-orchestrator.md ==================== @@ -1623,17 +1622,10 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor BMad employs a sophisticated template system with three key components: -1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives -2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction +1. **Template Format** (`utils/bmad-doc-template.md`): Defines markup language for variable substitution and AI processing directives from yaml templates +2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction to transform yaml spec to final markdown output 3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming -**Template Features**: - -- **Self-contained**: Templates embed both output structure and processing instructions -- **Variable Substitution**: `{{placeholders}}` for dynamic content -- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing -- **Interactive Refinement**: Built-in elicitation processes for quality improvement - ### Technical Preferences Integration The `technical-preferences.md` file serves as a persistent technical profile that: @@ -2461,35 +2453,6 @@ Handle conditional paths by asking clarifying questions when needed. Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs. ==================== END: .bmad-core/utils/workflow-management.md ==================== -==================== START: .bmad-core/utils/template-format.md ==================== -# Template Format Conventions - -Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation. - -## Template Markup Elements - -- **{{placeholders}}**: Variables to be replaced with actual content -- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users) -- **REPEAT** sections: Content blocks that may be repeated as needed -- **^^CONDITION^^** blocks: Conditional content included only if criteria are met -- **@{examples}**: Example content for guidance (never output to users) - -## Processing Rules - -- Replace all {{placeholders}} with project-specific content -- Execute all [[LLM: instructions]] internally without showing users -- Process conditional and repeat blocks as specified -- Use examples for guidance but never include them in final output -- Present only clean, formatted content to users - -## Critical Guidelines - -- **NEVER display template markup, LLM instructions, or examples to users** -- Template elements are for AI processing only -- Focus on faithful template execution and clean output -- All template-specific instructions are embedded within templates -==================== END: .bmad-core/utils/template-format.md ==================== - ==================== START: .bmad-core/tasks/execute-checklist.md ==================== # Checklist Validation Task diff --git a/dist/teams/team-no-ui.txt b/dist/teams/team-no-ui.txt index 5681b6cf..003b0be6 100644 --- a/dist/teams/team-no-ui.txt +++ b/dist/teams/team-no-ui.txt @@ -189,7 +189,6 @@ dependencies: utils: - plan-management.md - workflow-management.md - - template-format.md ``` ==================== END: .bmad-core/agents/bmad-orchestrator.md ==================== @@ -1666,17 +1665,10 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor BMad employs a sophisticated template system with three key components: -1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives -2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction +1. **Template Format** (`utils/bmad-doc-template.md`): Defines markup language for variable substitution and AI processing directives from yaml templates +2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction to transform yaml spec to final markdown output 3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming -**Template Features**: - -- **Self-contained**: Templates embed both output structure and processing instructions -- **Variable Substitution**: `{{placeholders}}` for dynamic content -- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing -- **Interactive Refinement**: Built-in elicitation processes for quality improvement - ### Technical Preferences Integration The `technical-preferences.md` file serves as a persistent technical profile that: @@ -2504,35 +2496,6 @@ Handle conditional paths by asking clarifying questions when needed. Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs. ==================== END: .bmad-core/utils/workflow-management.md ==================== -==================== START: .bmad-core/utils/template-format.md ==================== -# Template Format Conventions - -Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation. - -## Template Markup Elements - -- **{{placeholders}}**: Variables to be replaced with actual content -- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users) -- **REPEAT** sections: Content blocks that may be repeated as needed -- **^^CONDITION^^** blocks: Conditional content included only if criteria are met -- **@{examples}**: Example content for guidance (never output to users) - -## Processing Rules - -- Replace all {{placeholders}} with project-specific content -- Execute all [[LLM: instructions]] internally without showing users -- Process conditional and repeat blocks as specified -- Use examples for guidance but never include them in final output -- Present only clean, formatted content to users - -## Critical Guidelines - -- **NEVER display template markup, LLM instructions, or examples to users** -- Template elements are for AI processing only -- Focus on faithful template execution and clean output -- All template-specific instructions are embedded within templates -==================== END: .bmad-core/utils/template-format.md ==================== - ==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ==================== --- docOutputLocation: docs/brainstorming-session-results.md @@ -5145,9 +5108,9 @@ sections: - id: next-steps title: Next Steps sections: - - id: design-architect-prompt - title: Design Architect Prompt - instruction: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input. + - id: ux-expert-prompt + title: UX Expert Prompt + instruction: This section will contain the prompt for the UX Expert, keep it short and to the point to initiate create architecture mode using this document as input. - id: architect-prompt title: Architect Prompt instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input. @@ -6637,7 +6600,6 @@ sections: After completing the architecture: 1. If project has UI components: - - Recommend engaging Design Architect agent - Use "Frontend Architecture Mode" - Provide this document as input @@ -6648,22 +6610,15 @@ sections: 3. Include specific prompts for next agents if needed sections: - - id: design-architect-prompt - title: Design Architect Prompt + - id: architect-prompt + title: Architect Prompt condition: Project has UI components instruction: | - Create a brief prompt to hand off to Design Architect for Frontend Architecture creation. Include: + Create a brief prompt to hand off to Architect for Frontend Architecture creation. Include: - Reference to this architecture document - Key UI requirements from PRD - Any frontend-specific decisions made here - Request for detailed frontend architecture - - id: developer-handoff - title: Developer Handoff - instruction: | - Create a brief prompt for developers starting implementation. Include: - - Reference to this architecture and coding standards - - First epic/story to implement - - Key technical decisions to follow ==================== END: .bmad-core/templates/architecture-tmpl.yaml ==================== ==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================