appiq-solution 1.3.2 → 1.4.2

package/#Tools/APPIQ-METHOD/bmad-core/templates/flutter-ui-spec-tmpl.yaml

@@ -0,0 +1,415 @@
+document:
+  type: Flutter UI/UX Specification
+  version: 1.0
+  output_file: flutter-ui-spec.md
+
+metadata:
+  project_name: "[Project Name]"
+  feature_name: "[Feature Name]"
+  version: "[UI Spec Version]"
+  created_date: "[Date]"
+  designer: "[UX Designer Name]"
+  flutter_version: "[Flutter Version]"
+  material_design_version: "Material Design 3"
+  platforms: 
+    - iOS
+    - Android
+
+sections:
+  - name: design_overview
+    title: "🎨 Design Overview"
+    prompt: |
+      Provide comprehensive UI/UX overview:
+      
+      **Design Philosophy:**
+      - Material Design 3 implementation approach
+      - Brand integration with Material You principles
+      - User-centered design considerations
+      - Mobile-first responsive strategy
+      
+      **Target Platforms:**
+      - iOS specific design adaptations
+      - Android Material Design compliance
+      - Cross-platform consistency requirements
+      - Platform-specific interaction patterns
+
+  - name: user_flows
+    title: "🔄 User Flows & Navigation"
+    prompt: |
+      Define user journey and navigation patterns:
+      
+      **Primary User Flows:**
+      [For each major user flow, define:]
+      - Entry points and triggers
+      - Step-by-step navigation path
+      - Decision points and branching
+      - Success and error scenarios
+      - Exit points and completion states
+      
+      **Navigation Architecture:**
+      - App navigation structure (tabs, drawer, etc.)
+      - Deep linking and routing patterns
+      - Back navigation and gesture handling
+      - Navigation state management
+      
+      **Micro-interactions:**
+      - Button press feedback
+      - Loading state transitions
+      - Form validation feedback
+      - Success/error message patterns
+
+  - name: responsive_layout
+    title: "📱 Responsive Layout Design"
+    prompt: |
+      Define responsive design for different screen sizes:
+      
+      **Phone Layouts (Small Screens):**
+      - Portrait mode layouts (320-414px width)
+      - Landscape mode adaptations
+      - Single-column content arrangement
+      - Bottom navigation implementation
+      
+      **Tablet Layouts (Large Screens):**
+      - Portrait tablet layouts (768px+ width)
+      - Landscape tablet layouts
+      - Multi-column content arrangements
+      - Navigation rail implementation
+      
+      **Adaptive Components:**
+      - Responsive grid systems
+      - Flexible typography scaling
+      - Adaptive spacing and padding
+      - Context-aware component behavior
+
+  - name: material_design_system
+    title: "🎯 Material Design 3 System"
+    prompt: |
+      Define Material Design 3 implementation:
+      
+      **Color System:**
+      - Primary color palette (Material You)
+      - Secondary and tertiary colors
+      - Surface and background colors
+      - Error, warning, and success colors
+      - Dark and light theme variants
+      
+      **Typography Scale:**
+      - Display styles (Large, Medium, Small)
+      - Headline styles (Large, Medium, Small)
+      - Title styles (Large, Medium, Small)
+      - Body styles (Large, Medium, Small)
+      - Label styles (Large, Medium, Small)
+      
+      **Component Specifications:**
+      [For each component, define:]
+      - Material 3 implementation
+      - State variations (enabled, disabled, hover, pressed)
+      - Size variants and responsive behavior
+      - Custom styling requirements
+      - Animation and transition specifications
+
+  - name: feature_screens
+    title: "📋 Feature Screens Specification"
+    prompt: |
+      Define each screen in the Flutter feature:
+      
+      ## [Feature Name] Screens
+      
+      ### [Screen Name] Screen
+      **Purpose:** [Screen function and user goal]
+      
+      **Layout Structure:**
+      - AppBar configuration
+      - Body content arrangement
+      - Bottom navigation/FAB placement
+      - Safe area considerations
+      
+      **Widget Hierarchy:**
+      ```
+      Scaffold
+      ├── AppBar
+      │   ├── Leading widget
+      │   ├── Title widget
+      │   └── Actions widgets
+      ├── Body
+      │   └── [Define widget tree structure]
+      ├── BottomNavigationBar (if applicable)
+      └── FloatingActionButton (if applicable)
+      ```
+      
+      **State Management:**
+      - Initial loading state UI
+      - Success state content
+      - Error state handling
+      - Empty state design
+      - Loading indicators and progress
+      
+      **Responsive Behavior:**
+      - Phone layout adaptations
+      - Tablet layout changes
+      - Orientation handling
+      
+      **Localization Requirements:**
+      - Text content keys
+      - Right-to-left (RTL) support
+      - Cultural adaptations
+      
+      **Accessibility:**
+      - Semantic labels and hints
+      - Focus management
+      - Screen reader support
+      - High contrast support
+
+  - name: custom_widgets
+    title: "🧩 Custom Widget Specifications"
+    prompt: |
+      Define reusable custom widgets:
+      
+      ### [Widget Name] Widget
+      **Purpose:** [Widget function and reusability scope]
+      
+      **API Design:**
+      ```dart
+      class [WidgetName] extends StatelessWidget {
+        const [WidgetName]({
+          Key? key,
+          required this.property1,
+          this.property2,
+          // Define all required and optional properties
+        }) : super(key: key);
+        
+        final String property1;
+        final int? property2;
+      }
+      ```
+      
+      **Visual Specifications:**
+      - Default appearance and styling
+      - State variations (normal, pressed, disabled)
+      - Size and spacing requirements
+      - Animation and transition behavior
+      
+      **Responsive Behavior:**
+      - Adaptation to different screen sizes
+      - Content overflow handling
+      - Breakpoint-specific changes
+      
+      **Theming Integration:**
+      - Theme property usage
+      - Dark/light mode support
+      - Material 3 compliance
+
+  - name: animations_interactions
+    title: "✨ Animations & Interactions"
+    prompt: |
+      Define animation and interaction patterns:
+      
+      **Screen Transitions:**
+      - Page route animations
+      - Hero animations between screens
+      - Shared element transitions
+      - Custom transition specifications
+      
+      **Micro-animations:**
+      - Button press animations
+      - Loading spinner implementations
+      - Progress indicators
+      - Success/error feedback animations
+      
+      **Gesture Handling:**
+      - Swipe gestures and directions
+      - Pull-to-refresh implementations
+      - Drag and drop interactions
+      - Pinch-to-zoom (if applicable)
+      
+      **Animation Specifications:**
+      - Duration and easing curves
+      - Performance considerations
+      - Accessibility motion preferences
+      - Battery optimization
+
+  - name: theme_customization
+    title: "🎨 Theme & Customization"
+    prompt: |
+      Define theme customization approach:
+      
+      **Material Theme Configuration:**
+      ```dart
+      ThemeData(
+        useMaterial3: true,
+        colorScheme: ColorScheme.fromSeed(
+          seedColor: [Primary Color],
+          brightness: Brightness.light,
+        ),
+        // Define custom theme properties
+      )
+      ```
+      
+      **Custom Theme Extensions:**
+      - Additional color properties
+      - Custom text styles
+      - Component theme customizations
+      - Platform-specific adaptations
+      
+      **Dark Mode Implementation:**
+      - Dark theme color scheme
+      - Component adaptations
+      - System theme following
+      - User preference handling
+
+  - name: accessibility_compliance
+    title: "♿ Accessibility Compliance"
+    prompt: |
+      Define accessibility implementation:
+      
+      **WCAG Compliance:**
+      - Color contrast ratios (AA level minimum)
+      - Text size and readability
+      - Touch target sizes (44x44 minimum)
+      - Focus indicators and management
+      
+      **Screen Reader Support:**
+      - Semantic markup with Semantics widgets
+      - Content descriptions and labels
+      - Navigation announcements
+      - State change notifications
+      
+      **Motor Accessibility:**
+      - Large touch targets
+      - Gesture alternatives
+      - Voice navigation support
+      - Switch control compatibility
+      
+      **Cognitive Accessibility:**
+      - Clear navigation patterns
+      - Consistent UI conventions
+      - Error prevention and recovery
+      - Help and documentation access
+
+  - name: localization_design
+    title: "🌍 Localization Design Guidelines"
+    prompt: |
+      Define localization and internationalization:
+      
+      **Text Localization:**
+      - Translation key naming conventions
+      - Text expansion/contraction handling
+      - Context-sensitive translations
+      - Placeholder and dynamic content
+      
+      **Cultural Adaptations:**
+      - Right-to-left (RTL) layout support
+      - Date and time format variations
+      - Number and currency formatting
+      - Cultural color and symbol considerations
+      
+      **Layout Adaptations:**
+      - Text length variations
+      - Font and typography changes
+      - Icon and image localization
+      - Cultural UI pattern preferences
+
+  - name: performance_considerations
+    title: "⚡ Performance & Optimization"
+    prompt: |
+      Define performance optimization requirements:
+      
+      **Rendering Performance:**
+      - Widget tree optimization
+      - Build method efficiency
+      - Avoid unnecessary rebuilds
+      - Image optimization and caching
+      
+      **Memory Management:**
+      - Large list handling (ListView.builder)
+      - Image memory management
+      - Animation resource cleanup
+      - State management efficiency
+      
+      **Battery Optimization:**
+      - Animation frequency limits
+      - Background processing minimization
+      - Location and sensor usage
+      - Network request optimization
+
+  - name: implementation_guidelines
+    title: "🛠️ Implementation Guidelines"
+    prompt: |
+      Provide Flutter-specific implementation guidance:
+      
+      **Widget Implementation Patterns:**
+      - StatelessWidget vs StatefulWidget usage
+      - Widget composition best practices
+      - Key usage for performance
+      - Build method optimization
+      
+      **State Management Integration:**
+      - BlocBuilder and BlocListener usage
+      - State-dependent UI rendering
+      - Loading and error state handling
+      - State change animations
+      
+      **Asset Management:**
+      - Image asset organization
+      - Icon and graphic specifications
+      - Font asset requirements
+      - Platform-specific assets
+      
+      **Testing Considerations:**
+      - Widget testability requirements
+      - Key assignment for testing
+      - Semantic testing support
+      - Golden test specifications
+
+  - name: handoff_documentation
+    title: "📋 Developer Handoff"
+    prompt: |
+      Prepare comprehensive developer handoff:
+      
+      **Design Assets:**
+      - Figma/Design file links
+      - Exported assets and icons
+      - Color palette specifications
+      - Typography style guide
+      
+      **Implementation Priorities:**
+      - Must-have features and requirements
+      - Nice-to-have enhancements
+      - Future iteration considerations
+      - Technical debt considerations
+      
+      **Quality Assurance:**
+      - Visual testing requirements
+      - Cross-platform testing needs
+      - Accessibility testing checklist
+      - Performance benchmarking
+
+instructions:
+  pre_fill: |
+    Before creating this UI specification:
+    1. Review the Flutter PRD and understand feature requirements
+    2. Research Material Design 3 guidelines and best practices
+    3. Consider target audience and usage patterns
+    4. Plan for responsive design across device sizes
+    5. Understand Flutter's widget system and capabilities
+
+  post_completion: |
+    After completing this UI specification:
+    1. Review with stakeholders and development team
+    2. Validate Material Design 3 compliance
+    3. Ensure accessibility requirements are comprehensive
+    4. Verify responsive design coverage
+    5. Prepare for Cubit state management integration
+    6. Save as docs/flutter-ui-spec.md for development reference
+
+  quality_checklist:
+    - "Material Design 3 principles correctly applied"
+    - "Responsive design covers all screen sizes"
+    - "Accessibility compliance thoroughly addressed"
+    - "Localization requirements defined"
+    - "Performance considerations included"
+    - "Animation specifications are clear"
+    - "Custom widget APIs are well-defined"
+    - "Implementation guidelines are Flutter-specific"
+    - "Developer handoff documentation is complete"
+    - "Integration with Cubit state management considered"

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

