omgkit 2.12.0 → 2.15.0

package/plugin/templates/autonomous/archetypes/microservices-app.yaml

@@ -0,0 +1,431 @@
+name: "Microservices Application"
+id: microservices-app
+description: "Distributed system with independently deployable services, API gateway, and container orchestration"
+estimated_duration: "8-16 weeks"
+icon: "cubes"
+
+# Default technology recommendations
+defaults:
+  language: typescript
+  framework: nestjs
+  gateway: kong
+  discovery: kubernetes_dns
+  containers: docker
+  orchestration: kubernetes
+  tracing: jaeger
+  metrics: prometheus
+  cicd: github_actions
+
+# Alternative technology stacks
+alternatives:
+  language:
+    - id: typescript
+      name: "TypeScript/Node.js"
+      description: "Fast development, good ecosystem"
+    - id: go
+      name: "Go"
+      description: "High performance, low resource usage"
+    - id: java
+      name: "Java (Spring Boot)"
+      description: "Enterprise-grade, Spring Cloud ecosystem"
+    - id: python
+      name: "Python (FastAPI)"
+      description: "Rapid development, async support"
+
+  framework:
+    - id: nestjs
+      name: "NestJS"
+      description: "Modular architecture, built-in microservices"
+    - id: express
+      name: "Express.js"
+      description: "Lightweight, flexible"
+    - id: spring_boot
+      name: "Spring Boot"
+      description: "Full-featured enterprise framework"
+    - id: fastapi
+      name: "FastAPI"
+      description: "Modern Python with automatic docs"
+
+  gateway:
+    - id: kong
+      name: "Kong"
+      description: "Powerful API gateway with plugins"
+    - id: traefik
+      name: "Traefik"
+      description: "Cloud-native, auto-discovery"
+    - id: nginx
+      name: "Nginx"
+      description: "High performance reverse proxy"
+    - id: aws_api_gateway
+      name: "AWS API Gateway"
+      description: "Managed, serverless option"
+
+  orchestration:
+    - id: kubernetes
+      name: "Kubernetes"
+      description: "Industry standard container orchestration"
+    - id: docker_swarm
+      name: "Docker Swarm"
+      description: "Simpler orchestration"
+    - id: ecs
+      name: "AWS ECS"
+      description: "Managed container service"
+    - id: nomad
+      name: "HashiCorp Nomad"
+      description: "Flexible workload orchestration"
+
+# Phases of development
+phases:
+  - id: discovery
+    name: "Domain Discovery"
+    description: "Identify bounded contexts, service boundaries, and domain decomposition"
+    order: 1
+    checkpoint: true
+    checkpoint_message: |
+      Domain discovery complete. Review:
+      - Bounded contexts and service boundaries
+      - Service dependency map
+      - Data ownership strategy
+      - Communication patterns
+
+      Approve to proceed with architecture design.
+
+    steps:
+      - id: domain_analysis
+        name: "Domain Analysis"
+        agent: researcher
+        description: "Analyze business domain using DDD principles"
+
+      - id: bounded_contexts
+        name: "Bounded Contexts"
+        agent: architect
+        description: "Identify bounded contexts and service boundaries"
+
+      - id: service_mapping
+        name: "Service Mapping"
+        agent: architect
+        description: "Map service dependencies and interactions"
+
+      - id: data_strategy
+        name: "Data Strategy"
+        agent: architect
+        description: "Define data ownership per service"
+
+    outputs:
+      - ".omgkit/generated/domain-model.md"
+      - ".omgkit/generated/service-map.md"
+      - ".omgkit/generated/data-ownership.md"
+
+  - id: architecture
+    name: "Architecture Design"
+    description: "Design system architecture, contracts, and communication patterns"
+    order: 2
+    checkpoint: true
+    checkpoint_message: |
+      Architecture design complete. Review:
+      - Service contracts (OpenAPI specs)
+      - API Gateway routing
+      - Communication patterns
+      - Deployment strategy
+
+      Approve to begin foundation setup.
+
+    steps:
+      - id: service_contracts
+        name: "Service Contracts"
+        agent: api-designer
+        description: "Define OpenAPI specs for each service"
+
+      - id: gateway_design
+        name: "Gateway Design"
+        agent: architect
+        description: "Design API Gateway routing and policies"
+
+      - id: communication_patterns
+        name: "Communication Patterns"
+        agent: architect
+        description: "Define sync/async communication"
+
+      - id: deployment_strategy
+        name: "Deployment Strategy"
+        agent: architect
+        description: "Design deployment and scaling approach"
+
+    outputs:
+      - ".omgkit/generated/architecture.md"
+      - ".omgkit/generated/api-contracts/"
+      - ".omgkit/generated/deployment-strategy.md"
+
+  - id: foundation
+    name: "Infrastructure Foundation"
+    description: "Set up containerization, orchestration, and shared infrastructure"
+    order: 3
+    checkpoint: false
+
+    steps:
+      - id: monorepo_setup
+        name: "Monorepo Setup"
+        agent: fullstack-developer
+        description: "Initialize monorepo structure"
+
+      - id: docker_config
+        name: "Docker Configuration"
+        agent: fullstack-developer
+        description: "Create Dockerfiles for services"
+
+      - id: kubernetes_manifests
+        name: "Kubernetes Manifests"
+        agent: fullstack-developer
+        description: "Create K8s deployments, services"
+
+      - id: gateway_setup
+        name: "API Gateway Setup"
+        agent: fullstack-developer
+        description: "Configure API gateway"
+
+      - id: shared_libraries
+        name: "Shared Libraries"
+        agent: fullstack-developer
+        description: "Create shared code packages"
+
+    outputs:
+      - "docker-compose.yml"
+      - "k8s/"
+      - "packages/shared/"
+      - "services/"
+
+  - id: core_services
+    name: "Core Services"
+    description: "Implement individual microservices"
+    order: 4
+    checkpoint: true
+    checkpoint_message: |
+      Core services implemented. Review:
+      - Service implementations
+      - API endpoints
+      - Health checks
+      - Database schemas
+
+      Approve to proceed with integration.
+
+    steps:
+      - id: service_scaffolding
+        name: "Service Scaffolding"
+        agent: fullstack-developer
+        description: "Create service boilerplates"
+
+      - id: service_implementation
+        name: "Service Implementation"
+        agent: fullstack-developer
+        description: "Implement business logic per service"
+
+      - id: database_per_service
+        name: "Database Per Service"
+        agent: database-admin
+        description: "Set up databases for each service"
+
+      - id: health_checks
+        name: "Health Checks"
+        agent: fullstack-developer
+        description: "Implement health and readiness probes"
+
+      - id: service_tests
+        name: "Service Tests"
+        agent: tester
+        description: "Unit tests for each service"
+
+    outputs:
+      - "services/*/src/"
+      - "services/*/tests/"
+
+  - id: integration
+    name: "Service Integration"
+    description: "Inter-service communication, tracing, and resilience"
+    order: 5
+    checkpoint: true
+    checkpoint_message: |
+      Integration complete. Review:
+      - Inter-service communication
+      - Distributed tracing
+      - Circuit breakers
+      - Error handling
+
+      Approve to proceed with testing.
+
+    steps:
+      - id: service_communication
+        name: "Service Communication"
+        agent: fullstack-developer
+        description: "Implement inter-service calls"
+
+      - id: distributed_tracing
+        name: "Distributed Tracing"
+        agent: fullstack-developer
+        description: "Set up Jaeger/Zipkin tracing"
+
+      - id: circuit_breakers
+        name: "Circuit Breakers"
+        agent: fullstack-developer
+        description: "Implement resilience patterns"
+
+      - id: retry_policies
+        name: "Retry Policies"
+        agent: fullstack-developer
+        description: "Configure retry and timeout policies"
+
+    outputs:
+      - "services/*/src/clients/"
+      - "packages/resilience/"
+
+  - id: testing
+    name: "Comprehensive Testing"
+    description: "Integration tests, contract tests, and chaos engineering"
+    order: 6
+    checkpoint: false
+
+    steps:
+      - id: integration_tests
+        name: "Integration Tests"
+        agent: tester
+        description: "Cross-service integration tests"
+
+      - id: contract_tests
+        name: "Contract Tests"
+        agent: tester
+        description: "Consumer-driven contract tests (Pact)"
+
+      - id: e2e_tests
+        name: "E2E Tests"
+        agent: tester
+        description: "End-to-end flow tests"
+
+      - id: load_tests
+        name: "Load Tests"
+        agent: tester
+        description: "Performance and load testing"
+
+    outputs:
+      - "tests/integration/"
+      - "tests/contracts/"
+      - "tests/e2e/"
+      - "tests/load/"
+
+  - id: devops
+    name: "DevOps & Deployment"
+    description: "CI/CD pipelines, monitoring, and production deployment"
+    order: 7
+    checkpoint: true
+    checkpoint_message: |
+      DevOps setup complete. Review:
+      - CI/CD pipelines per service
+      - Monitoring dashboards
+      - Alerting rules
+      - Deployment procedures
+
+      This is the final checkpoint.
+
+    steps:
+      - id: cicd_pipelines
+        name: "CI/CD Pipelines"
+        agent: cicd-manager
+        description: "Create pipelines per service"
+
+      - id: monitoring
+        name: "Monitoring Setup"
+        agent: fullstack-developer
+        description: "Prometheus metrics, Grafana dashboards"
+
+      - id: alerting
+        name: "Alerting"
+        agent: fullstack-developer
+        description: "Configure alerts for SLOs"
+
+      - id: deployment_docs
+        name: "Deployment Documentation"
+        agent: docs-manager
+        description: "Document deployment procedures"
+
+    outputs:
+      - ".github/workflows/"
+      - "monitoring/"
+      - "docs/deployment/"
+
+# Autonomy rules for this archetype
+autonomy_rules:
+  - pattern: "**/gateway/**"
+    level: 3
+    reason: "API Gateway is critical infrastructure"
+  - pattern: "**/k8s/**"
+    level: 3
+    reason: "Kubernetes manifests affect deployment"
+  - pattern: "**/kubernetes/**"
+    level: 3
+    reason: "Kubernetes config is critical"
+  - pattern: "**/shared/**"
+    level: 3
+    reason: "Shared libraries affect all services"
+  - pattern: "**/services/*/src/**"
+    level: 2
+    reason: "Service implementation needs review"
+  - pattern: "Dockerfile*"
+    level: 2
+    reason: "Container configuration"
+  - pattern: "**/migrations/**"
+    level: 3
+    reason: "Database migrations critical"
+  - pattern: ".env*"
+    level: 4
+    reason: "Environment secrets"
+
+# Quality gates
+quality_gates:
+  after_feature:
+    - "npm test"
+    - "npm run lint"
+    - "docker build --check"
+  before_checkpoint:
+    - "all service tests pass"
+    - "integration tests pass"
+    - "contract tests pass"
+  before_deploy:
+    - "load tests pass"
+    - "security scan clean"
+    - "all services healthy"
+
+# Microservices-specific discovery questions
+discovery_additions:
+  - category: "Domain"
+    questions:
+      - "What are the main business domains/capabilities?"
+      - "How many services do you envision?"
+      - "What are the bounded contexts?"
+      - "Which services have the most dependencies?"
+      - "Any existing monolith to decompose?"
+
+  - category: "Communication"
+    questions:
+      - "Synchronous (REST/gRPC) or asynchronous (events)?"
+      - "Need for event-driven patterns?"
+      - "API versioning strategy?"
+      - "Rate limiting requirements?"
+
+  - category: "Data"
+    questions:
+      - "Database per service or shared?"
+      - "Data consistency requirements (eventual ok?)?"
+      - "Need for distributed transactions?"
+      - "Data replication strategy?"
+
+  - category: "Infrastructure"
+    questions:
+      - "Cloud provider preference?"
+      - "Existing Kubernetes cluster?"
+      - "Container registry?"
+      - "Service mesh needed (Istio, Linkerd)?"
+
+  - category: "Team"
+    questions:
+      - "Team structure (aligned with services)?"
+      - "Deployment ownership model?"
+      - "On-call rotation?"
+      - "Experience with K8s?"

