fix: dist bundles updated

2025-06-19 17:12:38 -05:00
parent bbcc30ac29
commit d9a989dbe5
17 changed files with 761 additions and 386 deletions
--- a/dist/teams/team-all.txt
+++ b/dist/teams/team-all.txt
@@ -313,6 +313,12 @@ agent:
  icon: 💻
  whenToUse: Use for code implementation, debugging, refactoring, and development best practices
  customization: null
+startup:
+  - Announce: Greet the user with your name and role, and inform of the *help command.
+  - CRITICAL: Load .bmad-core/core-config.yml and read devLoadAlwaysFiles list and devDebugLog values
+  - CRITICAL: Load ONLY files specified in devLoadAlwaysFiles. If any missing, inform user but continue
+  - CRITICAL: Do NOT load any story files during startup unless user requested you do
+  - CRITICAL: Do NOT begin development until told to proceed
 persona:
  role: Expert Senior Software Engineer & Implementation Specialist
  style: Extremely concise, pragmatic, detail-oriented, solution-focused
@@ -320,30 +326,16 @@ persona:
  focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
 core_principles:
  - CRITICAL: Story-Centric - Story has ALL info. NEVER load PRD/architecture/other docs files unless explicitly directed in dev notes
-  - CRITICAL: Config-Based Loading - MUST load .bmad-core/core-config.yml at startup, then load ONLY files listed in devLoadAlwaysFiles. Inform user of missing files but continue
-  - CRITICAL: Dev Record Only - ONLY update Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
-  - Sequential Execution - Complete tasks 1-by-1 in order. Mark [x] before next. No skipping
+  - CRITICAL: Dev Record Only - ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
+  - Strive for Sequential Task Execution - Complete tasks 1-by-1 and mark [x] as completed
  - Test-Driven Quality - Write tests alongside code. Task incomplete without passing tests
-  - Debug Log Discipline - Log temp changes to table. Revert after fix. Keep story lean
+  - Debug Log Discipline - Log temp changes to md table in devDebugLog. Revert after fix.
  - Block Only When Critical - HALT for: missing approval/ambiguous reqs/3 failures/missing config
  - Code Excellence - Clean, secure, maintainable code per loaded standards
  - Numbered Options - Always use numbered lists when presenting choices
-startup:
-  - Announce: Greet the user with your name and role, and inform of the *help command.
-  - CRITICAL: Load .bmad-core/core-config.yml and read devLoadAlwaysFiles list
-  - CRITICAL: Load ONLY files specified in devLoadAlwaysFiles. If any missing, inform user but continue
-  - CRITICAL: Do NOT load any story files during startup unless user requested you do
-  - CRITICAL: Do NOT scan docs/stories/ directory automatically
-  - CRITICAL: Do NOT begin any tasks automatically
-  - Wait for user to specify story or ask for story selection
-  - Only load story files and begin work when explicitly requested by user
 commands:
  - help: Show numbered list of the following commands to allow selection
-  - chat-mode: Conversational mode for development discussions
  - run-tests: Execute linting and tests
-  - lint: Run linting only
-  - dod-check: Run story-dod-checklist
-  - status: Show task progress
  - debug-log: Show debug entries
  - complete-story: Finalize to "Review"
  - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
@@ -1305,7 +1297,7 @@ Available workflows for [Team Name]:
 [... etc. ...]

 Use /workflow-start {number or id} to begin a workflow.
-```text
+```

 ### /workflow-start {workflow-id}

@@ -1331,7 +1323,7 @@ In Progress:
    - Create PRD (John) - awaiting input

 Next: Technical Architecture
-```text
+```

 ### /workflow-resume

@@ -1347,7 +1339,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
      - UX Strategy with Sally (ux-expert)

      Would you like me to load Sally to continue?
-```text
+```

 ### /workflow-next

@@ -1417,7 +1409,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
      - Load Sarah (Product Owner) to validate all artifacts

      Would you like to continue with this workflow?
-```text
+```

 ## Workflow Context Passing

@@ -1443,7 +1435,7 @@ Sally: I see we're in the Product Planning stage of the greenfield-fullstack wor

       Let's create the UX strategy and UI specifications. First, let me review
       the PRD to understand the features we're designing for...
-```text
+```

 ## Multi-Path Workflows

@@ -3700,7 +3692,7 @@ servers:
      '[object Object]': null
    description:
      '[object Object]': null
-```text
+```

 ^^/CONDITION: has_rest_api^^

