appiq-solution 1.4.7 → 1.4.9

package/#Tools/APPIQ-METHOD/bmad-core/templates/story-tmpl.yaml

@@ -1,137 +0,0 @@
-template:
-  id: story-template-v2
-  name: Story Document
-  version: 2.0
-  output:
-    format: markdown
-    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md
-    title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}"
-
-workflow:
-  mode: interactive
-  elicitation: advanced-elicitation
-
-agent_config:
-  editable_sections: 
-    - Status
-    - Story
-    - Acceptance Criteria
-    - Tasks / Subtasks
-    - Dev Notes
-    - Testing
-    - Change Log
-
-sections:
-  - id: status
-    title: Status
-    type: choice
-    choices: [Draft, Approved, InProgress, Review, Done]
-    instruction: Select the current status of the story
-    owner: scrum-master
-    editors: [scrum-master, dev-agent]
-    
-  - id: story
-    title: Story
-    type: template-text
-    template: |
-      **As a** {{role}},
-      **I want** {{action}},
-      **so that** {{benefit}}
-    instruction: Define the user story using the standard format with role, action, and benefit
-    elicit: true
-    owner: scrum-master
-    editors: [scrum-master]
-    
-  - id: acceptance-criteria
-    title: Acceptance Criteria
-    type: numbered-list
-    instruction: Copy the acceptance criteria numbered list from the epic file
-    elicit: true
-    owner: scrum-master
-    editors: [scrum-master]
-    
-  - id: tasks-subtasks
-    title: Tasks / Subtasks
-    type: bullet-list
-    instruction: |
-      Break down the story into specific tasks and subtasks needed for implementation.
-      Reference applicable acceptance criteria numbers where relevant.
-    template: |
-      - [ ] Task 1 (AC: # if applicable)
-        - [ ] Subtask1.1...
-      - [ ] Task 2 (AC: # if applicable)
-        - [ ] Subtask 2.1...
-      - [ ] Task 3 (AC: # if applicable)
-        - [ ] Subtask 3.1...
-    elicit: true
-    owner: scrum-master
-    editors: [scrum-master, dev-agent]
-    
-  - id: dev-notes
-    title: Dev Notes
-    instruction: |
-      Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story:
-      - Do not invent information
-      - If known add Relevant Source Tree info that relates to this story
-      - If there were important notes from previous story that are relevant to this one, include them here
-      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story, meeting all AC and completing all tasks+subtasks
-    elicit: true
-    owner: scrum-master
-    editors: [scrum-master]
-    sections:
-      - id: testing-standards
-        title: Testing
-        instruction: |
-          List Relevant Testing Standards from Architecture the Developer needs to conform to:
-          - Test file location
-          - Test standards
-          - Testing frameworks and patterns to use
-          - Any specific testing requirements for this story
-        elicit: true
-        owner: scrum-master
-        editors: [scrum-master]
-        
-  - id: change-log
-    title: Change Log
-    type: table
-    columns: [Date, Version, Description, Author]
-    instruction: Track changes made to this story document
-    owner: scrum-master
-    editors: [scrum-master, dev-agent, qa-agent]
-    
-  - id: dev-agent-record
-    title: Dev Agent Record
-    instruction: This section is populated by the development agent during implementation
-    owner: dev-agent
-    editors: [dev-agent]
-    sections:
-      - id: agent-model
-        title: Agent Model Used
-        template: "{{agent_model_name_version}}"
-        instruction: Record the specific AI agent model and version used for development
-        owner: dev-agent
-        editors: [dev-agent]
-        
-      - id: debug-log-references
-        title: Debug Log References
-        instruction: Reference any debug logs or traces generated during development
-        owner: dev-agent
-        editors: [dev-agent]
-        
-      - id: completion-notes
-        title: Completion Notes List
-        instruction: Notes about the completion of tasks and any issues encountered
-        owner: dev-agent
-        editors: [dev-agent]
-        
-      - id: file-list
-        title: File List
-        instruction: List all files created, modified, or affected during story implementation
-        owner: dev-agent
-        editors: [dev-agent]
-        
-  - id: qa-results
-    title: QA Results
-    instruction: Results from QA Agent QA review of the completed story implementation
-    owner: qa-agent
-    editors: [qa-agent]

package/#Tools/APPIQ-METHOD/bmad-core/user-guide.md

@@ -1,251 +0,0 @@
-# BMad-Method BMAd Code User Guide
-
-This guide will help you understand and effectively use the BMad Method for agile AI driven planning and development.
-
-## The BMad Plan and Execute Workflow
-
-First, here is the full standard Greenfield Planning + Execution Workflow. Brownfield is very similar, but it's suggested to understand this greenfield first, even if on a simple project before tackling a brownfield project. The BMad Method needs to be installed to the root of your new project folder. For the planning phase, you can optionally perform it with powerful web agents, potentially resulting in higher quality results at a fraction of the cost it would take to complete if providing your own API key or credits in some Agentic tools. For planning, powerful thinking models and larger context - along with working as a partner with the agents will net the best results.
-
-If you are going to use the BMad Method with a Brownfield project (an existing project), review **[Working in the Brownfield](./working-in-the-brownfield.md)**.
-
-If you do not see the diagrams that following rendering, you can install Markdown All in One along with the Markdown Preview Mermaid Support plugins to VSCode (or one of the forked clones). With these plugin's, if you right click on the tab when open, there should be a Open Preview option, or check the IDE documentation.
-
-### The Planning Workflow (Web UI or Powerful IDE Agents)
-
-Before development begins, BMad follows a structured planning workflow that's ideally done in web UI for cost efficiency:
-
-```mermaid
-graph TD
-    A["Start: Project Idea"] --> B{"Optional: Analyst Research"}
-    B -->|Yes| C["Analyst: Brainstorming (Optional)"]
-    B -->|No| G{"Project Brief Available?"}
-    C --> C2["Analyst: Market Research (Optional)"]
-    C2 --> C3["Analyst: Competitor Analysis (Optional)"]
-    C3 --> D["Analyst: Create Project Brief"]
-    D --> G
-    G -->|Yes| E["PM: Create PRD from Brief (Fast Track)"]
-    G -->|No| E2["PM: Interactive PRD Creation (More Questions)"]
-    E --> F["PRD Created with FRs, NFRs, Epics & Stories"]
-    E2 --> F
-    F --> F2{"UX Required?"}
-    F2 -->|Yes| F3["UX Expert: Create Front End Spec"]
-    F2 -->|No| H["Architect: Create Architecture from PRD"]
-    F3 --> F4["UX Expert: Generate UI Prompt for Lovable/V0 (Optional)"]
-    F4 --> H2["Architect: Create Architecture from PRD + UX Spec"]
-    H --> I["PO: Run Master Checklist"]
-    H2 --> I
-    I --> J{"Documents Aligned?"}
-    J -->|Yes| K["Planning Complete"]
-    J -->|No| L["PO: Update Epics & Stories"]
-    L --> M["Update PRD/Architecture as needed"]
-    M --> I
-    K --> N["📁 Switch to IDE (If in a Web Agent Platform)"]
-    N --> O["PO: Shard Documents"]
-    O --> P["Ready for SM/Dev Cycle"]
-
-    style A fill:#f5f5f5,color:#000
-    style B fill:#e3f2fd,color:#000
-    style C fill:#e8f5e9,color:#000
-    style C2 fill:#e8f5e9,color:#000
-    style C3 fill:#e8f5e9,color:#000
-    style D fill:#e8f5e9,color:#000
-    style E fill:#fff3e0,color:#000
-    style E2 fill:#fff3e0,color:#000
-    style F fill:#fff3e0,color:#000
-    style F2 fill:#e3f2fd,color:#000
-    style F3 fill:#e1f5fe,color:#000
-    style F4 fill:#e1f5fe,color:#000
-    style G fill:#e3f2fd,color:#000
-    style H fill:#f3e5f5,color:#000
-    style H2 fill:#f3e5f5,color:#000
-    style I fill:#f9ab00,color:#fff
-    style J fill:#e3f2fd,color:#000
-    style K fill:#34a853,color:#fff
-    style L fill:#f9ab00,color:#fff
-    style M fill:#fff3e0,color:#000
-    style N fill:#1a73e8,color:#fff
-    style O fill:#f9ab00,color:#fff
-    style P fill:#34a853,color:#fff
-```
-
-#### Web UI to IDE Transition
-
-**Critical Transition Point**: Once the PO confirms document alignment, you must switch from web UI to IDE to begin the development workflow:
-
-1. **Copy Documents to Project**: Ensure `docs/prd.md` and `docs/architecture.md` are in your project's docs folder (or a custom location you can specify during installation)
-2. **Switch to IDE**: Open your project in your preferred Agentic IDE
-3. **Document Sharding**: Use the PO agent to shard the PRD and then the Architecture
-4. **Begin Development**: Start the Core Development Cycle that follows
-
-### The Core Development Cycle (IDE)
-
-Once planning is complete and documents are sharded, BMad follows a structured development workflow:
-
-```mermaid
-graph TD
-    A["Development Phase Start"] --> B["SM: Reviews Previous Story Dev/QA Notes"]
-    B --> B2["SM: Drafts Next Story from Sharded Epic + Architecture"]
-    B2 --> B3{"PO: Validate Story Draft (Optional)"}
-    B3 -->|Validation Requested| B4["PO: Validate Story Against Artifacts"]
-    B3 -->|Skip Validation| C{"User Approval"}
-    B4 --> C
-    C -->|Approved| D["Dev: Sequential Task Execution"]
-    C -->|Needs Changes| B2
-    D --> E["Dev: Implement Tasks + Tests"]
-    E --> F["Dev: Run All Validations"]
-    F --> G["Dev: Mark Ready for Review + Add Notes"]
-    G --> H{"User Verification"}
-    H -->|Request QA Review| I["QA: Senior Dev Review + Active Refactoring"]
-    H -->|Approve Without QA| M["IMPORTANT: Verify All Regression Tests and Linting are Passing"]
-    I --> J["QA: Review, Refactor Code, Add Tests, Document Notes"]
-    J --> L{"QA Decision"}
-    L -->|Needs Dev Work| D
-    L -->|Approved| M
-    H -->|Needs Fixes| D
-    M --> N["IMPORTANT: COMMIT YOUR CHANGES BEFORE PROCEEDING!"]
-    N --> K["Mark Story as Done"]
-    K --> B
-
-    style A fill:#f5f5f5,color:#000
-    style B fill:#e8f5e9,color:#000
-    style B2 fill:#e8f5e9,color:#000
-    style B3 fill:#e3f2fd,color:#000
-    style B4 fill:#fce4ec,color:#000
-    style C fill:#e3f2fd,color:#000
-    style D fill:#e3f2fd,color:#000
-    style E fill:#e3f2fd,color:#000
-    style F fill:#e3f2fd,color:#000
-    style G fill:#e3f2fd,color:#000
-    style H fill:#e3f2fd,color:#000
-    style I fill:#f9ab00,color:#fff
-    style J fill:#ffd54f,color:#000
-    style K fill:#34a853,color:#fff
-    style L fill:#e3f2fd,color:#000
-    style M fill:#ff5722,color:#fff
-    style N fill:#d32f2f,color:#fff
-```
-
-## Installation
-
-### Optional
-
-If you want to do the planning in the Web with Claude (Sonnet 4 or Opus), Gemini Gem (2.5 Pro), or Custom GPT's:
-
-1. Navigate to `dist/teams/`
-2. Copy `team-fullstack.txt`
-3. Create new Gemini Gem or CustomGPT
-4. Upload file with instructions: "Your critical operating instructions are attached, do not break character as directed"
-5. Type `/help` to see available commands
-
-### IDE Project Setup
-
-```bash
-# Interactive installation (recommended)
-npx bmad-method install
-```
-
-## Special Agents
-
-There are two bmad agents - in the future they will be consolidated into the single bmad-master.
-
-### BMad-Master
-
-This agent can do any task or command that all other agents can do, aside from actual story implementation. Additionally, this agent can help explain the BMad Method when in the web by accessing the knowledge base and explaining anything to you about the process.
-
-If you don't want to bother switching between different agents aside from the dev, this is the agent for you. Just remember that as the context grows, the performance of the agent degrades, therefore it is important to instruct the agent to compact the conversation and start a new conversation with the compacted conversation as the initial message. Do this often, preferably after each story is implemented.
-
-### BMad-Orchestrator
-
-This agent should NOT be used within the IDE, it is a heavy weight special purpose agent that utilizes a lot of context and can morph into any other agent. This exists solely to facilitate the team's within the web bundles. If you use a web bundle you will be greeted by the BMad Orchestrator.
-
-### How Agents Work
-
-#### Dependencies System
-
-Each agent has a YAML section that defines its dependencies:
-
-```yaml
-dependencies:
-  templates:
-    - prd-template.md
-    - user-story-template.md
-  tasks:
-    - create-doc.md
-    - shard-doc.md
-  data:
-    - bmad-kb.md
-```
-
-**Key Points:**
-
-- Agents only load resources they need (lean context)
-- Dependencies are automatically resolved during bundling
-- Resources are shared across agents to maintain consistency
-
-#### Agent Interaction
-
-**In IDE:**
-
-```bash
-# Some Ide's, like Cursor or Windsurf for example, utilize manual rules so interaction is done with the '@' symbol
-@pm Create a PRD for a task management app
-@architect Design the system architecture
-@dev Implement the user authentication
-
-# Some, like Claude Code use slash commands instead
-/pm Create user stories
-/dev Fix the login bug
-```
-
-#### Interactive Modes
-
-- **Incremental Mode**: Step-by-step with user input
-- **YOLO Mode**: Rapid generation with minimal interaction
-
-## IDE Integration
-
-### IDE Best Practices
-
-- **Context Management**: Keep relevant files only in context, keep files as lean and focused as necessary
-- **Agent Selection**: Use appropriate agent for task
-- **Iterative Development**: Work in small, focused tasks
-- **File Organization**: Maintain clean project structure
-- **Commit Regularly**: Save your work frequently
-
-## Technical Preferences System
-
-BMad includes a personalization system through the `technical-preferences.md` file located in `.bmad-core/data/` - this can help bias the PM and Architect to recommend your preferences for design patterns, technology selection, or anything else you would like to put in here.
-
-### Using with Web Bundles
-
-When creating custom web bundles or uploading to AI platforms, include your `technical-preferences.md` content to ensure agents have your preferences from the start of any conversation.
-
-## Core Configuration
-
-The `bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml.
-
-### Developer Context Files
-
-Define which files the dev agent should always load:
-
-```yaml
-devLoadAlwaysFiles:
-  - docs/architecture/coding-standards.md
-  - docs/architecture/tech-stack.md
-  - docs/architecture/project-structure.md
-```
-
-You will want to verify from sharding your architecture that these documents exist, that they are as lean as possible, and contain exactly the information you want your dev agent to ALWAYS load into it's context. These are the rules the agent will follow.
-
-As your project grows and the code starts to build consistent patterns, coding standards should be reduced to include only the standards that the agent still makes with. The agent will look at surrounding code in files to infer the coding standards that are relevant to the current task.
-
-## Getting Help
-
-- **Discord Community**: [Join Discord](https://discord.gg/gk8jAdXWmj)
-- **GitHub Issues**: [Report bugs](https://github.com/bmadcode/bmad-method/issues)
-- **Documentation**: [Browse docs](https://github.com/bmadcode/bmad-method/docs)
-- **YouTube**: [BMadCode Channel](https://www.youtube.com/@BMadCode)
-
-## Conclusion
-
-Remember: BMad is designed to enhance your development process, not replace your expertise. Use it as a powerful tool to accelerate your projects while maintaining control over design decisions and implementation details.

package/#Tools/APPIQ-METHOD/bmad-core/workflows/brownfield-fullstack.yaml

@@ -1,311 +0,0 @@
-workflow:
-  id: brownfield-fullstack
-  name: Brownfield Full-Stack Enhancement
-  description: >-
-    Agent workflow for enhancing existing full-stack applications with new features,
-    modernization, or significant changes. Handles existing system analysis and safe integration.
-  type: brownfield
-  project_types:
-    - feature-addition
-    - refactoring
-    - modernization
-    - integration-enhancement
-
-  sequence:
-    - step: enhancement_classification
-      agent: analyst
-      action: classify enhancement scope
-      notes: |
-        Determine enhancement complexity to route to appropriate path:
-        - Single story (< 4 hours) → Use brownfield-create-story task
-        - Small feature (1-3 stories) → Use brownfield-create-epic task  
-        - Major enhancement (multiple epics) → Continue with full workflow
-        
-        Ask user: "Can you describe the enhancement scope? Is this a small fix, a feature addition, or a major enhancement requiring architectural changes?"
-
-    - step: routing_decision
-      condition: based_on_classification
-      routes:
-        single_story:
-          agent: pm
-          uses: brownfield-create-story
-          notes: "Create single story for immediate implementation. Exit workflow after story creation."
-        small_feature:
-          agent: pm
-          uses: brownfield-create-epic
-          notes: "Create focused epic with 1-3 stories. Exit workflow after epic creation."
-        major_enhancement:
-          continue: to_next_step
-          notes: "Continue with comprehensive planning workflow below."
-
-    - step: documentation_check
-      agent: analyst
-      action: check existing documentation
-      condition: major_enhancement_path
-      notes: |
-        Check if adequate project documentation exists:
-        - Look for existing architecture docs, API specs, coding standards
-        - Assess if documentation is current and comprehensive
-        - If adequate: Skip document-project, proceed to PRD
-        - If inadequate: Run document-project first
-
-    - step: project_analysis
-      agent: architect
-      action: analyze existing project and use task document-project
-      creates: brownfield-architecture.md (or multiple documents)
-      condition: documentation_inadequate
-      notes: |
-        Run document-project to capture current system state, technical debt, and constraints. Pass findings to PRD creation.
-        
-        For Flutter projects, analyze:
-        - Current Flutter architecture (Clean Architecture compliance)
-        - Feature-based organization structure
-        - State management patterns (Cubit/BLoC usage)
-        - Dependencies and version compatibility
-        - Performance and accessibility compliance
-
-    - agent: pm
-      creates: prd.md
-      uses: brownfield-prd-tmpl
-      requires: existing_documentation_or_analysis
-      notes: |
-        Creates PRD for major enhancement. If document-project was run, reference its output to avoid re-analysis.
-        If skipped, use existing project documentation.
-        SAVE OUTPUT: Copy final prd.md to your project's docs/ folder.
-        
-        For Flutter projects, use flutter-mobile-prd-tmpl.yaml to ensure:
-        - Feature-based requirements organization
-        - Clean Architecture layer specifications
-        - Material Design 3 compliance requirements
-        - Mobile-specific performance and accessibility criteria
-
-    - step: architecture_decision
-      agent: pm/architect
-      action: determine if architecture document needed
-      condition: after_prd_creation
-      notes: |
-        Review PRD to determine if architectural planning is needed:
-        - New architectural patterns → Create architecture doc
-        - New libraries/frameworks → Create architecture doc
-        - Platform/infrastructure changes → Create architecture doc
-        - Following existing patterns → Skip to story creation
-
-    - agent: architect
-      creates: architecture.md
-      uses: brownfield-architecture-tmpl
-      requires: prd.md
-      condition: architecture_changes_needed
-      notes: "Creates architecture ONLY for significant architectural changes. SAVE OUTPUT: Copy final architecture.md to your project's docs/ folder."
-
-    - agent: po
-      validates: all_artifacts
-      uses: po-master-checklist
-      notes: "Validates all documents for integration safety and completeness. May require updates to any document."
-
-    - agent: various
-      updates: any_flagged_documents
-      condition: po_checklist_issues
-      notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
-
-    - agent: po
-      action: shard_documents
-      creates: sharded_docs
-      requires: all_artifacts_in_project
-      notes: |
-        Shard documents for IDE development:
-        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-        - Creates docs/prd/ and docs/architecture/ folders with sharded content
-
-    - agent: sm
-      action: create_story
-      creates: story.md
-      requires: sharded_docs_or_brownfield_docs
-      repeats: for_each_epic_or_enhancement
-      notes: |
-        Story creation cycle:
-        - For sharded PRD: @sm → *create (uses create-next-story)
-        - For brownfield docs: @sm → use create-brownfield-story task
-        - Creates story from available documentation
-        - Story starts in "Draft" status
-        - May require additional context gathering for brownfield
-
-    - agent: analyst/pm
-      action: review_draft_story
-      updates: story.md
-      requires: story.md
-      optional: true
-      condition: user_wants_story_review
-      notes: |
-        OPTIONAL: Review and approve draft story
-        - NOTE: story-review task coming soon
-        - Review story completeness and alignment
-        - Update story status: Draft → Approved
-
-    - agent: dev
-      action: implement_story
-      creates: implementation_files
-      requires: story.md
-      notes: |
-        Dev Agent (New Chat): @dev
-        - Implements approved story
-        - Updates File List with all changes
-        - Marks story as "Review" when complete
-
-    - agent: qa
-      action: review_implementation
-      updates: implementation_files
-      requires: implementation_files
-      optional: true
-      notes: |
-        OPTIONAL: QA Agent (New Chat): @qa → review-story
-        - Senior dev review with refactoring ability
-        - Fixes small issues directly
-        - Leaves checklist for remaining items
-        - Updates story status (Review → Done or stays Review)
-
-    - agent: dev
-      action: address_qa_feedback
-      updates: implementation_files
-      condition: qa_left_unchecked_items
-      notes: |
-        If QA left unchecked items:
-        - Dev Agent (New Chat): Address remaining items
-        - Return to QA for final approval
-
-    - repeat_development_cycle:
-      action: continue_for_all_stories
-      notes: |
-        Repeat story cycle (SM → Dev → QA) for all epic stories
-        Continue until all stories in PRD are complete
-
-    - agent: po
-      action: epic_retrospective
-      creates: epic-retrospective.md
-      condition: epic_complete
-      optional: true
-      notes: |
-        OPTIONAL: After epic completion
-        - NOTE: epic-retrospective task coming soon
-        - Validate epic was completed correctly
-        - Document learnings and improvements
-
-    - workflow_end:
-      action: project_complete
-      notes: |
-        All stories implemented and reviewed!
-        Project development phase complete.
-        
-        Reference: {root}/data/bmad-kb.md#IDE Development Workflow
-
-  flow_diagram: |
-    ```mermaid
-    graph TD
-        A[Start: Brownfield Enhancement] --> B[analyst: classify enhancement scope]
-        B --> C{Enhancement Size?}
-        
-        C -->|Single Story| D[pm: brownfield-create-story]
-        C -->|1-3 Stories| E[pm: brownfield-create-epic]
-        C -->|Major Enhancement| F[analyst: check documentation]
-        
-        D --> END1[To Dev Implementation]
-        E --> END2[To Story Creation]
-        
-        F --> G{Docs Adequate?}
-        G -->|No| H[architect: document-project]
-        G -->|Yes| I[pm: brownfield PRD]
-        H --> I
-        
-        I --> J{Architecture Needed?}
-        J -->|Yes| K[architect: architecture.md]
-        J -->|No| L[po: validate artifacts]
-        K --> L
-        
-        L --> M{PO finds issues?}
-        M -->|Yes| N[Fix issues]
-        M -->|No| O[po: shard documents]
-        N --> L
-        
-        O --> P[sm: create story]
-        P --> Q{Story Type?}
-        Q -->|Sharded PRD| R[create-next-story]
-        Q -->|Brownfield Docs| S[create-brownfield-story]
-        
-        R --> T{Review draft?}
-        S --> T
-        T -->|Yes| U[review & approve]
-        T -->|No| V[dev: implement]
-        U --> V
-        
-        V --> W{QA review?}
-        W -->|Yes| X[qa: review]
-        W -->|No| Y{More stories?}
-        X --> Z{Issues?}
-        Z -->|Yes| AA[dev: fix]
-        Z -->|No| Y
-        AA --> X
-        Y -->|Yes| P
-        Y -->|No| AB{Retrospective?}
-        AB -->|Yes| AC[po: retrospective]
-        AB -->|No| AD[Complete]
-        AC --> AD
-
-        style AD fill:#90EE90
-        style END1 fill:#90EE90
-        style END2 fill:#90EE90
-        style D fill:#87CEEB
-        style E fill:#87CEEB
-        style I fill:#FFE4B5
-        style K fill:#FFE4B5
-        style O fill:#ADD8E6
-        style P fill:#ADD8E6
-        style V fill:#ADD8E6
-        style U fill:#F0E68C
-        style X fill:#F0E68C
-        style AC fill:#F0E68C
-    ```
-
-  decision_guidance:
-    when_to_use:
-      - Enhancement requires coordinated stories
-      - Architectural changes are needed
-      - Significant integration work required
-      - Risk assessment and mitigation planning necessary
-      - Multiple team members will work on related changes
-
-  handoff_prompts:
-    classification_complete: |
-      Enhancement classified as: {{enhancement_type}}
-      {{if single_story}}: Proceeding with brownfield-create-story task for immediate implementation.
-      {{if small_feature}}: Creating focused epic with brownfield-create-epic task.
-      {{if major_enhancement}}: Continuing with comprehensive planning workflow.
-    
-    documentation_assessment: |
-      Documentation assessment complete:
-      {{if adequate}}: Existing documentation is sufficient. Proceeding directly to PRD creation.
-      {{if inadequate}}: Running document-project to capture current system state before PRD.
-    
-    document_project_to_pm: |
-      Project analysis complete. Key findings documented in:
-      - {{document_list}}
-      Use these findings to inform PRD creation and avoid re-analyzing the same aspects.
-    
-    pm_to_architect_decision: |
-      PRD complete and saved as docs/prd.md. 
-      Architectural changes identified: {{yes/no}}
-      {{if yes}}: Proceeding to create architecture document for: {{specific_changes}}
-      {{if no}}: No architectural changes needed. Proceeding to validation.
-    
-    architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for integration safety."
-    
-    po_to_sm: |
-      All artifacts validated. 
-      Documentation type available: {{sharded_prd / brownfield_docs}}
-      {{if sharded}}: Use standard create-next-story task.
-      {{if brownfield}}: Use create-brownfield-story task to handle varied documentation formats.
-    
-    sm_story_creation: |
-      Creating story from {{documentation_type}}.
-      {{if missing_context}}: May need to gather additional context from user during story creation.
-    
-    complete: "All planning artifacts validated and development can begin. Stories will be created based on available documentation format."