package/plugin/templates/autonomous/state-schema.yaml

@@ -14,7 +14,7 @@ schema:
     type:
       type: string
       required: true
-      enum: [saas, api, cli, library, fullstack, mobile, ai, desktop, iot, game, simulation]
+      enum: [saas, api, cli, library, fullstack, mobile, ai, desktop, iot, game, simulation, microservices, event_driven]
       description: Type of project being built
 
     archetype:

package/plugin/workflows/ai-engineering/agent-development.md

@@ -12,9 +12,9 @@ agents:
   - tester
   - security-auditor
 skills:
-  - ai-agents
-  - ai-architecture
-  - guardrails-safety
+  - ai-engineering/ai-agents
+  - ai-engineering/ai-architecture
+  - ai-engineering/guardrails-safety
 commands:
   - /planning:research
   - /planning:plan-detailed

package/plugin/workflows/ai-engineering/fine-tuning.md

@@ -10,9 +10,9 @@ agents:
   - fullstack-developer
   - tester
 skills:
-  - finetuning
-  - dataset-engineering
-  - evaluation-methodology
+  - ai-engineering/finetuning
+  - ai-engineering/dataset-engineering
+  - ai-engineering/evaluation-methodology
 commands:
   - /planning:plan
   - /dev:feature

package/plugin/workflows/ai-engineering/model-evaluation.md

@@ -9,9 +9,9 @@ agents:
   - planner
   - tester
 skills:
-  - ai-system-evaluation
-  - evaluation-methodology
-  - dataset-engineering
+  - ai-engineering/ai-system-evaluation
+  - ai-engineering/evaluation-methodology
+  - ai-engineering/dataset-engineering
 commands:
   - /planning:plan
   - /dev:test

package/plugin/workflows/ai-engineering/prompt-engineering.md

@@ -8,8 +8,8 @@ agents:
   - researcher
   - tester
 skills:
-  - prompt-engineering
-  - evaluation-methodology
+  - ai-engineering/prompt-engineering
+  - ai-engineering/evaluation-methodology
 commands:
   - /planning:research
   - /dev:test

package/plugin/workflows/ai-engineering/rag-development.md

@@ -11,10 +11,10 @@ agents:
   - fullstack-developer
   - tester
 skills:
-  - rag-systems
-  - dataset-engineering
-  - evaluation-methodology
-  - ai-architecture
+  - ai-engineering/rag-systems
+  - ai-engineering/dataset-engineering
+  - ai-engineering/evaluation-methodology
+  - ai-engineering/ai-architecture
 commands:
   - /planning:research
   - /planning:plan

package/plugin/workflows/ai-ml/data-pipeline.md

@@ -0,0 +1,188 @@
+---
+description: Build production data pipelines for ML training and inference
+triggers:
+  - manual
+  - ml:data
+agents:
+  - data-engineer
+  - ml-engineer
+---
+
+# Data Pipeline Workflow
+
+Create robust data pipelines for ML systems.
+
+## Prerequisites
+- [ ] Data sources identified
+- [ ] Data requirements defined
+- [ ] Storage infrastructure available
+
+## Phase 1: Data Source Integration
+
+### Step 1.1: Identify Data Sources
+```yaml
+agent: data-engineer
+action: catalog
+sources:
+  - databases: PostgreSQL, MySQL, MongoDB
+  - data_lakes: S3, GCS, ADLS
+  - streaming: Kafka, Kinesis
+  - apis: REST, GraphQL
+  - files: CSV, Parquet, JSON
+```
+
+### Step 1.2: Create Data Connectors
+```yaml
+agent: data-engineer
+action: implement
+connectors:
+  - Source connectors
+  - Schema inference
+  - Incremental extraction
+  - Change data capture
+tools:
+  - Airbyte
+  - Fivetran
+  - Custom extractors
+```
+
+## Phase 2: Data Transformation
+
+### Step 2.1: Design Transformation DAG
+```yaml
+agent: data-engineer
+action: design
+pipeline_tool:
+  - Airflow
+  - Prefect
+  - Dagster
+  - dbt
+transformations:
+  - Cleaning
+  - Normalization
+  - Feature engineering
+  - Aggregations
+```
+
+### Step 2.2: Implement Transformations
+```yaml
+agent: data-engineer
+action: implement
+best_practices:
+  - Idempotent operations
+  - Incremental processing
+  - Schema validation
+  - Data lineage tracking
+frameworks:
+  - Spark
+  - Pandas
+  - dbt
+  - Polars
+```
+
+## Phase 3: Data Quality
+
+### Step 3.1: Define Quality Rules
+```yaml
+agent: data-engineer
+action: define
+quality_dimensions:
+  - Completeness: No null required fields
+  - Accuracy: Values in valid ranges
+  - Consistency: Cross-field validation
+  - Timeliness: Data freshness
+  - Uniqueness: No duplicates
+```
+
+### Step 3.2: Implement Quality Checks
+```yaml
+agent: data-engineer
+action: implement
+tools:
+  - Great Expectations
+  - dbt tests
+  - Soda
+  - Custom validators
+checks:
+  - Schema validation
+  - Statistical checks
+  - Anomaly detection
+  - Referential integrity
+```
+
+## Phase 4: Feature Store Integration
+
+### Step 4.1: Define Features
+```yaml
+agent: ml-engineer
+action: define
+feature_types:
+  - Batch features (offline)
+  - Streaming features (online)
+  - On-demand features
+metadata:
+  - Feature name
+  - Data type
+  - Description
+  - Owner
+  - Freshness SLA
+```
+
+### Step 4.2: Implement Feature Pipeline
+```yaml
+agent: data-engineer
+action: implement
+feature_store:
+  - Feast
+  - Tecton
+  - Vertex AI Feature Store
+capabilities:
+  - Batch ingestion
+  - Stream ingestion
+  - Point-in-time correctness
+  - Online serving
+```
+
+## Phase 5: Pipeline Orchestration
+
+### Step 5.1: Configure Scheduling
+```yaml
+agent: data-engineer
+action: configure
+scheduling:
+  batch_pipeline:
+    schedule: "0 2 * * *"  # Daily at 2 AM
+    depends_on: source_data_available
+  streaming_pipeline:
+    trigger: continuous
+    checkpoint: s3://checkpoints/
+```
+
+### Step 5.2: Monitoring and Alerting
+```yaml
+agent: data-engineer
+action: configure
+monitoring:
+  - Pipeline success/failure
+  - Data quality metrics
+  - Processing latency
+  - Data freshness
+alerts:
+  - Pipeline failure
+  - Quality threshold breach
+  - SLA violation
+```
+
+## Outputs
+- [ ] Data connectors
+- [ ] Transformation DAG
+- [ ] Quality checks
+- [ ] Feature pipelines
+- [ ] Monitoring dashboards
+
+## Quality Gates
+- All quality checks pass
+- Pipeline runs successfully
+- Data freshness within SLA
+- No data loss
+- Lineage tracked