appiq-solution 1.2.0 → 1.3.0

package/#Tools/APPIQ-METHOD/README.md

@@ -0,0 +1,139 @@
+# BMad-Method: Universal AI Agent Framework
+
+[![Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=version)](https://www.npmjs.com/package/bmad-method)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+[![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org)
+[![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj)
+
+Foundations in Agentic Agile Driven Development, known as the Breakthrough Method of Agile AI-Driven Development, yet so much more. Transform any domain with specialized AI expertise: software development, entertainment, creative writing, business strategy to personal wellness just to name a few.
+
+**[Subscribe to BMadCode on YouTube](https://www.youtube.com/@BMadCode?sub_confirmation=1)**
+
+**[Join our Discord Community](https://discord.gg/gk8jAdXWmj)** - A growing community for AI enthusiasts! Get help, share ideas, explore AI agents & frameworks, collaborate on tech projects, enjoy hobbies, and help each other succeed. Whether you're stuck on BMad, building your own agents, or just want to chat about the latest in AI - we're here for you! **Some mobile and VPN may have issue joining the discord, this is a discord issue - if the invite does not work, try from your own internet or another network, or non-VPN.**
+
+⭐ **If you find this project helpful or useful, please give it a star in the upper right hand corner!** It helps others discover BMad-Method and you will be notified of updates!
+
+## Overview
+
+**BMad Method's Two Key Innovations:**
+
+**1. Agentic Planning:** Dedicated agents (Analyst, PM, Architect) collaborate with you to create detailed, consistent PRDs and Architecture documents. Through advanced prompt engineering and human-in-the-loop refinement, these planning agents produce comprehensive specifications that go far beyond generic AI task generation.
+
+**2. Context-Engineered Development:** The Scrum Master agent then transforms these detailed plans into hyper-detailed development stories that contain everything the Dev agent needs - full context, implementation details, and architectural guidance embedded directly in story files.
+
+This two-phase approach eliminates both **planning inconsistency** and **context loss** - the biggest problems in AI-assisted development. Your Dev agent opens a story file with complete understanding of what to build, how to build it, and why.
+
+**📖 [See the complete workflow in the User Guide](bmad-core/user-guide.md)** - Planning phase, development cycle, and all agent roles
+
+## Quick Navigation
+
+### Understanding the BMad Workflow
+
+**Before diving in, review these critical workflow diagrams that explain how BMad works:**
+
+1. **[Planning Workflow (Web UI)](bmad-core/user-guide.md#the-planning-workflow-web-ui)** - How to create PRD and Architecture documents
+2. **[Core Development Cycle (IDE)](bmad-core/user-guide.md#the-core-development-cycle-ide)** - How SM, Dev, and QA agents collaborate through story files
+
+> ⚠️ **These diagrams explain 90% of BMad Method Agentic Agile flow confusion** - Understanding the PRD+Architecture creation and the SM/Dev/QA workflow and how agents pass notes through story files is essential - and also explains why this is NOT taskmaster or just a simple task runner!
+
+### What would you like to do?
+
+- **[Install and Build software with Full Stack Agile AI Team](#quick-start)** → Quick Start Instruction
+- **[Learn how to use BMad](bmad-core/user-guide.md)** → Complete user guide and walkthrough
+- **[See available AI agents](#available-agents)** → Specialized roles for your team
+- **[Explore non-technical uses](#-beyond-software-development---expansion-packs)** → Creative writing, business, wellness, education
+- **[Create my own AI agents](#creating-your-own-expansion-pack)** → Build agents for your domain
+- **[Browse ready-made expansion packs](expansion-packs/)** → Game dev, DevOps, infrastructure and get inspired with ideas and examples
+- **[Understand the architecture](docs/core-architecture.md)** → Technical deep dive
+- **[Join the community](https://discord.gg/gk8jAdXWmj)** → Get help and share ideas
+
+## Important: Keep Your BMad Installation Updated
+
+**Stay up-to-date effortlessly!** If you already have BMad-Method installed in your project, simply run:
+
+```bash
+npx bmad-method install
+# OR
+git pull
+npm run install:bmad
+```
+
+This will:
+
+- ✅ Automatically detect your existing v4 installation
+- ✅ Update only the files that have changed and add new files
+- ✅ Create `.bak` backup files for any custom modifications you've made
+- ✅ Preserve your project-specific configurations
+
+This makes it easy to benefit from the latest improvements, bug fixes, and new agents without losing your customizations!
+
+## Quick Start
+
+### One Command for Everything (IDE Installation)
+
+**Just run one of these commands:**
+
+```bash
+npx bmad-method install
+# OR if you already have BMad installed:
+git pull
+npm run install:bmad
+```
+
+This single command handles:
+
+- **New installations** - Sets up BMad in your project
+- **Upgrades** - Updates existing installations automatically
+- **Expansion packs** - Installs any expansion packs you've added to package.json
+
+> **That's it!** Whether you're installing for the first time, upgrading, or adding expansion packs - these commands do everything.
+
+**Prerequisites**: [Node.js](https://nodejs.org) v20+ required
+
+### Fastest Start: Web UI Full Stack Team at your disposal (2 minutes)
+
+1. **Get the bundle**: Save or clone the [full stack team file](dist/teams/team-fullstack.txt) or choose another team
+2. **Create AI agent**: Create a new Gemini Gem or CustomGPT
+3. **Upload & configure**: Upload the file and set instructions: "Your critical operating instructions are attached, do not break character as directed"
+4. **Start Ideating and Planning**: Start chatting! Type `*help` to see available commands or pick an agent like `*analyst` to start right in on creating a brief.
+5. **CRITICAL**: Talk to BMad Orchestrator in the web at ANY TIME (#bmad-orchestrator command) and ask it questions about how this all works!
+6. **When to move to the IDE**: Once you have your PRD, Architecture, optional UX and Briefs - its time to switch over to the IDE to shard your docs, and start implementing the actual code! See the [User guide](bmad-core/user-guide.md) for more details
+
+### Alternative: Clone and Build
+
+```bash
+git clone https://github.com/bmadcode/bmad-method.git
+npm run install:bmad # build and install all to a destination folder
+```
+
+## 🌟 Beyond Software Development - Expansion Packs
+
+BMad's natural language framework works in ANY domain. Expansion packs provide specialized AI agents for creative writing, business strategy, health & wellness, education, and more. Also expansion packs can expand the core BMad-Method with specific functionality that is not generic for all cases. [See the Expansion Packs Guide](docs/expansion-packs.md) and learn to create your own!
+
+## Documentation & Resources
+
+### Essential Guides
+
+- 📖 **[User Guide](bmad-core/user-guide.md)** - Complete walkthrough from project inception to completion
+- 🏗️ **[Core Architecture](docs/core-architecture.md)** - Technical deep dive and system design
+- 🚀 **[Expansion Packs Guide](docs/expansion-packs.md)** - Extend BMad to any domain beyond software development
+
+## Support
+
+- 💬 [Discord Community](https://discord.gg/gk8jAdXWmj)
+- 🐛 [Issue Tracker](https://github.com/bmadcode/bmad-method/issues)
+- 💬 [Discussions](https://github.com/bmadcode/bmad-method/discussions)
+
+## Contributing
+
+**We're excited about contributions and welcome your ideas, improvements, and expansion packs!** 🎉
+
+📋 **[Read CONTRIBUTING.md](CONTRIBUTING.md)** - Complete guide to contributing, including guidelines, process, and requirements
+
+## License
+
+MIT License - see [LICENSE](LICENSE) for details.
+
+[![Contributors](https://contrib.rocks/image?repo=bmadcode/bmad-method)](https://github.com/bmadcode/bmad-method/graphs/contributors)
+
+<sub>Built with ❤️ for the AI-assisted development community</sub>

package/#Tools/APPIQ-METHOD/appiq_start.md

@@ -0,0 +1,232 @@
+ 🚀 Installation und Setup
+
+  1. System Installation
+
+  # Im Projekt-Verzeichnis
+  npx bmad-method install
+
+  # ODER falls bereits installiert
+  git pull
+  npm run install:bmad
+
+  2. Mobile Expansion Pack aktivieren
+
+  Das Mobile App Development Expansion Pack ist automatisch verfügbar nach der Installation.
+
+  📱 Mobile App Entwicklung starten
+
+  Option A: Web UI (Empfohlen für Planning)
+
+  1. Team Bundle laden
+
+  # Navigiere zu dist/teams/
+  cp dist/teams/team-fullstack.txt
+
+  2. AI Platform konfigurieren
+
+  - Claude (Sonnet 4): Neues Projekt erstellen
+  - Gemini (2.5 Pro): Neuen Gem erstellen
+  - ChatGPT: Custom GPT erstellen
+
+  3. Bundle hochladen
+
+  - Datei team-fullstack.txt hochladen
+  - Instructions: "Your critical operating instructions are attached, do not break character as directed"
+
+  4. Mobile Entwicklung starten
+
+  Typ einfach: "Ich möchte eine mobile App entwickeln"
+
+  Das System fragt automatisch:
+  1. ✅ "Ist das eine neue App oder eine existierende App?"
+  2. ✅ "Welche Platform: Flutter oder React Native?"
+  3. ✅ "Wie komplex ist die App?" (für State Management)
+
+  Option B: IDE (Für Development)
+
+  1. IDE mit BMad öffnen
+
+  - Cursor: @mobile-architect verwenden
+  - Claude Code: /mobile-architect verwenden
+  - Windsurf: @mobile-architect verwenden
+
+  2. Workflow starten
+
+  @mobile-architect Ich möchte eine mobile App entwickeln
+
+  🔄 Workflow-Übersicht
+
+  Für NEUE Mobile Apps:
+
+  graph LR
+      A[Start] --> B[Platform Selection]
+      B --> C[State Management]
+      C --> D[Architecture Design]
+      D --> E[Development Setup]
+      E --> F[Team Training]
+      F --> G[Development Start]
+
+  Konkrete Schritte:
+  1. Platform Selection: Flutter vs React Native Analyse
+  2. Requirements: Mobile-spezifische PRD erstellen
+  3. Architecture: Clean Architecture mit gewählter Platform
+  4. Setup: Projekt-Struktur und Guidelines
+  5. Development: Story-basierte Entwicklung
+
+  Für EXISTIERENDE Mobile Apps:
+
+  graph LR
+      A[Start] --> B[Code Analysis]
+      B --> C[Assessment Report]
+      C --> D[Strategy Planning]
+      D --> E[Architecture Evolution]
+      E --> F[Implementation]
+
+  Konkrete Schritte:
+  1. Code Analysis: Umfassende App-Analyse
+  2. Assessment: Technische Schulden und Verbesserungen
+  3. Strategy: Incremental vs Complete Rewrite
+  4. Evolution: Architektur-Modernisierung
+  5. Implementation: Schrittweise Verbesserung
+
+  🎯 Praktische Anwendungsbeispiele
+
+  Beispiel 1: Neue Flutter App
+
+  User: "Ich möchte eine neue E-Commerce App mit Flutter entwickeln"
+
+  System:
+  ✅ Erkennt: NEUE MOBILE APP
+  ✅ Startet: Platform Selection Workflow
+  ✅ Fragt: Team-Expertise, Performance-Anforderungen, Timeline
+  ✅ Empfiehlt: Flutter + BLoC/Cubit (für Enterprise) oder GetX (für MVP)
+  ✅ Erstellt: Komplette Architektur mit Ihren Coding Guidelines
+
+  Beispiel 2: Existierende React Native App verbessern
+
+  User: "Meine React Native App ist langsam und hat viele Bugs"
+
+  System:
+  ✅ Erkennt: EXISTIERENDE MOBILE APP
+  ✅ Startet: Existing App Analysis
+  ✅ Analysiert: Code Quality, Performance, Architecture
+  ✅ Erstellt: Detaillierten Verbesserungsplan
+  ✅ Priorisiert: Critical Fixes → Quality → Features → Modernization
+
+  Beispiel 3: Platform Migration
+
+  User: "Ich will von nativen iOS/Android Apps zu Flutter migrieren"
+
+  System:
+  ✅ Erkennt: PLATFORM MIGRATION
+  ✅ Analysiert: Bestehende Apps und Features
+  ✅ Plant: Schritt-für-Schritt Migration
+  ✅ Berücksichtigt: Data Migration, Feature Parity, Timeline
+
+  📋 Verfügbare Commands
+
+  In Web UI:
+
+  *help                    - Zeigt alle Commands
+  *analyst                 - Startet Requirements Analysis
+  *mobile-architect        - Platform Selection & Architecture
+  *pm                      - Mobile PRD Creation
+  *dev                     - Mobile Development
+  *bmad-orchestrator       - System Help & Guidance
+
+  In IDE:
+
+  @mobile-architect        - Platform & Architecture Guidance
+  @mobile-pm              - Mobile Requirements & Planning
+  @mobile-developer       - Implementation & Development
+  @po                     - Document Sharding & Validation
+  @sm                     - Story Creation
+  @qa                     - Quality Assurance & Review
+
+  🛠️ Spezifische Workflows
+
+  1. Platform Selection Workflow
+
+  @mobile-architect *platform-select
+
+  Führt durch:
+  - Requirements Analysis
+  - Team Assessment  
+  - Technical Constraints
+  - Platform Comparison Matrix
+  - State Management Selection
+  - Final Recommendation
+
+  2. Existing App Analysis
+
+  @mobile-architect *analyze-existing
+
+  Analysiert:
+  - Current Architecture
+  - Code Quality Metrics
+  - Performance Issues
+  - Security Vulnerabilities
+  - Technical Debt
+  - Improvement Roadmap
+
+  3. State Management Guidance
+
+  @mobile-architect *state-management
+
+  Für Flutter:
+  - BLoC/Cubit: Enterprise/Complex Apps
+  - Riverpod: Modern/Medium Apps  
+  - GetX: Rapid Development
+  - Provider: Learning/Simple Apps
+
+  Für React Native:
+  - Redux Toolkit: Enterprise/Complex
+  - Zustand: Performance/Medium
+  - Context API: Simple Global State
+
+  📚 Integration mit bestehendem Workflow
+
+  Nach Platform Selection:
+
+  1. PRD Creation: @pm → Mobile-spezifische Requirements
+  2. Architecture: @architect → Clean Architecture Design
+  3. Story Creation: @sm → Mobile-optimierte Stories
+  4. Development: @dev → Mit Ihren Flutter Guidelines
+  5. QA: @qa → Mobile Testing & Performance
+
+  Automatische Guidelines Integration:
+
+  - Flutter: Ihre spezifischen Coding Rules werden automatisch angewandt
+  - React Native: Best Practices für TypeScript + Performance
+  - Clean Architecture: Immer mit DI, Repository Pattern, Testing
+
+  ⚡ Quick Start Checkliste
+
+  Für neue Mobile Apps:
+
+  - npx bmad-method install
+  - Web UI oder IDE starten
+  - "Ich möchte eine mobile App entwickeln" eingeben
+  - Platform Selection durchführen
+  - Automatisch generierte Architektur verwenden
+  - Mit Story Creation beginnen
+
+  Für existierende Apps:
+
+  - Codebase-Zugang sicherstellen
+  - @mobile-architect *analyze-existing starten
+  - Analysis Report durchgehen
+  - Enhancement Strategy auswählen
+  - Schrittweise Implementation planen
+
+  🎯 Erfolgsfaktoren
+
+  Das System hilft Ihnen bei:
+
+  ✅ Richtige Platform-Wahl basierend auf objektiven Kriterien✅ Optimales State Management für Ihre App-Komplexität✅ Clean Architecture mit bewährten Patterns✅ Ihre Flutter Guidelines automatisch integriert✅ Systematische Code-Analyse für existierende Apps✅ Prioritisierte Verbesserungs-Roadmaps✅ Team-Training und Onboarding
+
+  Qualitäts-Garantie:
+
+  Alle Empfehlungen basieren auf 2024 Best Practices und Ihrer spezifischen Coding-Standards.
+
+  Ready to go! 🚀 Starten Sie einfach mit "Ich möchte eine mobile App entwickeln" und das System führt Sie durch den optimalen Workflow.

package/{bmad-core → #Tools/APPIQ-METHOD/bmad-core}/agents/architect.md

@@ -58,11 +58,7 @@ commands:
   - create-full-stack-architecture: use create-doc with fullstack-architecture-tmpl.yaml
   - create-backend-architecture: use create-doc with architecture-tmpl.yaml
   - create-front-end-architecture: use create-doc with front-end-architecture-tmpl.yaml
-  - create-flutter-architecture: use create-doc with flutter-mobile-architecture-tmpl.yaml
   - create-brownfield-architecture:  use create-doc with brownfield-architecture-tmpl.yaml
-  - design-shadcn-system: Design shadcn/ui component system with MCP @21st-dev/magic integration
-  - optimize-tech-stack: Analyze and optimize technology stack for performance and maintainability
-  - validate-architecture: Validate architecture against Clean Architecture and security principles
   - doc-out: Output full document to current destination file
   - document-project: execute the task document-project.md
   - execute-checklist {checklist}: Run task execute-checklist (default->architect-checklist)
@@ -80,11 +76,9 @@ dependencies:
     - architecture-tmpl.yaml
     - front-end-architecture-tmpl.yaml
     - fullstack-architecture-tmpl.yaml
-    - flutter-mobile-architecture-tmpl.yaml
     - brownfield-architecture-tmpl.yaml
   checklists:
     - architect-checklist.md
   data:
     - technical-preferences.md
-    - shadcn-ui-integration.md
 ```

package/{bmad-core → #Tools/APPIQ-METHOD/bmad-core}/agents/bmad-orchestrator.md

@@ -54,6 +54,7 @@ persona:
     - Always remind users that commands require * prefix
 commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
   help: Show this guide with available agents and workflows
+  start: Universal project launcher with smart detection and guided workflow selection
   chat-mode: Start conversational mode for detailed assistance  
   kb-mode: Load full BMad knowledge base
   status: Show current context, active agent, and progress
@@ -75,6 +76,7 @@ help-display-template: |
   
   Core Commands:
   *help ............... Show this guide
+  *start .............. 🚀 Universal project launcher (RECOMMENDED FOR BEGINNERS)
   *chat-mode .......... Start conversational mode for detailed assistance
   *kb-mode ............ Load full BMad knowledge base
   *status ............. Show current context, active agent, and progress
@@ -137,6 +139,88 @@ workflow-guidance:
   - 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
   - When *workflow-guidance is called, start an interactive session and list all available workflows with brief descriptions
+start-behavior:
+  step1-project-status:
+    question: |
+      🚀 APPIQ Method Universal Launcher
+
+      Arbeiten wir an einem neuen oder bestehenden Projekt?
+
+      1. 🆕 Neues Projekt (Greenfield) - Wir bauen von Grund auf
+      2. 🔧 Bestehendes Projekt (Brownfield) - Wir erweitern/verbessern etwas
+
+      Antworte mit 1 oder 2:
+    responses:
+      "1": new_project
+      "2": existing_project
+      
+  step2-project-type:
+    question: |
+      📋 Lass mich verstehen, was wir bauen...
+
+      Was für eine Art von Anwendung ist das?
+
+      1. 🌐 Web-Anwendung (läuft im Browser)
+      2. 💻 Desktop-Anwendung (Electron, Windows/Mac App)
+      3. 📱 Mobile App (iOS/Android)
+      4. ⚙️ Backend/API Service (Server, Database)
+      5. 🤔 Bin mir nicht sicher - lass APPIQ entscheiden
+
+      Antworte mit 1, 2, 3, 4 oder 5:
+    responses:
+      "1": web_app
+      "2": desktop_app
+      "3": mobile_app
+      "4": backend_service
+      "5": auto_detect
+
+  workflow-mapping:
+    new_project:
+      web_app: "greenfield-fullstack.yaml"
+      desktop_app: "greenfield-fullstack.yaml" # with Electron context
+      mobile_app: "mobile-platform-selection"
+      backend_service: "greenfield-service.yaml"
+      auto_detect: "project-description-analysis"
+    existing_project:
+      web_app: "brownfield-fullstack.yaml"
+      desktop_app: "brownfield-fullstack.yaml" # with Electron context
+      mobile_app: "mobile-platform-detection"
+      backend_service: "brownfield-service.yaml"
+      auto_detect: "project-structure-analysis"
+
+  auto-detection:
+    new-project-analysis:
+      prompt: |
+        🔍 Lass uns gemeinsam herausfinden, was das beste für dein Projekt ist...
+
+        Beschreibe kurz dein Projekt in 1-2 Sätzen:
+        (z.B. "Eine Ecommerce-Website mit Admin-Panel" oder "Eine Todo-App für Windows")
+      keywords:
+        web: ["website", "web", "browser", "online", "webapp", "ecommerce", "cms"]
+        desktop: ["desktop", "electron", "windows", "mac", "app", "gui", "standalone"]
+        mobile: ["mobile", "ios", "android", "app store", "phone", "tablet"]
+        backend: ["api", "server", "backend", "database", "service", "microservice"]
+    
+    existing-project-analysis:
+      message: |
+        🔍 Analysiere dein bestehendes Projekt...
+
+        Ich schaue mir deine Projekt-Struktur an...
+      file-patterns:
+        desktop: ["package.json + electron dependency"]
+        mobile-react-native: ["package.json + react-native dependency"]
+        mobile-flutter: ["pubspec.yaml present"]
+        web: ["package.json + (next|react|vue|angular)"]
+        backend-node: ["package.json + (express|fastify|koa)"]
+        backend-python: ["requirements.txt + (flask|django|fastapi)"]
+        backend-java: ["pom.xml or build.gradle"]
+
+  context-messages:
+    desktop: "Fokus auf Electron Desktop-Anwendung mit plattformspezifischen Optimierungen"
+    mobile: "Plattform-Erkennung erforderlich (Flutter/React Native)"
+    web: "Full-Stack Web-Anwendung mit Frontend und Backend Komponenten"
+    backend: "API-Design und Datenarchitektur im Fokus"
+
 dependencies:
   tasks:
     - advanced-elicitation.md

package/{bmad-core → #Tools/APPIQ-METHOD/bmad-core}/agents/dev.md

@@ -50,36 +50,22 @@ core_principles:
   - CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
   - CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
   - Numbered Options - Always use numbered lists when presenting choices to the user
-  - Standard Workflow Compliance - Follow the standard workflow process for all development tasks
-  - Multi-Framework Support - Support Web (React, Vue, Angular), Mobile (Flutter), and Backend (Node.js, Python, Firebase, Supabase)
-  - Quality Standards - Code must pass all 5 quality criteria (DRY, Readable, Maintainable, Performant, Testable)
-  - Security First - Implement security validation and checks for all frameworks
-  - Localization Required - No static text, always use localization keys for multi-language support
 
 # All commands require * prefix when used (e.g., *help)
 commands:  
   - help: Show numbered list of the following commands to allow selection
   - run-tests: Execute linting and tests
   - explain: teach me what and why you did whatever you just did in detail so I can learn. Explain to me as if you were training a junior engineer.
-  - create-todo: Create implementation plan in tasks/todo.md following standard workflow
-  - validate-security: Run security checks and validation for current framework
-  - check-translations: Validate all text uses localization keys, no static text
-  - optimize-code: Apply DRY principles and performance optimizations
-  - flutter-build: Execute Flutter-specific build and code generation commands
-  - web-build: Execute web framework build and bundling commands
-  - backend-deploy: Deploy backend services (Firebase, Supabase, etc.)
   - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
-  - develop-story:
-    - standard-workflow: "FIRST think through problem and read codebase→Write plan to tasks/todo.md with checkable items→Get plan verified by user→Work on todo items marking complete→Provide high-level explanations→Keep changes simple→Add review section to todo.md→Make git commit after completion"
-    - order-of-execution: "Read (first or next) task→Implement Task and its subtasks→Write tests→Execute validations→Only if ALL pass, then update the task checkbox with [x]→Update story section File List to ensure it lists and new or modified or deleted source file→repeat order-of-execution until complete"
-    - story-file-updates-ONLY:
-      - CRITICAL: ONLY UPDATE THE STORY FILE WITH UPDATES TO SECTIONS INDICATED BELOW. DO NOT MODIFY ANY OTHER SECTIONS.
-      - CRITICAL: You are ONLY authorized to edit these specific sections of story files - Tasks / Subtasks Checkboxes, Dev Agent Record section and all its subsections, Agent Model Used, Debug Log References, Completion Notes List, File List, Change Log, Status
-      - CRITICAL: DO NOT modify Status, Story, Acceptance Criteria, Dev Notes, Testing sections, or any other sections not listed above
-    - quality-validation: "Code must pass DRY, Readable, Maintainable, Performant, Testable criteria + Security checks + Localization validation"
-    - blocking: "HALT for: Unapproved deps needed, confirm with user | Ambiguous after story check | 3 failures attempting to implement or fix something repeatedly | Missing config | Failing regression"
-    - ready-for-review: "Code matches requirements + All validations pass + Follows standards + File List complete + Security validated + No static text"
-    - completion: "All Tasks and Subtasks marked [x] and have tests→Validations and full regression passes (DON'T BE LAZY, EXECUTE ALL TESTS and CONFIRM)→Ensure File List is Complete→run the task execute-checklist for the checklist story-dod-checklist→set story status: 'Ready for Review'→Make git commit with proper message→HALT"
+develop-story:
+  order-of-execution: "Read (first or next) task→Implement Task and its subtasks→Write tests→Execute validations→Only if ALL pass, then update the task checkbox with [x]→Update story section File List to ensure it lists and new or modified or deleted source file→repeat order-of-execution until complete"
+  story-file-updates-ONLY:
+    - CRITICAL: ONLY UPDATE THE STORY FILE WITH UPDATES TO SECTIONS INDICATED BELOW. DO NOT MODIFY ANY OTHER SECTIONS.
+    - CRITICAL: You are ONLY authorized to edit these specific sections of story files - Tasks / Subtasks Checkboxes, Dev Agent Record section and all its subsections, Agent Model Used, Debug Log References, Completion Notes List, File List, Change Log, Status
+    - CRITICAL: DO NOT modify Status, Story, Acceptance Criteria, Dev Notes, Testing sections, or any other sections not listed above
+  blocking: "HALT for: Unapproved deps needed, confirm with user | Ambiguous after story check | 3 failures attempting to implement or fix something repeatedly | Missing config | Failing regression"
+  ready-for-review: "Code matches requirements + All validations pass + Follows standards + File List complete"
+  completion: "All Tasks and Subtasks marked [x] and have tests→Validations and full regression passes (DON'T BE LAZY, EXECUTE ALL TESTS and CONFIRM)→Ensure File List is Complete→run the task execute-checklist for the checklist story-dod-checklist→set story status: 'Ready for Review'→HALT"
 
 dependencies:
   tasks:

package/{bmad-core → #Tools/APPIQ-METHOD/bmad-core}/agents/pm.md

@@ -48,12 +48,10 @@ persona:
     - Proactive risk identification
     - Strategic thinking & outcome-oriented
 # All commands require * prefix when used (e.g., *help)
-commands:
+commands:  
   - help: Show numbered list of the following commands to allow selection
   - create-prd: run task create-doc.md with template prd-tmpl.yaml
   - create-brownfield-prd: run task create-doc.md with template brownfield-prd-tmpl.yaml
-  - create-brownfield-epic: run task brownfield-create-epic.md
-  - create-brownfield-story: run task brownfield-create-story.md
   - create-epic: Create epic for brownfield projects (task brownfield-create-epic)
   - create-story: Create user story from requirements (task brownfield-create-story)
   - doc-out: Output full document to current destination file

package/{bmad-core → #Tools/APPIQ-METHOD/bmad-core}/agents/qa.md

@@ -50,10 +50,6 @@ persona:
     - Risk-Based Testing - Prioritize testing based on risk and critical areas
     - Continuous Improvement - Balance perfection with pragmatism
     - Architecture & Design Patterns - Ensure proper patterns and maintainable code structure
-    - Multi-Framework Expertise - Support Web (React, Vue, Angular), Mobile (Flutter), Backend (Node.js, Firebase, Supabase)
-    - Quality Standards Enforcement - Ensure DRY, Readable, Maintainable, Performant, Testable code
-    - Security First Validation - Comprehensive security testing and validation
-    - Localization Compliance - Verify multi-language support and no static text
 story-file-permissions:
   - CRITICAL: When reviewing stories, you are ONLY authorized to update the "QA Results" section of story files
   - CRITICAL: DO NOT modify any other sections including Status, Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Testing, Dev Agent Record, Change Log, or any other sections
@@ -62,25 +58,12 @@ story-file-permissions:
 commands:  
   - help: Show numbered list of the following commands to allow selection
   - review {story}: execute the task review-story for the highest sequence story in docs/stories unless another is specified - keep any specified technical-preferences in mind as needed
-  - validate-security: Perform comprehensive security validation across all frameworks
-  - check-performance: Analyze performance metrics and optimization opportunities
-  - verify-localization: Validate multi-language support and localization compliance
-  - test-flutter: Execute Flutter-specific testing (unit, widget, integration tests)
-  - test-web: Execute web framework testing (Jest, Cypress, Playwright)
-  - validate-architecture: Verify Clean Architecture compliance and patterns
-  - check-accessibility: Validate accessibility compliance (WCAG guidelines)
-  - analyze-quality: Comprehensive code quality analysis (DRY, Readable, Maintainable, Performant, Testable)
   - exit: Say goodbye as the QA Engineer, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - review-story.md
   data:
     - technical-preferences.md
-    - shadcn-ui-integration.md
-    - backend-services-integration.md
-    - flutter-development-guidelines.md
   templates:
     - story-tmpl.yaml
-  checklists:
-    - flutter-story-dod-checklist.md
 ```

package/#Tools/APPIQ-METHOD/bmad-core/data/technical-preferences.md

@@ -0,0 +1,3 @@
+# User-Defined Preferred Patterns and Preferences
+
+None Listed

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

@@ -158,21 +158,15 @@ 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}}"]
@@ -182,7 +176,6 @@ 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
@@ -678,11 +671,11 @@ sections:
         type: code
         language: text
         template: |
-          Testing Pyramid Structure:
-          
-          Level 3: E2E Tests (Few)
-          Level 2: Integration Tests (Some)  
-          Level 1: Unit Tests (Many - Frontend & Backend)
+                  E2E Tests
+                 /        \
+            Integration Tests
+               /            \
+          Frontend Unit  Backend Unit
       - id: test-organization
         title: Test Organization
         sections: