feat: removed some templates that are not ready for use

2025-06-17 22:04:24 -05:00
parent bc7cc0439a
commit b03aece79e
16 changed files with 802 additions and 2121 deletions
--- a/dist/teams/team-no-ui.txt
+++ b/dist/teams/team-no-ui.txt
@@ -3496,13 +3496,13 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]

 **TypeScript Interface:**

-````typescript
+```typescript
 {
  {
    model_interface;
  }
 }
-```text
+```

 **Relationships:**

@@ -3542,7 +3542,7 @@ interface UserProfile {
  bio?: string;
  preferences: Record<string, any>;
 }
-````
+```

 **Relationships:**

@@ -3566,7 +3566,7 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),

 ^^CONDITION: has_rest_api^^

-````yml
+```yml
 openapi: 3.0.0
 info:
  title:
@@ -3580,7 +3580,7 @@ servers:
      '[object Object]': null
    description:
      '[object Object]': null
-```text
+```

 ^^/CONDITION: has_rest_api^^

@@ -3589,7 +3589,7 @@ servers:
 ```graphql
 # GraphQL Schema
 {{graphql_schema}}
-````
+```

 ^^/CONDITION: has_graphql_api^^

@@ -5846,9 +5846,9 @@ Document the choice and key services that will be used.]]

 Use appropriate diagram type for clarity.]]

-````mermaid
+```mermaid
 {{architecture_diagram}}
-```text
+```

 ### Architectural Patterns

@@ -5959,7 +5959,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
    model_interface;
  }
 }
-````
+```

 **Relationships:**

@@ -5983,7 +5983,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]

 **TypeScript Interface:**

-````typescript
+```typescript
 interface User {
  id: string;
  email: string;
@@ -6037,16 +6037,16 @@ servers:
      '[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^^

@@ -6059,7 +6059,7 @@ servers:
    trpc_routers;
  }
 }
-````
+```

 ^^/CONDITION: has_trpc_api^^

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

 **Component Organization:**

-`````text
-{{component_structure}}
 ```text
+{{component_structure}}
+```

 **Component Template:**

-````typescript
+```typescript
 {
  {
    component_template;
  }
 }
-```text
+```

 ### State Management Architecture

@@ -6230,7 +6230,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
    state_structure;
  }
 }
-`````
+```

 **State Management Patterns:**

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

 **Protected Route Pattern:**

-````typescript
+```typescript
 {
  {
    protected_route_example;
  }
 }
-```text
+```

 ### Frontend Services Layer

@@ -6269,17 +6269,17 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
    api_client_setup;
  }
 }
-````
+```

 **Service Example:**

-````typescript
+```typescript
 {
  {
    service_example;
  }
 }
-```text
+```

 ## Backend Architecture

@@ -6294,11 +6294,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 ^^CONDITION: serverless^^
 **Function Organization:**

-````
+```text

 {{function_structure}}

-````text
+```

 **Function Template:**

@@ -6308,26 +6308,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_structure}}
+```

 **Controller Template:**

-````typescript
+```typescript
 {
  {
    controller_template;
  }
 }
-```text
+```

 ^^/CONDITION: traditional_server^^

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

 ```sql
 {{database_schema}}
-`````
+```

 **Data Access Layer:**

-````typescript
+```typescript
 {
  {
    repository_pattern;
  }
 }
-```text
+```

 ### Authentication and Authorization

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

 ```mermaid
 {{auth_flow_diagram}}
-````
+```

 **Middleware/Guards:**

-````typescript
+```typescript
 {
  {
    auth_middleware;
  }
 }
-```text
+```

 ## Unified Project Structure

@@ -6429,7 +6429,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/
@@ -6451,19 +6451,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}}

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

 # Run tests
 {{test_commands}}
-```text
+```

 ### Environment Configuration

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

 # Shared
 {{shared_env_vars}}
-````
+```

 ## Deployment Architecture

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

 ### CI/CD Pipeline

-````yaml
+```yaml
 '[object Object]': null
-```text
+```

 ### Environments

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

 ### Testing Pyramid

-````
+```text

        E2E Tests
       /          \
@@ -6582,17 +6582,17 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 / \
 Frontend Unit Backend Unit

-```text
+```

 ### Test Organization

 **Frontend Tests:**

-```
+```text

 {{frontend_test_structure}}

-````text
+```

 **Backend Tests:**

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

 {{backend_test_structure}}

-```text
+```

 **E2E Tests:**

-````
+```text

 {{e2e_test_structure}}

-````text
+```

 ### Test Examples

@@ -6620,17 +6620,17 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
    frontend_test_example;
  }
 }
-````
+```

 **Backend API Test:**

-````typescript
+```typescript
 {
  {
    backend_test_example;
  }
 }
-```text
+```

 **E2E Test:**

@@ -6640,7 +6640,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
    e2e_test_example;
  }
 }
-````
+```

 ## Coding Standards

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

 ### Error Flow