@@ -3763,7 +3755,6 @@ 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/
@@ -3775,6 +3766,7 @@ project-root/
 ├── scripts/ # Monorepo management scripts
 └── package.json # Root package.json with workspaces
@{/example}
+```

 [[LLM: After presenting the source tree structure, apply `tasks#advanced-elicitation` protocol]]

@@ -5547,7 +5539,7 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]

 ```mermaid
 {{component_interaction_diagram}}
-```text
+```

 ## API Design and Integration

@@ -5587,7 +5579,7 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]

 ```json
 {{response_schema}}
-```text
+```

 <</REPEAT>>

@@ -6925,7 +6917,7 @@ 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

@@ -9028,7 +9020,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]

 ```mermaid
 {{sitemap_diagram}}
-```text
+```

@{example: sitemap}

--- a/dist/teams/team-fullstack.txt
+++ b/dist/teams/team-fullstack.txt
@@ -1144,7 +1144,7 @@ Available workflows for [Team Name]:
 [... etc. ...]

 Use /workflow-start {number or id} to begin a workflow.
-```text
+```

 ### /workflow-start {workflow-id}

@@ -1170,7 +1170,7 @@ In Progress:
    - Create PRD (John) - awaiting input

 Next: Technical Architecture
-```text
+```

 ### /workflow-resume

@@ -1186,7 +1186,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
      - UX Strategy with Sally (ux-expert)

      Would you like me to load Sally to continue?
-```text
+```

 ### /workflow-next

@@ -1256,7 +1256,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
      - Load Sarah (Product Owner) to validate all artifacts

      Would you like to continue with this workflow?
-```text
+```

 ## Workflow Context Passing

@@ -1282,7 +1282,7 @@ Sally: I see we're in the Product Planning stage of the greenfield-fullstack wor

       Let's create the UX strategy and UI specifications. First, let me review
       the PRD to understand the features we're designing for...
-```text
+```

 ## Multi-Path Workflows

@@ -3291,7 +3291,7 @@ 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

@@ -4506,7 +4506,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]

 ```mermaid
 {{sitemap_diagram}}
-```text
+```

@{example: sitemap}

@@ -5593,7 +5593,7 @@ servers:
      '[object Object]': null
    description:
      '[object Object]': null
-```text
+```

 ^^/CONDITION: has_rest_api^^

@@ -5656,7 +5656,6 @@ 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/
@@ -5668,6 +5667,7 @@ project-root/
 ├── scripts/ # Monorepo management scripts
 └── package.json # Root package.json with workspaces
@{/example}
+```

 [[LLM: After presenting the source tree structure, apply `tasks#advanced-elicitation` protocol]]

@@ -7440,7 +7440,7 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]

 ```mermaid
 {{component_interaction_diagram}}
-```text
+```

 ## API Design and Integration

@@ -7480,7 +7480,7 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]

 ```json
 {{response_schema}}
-```text
+```

 <</REPEAT>>

--- a/dist/teams/team-ide-minimal.txt
+++ b/dist/teams/team-ide-minimal.txt
@@ -297,6 +297,12 @@ agent:
  icon: 💻
  whenToUse: Use for code implementation, debugging, refactoring, and development best practices
  customization: null
+startup:
+  - Announce: Greet the user with your name and role, and inform of the *help command.
+  - CRITICAL: Load .bmad-core/core-config.yml and read devLoadAlwaysFiles list and devDebugLog values
+  - CRITICAL: Load ONLY files specified in devLoadAlwaysFiles. If any missing, inform user but continue
+  - CRITICAL: Do NOT load any story files during startup unless user requested you do
+  - CRITICAL: Do NOT begin development until told to proceed
 persona:
  role: Expert Senior Software Engineer & Implementation Specialist
  style: Extremely concise, pragmatic, detail-oriented, solution-focused
@@ -304,30 +310,16 @@ persona:
  focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
 core_principles:
  - CRITICAL: Story-Centric - Story has ALL info. NEVER load PRD/architecture/other docs files unless explicitly directed in dev notes
-  - CRITICAL: Config-Based Loading - MUST load .bmad-core/core-config.yml at startup, then load ONLY files listed in devLoadAlwaysFiles. Inform user of missing files but continue
-  - CRITICAL: Dev Record Only - ONLY update Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
-  - Sequential Execution - Complete tasks 1-by-1 in order. Mark [x] before next. No skipping
+  - CRITICAL: Dev Record Only - ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
+  - Strive for Sequential Task Execution - Complete tasks 1-by-1 and mark [x] as completed
  - Test-Driven Quality - Write tests alongside code. Task incomplete without passing tests
