aios-core 2.1.0

package/.aios-core/data/technical-preferences.md

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

package/.aios-core/data/workflow-patterns.yaml

@@ -0,0 +1,267 @@
+# Workflow Patterns Definition
+# Defines common AIOS workflow sequences for context detection
+#
+# Version: 1.0
+# Created: 2025-01-15
+# Story: 6.1.2.5 - Contextual Agent Load System
+#
+# Format:
+# - workflow_name: Unique identifier
+# - description: Human-readable workflow description
+# - agent_sequence: Expected sequence of agents used
+# - key_commands: Commands that signal this workflow
+# - trigger_threshold: Minimum matching commands to detect pattern (default: 2)
+
+workflows:
+  # Story Development Workflow (Most Common)
+  story_development:
+    description: "Complete story lifecycle from validation to deployment"
+    agent_sequence:
+      - po         # Story validation
+      - dev        # Implementation
+      - qa         # Quality assurance
+      - devops     # Deployment
+    key_commands:
+      - validate-story-draft
+      - validate-next-story
+      - develop
+      - develop-yolo
+      - develop-interactive
+      - develop-preflight
+      - review-qa
+      - apply-qa-fixes
+      - pre-push-quality-gate
+      - github-pr-automation
+    trigger_threshold: 2
+    typical_duration: "1-5 days"
+    success_indicators:
+      - "Story status: Ready for Review"
+      - "All tests passing"
+      - "PR created and merged"
+    # Workflow transitions (Story 6.1.2.5 - Workflow Navigation)
+    transitions:
+      validated:
+        trigger: "validate-story-draft completed successfully"
+        greeting_message: "Story validated! Ready to implement."
+        next_steps:
+          - command: develop-yolo
+            args_template: "${story_path}"
+            description: "Autonomous YOLO mode (no interruptions)"
+          - command: develop-interactive
+            args_template: "${story_path}"
+            description: "Interactive mode with checkpoints (default)"
+          - command: develop-preflight
+            args_template: "${story_path}"
+            description: "Plan everything upfront, then execute"
+      in_development:
+        trigger: "develop completed successfully"
+        greeting_message: "Development complete! Ready for QA review."
+        next_steps:
+          - command: review-qa
+            args_template: "${story_path}"
+            description: "Run QA review and tests"
+          - command: run-tests
+            args_template: ""
+            description: "Execute test suite manually"
+      qa_reviewed:
+        trigger: "review-qa completed successfully"
+        greeting_message: "QA review complete!"
+        next_steps:
+          - command: apply-qa-fixes
+            args_template: ""
+            description: "Apply QA feedback and fixes"
+          - command: pre-push-quality-gate
+            args_template: ""
+            description: "Run final quality checks before push"
+
+  # Epic Creation Workflow
+  epic_creation:
+    description: "Create and organize epics with initial stories"
+    agent_sequence:
+      - po         # Epic planning
+      - sm         # Story creation
+      - architect  # Technical review
+    key_commands:
+      - create-epic
+      - brownfield-create-epic
+      - create-story
+      - brownfield-create-story
+      - create-next-story
+      - validate-story-draft
+      - analyze-impact
+    trigger_threshold: 2
+    typical_duration: "0.5-2 days"
+    success_indicators:
+      - "Epic documented"
+      - "Initial stories created"
+      - "Stories validated"
+
+  # Backlog Management Workflow
+  backlog_management:
+    description: "Review, prioritize, and schedule backlog items"
+    agent_sequence:
+      - qa         # Backlog review
+      - po         # Prioritization
+      - pm         # Scheduling
+    key_commands:
+      - backlog-add
+      - backlog-update
+      - backlog-review
+      - backlog-debt
+      - backlog-summary
+      - backlog-prioritize
+      - backlog-schedule
+    trigger_threshold: 2
+    typical_duration: "0.5-1 day"
+    success_indicators:
+      - "Backlog items prioritized"
+      - "Sprint planned"
+
+  # Architecture Review Workflow
+  architecture_review:
+    description: "Design review and documentation of architectural decisions"
+    agent_sequence:
+      - architect  # Design and review
+      - qa         # Review validation
+      - dev        # Implementation planning
+    key_commands:
+      - analyze-impact
+      - analyze-framework
+      - create-doc
+      - shard-doc
+      - review-proposal
+      - review-story
+      - architect-analyze-impact
+    trigger_threshold: 2
+    typical_duration: "1-3 days"
+    success_indicators:
+      - "Architecture documented"
+      - "Decision reviewed"
+      - "Implementation plan approved"
+
+  # Git Workflow (DevOps)
+  git_workflow:
+    description: "Version control and deployment workflow"
+    agent_sequence:
+      - dev        # Code changes
+      - devops     # Git operations
+    key_commands:
+      - pre-push-quality-gate
+      - github-pr-automation
+      - repository-cleanup
+      - version-management
+    trigger_threshold: 2
+    typical_duration: "0.5-1 day"
+    success_indicators:
+      - "Changes committed"
+      - "PR created"
+      - "Code merged"
+
+  # Database Development Workflow
+  database_workflow:
+    description: "Database schema design and migration workflow"
+    agent_sequence:
+      - data-engineer  # Schema design
+      - dev            # Migration implementation
+      - qa             # Testing
+    key_commands:
+      - db-domain-modeling
+      - db-schema-audit
+      - db-dry-run
+      - db-apply-migration
+      - db-rollback
+      - db-smoke-test
+      - db-rls-audit
+      - db-verify-order
+    trigger_threshold: 2
+    typical_duration: "1-3 days"
+    success_indicators:
+      - "Schema designed"
+      - "Migrations tested"
+      - "RLS policies validated"
+
+  # Code Quality Improvement Workflow
+  code_quality_workflow:
+    description: "Refactoring and code quality improvements"
+    agent_sequence:
+      - qa         # Quality assessment
+      - dev        # Refactoring
+    key_commands:
+      - improve-code-quality
+      - suggest-refactoring
+      - optimize-performance
+      - security-scan
+      - generate-tests
+      - nfr-assess
+    trigger_threshold: 2
+    typical_duration: "0.5-2 days"
+    success_indicators:
+      - "Code refactored"
+      - "Tests added"
+      - "Quality metrics improved"
+
+  # Documentation Workflow
+  documentation_workflow:
+    description: "Create and synchronize project documentation"
+    agent_sequence:
+      - analyst    # Research and analysis
+      - architect  # Documentation creation
+      - po         # Review
+    key_commands:
+      - document-project
+      - sync-documentation
+      - create-doc
+      - shard-doc
+      - index-docs
+      - generate-documentation
+    trigger_threshold: 2
+    typical_duration: "0.5-2 days"
+    success_indicators:
+      - "Documentation created"
+      - "Documentation synchronized"
+      - "Documentation indexed"
+
+  # UX Design Workflow
+  ux_workflow:
+    description: "User experience design and validation"
+    agent_sequence:
+      - ux-design-expert  # Design
+      - dev               # Implementation
+      - qa                # Validation
+    key_commands:
+      - ux-create-wireframe
+      - ux-user-research
+      - ux-ds-scan-artifact
+      - build-component
+      - audit-codebase
+    trigger_threshold: 2
+    typical_duration: "1-3 days"
+    success_indicators:
+      - "Wireframes created"
+      - "Components implemented"
+      - "UX validated"
+
+  # Brainstorming and Research Workflow
+  research_workflow:
+    description: "Facilitated brainstorming and research sessions"
+    agent_sequence:
+      - analyst    # Research
+      - architect  # Analysis
+      - po         # Documentation
+    key_commands:
+      - analyst-facilitate-brainstorming
+      - advanced-elicitation
+      - create-deep-research-prompt
+      - kb-mode-interaction
+    trigger_threshold: 2
+    typical_duration: "0.5-1 day"
+    success_indicators:
+      - "Research completed"
+      - "Ideas documented"
+      - "Action items created"
+
+# Validation Notes:
+# - Patterns cross-referenced with Epic 6.1 workflow analysis
+# - Commands verified against actual project usage in .aios-core/agents/*.md
+# - Agent sequences match actual workflow patterns from recent stories
+# - Threshold of 2 ensures workflow detection is accurate but not overly sensitive

