appiq-solution 1.0.8 → 1.1.0

package/expansion-packs/bmad-flutter-mobile-dev/workflows/flutter-ui-first-development.yaml

@@ -0,0 +1,220 @@
+workflow:
+  id: flutter-ui-first-development
+  name: Flutter UI-First Development Workflow
+  description: Specialized Flutter development workflow starting with UI design, then building Cubit, Domain, and Data layers progressively
+  version: 1.0
+  
+phases:
+  - id: planning
+    name: Planning & Analysis
+    description: Initial planning and requirement analysis
+    agents:
+      - analyst: Analyze requirements and create brief
+      - pm: Create product requirements and user stories
+      - ux-expert: Design user experience and wireframes
+      - architect: Create overall architecture and tech stack decisions
+      - po: Review and approve requirements
+    deliverables:
+      - Project brief
+      - Product Requirements Document (PRD)
+      - UX/UI specifications
+      - Flutter architecture document
+      - Technical specifications
+    
+  - id: ui-implementation
+    name: UI Implementation
+    description: Design and implement Flutter user interface
+    agents:
+      - flutter-ui-agent: 
+          role: Primary implementer
+          responsibilities:
+            - Design responsive Flutter UI
+            - Create custom widgets
+            - Implement Material Design 3
+            - Set up localization keys
+            - Ensure accessibility compliance
+            - Create UI documentation
+      - shared-components-agent:
+          role: Support
+          responsibilities:
+            - Identify reusable components
+            - Create shared widgets
+            - Establish design system
+    deliverables:
+      - Flutter pages and widgets
+      - Responsive layout implementation
+      - Localization keys and ARB files
+      - UI component documentation
+      - Accessibility compliance report
+    handoff_data:
+      - UI specifications and requirements
+      - Widget structure and hierarchy
+      - State requirements for Cubit layer
+      - User interaction flows
+      - Localization key definitions
+    
+  - id: state-management
+    name: State Management Implementation
+    description: Implement Cubit-based state management based on UI requirements
+    agents:
+      - flutter-cubit-agent:
+          role: Primary implementer
+          responsibilities:
+            - Analyze UI state requirements
+            - Implement Cubit classes
+            - Create state classes with Equatable
+            - Handle business logic coordination
+            - Implement error handling
+            - Create comprehensive tests
+    deliverables:
+      - Cubit implementations
+      - State classes with proper patterns
+      - Business logic coordination
+      - Error handling implementation
+      - Cubit unit tests
+    handoff_data:
+      - State management requirements
+      - Business logic specifications
+      - Data requirements for domain layer
+      - Error handling patterns
+      - Performance constraints
+    
+  - id: domain-implementation
+    name: Domain Layer Implementation
+    description: Implement business entities, use cases, and repository interfaces
+    agents:
+      - flutter-domain-agent:
+          role: Primary implementer
+          responsibilities:
+            - Design business entities
+            - Implement use cases with validation
+            - Create repository interfaces
+            - Define business rules
+            - Ensure Clean Architecture compliance
+            - Create domain layer tests
+    deliverables:
+      - Business entities with Equatable
+      - Use cases with business validation
+      - Repository interfaces
+      - Business rule implementations
+      - Domain layer unit tests
+    handoff_data:
+      - Entity definitions and relationships
+      - Use case specifications
+      - Repository interface requirements
+      - Business rule definitions
+      - Data access patterns
+    
+  - id: data-implementation
+    name: Data Layer Implementation
+    description: Implement data sources, repositories, and external integrations
+    agents:
+      - flutter-data-agent:
+          role: Primary implementer
+          responsibilities:
+            - Implement repository concrete classes
+            - Create remote and local data sources
+            - Set up API client configuration
+            - Implement data models with JSON serialization
+            - Add caching strategies
+            - Handle offline scenarios
+            - Create data layer tests
+    deliverables:
+      - Repository implementations
+      - Remote and local data sources
+      - API client setup
+      - Data models with Freezed
+      - Caching implementation
+      - Offline support
+      - Data layer tests
+    
+  - id: integration-testing
+    name: Integration & Testing
+    description: Integrate all layers and perform comprehensive testing
+    agents:
+      - qa:
+          role: Primary tester
+          responsibilities:
+            - Create integration tests
+            - Perform widget testing
+            - Validate user flows
+            - Test multi-language support
+            - Perform security testing
+            - Create test reports
+      - shared-components-agent:
+          role: Support
+          responsibilities:
+            - Test shared components
+            - Validate reusability
+            - Performance testing
+    deliverables:
+      - Integration test suite
+      - Widget test coverage
+      - Security validation report
+      - Performance benchmarks
+      - Multi-language testing
+      - Final test report
+    
+  - id: deployment-preparation
+    name: Deployment Preparation
+    description: Prepare app for production deployment
+    agents:
+      - sm:
+          role: Deployment coordinator
+          responsibilities:
+            - Configure build settings
+            - Set up CI/CD pipeline
+            - Prepare app store assets
+            - Security final validation
+            - Performance optimization
+            - Release preparation
+    deliverables:
+      - Production build configuration
+      - CI/CD pipeline setup
+      - App store preparation
+      - Security compliance report
+      - Performance optimization report
+      - Release documentation
+
+workflow_rules:
+  - Each phase must be completed before moving to the next
+  - UI Agent provides requirements to Cubit Agent
+  - Cubit Agent provides requirements to Domain Agent
+  - Domain Agent provides requirements to Data Agent
+  - All agents must follow standard workflow process
+  - Quality gates must be passed at each phase
+  - Security validation required at each layer
+  - All text must use localization keys
+  - Git commits required after each completed phase
+
+quality_gates:
+  - DRY: No code duplication across layers
+  - Readable: Clear code structure and documentation
+  - Maintainable: Modular architecture following Clean Architecture
+  - Performant: Efficient state management and UI rendering
+  - Testable: Comprehensive test coverage at all layers
+  - Secure: Security validation at each layer
+  - Localized: All text uses localization keys
+
+agent_coordination:
+  ui_to_cubit:
+    - State requirements specification
+    - User interaction patterns
+    - Loading and error states
+    - Navigation requirements
+  cubit_to_domain:
+    - Business logic requirements
+    - Entity specifications
+    - Use case definitions
+    - Validation rules
+  domain_to_data:
+    - Repository interface implementations
+    - Data model requirements
+    - API endpoint specifications
+    - Caching strategies
+
+mcp_integrations:
+  - sequential-thinking: For complex workflow analysis and decision making
+  - supabase: For Supabase backend integration
+  - firebase: For Firebase services integration
+  - dart: For Dart code analysis and generation

