appiq-solution 1.2.0 → 1.3.1

package/#Tools/APPIQ-METHOD/expansion-packs/bmad-2d-unity-game-dev/workflows/game-prototype.yaml

@@ -0,0 +1,175 @@
+workflow:
+  id: unity-game-prototype
+  name: Game Prototype Development (Unity)
+  description: Fast-track workflow for rapid game prototyping and concept validation. Optimized for game jams, proof-of-concept development, and quick iteration on game mechanics using Unity and C#.
+  type: prototype
+  project_types:
+    - game-jam
+    - proof-of-concept
+    - mechanic-test
+    - technical-demo
+    - learning-project
+    - rapid-iteration
+  prototype_sequence:
+    - step: concept_definition
+      agent: game-designer
+      duration: 15-30 minutes
+      creates: concept-summary.md
+      notes: Quickly define core game concept, primary mechanic, and target experience. Focus on what makes this game unique and fun.
+    - step: rapid_design
+      agent: game-designer
+      duration: 30-60 minutes
+      creates: prototype-spec.md
+      requires: concept-summary.md
+      optional_steps:
+        - quick_brainstorming
+        - reference_research
+      notes: Create minimal but complete design specification. Focus on core mechanics, basic controls, and success/failure conditions.
+    - step: technical_planning
+      agent: game-developer
+      duration: 15-30 minutes
+      creates: prototype-architecture.md
+      requires: prototype-spec.md
+      notes: Define minimal technical implementation plan. Identify core Unity systems needed and performance constraints.
+    - step: implementation_stories
+      agent: game-sm
+      duration: 30-45 minutes
+      creates: prototype-stories/
+      requires: prototype-spec.md, prototype-architecture.md
+      notes: Create 3-5 focused implementation stories for core prototype features. Each story should be completable in 2-4 hours.
+    - step: iterative_development
+      agent: game-developer
+      duration: varies
+      implements: prototype-stories/
+      notes: Implement stories in priority order. Test frequently in the Unity Editor and adjust design based on what feels fun. Document discoveries.
+  workflow_end:
+    action: prototype_evaluation
+    notes: 'Prototype complete. Evaluate core mechanics, gather feedback, and decide next steps: iterate, expand, or archive.'
+  game_jam_sequence:
+    - step: jam_concept
+      agent: game-designer
+      duration: 10-15 minutes
+      creates: jam-concept.md
+      notes: Define game concept based on jam theme. One sentence core mechanic, basic controls, win condition.
+    - step: jam_implementation
+      agent: game-developer
+      duration: varies (jam timeline)
+      creates: working-prototype
+      requires: jam-concept.md
+      notes: Directly implement core mechanic in Unity. No formal stories - iterate rapidly on what's fun. Document major decisions.
+  jam_workflow_end:
+    action: jam_submission
+    notes: Submit to game jam. Capture lessons learned and consider post-jam development if concept shows promise.
+  flow_diagram: |
+    ```mermaid
+    graph TD
+        A[Start: Prototype Project] --> B{Development Context?}
+        B -->|Standard Prototype| C[game-designer: concept-summary.md]
+        B -->|Game Jam| D[game-designer: jam-concept.md]
+
+        C --> E[game-designer: prototype-spec.md]
+        E --> F[game-developer: prototype-architecture.md]
+        F --> G[game-sm: create prototype stories]
+        G --> H[game-developer: iterative implementation]
+        H --> I[Prototype Evaluation]
+
+        D --> J[game-developer: direct implementation]
+        J --> K[Game Jam Submission]
+
+        E -.-> E1[Optional: quick brainstorming]
+        E -.-> E2[Optional: reference research]
+
+        style I fill:#90EE90
+        style K fill:#90EE90
+        style C fill:#FFE4B5
+        style E fill:#FFE4B5
+        style F fill:#FFE4B5
+        style G fill:#FFE4B5
+        style H fill:#FFE4B5
+        style D fill:#FFB6C1
+        style J fill:#FFB6C1
+    ```
+  decision_guidance:
+    use_prototype_sequence_when:
+      - Learning new game development concepts
+      - Testing specific game mechanics
+      - Building portfolio pieces
+      - Have 1-7 days for development
+      - Need structured but fast development
+      - Want to validate game concepts before full development
+    use_game_jam_sequence_when:
+      - Participating in time-constrained game jams
+      - Have 24-72 hours total development time
+      - Want to experiment with wild or unusual concepts
+      - Learning through rapid iteration
+      - Building networking/portfolio presence
+  prototype_best_practices:
+    scope_management:
+      - Start with absolute minimum viable gameplay
+      - One core mechanic implemented well beats many mechanics poorly
+      - Focus on "game feel" over features
+      - Cut features ruthlessly to meet timeline
+    rapid_iteration:
+      - Test the game every 1-2 hours of development in the Unity Editor
+      - Ask "Is this fun?" frequently during development
+      - Be willing to pivot mechanics if they don't feel good
+      - Document what works and what doesn't
+    technical_efficiency:
+      - Use simple graphics (geometric shapes, basic sprites)
+      - Leverage Unity's built-in components heavily
+      - Avoid complex custom systems in prototypes
+      - Prioritize functional over polished
+  prototype_evaluation_criteria:
+    core_mechanic_validation:
+      - Is the primary mechanic engaging for 30+ seconds?
+      - Do players understand the mechanic without explanation?
+      - Does the mechanic have depth for extended play?
+      - Are there natural difficulty progression opportunities?
+    technical_feasibility:
+      - Does the prototype run at acceptable frame rates?
+      - Are there obvious technical blockers for expansion?
+      - Is the codebase clean enough for further development?
+      - Are performance targets realistic for full game?
+    player_experience:
+      - Do testers engage with the game voluntarily?
+      - What emotions does the game create in players?
+      - Are players asking for "just one more try"?
+      - What do players want to see added or changed?
+  post_prototype_options:
+    iterate_and_improve:
+      action: continue_prototyping
+      when: Core mechanic shows promise but needs refinement
+      next_steps: Create new prototype iteration focusing on identified improvements
+    expand_to_full_game:
+      action: transition_to_full_development
+      when: Prototype validates strong game concept
+      next_steps: Use game-dev-greenfield workflow to create full game design and architecture
+    pivot_concept:
+      action: new_prototype_direction
+      when: Current mechanic doesn't work but insights suggest new direction
+      next_steps: Apply learnings to new prototype concept
+    archive_and_learn:
+      action: document_learnings
+      when: Prototype doesn't work but provides valuable insights
+      next_steps: Document lessons learned and move to next prototype concept
+  time_boxing_guidance:
+    concept_phase: Maximum 30 minutes - if you can't explain the game simply, simplify it
+    design_phase: Maximum 1 hour - focus on core mechanics only
+    planning_phase: Maximum 30 minutes - identify critical path to playable prototype
+    implementation_phase: Time-boxed iterations - test every 2-4 hours of work
+  success_metrics:
+    development_velocity:
+      - Playable prototype in first day of development
+      - Core mechanic demonstrable within 4-6 hours of coding
+      - Major iteration cycles completed in 2-4 hour blocks
+    learning_objectives:
+      - Clear understanding of what makes the mechanic fun (or not)
+      - Technical feasibility assessment for full development
+      - Player reaction and engagement validation
+      - Design insights for future development
+  handoff_prompts:
+    concept_to_design: Game concept defined. Create minimal design specification focusing on core mechanics and player experience.
+    design_to_technical: Design specification ready. Create technical implementation plan for rapid prototyping.
+    technical_to_stories: Technical plan complete. Create focused implementation stories for prototype development.
+    stories_to_implementation: Stories ready. Begin iterative implementation with frequent playtesting and design validation.
+    prototype_to_evaluation: Prototype playable. Evaluate core mechanics, gather feedback, and determine next development steps.

package/#Tools/APPIQ-METHOD/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/#Tools/APPIQ-METHOD/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
+```