package/.aios-core/development/README.md

@@ -0,0 +1,142 @@
+# Development Module
+
+The Development module contains all agent-related assets: agent definitions, team configurations, tasks, workflows, and supporting scripts.
+
+## Structure
+
+```
+development/
+├── agents/           # 11 agent persona definitions
+├── agent-teams/      # 5 team configurations
+├── tasks/            # 115+ task definitions
+├── workflows/        # 7 workflow definitions
+└── scripts/          # 24 supporting scripts
+```
+
+## Agents (11 files)
+
+| Agent | ID | Description |
+|-------|-----|------------|
+| AIOS Master | `aios-master` | Framework orchestrator |
+| Analyst | `analyst` | Business analyst |
+| Architect | `architect` | Technical architect |
+| Data Engineer | `data-engineer` | Data engineering |
+| Developer | `dev` | Full-stack developer |
+| DevOps | `devops` | DevOps engineer |
+| Product Manager | `pm` | Product manager |
+| Product Owner | `po` | Product owner |
+| QA | `qa` | Quality assurance |
+| Scrum Master | `sm` | Scrum master |
+| UX Expert | `ux-design-expert` | UX designer |
+
+### Activation
+
+Agents are activated via IDE commands (`@agent-name`) or by loading the Markdown definition file.
+
+```javascript
+const { AgentConfigLoader } = require('./scripts/agent-config-loader');
+const loader = new AgentConfigLoader('dev');
+const config = await loader.loadAgent('dev');
+```
+
+## Agent Teams (5 files)
+
+Pre-configured agent team compositions:
+
+| Team | Agents | Use Case |
+|------|--------|----------|
+| `team-all` | All 11 agents | Full development team |
+| `team-fullstack` | dev, qa, architect, devops | Full-stack projects |
+| `team-ide-minimal` | dev, qa | Minimal IDE setup |
+| `team-no-ui` | dev, architect, devops, data-engineer | Backend/API projects |
+| `team-qa-focused` | qa, dev, architect | Quality-focused work |
+
+## Tasks (115+ files)
+
+Task definitions for agent workflows. Each task is a Markdown file with YAML frontmatter defining execution parameters.
+
+### Categories
+
+- **Story Management:** create-story, validate-story, sync-story
+- **Code Operations:** review-code, generate-tests, refactor
+- **Documentation:** create-doc, update-readme, document-api
+- **Process:** execute-checklist, correct-course, handoff
+
+### Example Usage
+
+```javascript
+const fs = require('fs');
+const task = fs.readFileSync('./tasks/create-story.md', 'utf-8');
+// Parse and execute task workflow
+```
+
+## Workflows (7 files)
+
+Multi-step development workflows:
+
+| Workflow | Description |
+|----------|-------------|
+| `greenfield-fullstack.yaml` | New full-stack project |
+| `greenfield-service.yaml` | New backend service |
+| `greenfield-ui.yaml` | New frontend project |
+| `brownfield-fullstack.yaml` | Existing full-stack enhancement |
+| `brownfield-service.yaml` | Existing backend enhancement |
+| `brownfield-ui.yaml` | Existing frontend enhancement |
+
+## Scripts (24 files)
+
+Supporting JavaScript modules:
+
+| Script | Purpose |
+|--------|---------|
+| `agent-config-loader.js` | Load and parse agent definitions |
+| `greeting-builder.js` | Build contextual agent greetings |
+| `story-manager.js` | Manage story files and updates |
+| `decision-recorder.js` | Record agent decisions |
+| `workflow-navigator.js` | Navigate between workflow steps |
+| `task-identifier-resolver.js` | Resolve task references |
+
+### Key APIs
+
+```javascript
+// Greeting Builder
+const GreetingBuilder = require('./scripts/greeting-builder');
+const builder = new GreetingBuilder();
+const greeting = await builder.buildGreeting(agentDef, context);
+
+// Story Manager
+const StoryManager = require('./scripts/story-manager');
+const story = await StoryManager.loadStory(storyId);
+await story.updateTask(taskId, { status: 'completed' });
+```
+
+## Dependencies
+
+This module depends on:
+- `../core/` - Configuration, session management, elicitation
+- `../scripts/` - Infrastructure utilities (git, PM tools)
+
+## Migration Notes
+
+This module was created as part of ADR-002 modular architecture migration. Previously, these files were scattered across multiple directories.
+
+**Reference:** [ADR-002-migration-map.md](../../docs/architecture/decisions/ADR-002-migration-map.md)
+
+## Testing
+
+Run development module tests:
+
+```bash
+npm test -- --grep "DEVELOPMENT"
+```
+
+Smoke tests:
+- DEV-01: Agent Load
+- DEV-02: Agent Config Parse
+- DEV-03: Greeting Build
+- DEV-04: Task Load
+- DEV-05: Workflow Load
+- DEV-06: Team Config
+- DEV-07: Story Management
+- DEV-08: Decision Log
+- DEV-09: Agent Exit Hooks