package/expansion-packs/bmad-infrastructure-devops/README.md

@@ -0,0 +1,147 @@
+# Infrastructure & DevOps Expansion Pack
+
+## Overview
+
+This expansion pack extends BMad Method with comprehensive infrastructure and DevOps capabilities. It's designed for teams that need to define, implement, and manage cloud infrastructure alongside their application development.
+
+## Purpose
+
+While the core BMad flow focuses on getting from business requirements to development (Analyst → PM → Architect → SM → Dev), many projects require sophisticated infrastructure planning and implementation. This expansion pack adds:
+
+- Infrastructure architecture design capabilities
+- Platform engineering implementation workflows
+- DevOps automation and CI/CD pipeline design
+- Cloud resource management and optimization
+- Security and compliance validation
+
+## When to Use This Pack
+
+Install this expansion pack when your project requires:
+
+- Cloud infrastructure design and implementation
+- Kubernetes/container platform setup
+- Service mesh and GitOps workflows
+- Infrastructure as Code (IaC) development
+- Platform engineering and DevOps practices
+
+## What's Included
+
+### Agents
+
+- `devops.yaml` - DevOps and Platform Engineering agent configuration
+
+### Personas
+
+- `devops.md` - DevOps Engineer persona (Alex)
+
+### IDE Agents
+
+- `devops.ide.md` - IDE-specific DevOps agent configuration
+
+### Templates
+
+- `infrastructure-architecture-tmpl.md` - Infrastructure architecture design template
+- `infrastructure-platform-from-arch-tmpl.md` - Platform implementation from architecture template
+
+### Tasks
+
+- `infra/validate-infrastructure.md` - Infrastructure validation workflow
+- `infra/review-infrastructure.md` - Infrastructure review process
+
+### Checklists
+
+- `infrastructure-checklist.md` - Comprehensive 16-section infrastructure validation checklist
+
+## Integration with Core BMad
+
+This expansion pack integrates with the core BMad flow at these points:
+
+1. **After Architecture Phase**: The Architect can trigger infrastructure architecture design
+2. **Parallel to Development**: Infrastructure implementation can proceed alongside application development
+3. **Before Deployment**: Infrastructure must be validated before application deployment
+
+## Installation
+
+To install this expansion pack, run:
+
+```bash
+npm run install:expansion infrastructure
+```
+
+Or manually:
+
+```bash
+node tools/install-expansion-pack.js infrastructure
+```
+
+This will:
+
+1. Copy all files to their appropriate locations in `.bmad-core/`
+2. Update any necessary configurations
+3. Make the DevOps agent available in teams
+
+## Usage Examples
+
+### 1. Infrastructure Architecture Design
+
+After the main architecture is complete:
+
+```bash
+# Using the Architect agent
+*create-infrastructure
+
+# Or directly with DevOps agent
+npm run agent devops
+```
+
+### 2. Platform Implementation
+
+With an approved infrastructure architecture:
+
+```bash
+# DevOps agent implements the platform
+*implement-platform
+```
+
+### 3. Infrastructure Validation
+
+Before deployment:
+
+```bash
+# Validate infrastructure against checklist
+*validate-infra
+```
+
+## Team Integration
+
+The DevOps agent can be added to team configurations:
+
+- `team-technical.yaml` - For technical implementation teams
+- `team-full-org.yaml` - For complete organizational teams
+
+## Dependencies
+
+This expansion pack works best when used with:
+
+- Core BMad agents (especially Architect)
+- Technical preferences documentation
+- Approved PRD and system architecture
+
+## Customization
+
+You can customize this expansion pack by:
+
+1. Modifying the infrastructure templates for your cloud provider
+2. Adjusting the checklist items for your compliance needs
+3. Adding custom tasks for your specific workflows
+
+## Notes
+
+- Infrastructure work requires real-world cloud credentials and configurations
+- The templates use placeholders ({{variable}}) that need actual values
+- Always validate infrastructure changes before production deployment
+
+---
+
+_Version: 1.0_
+_Compatible with: BMad Method v4_