-````mermaid
+```mermaid
 {{error_flow_diagram}}
-```text
+```

 ### Error Response Format

@@ -6697,17 +6697,17 @@ interface ApiError {
    requestId: string;
  };
 }
-````
+```

 ### Frontend Error Handling

-````typescript
+```typescript
 {
  {
    frontend_error_handler;
  }
 }
-```text
+```

 ### Backend Error Handling

@@ -6717,7 +6717,7 @@ interface ApiError {
    backend_error_handler;
  }
 }
-````
+```

 ## Monitoring and Observability

@@ -8268,8 +8268,7 @@ workflow:
    - api-prototype
    - simple-service

-  # For Complex Services (Production APIs, Multiple Endpoints)
-  complex_service_sequence:
+  sequence:
    - agent: analyst
      creates: project-brief.md
      optional_steps:
@@ -8309,65 +8308,33 @@ workflow:
      action: move_to_ide
      notes: "All planning artifacts complete. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"

-  # For Simple Services (Simple APIs, Single Purpose Services)
-  simple_service_sequence:
-    - step: service_scope
-      action: assess complexity
-      notes: "First, assess if this needs full planning (use complex_service_sequence) or can be a simple API/service."
-
-    - agent: analyst
-      creates: project-brief.md
-      optional_steps:
-        - brainstorming_session
-      notes: "Creates focused project brief for simple service. SAVE OUTPUT: Copy final project-brief.md to your project's docs/ folder."
-
-    - agent: pm
-      creates: simple_epic OR single_story
-      uses: create-epic OR create-story
-      requires: project-brief.md
-      notes: "Create simple epic or story for API endpoints instead of full PRD for rapid development."
-
-    - workflow_end:
-      action: move_to_ide
-      notes: "Simple service defined. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
-
  flow_diagram: |
    ```mermaid
    graph TD
-        A[Start: Service Development] --> B{Service Complexity?}
-        B -->|Complex/Production| C[analyst: project-brief.md]
-        B -->|Simple/Prototype| D[analyst: focused project-brief.md]
+        A[Start: Service Development] --> B[analyst: project-brief.md]
+        B --> C[pm: prd.md]
+        C --> D[architect: architecture.md]
+        D --> E{Architecture suggests PRD changes?}
+        E -->|Yes| F[pm: update prd.md]
+        E -->|No| G[po: validate all artifacts]
+        F --> G
+        G --> H{PO finds issues?}
+        H -->|Yes| I[Return to relevant agent for fixes]
+        H -->|No| J[Move to IDE Environment]
+        I --> G

-        C --> E[pm: prd.md]
-        E --> F[architect: architecture.md]
-        F --> G{Architecture suggests PRD changes?}
-        G -->|Yes| H[pm: update prd.md]
-        G -->|No| I[po: validate all artifacts]
-        H --> I
-        I --> J{PO finds issues?}
-        J -->|Yes| K[Return to relevant agent for fixes]
-        J -->|No| L[Move to IDE Environment]
-        K --> I
+        B -.-> B1[Optional: brainstorming]
+        B -.-> B2[Optional: market research]
+        D -.-> D1[Optional: technical research]

-        D --> M[pm: simple epic or story]
-        M --> N[Move to IDE Environment]
-
-        C -.-> C1[Optional: brainstorming]
-        C -.-> C2[Optional: market research]
-        F -.-> F1[Optional: technical research]
-        D -.-> D1[Optional: brainstorming]
-
-        style L fill:#90EE90
-        style N fill:#90EE90
+        style J fill:#90EE90
+        style B fill:#FFE4B5
        style C fill:#FFE4B5
-        style E fill:#FFE4B5
-        style F fill:#FFE4B5
-        style D fill:#FFB6C1
-        style M fill:#FFB6C1
+        style D fill:#FFE4B5
    ```

  decision_guidance:
-    use_complex_sequence_when:
+    when_to_use:
      - Building production APIs or microservices
      - Multiple endpoints and complex business logic
      - Need comprehensive documentation and testing
@@ -8375,27 +8342,14 @@ workflow:
      - Long-term maintenance expected
      - Enterprise or external-facing APIs

-    use_simple_sequence_when:
-      - Building simple APIs or single-purpose services
-      - Few endpoints with straightforward logic
-      - Prototyping or proof-of-concept APIs
-      - Solo developer or small team
-      - Internal tools or utilities
-      - Learning or experimental projects
-
  handoff_prompts:
-    # Complex sequence prompts
    analyst_to_pm: "Project brief is complete. Save it as docs/project-brief.md in your project, then create the PRD."
    pm_to_architect: "PRD is ready. Save it as docs/prd.md in your project, then create the service architecture."
    architect_review: "Architecture complete. Save it as docs/architecture.md. Do you suggest any changes to the PRD stories or need new stories added?"
    architect_to_pm: "Please update the PRD with the suggested story changes, then re-export the complete prd.md to docs/."
    updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
    po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