package/.aios-core/development/agent-teams/team-all.yaml

@@ -0,0 +1,15 @@
+bundle:
+  name: Team All
+  icon: 👥
+  description: Includes every core system agent.
+agents:
+  - aios-orchestrator
+  - aios-developer
+  - '*'
+workflows:
+  - brownfield-fullstack.yaml
+  - brownfield-service.yaml
+  - brownfield-ui.yaml
+  - greenfield-fullstack.yaml
+  - greenfield-service.yaml
+  - greenfield-ui.yaml

package/.aios-core/development/agent-teams/team-fullstack.yaml

@@ -0,0 +1,18 @@
+bundle:
+  name: Team Fullstack
+  icon: 🚀
+  description: Team capable of full stack, front end only, or service development.
+agents:
+  - aios-orchestrator
+  - analyst
+  - pm
+  - ux-expert
+  - architect
+  - po
+workflows:
+  - brownfield-fullstack.yaml
+  - brownfield-service.yaml
+  - brownfield-ui.yaml
+  - greenfield-fullstack.yaml
+  - greenfield-service.yaml
+  - greenfield-ui.yaml

package/.aios-core/development/agent-teams/team-ide-minimal.yaml

@@ -0,0 +1,10 @@
+bundle:
+  name: Team IDE Minimal
+  icon: ⚡
+  description: Only the bare minimum for the IDE PO SM dev qa cycle.
+agents:
+  - po
+  - sm
+  - dev
+  - qa
+workflows: null