package/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.md

@@ -0,0 +1,71 @@
+# infra-devops-platform
+
+ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
+
+CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+
+## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
+
+```yaml
+IIDE-FILE-RESOLUTION:
+  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
+  - Dependencies map to {root}/{type}/{name}
+  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
+  - Example: create-doc.md → {root}/tasks/create-doc.md
+  - IMPORTANT: Only load these files when user requests specific command execution
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
+activation-instructions:
+  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
+  - STEP 3: Greet user with your name/role and mention `*help` command
+  - DO NOT: Load any other agent files during activation
+  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
+  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
+  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
+  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
+  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - STAY IN CHARACTER!
+  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+agent:
+  name: Alex
+  id: infra-devops-platform
+  title: DevOps Infrastructure Specialist Platform Engineer
+  customization: Specialized in cloud-native system architectures and tools, like Kubernetes, Docker, GitHub Actions, CI/CD pipelines, and infrastructure-as-code practices (e.g., Terraform, CloudFormation, Bicep, etc.).
+persona:
+  role: DevOps Engineer & Platform Reliability Expert
+  style: Systematic, automation-focused, reliability-driven, proactive. Focuses on building and maintaining robust infrastructure, CI/CD pipelines, and operational excellence.
+  identity: Master Expert Senior Platform Engineer with 15+ years of experience in DevSecOps, Cloud Engineering, and Platform Engineering with deep SRE knowledge
+  focus: Production environment resilience, reliability, security, and performance for optimal customer experience
+  core_principles:
+    - Infrastructure as Code - Treat all infrastructure configuration as code. Use declarative approaches, version control everything, ensure reproducibility
+    - Automation First - Automate repetitive tasks, deployments, and operational procedures. Build self-healing and self-scaling systems
+    - Reliability & Resilience - Design for failure. Build fault-tolerant, highly available systems with graceful degradation
+    - Security & Compliance - Embed security in every layer. Implement least privilege, encryption, and maintain compliance standards
+    - Performance Optimization - Continuously monitor and optimize. Implement caching, load balancing, and resource scaling for SLAs
+    - Cost Efficiency - Balance technical requirements with cost. Optimize resource usage and implement auto-scaling
+    - Observability & Monitoring - Implement comprehensive logging, monitoring, and tracing for quick issue diagnosis
+    - CI/CD Excellence - Build robust pipelines for fast, safe, reliable software delivery through automation and testing
+    - Disaster Recovery - Plan for worst-case scenarios with backup strategies and regularly tested recovery procedures
+    - Collaborative Operations - Work closely with development teams fostering shared responsibility for system reliability
+commands:
+  - '*help" - Show: numbered list of the following commands to allow selection'
+  - '*chat-mode" - (Default) Conversational mode for infrastructure and DevOps guidance'
+  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - '*review-infrastructure" - Review existing infrastructure for best practices'
+  - '*validate-infrastructure" - Validate infrastructure against security and reliability standards'
+  - '*checklist" - Run infrastructure checklist for comprehensive review'
+  - '*exit" - Say goodbye as Alex, the DevOps Infrastructure Specialist, and then abandon inhabiting this persona'
+dependencies:
+  tasks:
+    - create-doc.md
+    - review-infrastructure.md
+    - validate-infrastructure.md
+  templates:
+    - infrastructure-architecture-tmpl.yaml
+    - infrastructure-platform-from-arch-tmpl.yaml
+  checklists:
+    - infrastructure-checklist.md
+  data:
+    - technical-preferences.md
+```