-    complex_complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-
-    # Simple sequence prompts
-    simple_analyst_to_pm: "Focused project brief complete. Save it as docs/project-brief.md, then create simple epic or story for API development."
-    simple_complete: "Simple service defined. Move to IDE environment to begin development."
+    complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
 ==================== END: workflows#greenfield-service ====================

 ==================== START: workflows#brownfield-service ====================
@@ -8413,16 +8367,11 @@ workflow:
    - performance-optimization
    - integration-enhancement

-  # For Complex Service Enhancements (Multiple Stories, Architectural Changes)
-  complex_enhancement_sequence:
-    - step: scope_assessment
-      agent: any
-      action: assess complexity
-      notes: "First, assess if this is a simple service change (use simple_enhancement_sequence) or complex enhancement requiring full planning."
-
+  sequence:
    - step: service_analysis
-      agent: analyst
-      action: analyze existing service
+     agent: architect
+      action: analyze existing project and use task document-project
+      creates: multiple documents per the document-project template
      notes: "Review existing service documentation, codebase, performance metrics, and identify integration dependencies."

    - agent: pm
@@ -8451,69 +8400,35 @@ workflow:
      action: move_to_ide
      notes: "All planning artifacts complete. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"

-  # For Simple Service Enhancements (1-3 Stories, Following Existing Patterns)
-  simple_enhancement_sequence:
-    - step: enhancement_type
-      action: choose approach
-      notes: "Choose between creating single story (simple API endpoint) or epic (1-3 related service changes)."
-
-    - agent: pm|po|sm
-      creates: brownfield_epic OR brownfield_story
-      uses: brownfield-create-epic OR brownfield-create-story
-      notes: "Create focused service enhancement with existing API integration. Choose agent based on team preference and context."
-
-    - workflow_end:
-      action: move_to_ide
-      notes: "Service enhancement defined. Move to IDE environment to begin development. Explain to the user the IDE Development Workflow next steps: data#bmad-kb:IDE Development Workflow"
-
  flow_diagram: |
    ```mermaid
    graph TD
-        A[Start: Service Enhancement] --> B{Enhancement Complexity?}
-        B -->|Complex/Significant| C[analyst: analyze existing service]
-        B -->|Simple| D{1 Story or 2-3 Stories?}
+        A[Start: Service Enhancement] --> B[analyst: analyze existing service]
+        B --> C[pm: brownfield-prd.md]
+        C --> D[architect: brownfield-architecture.md]
+        D --> E[po: validate with po-master-checklist]
+        E --> F{PO finds issues?}
+        F -->|Yes| G[Return to relevant agent for fixes]
+        F -->|No| H[Move to IDE Environment]
+        G --> E

-        C --> E[pm: brownfield-prd.md]
-        E --> F[architect: brownfield-architecture.md]
-        F --> G[po: validate with po-master-checklist]
-        G --> H{PO finds issues?}
-        H -->|Yes| I[Return to relevant agent for fixes]
-        H -->|No| J[Move to IDE Environment]
-        I --> G
-
-        D -->|1 Story| K[pm/po/sm: brownfield-create-story]
-        D -->|2-3 Stories| L[pm/po/sm: brownfield-create-epic]
-        K --> M[Move to IDE Environment]
-        L --> M
-
-        style J fill:#90EE90
-        style M fill:#90EE90
-        style E fill:#FFE4B5
-        style F fill:#FFE4B5
-        style K fill:#FFB6C1
-        style L fill:#FFB6C1
+        style H fill:#90EE90
+        style C fill:#FFE4B5
+        style D fill:#FFE4B5
    ```

  decision_guidance:
-    use_complex_sequence_when:
-      - Service enhancement requires multiple coordinated stories (4+)
+    when_to_use:
+      - Service enhancement requires coordinated stories
      - API versioning or breaking changes needed
      - Database schema changes required
      - Performance or scalability improvements needed
      - Multiple integration points affected

-    use_simple_sequence_when:
-      - Adding simple endpoints or modifying existing ones
-      - Enhancement follows existing service patterns
-      - API compatibility maintained
-      - Risk to existing service is low
-      - Change is isolated with clear boundaries
-
  handoff_prompts:
    analyst_to_pm: "Service analysis complete. Create comprehensive brownfield PRD with service integration strategy."
    pm_to_architect: "Brownfield PRD ready. Save it as docs/brownfield-prd.md, then create the service architecture."
    architect_to_po: "Architecture complete. Save it as docs/brownfield-architecture.md. Please validate all artifacts for service integration safety."
    po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
-    simple_to_ide: "Service enhancement defined with existing API integration. Move to IDE environment to begin development."
-    complex_complete: "All brownfield planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
+    complete: "All brownfield planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
 ==================== END: workflows#brownfield-service ====================