package/.aios-core/development/agent-teams/team-no-ui.yaml

@@ -0,0 +1,13 @@
+bundle:
+  name: Team No UI
+  icon: 🔧
+  description: Team with no UX or UI Planning.
+agents:
+  - aios-orchestrator
+  - analyst
+  - pm
+  - architect
+  - po
+workflows:
+  - greenfield-service.yaml
+  - brownfield-service.yaml

package/.aios-core/development/agent-teams/team-qa-focused.yaml

@@ -0,0 +1,155 @@
+bundle:
+  name: Team QA-Focused
+  icon: 🔍
+  description: Quality-focused team that orchestrates code review, testing, and deployment validation using CodeRabbit integration. Ideal for pre-PR reviews, deployment gates, and comprehensive quality assurance.
+
+agents:
+  - dev                # Pre-commit CodeRabbit reviews, development quality
+  - qa                 # Automated and manual QA, story validation
+  - github-devops      # PR quality gates, deployment safety checks
+
+workflows:
+  - code-quality-gate.yaml          # Unified quality validation (lint, tests, CodeRabbit)
+  - pr-validation.yaml              # Comprehensive PR validation before creation
+  - deployment-safety-check.yaml    # Pre-deployment security and quality scan
+
+tasks:
+  - run-tests.md                    # Test execution with CodeRabbit integration
+  - github-pr-automation.md         # PR automation with quality gates
+
+purpose: |
+  This team ensures code quality throughout the development lifecycle:
+
+  1. **Development Phase** (@dev):
+     - Pre-commit CodeRabbit reviews catch issues early
+     - Fix CRITICAL issues before commit
+     - Document HIGH issues in story notes
+
+  2. **QA Phase** (@qa):
+     - Automated code review before human QA
+     - Run comprehensive test suites
+     - Validate story acceptance criteria
+     - Block completion on CRITICAL issues
+
+  3. **PR Phase** (@github-devops):
+     - Pre-PR quality gate (0 CRITICAL issues required)
+     - Automated PR validation workflow
+     - Lint + Tests + CodeRabbit scan
+     - Generate comprehensive PR validation report
+
+  4. **Deployment Phase** (@github-devops):
+     - Deep security scan with CodeRabbit
+     - Risk analysis and blocking issue detection
+     - Environment configuration validation
+     - Migration status checks
+     - Generate deployment safety report
+
+when_to_use:
+  - Before marking stories "Ready for Review"
+  - Before creating pull requests
+  - Before production/staging deployments
+  - During QA story validation
+  - When enforcing quality standards
+  - For comprehensive code quality audits
+
+quality_gates:
+  pre_commit:
+    trigger: Developer marks story complete
+    agent: dev
+    checks:
+      - coderabbit --prompt-only -t uncommitted
+      - Fix all CRITICAL issues
+      - Document HIGH issues
+    threshold: 0 CRITICAL issues
+
+  pre_pr:
+    trigger: Before creating PR
+    agent: github-devops
+    checks:
+      - coderabbit --prompt-only --base main
+      - npm run lint
+      - npm test
+    threshold: 0 CRITICAL issues, lint PASS, tests PASS
+
+  pre_merge:
+    trigger: PR opened/updated
+    agent: github-devops
+    checks:
+      - GitHub Actions CI (coderabbit-ci.yml)
+      - PR validation workflow
+      - Coverage check
+    threshold: Quality gate PASS from CI
+
+  pre_deployment:
+    trigger: Before production/staging deploy
+    agent: github-devops
+    checks:
+      - Deep CodeRabbit scan (last 10 commits)
+      - Environment configuration validation
+      - Database migration status
+      - Test suite execution
+    threshold: 0 CRITICAL, ≤3 HIGH (production), env 100%, tests PASS
+
+coderabbit_integration:
+  enabled: true
+  version: 0.3.4
+
+  severity_thresholds:
+    CRITICAL: 0      # Block at all gates
+    HIGH: 10         # Warn at development, block at deployment (≤3 for production)
+    MEDIUM: tracked  # Technical debt, does not block
+    LOW: optional    # Improvements, does not block
+
+  workflows_with_integration:
+    - code-quality-gate.yaml
+    - pr-validation.yaml
+    - deployment-safety-check.yaml
+
+  github_actions:
+    - .github/workflows/coderabbit-ci.yml
+
+  scripts:
+    - scripts/generate-quality-dashboard.js
+
+  report_directories:
+    - docs/qa/coderabbit-reports/
+    - docs/qa/pr-validations/
+    - docs/deployments/
+
+usage_example: |
+  # Typical workflow with this team:
+
+  ## 1. Development (by @dev)
+  "Mark this story as ready for review"
+  → @dev runs pre-commit CodeRabbit check
+  → Fixes CRITICAL issues
+  → Documents HIGH issues in story
+  → Story marked complete
+
+  ## 2. QA Validation (by @qa)
+  "*code-review uncommitted"
+  → @qa runs automated review
+  → Executes test suites
+  → Validates acceptance criteria
+  → Reports any quality gate failures
+
+  ## 3. PR Creation (by @github-devops)
+  "Create PR for this feature"
+  → @github-devops runs pr-validation workflow
+  → Checks: sync, CodeRabbit, lint, tests, coverage
+  → Generates validation report
+  → Creates PR with report link
+
+  ## 4. Deployment (by @github-devops)
+  "Run deployment safety check for production"
+  → @github-devops runs deployment-safety-check workflow
+  → Deep scan, risk analysis, env check, migrations, tests
+  → Generates safety report with GO/NO-GO decision
+  → Blocks if critical issues found
+
+notes:
+  - All three agents use CodeRabbit CLI v0.3.4
+  - Quality gates are enforced at multiple levels
+  - Reports are generated and stored for audit trail
+  - GitHub Actions provide automated enforcement
+  - Dashboard aggregates metrics across all reviews