@@ -158,15 +158,21 @@ sections:
           - ["Frontend Language", "{{fe_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Frontend Framework", "{{fe_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["UI Component Library", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["UI Design System", "{{ui_design_system}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["State Management", "{{state_mgmt}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Mobile Framework", "{{mobile_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Mobile State Management", "{{mobile_state_mgmt}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Backend Language", "{{be_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Backend Framework", "{{be_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Backend Service", "{{backend_service}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["API Style", "{{api_style}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Database", "{{database}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Cache", "{{cache}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["File Storage", "{{storage}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Authentication", "{{auth}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Real-time", "{{realtime}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Frontend Testing", "{{fe_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Mobile Testing", "{{mobile_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Backend Testing", "{{be_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["E2E Testing", "{{e2e_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
@@ -176,6 +182,7 @@ sections:
           - ["Monitoring", "{{monitoring}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Logging", "{{logging}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["CSS Framework", "{{css_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
+          - ["Localization", "{{localization}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
 
   - id: data-models
     title: Data Models
@@ -671,11 +678,11 @@ sections:
         type: code
         language: text
         template: |
-                  E2E Tests
-                 /        \
-            Integration Tests
-               /            \
-          Frontend Unit  Backend Unit
+          Testing Pyramid Structure:
+          
+          Level 3: E2E Tests (Few)
+          Level 2: Integration Tests (Some)  
+          Level 1: Unit Tests (Many - Frontend & Backend)
       - id: test-organization
         title: Test Organization
         sections:

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

@@ -1,12 +1,12 @@
 # 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.
+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 its 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.
+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 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.
 
@@ -85,9 +85,9 @@ Once planning is complete and documents are sharded, BMad follows a structured d
 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{"QA: Review Story Draft (Optional)"}
-    B3 -->|Review Requested| B4["QA: Review Story Against Artifacts"]
-    B3 -->|Skip Review| C{"User Approval"}
+    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
@@ -132,7 +132,7 @@ graph TD
 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` content
+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
@@ -152,7 +152,7 @@ There are two bmad agents - in the future they will be consolidated into the sin
 
 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 dont want to bother switching between different agents aside from the dev, this is the agent for you.
+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
 
@@ -210,6 +210,7 @@ dependencies:
 - **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
 
@@ -236,7 +237,7 @@ devLoadAlwaysFiles:
 
 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 just the items that the agent makes mistakes at still - must with the better models, they will look at surrounding code in files and not need a rule from that file to guide them.
+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
 

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

@@ -54,7 +54,15 @@ workflow:
       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."
+      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
@@ -64,6 +72,12 @@ workflow:
         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

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

@@ -11,6 +11,7 @@ workflow:
     - enterprise-app
     - prototype
     - mvp
+    - flutter-mobile-app
 
   sequence:
     - agent: analyst
@@ -23,14 +24,35 @@ workflow:
     - agent: pm
       creates: prd.md
       requires: project-brief.md
-      notes: "Creates PRD from project brief using prd-tmpl. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder."
+      notes: |
+        Creates PRD from project brief using prd-tmpl (or flutter-mobile-prd-tmpl for Flutter projects).
+        
+        For Flutter mobile apps:
+        - Use flutter-mobile-prd-tmpl.yaml template
+        - Focus on feature-based architecture requirements
+        - Include Material Design 3 specifications
+        - Define mobile-specific performance criteria
+        - Plan Clean Architecture layers (data/domain/presentation)
+        
+        SAVE OUTPUT: Copy final prd.md to your project's docs/ folder.
 
     - agent: ux-expert
       creates: front-end-spec.md
       requires: prd.md
       optional_steps:
         - user_research_prompt
-      notes: "Creates UI/UX specification using front-end-spec-tmpl. SAVE OUTPUT: Copy final front-end-spec.md to your project's docs/ folder."
+      notes: |
+        Creates UI/UX specification using front-end-spec-tmpl (or flutter-ui-spec-tmpl for Flutter projects).
+        
+        For Flutter mobile apps:
+        - Use flutter-ui-spec-tmpl.yaml template
+        - Design with Material Design 3 principles
+        - Plan responsive layouts for phone/tablet
+        - Define custom widget specifications
+        - Include accessibility and localization requirements
+        - Consider mobile-specific user interactions
+        
+        SAVE OUTPUT: Copy final front-end-spec.md to your project's docs/ folder.
 
     - agent: ux-expert
       creates: v0_prompt (optional)
@@ -46,7 +68,21 @@ workflow:
       optional_steps:
         - technical_research_prompt
         - review_generated_ui_structure
-      notes: "Creates comprehensive architecture using fullstack-architecture-tmpl. If user generated UI with v0/Lovable, can incorporate the project structure into architecture. May suggest changes to PRD stories or new stories. SAVE OUTPUT: Copy final fullstack-architecture.md to your project's docs/ folder."
+      notes: |
+        Creates comprehensive architecture using fullstack-architecture-tmpl (or flutter-mobile-architecture-tmpl for Flutter projects).
+        
+        For Flutter mobile apps:
+        - Use flutter-mobile-architecture-tmpl.yaml template
+        - Define Clean Architecture with feature-based structure
+        - Plan Cubit state management architecture
+        - Specify dependency injection setup
+        - Include testing strategy across all layers
+        - Define performance and security considerations
+        
+        If user generated UI with v0/Lovable, can incorporate the project structure into architecture.
+        May suggest changes to PRD stories or new stories.
+        
+        SAVE OUTPUT: Copy final fullstack-architecture.md to your project's docs/ folder.
 
     - agent: pm
       updates: prd.md (if needed)
@@ -90,8 +126,9 @@ workflow:
       repeats: for_each_epic
       notes: |
         Story creation cycle:
-        - SM Agent (New Chat): @sm → *create
+        - SM Agent (New Chat): @sm → *create (or *create-flutter-story for Flutter projects)
         - Creates next story from sharded docs
+        - For Flutter: Uses flutter-story-tmpl.yaml with all three architecture layers
         - Story starts in "Draft" status
 
     - agent: analyst/pm
@@ -111,7 +148,14 @@ workflow:
       creates: implementation_files
       requires: story.md
       notes: |
-        Dev Agent (New Chat): @dev
+        Dev Agent (New Chat): @dev (or Flutter-specific agents for complex features)
+        
+        For Flutter projects:
+        - Use @flutter-ui-agent for presentation layer
+        - Use @flutter-cubit-agent for state management  
+        - Use @flutter-domain-agent for business logic
+        - Use @flutter-data-agent for data layer
+        - Or use general @dev with Flutter expertise
         - Implements approved story
         - Updates File List with all changes
         - Marks story as "Review" when complete