rebuild corrected a few bmad agent errors in orchestration where it thought tasks were actual configurations

agent-teams/team-all.yml

@@ -1,7 +1,15 @@
 bundle:
-  name: Every Agent Team Bundle
+  name: Team All
   description: This is a full organization of agents and includes every possible agent. This will produce the larges bundle but give the most options for discussion in a single session
 
 agents:
   - bmad
   - "*"
+
+workflows:
+  - brownfield-fullstack
+  - brownfield-service
+  - brownfield-ui
+  - greenfield-fullstack
+  - greenfield-service
+  - greenfield-ui

agent-teams/team-fullstack.yml

@@ -1,5 +1,5 @@
 bundle:
-  name: Full-Stack Development Team
+  name: Team Fullstack
   description: >-
     Comprehensive full-stack development team capable of handling both greenfield 
     application development and brownfield enhancement projects. This team combines 
@@ -10,6 +10,14 @@ bundle:
 
 agents:
   - bmad
+  - analyst
   - pm
   - ux-expert
   - fullstack-architect
+  - po
+
+workflows:
+  - greenfield-fullstack
+  - brownfield-fullstack
+  - greenfield-ui
+  - brownfield-ui

agent-teams/team-no-ui.yml

@@ -8,3 +8,7 @@ agents:
   - pm
   - architect
   - po
+
+workflows:
+  - greenfield-service
+  - brownfield-service

agent-teams/team-scrum.yml

@@ -1,5 +1,5 @@
 bundle:
-  name: Development Team Bundle
+  name: Team Scrum
   description: This is a core development Agile implementation scrum team.
 
 agents:

agent-teams/team-technical.yml

@@ -1,6 +1,6 @@
 bundle:
-  name: Technical Planning and Assessment Team Bundle
-  description: This is good for deep technical discussions and assessments.
+  name: team-technical
+  description: The Technical Planning and Assessment Team Bundle is good for deep technical discussions and assessments.
 
 agents:
   - bmad