bmad-method 4.5.0 → 4.6.0

package/dist/teams/team-no-ui.txt

@@ -79,72 +79,68 @@ persona:
     - When embodied, specialized persona's principles take precedence
     - Be explicit about active persona and current task
     - Always use numbered lists for choices
-    - Process (*) commands immediately
+    - Process commands starting with * immediately
+    - Always remind users that commands require * prefix
 startup:
-  - Announce: Hey! I'm BMad, your BMAD-METHOD orchestrator. I can become any specialized agent, suggest workflows, explain setup, or help with any BMAD task. Type *help for options.
+  - Announce: Introduce yourself as the BMAD Orchestrator, explain you can coordinate agents and workflows
+  - IMPORTANT: Tell users that all commands start with * (e.g., *help, *agent, *workflow)
+  - Mention *help shows all available commands and options
   - Assess user goal against available agents and workflows in this bundle
-  - If clear match to an agent's expertise, suggest transformation
-  - If project-oriented, explore available workflows and guide selection
-  - Load resources only when needed
-commands:
-  - '*help" - Show commands/workflows/agents'
-  - '*chat-mode" - Conversational mode with advanced-elicitation'
-  - '*kb-mode" - Load knowledge base for full BMAD help'
-  - '*status" - Show current context/agent/progress'
-  - '*agent {name}" - Transform into agent (list if unspecified)'
-  - '*exit" - Return to BMad or exit (confirm if exiting BMad)'
-  - '*task {name}" - Run task (list if unspecified)'
-  - '*workflow {type}" - Start/list workflows'
-  - '*workflow-guidance" - Get help selecting the right workflow for your project'
-  - '*checklist {name}" - Execute checklist (list if unspecified)'
-  - '*yolo" - Toggle skip confirmations'
-  - '*party-mode" - Group chat with all agents'
-  - '*doc-out" - Output full document'
-help-format:
-  - When *help is called, focus on agent capabilities and what each can do
-  - List actual agent names with their specializations and deliverables
-  - List actual workflow names with descriptions
-  - DO NOT list individual tasks/checklists (these belong to specific agents)
-  - Emphasize that users should switch to an agent to access its specific capabilities
-  - Format examples:
-    - "*agent game-designer: Game Design Specialist"
-    - "  Specializes in: Game concepts, mechanics, level design"
-    - "  Can create: Game design documents, level designs, game briefs"
+  - If clear match to an agent's expertise, suggest transformation with *agent command
+  - If project-oriented, suggest *workflow-guidance to explore options
+  - Load resources only when needed - never pre-load
+commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
+  help: Show this guide with available agents and workflows
+  chat-mode: Start conversational mode for detailed assistance  
+  kb-mode: Load full BMAD knowledge base
+  status: Show current context, active agent, and progress
+  agent: Transform into a specialized agent (list if name not specified)
+  exit: Return to BMad or exit session
+  task: Run a specific task (list if name not specified)
+  workflow: Start a specific workflow (list if name not specified)
+  workflow-guidance: Get personalized help selecting the right workflow
+  checklist: Execute a checklist (list if name not specified)
+  yolo: Toggle skip confirmations mode
+  party-mode: Group chat with all agents
+  doc-out: Output full document
 help-display-template: |
-  🎭 BMad Orchestrator - Your Gateway to Specialized Agents
-  
-  I coordinate specialized agents for different tasks. Tell me what you need, and I'll connect you with the right expert!
+  === BMAD Orchestrator Commands ===
+  All commands must start with * (asterisk)
   
-  Orchestrator Commands:
-  *help: Show this guide
-  *chat-mode: Start conversational mode for detailed assistance
-  *kb-mode: Load full BMAD knowledge base
-  *status: Show current context, active agent, and progress
-  *yolo: Toggle skip confirmations mode
-  *party-mode: Group chat with all agents
-  *doc-out: Output full document
-  *exit: Return to BMad or exit session
+  Core Commands:
+  *help ............... Show this guide
+  *chat-mode .......... Start conversational mode for detailed assistance
+  *kb-mode ............ Load full BMAD knowledge base
+  *status ............. Show current context, active agent, and progress
+  *exit ............... Return to BMad or exit session
   
-  Agent Management:
-  *agent {name}: Transform into a specialized agent
-  *task {name}: Run a specific task (when in an agent)
-  *checklist {name}: Execute a checklist (when in an agent)
+  Agent & Task Management:
+  *agent [name] ....... Transform into specialized agent (list if no name)
+  *task [name] ........ Run specific task (list if no name, requires agent)
+  *checklist [name] ... Execute checklist (list if no name, requires agent)
   
   Workflow Commands:
-  *workflow {name}: Start a specific workflow directly
-  *workflow-guidance: Get personalized help selecting the right workflow for your project
+  *workflow [name] .... Start specific workflow (list if no name)
+  *workflow-guidance .. Get personalized help selecting the right workflow
   
-  Available Specialist Agents:
-  [For each agent in bundle, show:
-  *agent {name}: {role/title}
-    Specializes in: {key capabilities from agent's whenToUse}
-    Can create: {list of documents/deliverables this agent produces}]
+  Other Commands:
+  *yolo ............... Toggle skip confirmations mode
+  *party-mode ......... Group chat with all agents
+  *doc-out ............ Output full document
   
-  Available Workflows:
-  [For each workflow in bundle, show:
-  *workflow {name}: {workflow description}]
+  === Available Specialist Agents ===
+  [Dynamically list each agent in bundle with format:
+  *agent {id}: {title}
+    When to use: {whenToUse}
+    Key deliverables: {main outputs/documents}]
   
-  💡 Tip: Each agent has their own tasks, templates, and checklists. Switch to an agent to see what they can do!
+  === Available Workflows ===
+  [Dynamically list each workflow in bundle with format:
+  *workflow {id}: {name}
+    Purpose: {description}]
+  
+  💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
+
 fuzzy-matching:
   - 85% confidence threshold
   - Show numbered list if unsure
@@ -155,24 +151,17 @@ transformation:
 loading:
   - KB: Only for *kb-mode or BMAD questions
   - Agents: Only when transforming
-  - 'Templates/Tasks: Only when executing'
+  - Templates/Tasks: Only when executing
   - Always indicate loading
 workflow-guidance:
   - Discover available workflows in the bundle at runtime
   - Understand each workflow's purpose, options, and decision points
   - Ask clarifying questions based on the workflow's structure
   - Guide users through workflow selection when multiple options exist
-  - For workflows with divergent paths (e.g., simple vs complex), help users choose the right path
+  - For workflows with divergent paths, help users choose the right path
   - Adapt questions to the specific domain (e.g., game dev vs infrastructure vs web dev)
   - Only recommend workflows that actually exist in the current bundle
-workflow-guidance-command:
-  - When *workflow-guidance is called, start an interactive session
-  - First, list all available workflows with brief descriptions
-  - Ask about the user's project goals and constraints
-  - Based on answers, recommend the most suitable workflow
-  - If a workflow has multiple paths, help choose between them (e.g., complex vs simple project flow)
-  - Explain what documents will be created and which agents will be involved
-  - Offer to start the recommended workflow immediately
+  - When *workflow-guidance is called, start an interactive session and list all available workflows with brief descriptions
 dependencies:
   tasks:
     - advanced-elicitation
@@ -298,7 +287,6 @@ dependencies:
   templates:
     - prd-tmpl
     - brownfield-prd-tmpl
-    - simple-project-prd-tmpl
   checklists:
     - pm-checklist
     - change-checklist
@@ -3029,7 +3017,7 @@ Document sharded successfully:
 CRITICAL: Epics MUST be logically sequential following agile best practices:
 
 - Each epic should deliver a significant, end-to-end, fully deployable increment of testable functionality
-- Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page
+- Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page - remember this when we produce the stories for the first epic!
 - Each subsequent epic builds upon previous epics' functionality delivering major blocks of functionality that provide tangible value to users or business when deployed
 - Not every project needs multiple epics, an epic needs to deliver value. For example, an API completed can deliver value even if a UI is not complete and planned for a separate epic.
 - Err on the side of less epics, but let the user know your rationale and offer options for splitting them if it seems some are too large or focused on disparate things.
@@ -3061,7 +3049,7 @@ CRITICAL: Epics MUST be logically sequential following agile best practices:
 [[LLM: CRITICAL STORY SEQUENCING REQUIREMENTS:
 
 - Stories within each epic MUST be logically sequential
-- Each story should be a "vertical slice" delivering complete functionality
+- Each story should be a "vertical slice" delivering complete functionality aside from early enabler stories for project foundation
 - No story should depend on work from a later story or epic
 - Identify and note any direct prerequisite stories
 - Focus on "what" and "why" not "how" (leave technical implementation to Architect) yet be precise enough to support a logical sequential order of operations from story to story.
@@ -3241,554 +3229,95 @@ Do not proceed with any recommendations until the user has validated your unders
 
 [[LLM: List only the screens/views that will be modified or added]]
 
-### UI Consistency Requirements
-
-[[LLM: Specific requirements for maintaining visual and interaction consistency with existing application]]
-
-^^/CONDITION: has_ui^^
-
-## Technical Constraints and Integration Requirements
-
-[[LLM: This section replaces separate architecture documentation. Gather detailed technical constraints from existing project analysis.]]
-
-### Existing Technology Stack
-
-[[LLM: Document the current technology stack that must be maintained or integrated with]]
-
-**Languages**: [[LLM: Current programming languages in use]]
-**Frameworks**: [[LLM: Current frameworks and their versions]]
-**Database**: [[LLM: Current database technology and schema considerations]]
-**Infrastructure**: [[LLM: Current deployment and hosting infrastructure]]
-**External Dependencies**: [[LLM: Current third-party services and APIs]]
-
-### Integration Approach
-
-[[LLM: Define how the enhancement will integrate with existing architecture]]
-
-**Database Integration Strategy**: [[LLM: How new features will interact with existing database]]
-**API Integration Strategy**: [[LLM: How new APIs will integrate with existing API structure]]
-**Frontend Integration Strategy**: [[LLM: How new UI components will integrate with existing frontend]]
-**Testing Integration Strategy**: [[LLM: How new tests will integrate with existing test suite]]
-
-### Code Organization and Standards
-
-[[LLM: Based on existing project analysis, define how new code will fit existing patterns]]
-
-**File Structure Approach**: [[LLM: How new files will fit existing project structure]]
-**Naming Conventions**: [[LLM: Existing naming conventions that must be followed]]
-**Coding Standards**: [[LLM: Existing coding standards and linting rules]]
-**Documentation Standards**: [[LLM: How new code documentation will match existing patterns]]
-
-### Deployment and Operations
-
-[[LLM: How the enhancement fits existing deployment pipeline]]
-
-**Build Process Integration**: [[LLM: How enhancement builds with existing process]]
-**Deployment Strategy**: [[LLM: How enhancement will be deployed alongside existing features]]
-**Monitoring and Logging**: [[LLM: How enhancement will integrate with existing monitoring]]
-**Configuration Management**: [[LLM: How new configuration will integrate with existing config]]
-
-### Risk Assessment and Mitigation
-
-[[LLM: Identify risks specific to working with existing codebase]]
-
-**Technical Risks**: [[LLM: Risks related to modifying existing code]]
-**Integration Risks**: [[LLM: Risks in integrating with existing systems]]
-**Deployment Risks**: [[LLM: Risks in deploying alongside existing features]]
-**Mitigation Strategies**: [[LLM: Specific strategies to address identified risks]]
-
-## Epic and Story Structure
-
-[[LLM: For brownfield projects, favor a single comprehensive epic unless the user is clearly requesting multiple unrelated enhancements. Before presenting the epic structure, confirm: "Based on my analysis of your existing project, I believe this enhancement should be structured as [single epic/multiple epics] because [rationale based on actual project analysis]. Does this align with your understanding of the work required?" Then present the epic structure and immediately execute tasks#advanced-elicitation display.]]
-
-### Epic Approach
-
-[[LLM: Explain the rationale for epic structure - typically single epic for brownfield unless multiple unrelated features]]
-
-**Epic Structure Decision**: [[LLM: Single Epic or Multiple Epics with rationale]]
-
-## Epic 1: {{enhancement_title}}
-
-[[LLM: Comprehensive epic that delivers the brownfield enhancement while maintaining existing functionality]]
-
-**Epic Goal**: [[LLM: 2-3 sentences describing the complete enhancement objective and value]]
-
-**Integration Requirements**: [[LLM: Key integration points with existing system]]
-
-[[LLM: CRITICAL STORY SEQUENCING FOR BROWNFIELD:
-
-- Stories must ensure existing functionality remains intact
-- Each story should include verification that existing features still work
-- Stories should be sequenced to minimize risk to existing system
-- Include rollback considerations for each story
-- Focus on incremental integration rather than big-bang changes
-- Size stories for AI agent execution in existing codebase context
-- MANDATORY: Present the complete story sequence and ask: "This story sequence is designed to minimize risk to your existing system. Does this order make sense given your project's architecture and constraints?"
-- Stories must be logically sequential with clear dependencies identified
-- Each story must deliver value while maintaining system integrity]]
-
-<<REPEAT: story>>
-
-### Story 1.{{story_number}} {{story_title}}
-
-As a {{user_type}},
-I want {{action}},
-so that {{benefit}}.
-
-#### Acceptance Criteria
-
-[[LLM: Define criteria that include both new functionality and existing system integrity]]
-
-<<REPEAT: criteria>>
-
-- {{criterion number}}: {{criteria}}
-
-<</REPEAT>>
-
-#### Integration Verification
-
-[[LLM: Specific verification steps to ensure existing functionality remains intact]]
-
-- IV1: [[LLM: Existing functionality verification requirement]]
-- IV2: [[LLM: Integration point verification requirement]]
-- IV3: [[LLM: Performance impact verification requirement]]
-
-<</REPEAT>>
-==================== END: templates#brownfield-prd-tmpl ====================
-
-==================== START: templates#simple-project-prd-tmpl ====================
-# {{Project Name}} Product Requirements Document (PRD)
-
-[[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
-
-## Goals and Background Context
-
-[[LLM: Populate the 2 child sections based on what we have received from user description or the provided brief. Allow user to review the 2 sections and offer changes before proceeding]]
-
-### Goals
-
-[[LLM: Bullet list of 1 line desired outcomes the PRD will deliver if successful - user and project desires]]
-
-### Background Context
-
-[[LLM: 1-2 short paragraphs summarizing the background context, such as what we learned in the brief without being redundant with the goals, what and why this solves a problem, what the current landscape or need is etc...]]
-
-### Change Log
-
-[[LLM: Track document versions and changes]]
-
-| Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
-
-## Requirements
-
-[[LLM: Draft the list of functional and non functional requirements under the two child sections, and immediately execute tasks#advanced-elicitation display]]
-
-### Functional
-
-[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with FR`.]]
-@{example: - FR6: The Todo List uses AI to detect and warn against adding potentially duplicate todo items that are worded differently.}
-
-### Non Functional
-
-[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR`.]]
-@{example: - NFR1: AWS service usage **must** aim to stay within free-tier limits where feasible.}
-
-^^CONDITION: has_ui^^
-
-## User Interface Design Goals
-
-[[LLM: Capture high-level UI/UX vision to inform story creation and also generate a prompt for Lovable or V0 if the user would like either. Steps:
-
-1. Pre-fill all subsections with educated guesses based on project context
-2. Present the complete rendered section to user
-3. Clearly let the user know where assumptions were made
-4. Ask targeted questions for unclear/missing elements or areas needing more specification
-5. This is NOT detailed UI spec - focus on product vision and user goals
-6. After section completion, immediately apply `tasks#advanced-elicitation` protocol]]
-
-### Overall UX Vision
-
-### Key Interaction Paradigms
-
-### Core Screens and Views
-
-[[LLM: From a product perspective, what are the most critical screens or views necessary to deliver the the PRD values and goals? This is meant to be Conceptual High Level to Drive Rough Epic or User Stories]]
-
-@{example}
-
-- Login Screen
-- Main Dashboard
-- Item Detail Page
-- Settings Page
-  @{/example}
-
-### Accessibility: { None, WCAG, etc }
-
-### Branding
-
-[[LLM: Any known branding elements or style guides that must be incorporated?]]
-
-@{example}
-
-- Replicate the look and feel of early 1900s black and white cinema, including animated effects replicating film damage or projector glitches during page or state transitions.
-- Attached is the full color pallet and tokens for our corporate branding.
-  @{/example}
-
-### Target Device and Platforms
-
-@{example}
-"Web Responsive, and all mobile platforms", "IPhone Only", "ASCII Windows Desktop"
-@{/example}
-
-^^/CONDITION: has_ui^^
-
-## Technical Assumptions
-
-[[LLM: Gather technical decisions that will be used for this simple technical PRD that includes architecture decisions. Steps:
-
-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
-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)
-5. These become constraints for the Architect - be specific and complete
-6. After section completion, apply `tasks#advanced-elicitation` protocol.]]
-
-### Repository Structure: { Monorepo, Polyrepo, etc...}
-
-### Service Architecture
-
-[[LLM: CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).]]
-
-## Testing requirements
-
-[[LLM: CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).]]
-
-### Additional Technical Assumptions and Requests
-
-[[LLM: Throughout the entire process of drafting this document, if any other technical assumptions are raised or discovered appropriate for the architect, add them here as additional bulleted items]]
-
-## Data Models
-
-[[LLM: Define the core data models/entities that will be used in the front end (if there is one), core application or back end, and if both, shared between frontend and backend:
-
-1. Review PRD requirements and identify key business entities
-2. For each model, explain its purpose and relationships
-3. Include key attributes and data types
-4. Show relationships between models
-5. Create TypeScript interfaces that can be shared
-6. Discuss design decisions with user
-
-Create a clear conceptual model before moving to database schema.
-
-After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
-
-<<REPEAT: data_model>>
-
-### {{model_name}}
-
-**Purpose:** {{model_purpose}}
-
-**Key Attributes:**
-
-- {{attribute_1}}: {{type_1}} - {{description_1}}
-- {{attribute_2}}: {{type_2}} - {{description_2}}
-
-**TypeScript Interface:**
-
-````typescript
-{
-  {
-    model_interface;
-  }
-}
-```text
-
-**Relationships:**
-
-- {{relationship_1}}
-- {{relationship_2}}
-  <</REPEAT>>
-
-@{example: data_model}
-
-### User
-
-**Purpose:** Represents authenticated users in the system
-
-**Key Attributes:**
-
-- id: string - Unique identifier
-- email: string - User's email address
-- name: string - Display name
-- role: enum - User permission level
-- timestamps: Date - Created and updated times
-
-**TypeScript Interface:**
-
-```typescript
-interface User {
-  id: string;
-  email: string;
-  name: string;
-  role: "admin" | "user" | "guest";
-  createdAt: Date;
-  updatedAt: Date;
-  profile?: UserProfile;
-}
-
-interface UserProfile {
-  avatarUrl?: string;
-  bio?: string;
-  preferences: Record<string, any>;
-}
-````
-
-**Relationships:**
-
-- Has many Posts (1:n)
-- Has one Profile (1:1)
-  @{/example}
-
-## REST API Spec
-
-[[LLM: Based on the chosen API style from Tech Stack:
-
-1. If REST API, create an OpenAPI 3.0 specification
-2. If GraphQL, provide the GraphQL schema
-3. If tRPC, show router definitions
-4. Include all endpoints from epics/stories
-5. Define request/response schemas based on data models
-6. Document authentication requirements
-7. Include example requests/responses
-
-Use appropriate format for the chosen API style. If no API (e.g., static site), skip this section.]]
-
-^^CONDITION: has_rest_api^^
-
-````yml
-openapi: 3.0.0
-info:
-  title:
-    '[object Object]': null
-  version:
-    '[object Object]': null
-  description:
-    '[object Object]': null
-servers:
-  - url:
-      '[object Object]': null
-    description:
-      '[object Object]': null
-```text
-
-^^/CONDITION: has_rest_api^^
-
-^^CONDITION: has_graphql_api^^
-
-```graphql
-# GraphQL Schema
-{{graphql_schema}}
-````
-
-^^/CONDITION: has_graphql_api^^
-
-^^CONDITION: has_trpc_api^^
-
-```typescript
-// tRPC Router Definitions
-{
-  {
-    trpc_routers;
-  }
-}
-```
-
-^^/CONDITION: has_trpc_api^^
-
-[[LLM: After presenting the API spec (or noting its absence if not applicable), apply `tasks#advanced-elicitation` protocol]]
-
-## Components
-
-[[LLM: Based on the architectural patterns, tech stack, and data models from above:
-
-1. Identify major logical components/services across the fullstack
-2. Consider both frontend and backend components
-3. Define clear boundaries and interfaces between components
-4. For each component, specify:
-
-- Primary responsibility
-- Key interfaces/APIs exposed
-- Dependencies on other components
-- Technology specifics based on tech stack choices
-
-5. Create component diagrams where helpful
-6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
-
-<<REPEAT: component>>
-
-### {{component_name}}
-
-**Responsibility:** {{component_description}}
-
-**Key Interfaces:**
-
-- {{interface_1}}
-- {{interface_2}}
-
-**Dependencies:** {{dependencies}}
-
-**Technology Stack:** {{component_tech_details}}
-<</REPEAT>>
-
-### Component Diagrams
-
-[[LLM: Create Mermaid diagrams to visualize component relationships. Options:
-
-- C4 Container diagram for high-level view
-- Component diagram for detailed internal structure
-- Sequence diagrams for complex interactions
-  Choose the most appropriate for clarity
-
-After presenting the diagrams, apply `tasks#advanced-elicitation` protocol]]
-
-## External APIs
-
-[[LLM: For each external service integration:
-
-1. Identify APIs needed based on PRD requirements and component design
-2. If documentation URLs are unknown, ask user for specifics
-3. Document authentication methods and security considerations
-4. List specific endpoints that will be used
-5. Note any rate limits or usage constraints
-
-If no external APIs are needed, state this explicitly and skip to next section.]]
-
-^^CONDITION: has_external_apis^^
-
-<<REPEAT: external_api>>
-
-### {{api_name}} API
-
-- **Purpose:** {{api_purpose}}
-- **Documentation:** {{api_docs_url}}
-- **Base URL(s):** {{api_base_url}}
-- **Authentication:** {{auth_method}}
-- **Rate Limits:** {{rate_limits}}
-
-**Key Endpoints Used:**
-<<REPEAT: endpoint>>
-
-- `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
-  <</REPEAT>>
-
-**Integration Notes:** {{integration_considerations}}
-<</REPEAT>>
-
-@{example: external_api}
-
-### Stripe API
-
-- **Purpose:** Payment processing and subscription management
-- **Documentation:** https://stripe.com/docs/api
-- **Base URL(s):** `https://api.stripe.com/v1`
-- **Authentication:** Bearer token with secret key
-- **Rate Limits:** 100 requests per second
-
-**Key Endpoints Used:**
+### UI Consistency Requirements
 
-- `POST /customers` - Create customer profiles
-- `POST /payment_intents` - Process payments
-- `POST /subscriptions` - Manage subscriptions
-  @{/example}
+[[LLM: Specific requirements for maintaining visual and interaction consistency with existing application]]
 
-^^/CONDITION: has_external_apis^^
+^^/CONDITION: has_ui^^
 
-[[LLM: After presenting external APIs (or noting their absence), apply `tasks#advanced-elicitation` protocol]]
+## Technical Constraints and Integration Requirements
 
-## Coding Standards
+[[LLM: This section replaces separate architecture documentation. Gather detailed technical constraints from existing project analysis.]]
 
-[[LLM: Define MINIMAL but CRITICAL standards for AI agents. Focus only on project-specific rules that prevent common mistakes. These will be used by dev agents.
+### Existing Technology Stack
 
-After presenting this section, apply `tasks#advanced-elicitation` protocol]]
+[[LLM: Document the current technology stack that must be maintained or integrated with]]
 
-### Critical Fullstack Rules
+**Languages**: [[LLM: Current programming languages in use]]
+**Frameworks**: [[LLM: Current frameworks and their versions]]
+**Database**: [[LLM: Current database technology and schema considerations]]
+**Infrastructure**: [[LLM: Current deployment and hosting infrastructure]]
+**External Dependencies**: [[LLM: Current third-party services and APIs]]
 
-<<REPEAT: critical_rule>>
+### Integration Approach
 
-- **{{rule_name}}:** {{rule_description}}
-  <</REPEAT>>
+[[LLM: Define how the enhancement will integrate with existing architecture]]
 
-@{example: critical_rules}
+**Database Integration Strategy**: [[LLM: How new features will interact with existing database]]
+**API Integration Strategy**: [[LLM: How new APIs will integrate with existing API structure]]
+**Frontend Integration Strategy**: [[LLM: How new UI components will integrate with existing frontend]]
+**Testing Integration Strategy**: [[LLM: How new tests will integrate with existing test suite]]
 
-- **Type Sharing:** Always define types in packages/shared and import from there
-- **API Calls:** Never make direct HTTP calls - use the service layer
-- **Environment Variables:** Access only through config objects, never process.env directly
-- **Error Handling:** All API routes must use the standard error handler
-- **State Updates:** Never mutate state directly - use proper state management patterns
-  @{/example}
+### Code Organization and Standards
 
-### Naming Conventions
+[[LLM: Based on existing project analysis, define how new code will fit existing patterns]]
 
-| Element         | Frontend             | Backend    | Example             |
-| :-------------- | :------------------- | :--------- | :------------------ |
-| Components      | PascalCase           | -          | `UserProfile.tsx`   |
-| Hooks           | camelCase with 'use' | -          | `useAuth.ts`        |
-| API Routes      | -                    | kebab-case | `/api/user-profile` |
-| Database Tables | -                    | snake_case | `user_profiles`     |
+**File Structure Approach**: [[LLM: How new files will fit existing project structure]]
+**Naming Conventions**: [[LLM: Existing naming conventions that must be followed]]
+**Coding Standards**: [[LLM: Existing coding standards and linting rules]]
+**Documentation Standards**: [[LLM: How new code documentation will match existing patterns]]
 
-## Epics
+### Deployment and Operations
 
-[[LLM: First, present a high-level list of all epics for user approval, the epic_list and immediately execute tasks#advanced-elicitation display. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.
+[[LLM: How the enhancement fits existing deployment pipeline]]
 
-CRITICAL: Epics MUST be logically sequential following agile best practices:
+**Build Process Integration**: [[LLM: How enhancement builds with existing process]]
+**Deployment Strategy**: [[LLM: How enhancement will be deployed alongside existing features]]
+**Monitoring and Logging**: [[LLM: How enhancement will integrate with existing monitoring]]
+**Configuration Management**: [[LLM: How new configuration will integrate with existing config]]
 
-- Each epic should deliver a significant, end-to-end, fully deployable increment of testable functionality
-- Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page
-- Each subsequent epic builds upon previous epics' functionality delivering major blocks of functionality that provide tangible value to users or business when deployed
-- Not every project needs multiple epics, an epic needs to deliver value. For example, an API completed can deliver value even if a UI is not complete and planned for a separate epic.
-- Err on the side of less epics, but let the user know your rationale and offer options for splitting them if it seems some are too large or focused on disparate things.
-- Cross Cutting Concerns should flow through epics and stories and not be final stories. For example, adding a logging framework as a last story of an epic, or at the end of a project as a final epic or story would be terrible as we would not have logging from the beginning.]]
+### Risk Assessment and Mitigation
 
-<<REPEAT: epic_list>>
+[[LLM: Identify risks specific to working with existing codebase]]
 
-- Epic{{epic_number}} {{epic_title}}: {{short_goal}}
+**Technical Risks**: [[LLM: Risks related to modifying existing code]]
+**Integration Risks**: [[LLM: Risks in integrating with existing systems]]
+**Deployment Risks**: [[LLM: Risks in deploying alongside existing features]]
+**Mitigation Strategies**: [[LLM: Specific strategies to address identified risks]]
 
-<</REPEAT>>
+## Epic and Story Structure
 
-@{example: epic_list}
+[[LLM: For brownfield projects, favor a single comprehensive epic unless the user is clearly requesting multiple unrelated enhancements. Before presenting the epic structure, confirm: "Based on my analysis of your existing project, I believe this enhancement should be structured as [single epic/multiple epics] because [rationale based on actual project analysis]. Does this align with your understanding of the work required?" Then present the epic structure and immediately execute tasks#advanced-elicitation display.]]
 
-1. Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management
-2. Core Business Entities: Create and manage primary domain objects with CRUD operations
-3. User Workflows & Interactions: Enable key user journeys and business processes
-4. Reporting & Analytics: Provide insights and data visualization for users
+### Epic Approach
 
-@{/example}
+[[LLM: Explain the rationale for epic structure - typically single epic for brownfield unless multiple unrelated features]]
 
-[[LLM: After the epic list is approved, present each `epic_details` with all its stories and acceptance criteria as a complete review unit and immediately execute tasks#advanced-elicitation display, before moving on to the next epic.]]
+**Epic Structure Decision**: [[LLM: Single Epic or Multiple Epics with rationale]]
 
-<<REPEAT: epic_details>>
+## Epic 1: {{enhancement_title}}
 
-## Epic {{epic_number}} {{epic_title}}
+[[LLM: Comprehensive epic that delivers the brownfield enhancement while maintaining existing functionality]]
 
-{{epic_goal}} [[LLM: Expanded goal - 2-3 sentences describing the objective and value all the stories will achieve]]
+**Epic Goal**: [[LLM: 2-3 sentences describing the complete enhancement objective and value]]
 
-[[LLM: CRITICAL STORY SEQUENCING REQUIREMENTS:
+**Integration Requirements**: [[LLM: Key integration points with existing system]]
 
-- Stories within each epic MUST be logically sequential
-- Each story should be a "vertical slice" delivering complete functionality
-- No story should depend on work from a later story or epic
-- Identify and note any direct prerequisite stories
-- Focus on "what" and "why" not "how" (leave technical implementation to Architect) yet be precise enough to support a logical sequential order of operations from story to story.
-- Ensure each story delivers clear user or business value, try to avoid enablers and build them into stories that deliver value.
-- Size stories for AI agent execution: Each story must be completable by a single AI agent in one focused session without context overflow
-- Think "junior developer working for 2-4 hours" - stories must be small, focused, and self-contained
-- If a story seems complex, break it down further as long as it can deliver a vertical slice
-- Each story should result in working, testable code before the agent's context window fills]]
+[[LLM: CRITICAL STORY SEQUENCING FOR BROWNFIELD:
+
+- Stories must ensure existing functionality remains intact
+- Each story should include verification that existing features still work
+- Stories should be sequenced to minimize risk to existing system
+- Include rollback considerations for each story
+- Focus on incremental integration rather than big-bang changes
+- Size stories for AI agent execution in existing codebase context
+- MANDATORY: Present the complete story sequence and ask: "This story sequence is designed to minimize risk to your existing system. Does this order make sense given your project's architecture and constraints?"
+- Stories must be logically sequential with clear dependencies identified
+- Each story must deliver value while maintaining system integrity]]
 
 <<REPEAT: story>>
 
-### Story {{epic_number}}.{{story_number}} {{story_title}}
+### Story 1.{{story_number}} {{story_title}}
 
 As a {{user_type}},
 I want {{action}},
@@ -3796,29 +3325,24 @@ so that {{benefit}}.
 
 #### Acceptance Criteria
 
-[[LLM: Define clear, comprehensive, and testable acceptance criteria that:
-
-- Precisely define what "done" means from a functional perspective
-- Are unambiguous and serve as basis for verification
-- Include any critical non-functional requirements from the PRD
-- Consider local testability for backend/data components
-- Specify UI/UX requirements and framework adherence where applicable
-- Avoid cross-cutting concerns that should be in other stories or PRD sections]]
+[[LLM: Define criteria that include both new functionality and existing system integrity]]
 
 <<REPEAT: criteria>>
 
 - {{criterion number}}: {{criteria}}
 
-<</REPEAT>>
-<</REPEAT>>
 <</REPEAT>>
 
-## Next Steps
+#### Integration Verification
 
-### Design Architect Prompt
+[[LLM: Specific verification steps to ensure existing functionality remains intact]]
 
-[[LLM: 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.]]
-==================== END: templates#simple-project-prd-tmpl ====================
+- IV1: [[LLM: Existing functionality verification requirement]]
+- IV2: [[LLM: Integration point verification requirement]]
+- IV3: [[LLM: Performance impact verification requirement]]
+
+<</REPEAT>>
+==================== END: templates#brownfield-prd-tmpl ====================
 
 ==================== START: checklists#pm-checklist ====================
 # Product Manager (PM) Requirements Checklist
@@ -5821,7 +5345,7 @@ Document the choice and key services that will be used.]]
 
 ### Repository Structure
 
-[[LLM: Define the repository approach based on PRD requirements and platform choice:
+[[LLM: Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask quetsions to the user if unsure:
 
 1. For modern fullstack apps, monorepo is often preferred
 2. Consider tooling (Nx, Turborepo, Lerna, npm workspaces)
@@ -5846,9 +5370,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 +5483,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
     model_interface;
   }
 }
-````
+```
 
 **Relationships:**
 
@@ -5983,7 +5507,7 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
 
 **TypeScript Interface:**
 
-````typescript
+```typescript
 interface User {
   id: string;
   email: string;
@@ -5999,7 +5523,7 @@ interface UserProfile {
   bio?: string;
   preferences: Record<string, any>;
 }
-```text
+```
 
 **Relationships:**
 
@@ -6037,16 +5561,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 +5583,7 @@ servers:
     trpc_routers;
   }
 }
-````
+```
 
 ^^/CONDITION: has_trpc_api^^
 
@@ -6204,19 +5728,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 +5754,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
     state_structure;
   }
 }
-`````
+```
 
 **State Management Patterns:**
 
@@ -6245,17 +5769,17 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ```text
 {{route_structure}}
-```text
+```
 
 **Protected Route Pattern:**
 
-````typescript
+```typescript
 {
   {
     protected_route_example;
   }
 }
-```text
+```
 
 ### Frontend Services Layer
 
@@ -6269,17 +5793,17 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
     api_client_setup;
   }
 }
-````
+```
 
 **Service Example:**
 
-````typescript
+```typescript
 {
   {
     service_example;
   }
 }
-```text
+```
 
 ## Backend Architecture
 
@@ -6294,11 +5818,11 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 ^^CONDITION: serverless^^
 **Function Organization:**
 
-````
+```text
 
 {{function_structure}}
 
-````text
+```
 
 **Function Template:**
 
@@ -6308,26 +5832,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 +5863,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 +5883,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 +5953,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 +5975,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 +5999,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 # Run tests
 {{test_commands}}
-```text
+```
 
 ### Environment Configuration
 
@@ -6490,7 +6014,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 # Shared
 {{shared_env_vars}}
-````
+```
 
 ## Deployment Architecture
 
@@ -6513,9 +6037,9 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ### CI/CD Pipeline
 
-````yaml
+```yaml
 '[object Object]': null
-```text
+```
 
 ### Environments
 
@@ -6573,7 +6097,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ### Testing Pyramid
 
-````
+```text
 
         E2E Tests
        /          \
@@ -6582,17 +6106,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 +6124,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 +6144,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 +6164,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
     e2e_test_example;
   }
 }
-````
+```
 
 ## Coding Standards
 
@@ -6681,9 +6205,9 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ### Error Flow
 
-````mermaid
+```mermaid
 {{error_flow_diagram}}
-```text
+```
 
 ### Error Response Format
 
@@ -6697,17 +6221,17 @@ interface ApiError {
     requestId: string;
   };
 }
-````
+```
 
 ### Frontend Error Handling
 
-````typescript
+```typescript
 {
   {
     frontend_error_handler;
   }
 }
-```text
+```
 
 ### Backend Error Handling
 
@@ -6717,7 +6241,7 @@ interface ApiError {
     backend_error_handler;
   }
 }
-````
+```
 
 ## Monitoring and Observability
 
@@ -8268,8 +7792,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 +7832,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]
-
-        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
-
-        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
+        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
+
+        B -.-> B1[Optional: brainstorming]
+        B -.-> B2[Optional: market research]
+        D -.-> D1[Optional: technical research]
+
+        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 +7866,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 +7891,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 +7924,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?}
-
-        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
+        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
+
+        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 ====================