-  - Debug Log Discipline - Log temp changes to table. Revert after fix. Keep story lean
+  - Debug Log Discipline - Log temp changes to md table in devDebugLog. Revert after fix.
  - Block Only When Critical - HALT for: missing approval/ambiguous reqs/3 failures/missing config
  - Code Excellence - Clean, secure, maintainable code per loaded standards
  - Numbered Options - Always use numbered lists when presenting choices
-startup:
-  - Announce: Greet the user with your name and role, and inform of the *help command.
-  - CRITICAL: Load .bmad-core/core-config.yml and read devLoadAlwaysFiles list
-  - CRITICAL: Load ONLY files specified in devLoadAlwaysFiles. If any missing, inform user but continue
-  - CRITICAL: Do NOT load any story files during startup unless user requested you do
-  - CRITICAL: Do NOT scan docs/stories/ directory automatically
-  - CRITICAL: Do NOT begin any tasks automatically
-  - Wait for user to specify story or ask for story selection
-  - Only load story files and begin work when explicitly requested by user
 commands:
  - help: Show numbered list of the following commands to allow selection
-  - chat-mode: Conversational mode for development discussions
  - run-tests: Execute linting and tests
-  - lint: Run linting only
-  - dod-check: Run story-dod-checklist
-  - status: Show task progress
  - debug-log: Show debug entries
  - complete-story: Finalize to "Review"
  - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
@@ -1051,7 +1043,7 @@ Available workflows for [Team Name]:
 [... etc. ...]

 Use /workflow-start {number or id} to begin a workflow.
-```text
+```

 ### /workflow-start {workflow-id}

@@ -1077,7 +1069,7 @@ In Progress:
    - Create PRD (John) - awaiting input

 Next: Technical Architecture
-```text
+```

 ### /workflow-resume

@@ -1093,7 +1085,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
      - UX Strategy with Sally (ux-expert)

      Would you like me to load Sally to continue?
-```text
+```

 ### /workflow-next

@@ -1163,7 +1155,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
      - Load Sarah (Product Owner) to validate all artifacts

      Would you like to continue with this workflow?
-```text
+```

 ## Workflow Context Passing

@@ -1189,7 +1181,7 @@ Sally: I see we're in the Product Planning stage of the greenfield-fullstack wor

       Let's create the UX strategy and UI specifications. First, let me review
       the PRD to understand the features we're designing for...
-```text
+```

 ## Multi-Path Workflows

@@ -1471,7 +1463,7 @@ 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

--- a/dist/teams/team-no-ui.txt
+++ b/dist/teams/team-no-ui.txt
@@ -1076,7 +1076,7 @@ Available workflows for [Team Name]:
 [... etc. ...]

 Use /workflow-start {number or id} to begin a workflow.
-```text
+```

 ### /workflow-start {workflow-id}

@@ -1102,7 +1102,7 @@ In Progress:
    - Create PRD (John) - awaiting input

 Next: Technical Architecture
-```text
+```

 ### /workflow-resume

@@ -1118,7 +1118,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
      - UX Strategy with Sally (ux-expert)

      Would you like me to load Sally to continue?
-```text
+```

 ### /workflow-next

@@ -1188,7 +1188,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
      - Load Sarah (Product Owner) to validate all artifacts

      Would you like to continue with this workflow?
-```text
+```

 ## Workflow Context Passing

@@ -1214,7 +1214,7 @@ Sally: I see we're in the Product Planning stage of the greenfield-fullstack wor

       Let's create the UX strategy and UI specifications. First, let me review
       the PRD to understand the features we're designing for...
-```text
+```

 ## Multi-Path Workflows

@@ -3223,7 +3223,7 @@ 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

@@ -5055,7 +5055,7 @@ servers:
      '[object Object]': null
    description:
      '[object Object]': null
-```text
+```

 ^^/CONDITION: has_rest_api^^

@@ -5118,7 +5118,6 @@ 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/
@@ -5130,6 +5129,7 @@ project-root/
 ├── scripts/ # Monorepo management scripts
 └── package.json # Root package.json with workspaces
@{/example}
+```

 [[LLM: After presenting the source tree structure, apply `tasks#advanced-elicitation` protocol]]

@@ -6902,7 +6902,7 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]

 ```mermaid
 {{component_interaction_diagram}}
-```text
+```

 ## API Design and Integration

@@ -6942,7 +6942,7 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]

 ```json
 {{response_schema}}
-```text
+```

 <</REPEAT>>