omgkit 2.12.0 → 2.13.0

package/README.md

@@ -7,7 +7,7 @@
 [![License](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
 
 > **AI Team System for Claude Code**
-> 23 Agents • 58 Commands • 29 Workflows • 88 Skills • 10 Modes • 12 Archetypes
+> 23 Agents • 58 Commands • 29 Workflows • 88 Skills • 10 Modes • 14 Archetypes
 > *"Think Omega. Build Omega. Be Omega."*
 
 OMGKIT transforms Claude Code into an autonomous AI development team with sprint management, specialized agents, and Omega-level thinking for 10x-1000x productivity improvements.
@@ -21,7 +21,7 @@ OMGKIT transforms Claude Code into an autonomous AI development team with sprint
 | **Workflows** | 29 | Complete development processes |
 | **Skills** | 88 | Domain expertise modules |
 | **Modes** | 10 | Behavioral configurations |
-| **Archetypes** | 12 | Project templates for autonomous dev |
+| **Archetypes** | 14 | Project templates for autonomous dev |
 | **Sprint Management** | ✅ | Vision, backlog, team autonomy |
 | **Omega Thinking** | ✅ | 7 modes for 10x-1000x solutions |
 | **Autonomous Dev** | ✅ | Build complete apps from idea to deploy |
@@ -176,7 +176,7 @@ After installation, use these commands in Claude Code:
 /auto:resume        # Resume from saved state
 ```
 
-## 🤖 Autonomous Development (12 Archetypes)
+## 🤖 Autonomous Development (14 Archetypes)
 
 Build complete applications autonomously from idea to deployment.
 
@@ -194,6 +194,8 @@ Build complete applications autonomously from idea to deployment.
 | **IoT App** | Device management, real-time data |
 | **Game** | Unity/Godot game development |
 | **Simulation** | Scientific/engineering simulations |
+| **Microservices** | Distributed services with K8s, API gateway |
+| **Event-Driven** | Async systems with Kafka, CQRS, sagas |
 
 ### Artifacts System
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omgkit",
-  "version": "2.12.0",
+  "version": "2.13.0",
   "description": "Omega-Level Development Kit - AI Team System for Claude Code. 23 agents, 58 commands, 88 skills, sprint management.",
   "keywords": [
     "claude-code",

package/plugin/templates/autonomous/archetypes/event-driven-app.yaml

@@ -0,0 +1,460 @@
+name: "Event-Driven Application"
+id: event-driven-app
+description: "Asynchronous system with message brokers, event sourcing, CQRS, and saga patterns"
+estimated_duration: "6-14 weeks"
+icon: "bolt"
+
+# Default technology recommendations
+defaults:
+  broker: kafka
+  language: typescript
+  framework: nestjs
+  event_store: kafka
+  read_database: postgresql
+  schema_registry: confluent
+  streaming: kafka_streams
+
+# Alternative technology stacks
+alternatives:
+  broker:
+    - id: kafka
+      name: "Apache Kafka"
+      description: "High-throughput distributed streaming"
+    - id: rabbitmq
+      name: "RabbitMQ"
+      description: "Feature-rich message broker"
+    - id: aws_sqs_sns
+      name: "AWS SQS/SNS"
+      description: "Managed messaging service"
+    - id: redis_streams
+      name: "Redis Streams"
+      description: "Lightweight, low-latency"
+    - id: azure_service_bus
+      name: "Azure Service Bus"
+      description: "Enterprise messaging"
+
+  language:
+    - id: typescript
+      name: "TypeScript/Node.js"
+      description: "Async-first, good Kafka libraries"
+    - id: java
+      name: "Java (Spring Cloud Stream)"
+      description: "Mature ecosystem, Kafka Streams"
+    - id: go
+      name: "Go"
+      description: "High performance consumers"
+    - id: python
+      name: "Python"
+      description: "Data processing, Faust library"
+
+  framework:
+    - id: nestjs
+      name: "NestJS"
+      description: "Built-in microservices transport"
+    - id: spring_cloud_stream
+      name: "Spring Cloud Stream"
+      description: "Declarative event binding"
+    - id: fastapi
+      name: "FastAPI"
+      description: "Async Python framework"
+    - id: axon
+      name: "Axon Framework"
+      description: "Event sourcing & CQRS framework"
+
+  event_store:
+    - id: kafka
+      name: "Kafka (as event store)"
+      description: "Log-based event storage"
+    - id: eventstoredb
+      name: "EventStoreDB"
+      description: "Purpose-built event store"
+    - id: postgres_eventide
+      name: "PostgreSQL + Eventide"
+      description: "SQL-based event store"
+    - id: dynamodb
+      name: "DynamoDB Streams"
+      description: "Serverless event storage"
+
+  streaming:
+    - id: kafka_streams
+      name: "Kafka Streams"
+      description: "Native Kafka stream processing"
+    - id: ksqldb
+      name: "ksqlDB"
+      description: "SQL for stream processing"
+    - id: flink
+      name: "Apache Flink"
+      description: "Stateful stream processing"
+    - id: spark_streaming
+      name: "Spark Streaming"
+      description: "Big data stream processing"
+
+# Phases of development
+phases:
+  - id: discovery
+    name: "Event Discovery"
+    description: "Event storming, domain events identification, and aggregate design"
+    order: 1
+    checkpoint: true
+    checkpoint_message: |
+      Event discovery complete. Review:
+      - Domain events catalog
+      - Aggregate boundaries
+      - Command/event flows
+      - Event ownership
+
+      Approve to proceed with architecture.
+
+    steps:
+      - id: event_storming
+        name: "Event Storming"
+        agent: researcher
+        description: "Conduct event storming workshop"
+
+      - id: domain_events
+        name: "Domain Events"
+        agent: architect
+        description: "Catalog all domain events"
+
+      - id: aggregates
+        name: "Aggregate Design"
+        agent: architect
+        description: "Define aggregate boundaries"
+
+      - id: command_flows
+        name: "Command Flows"
+        agent: architect
+        description: "Map commands to events"
+
+    outputs:
+      - ".omgkit/generated/event-catalog.md"
+      - ".omgkit/generated/aggregates.md"
+      - ".omgkit/generated/command-flows.md"
+
+  - id: architecture
+    name: "Event Architecture"
+    description: "Topic design, schemas, CQRS strategy, and saga patterns"
+    order: 2
+    checkpoint: true
+    checkpoint_message: |
+      Architecture design complete. Review:
+      - Topic/queue design
+      - Event schemas (Avro/JSON)
+      - CQRS implementation plan
+      - Saga patterns for transactions
+
+      Approve to begin foundation.
+
+    steps:
+      - id: topic_design
+        name: "Topic Design"
+        agent: architect
+        description: "Design topics, partitions, retention"
+
+      - id: schema_design
+        name: "Schema Design"
+        agent: architect
+        description: "Design event schemas with versioning"
+
+      - id: cqrs_design
+        name: "CQRS Design"
+        agent: architect
+        description: "Plan command/query separation"
+
+      - id: saga_design
+        name: "Saga Design"
+        agent: architect
+        description: "Design distributed transaction patterns"
+
+    outputs:
+      - ".omgkit/generated/topic-design.md"
+      - ".omgkit/generated/event-schemas/"
+      - ".omgkit/generated/cqrs-design.md"
+      - ".omgkit/generated/saga-patterns.md"
+
+  - id: foundation
+    name: "Infrastructure Foundation"
+    description: "Message broker, schema registry, and base configuration"
+    order: 3
+    checkpoint: false
+
+    steps:
+      - id: broker_setup
+        name: "Broker Setup"
+        agent: fullstack-developer
+        description: "Set up Kafka/RabbitMQ"
+
+      - id: schema_registry
+        name: "Schema Registry"
+        agent: fullstack-developer
+        description: "Configure schema registry"
+
+      - id: topic_creation
+        name: "Topic Creation"
+        agent: fullstack-developer
+        description: "Create topics with configs"
+
+      - id: dlq_setup
+        name: "Dead Letter Queue"
+        agent: fullstack-developer
+        description: "Set up DLQ for failed messages"
+
+      - id: shared_libs
+        name: "Shared Libraries"
+        agent: fullstack-developer
+        description: "Event types, serialization"
+
+    outputs:
+      - "docker-compose.yml"
+      - "schemas/"
+      - "packages/events/"
+
+  - id: producers
+    name: "Event Producers"
+    description: "Implement command handlers and event publishing"
+    order: 4
+    checkpoint: true
+    checkpoint_message: |
+      Producers implemented. Review:
+      - Command handlers
+      - Event publishing
+      - Transactional outbox
+      - Idempotency keys
+
+      Approve to proceed with consumers.
+
+    steps:
+      - id: command_handlers
+        name: "Command Handlers"
+        agent: fullstack-developer
+        description: "Implement command processing"
+
+      - id: event_publishing
+        name: "Event Publishing"
+        agent: fullstack-developer
+        description: "Implement event producers"
+
+      - id: outbox_pattern
+        name: "Transactional Outbox"
+        agent: fullstack-developer
+        description: "Implement outbox for reliability"
+
+      - id: idempotency
+        name: "Idempotency"
+        agent: fullstack-developer
+        description: "Add idempotency keys"
+
+      - id: producer_tests
+        name: "Producer Tests"
+        agent: tester
+        description: "Test event publishing"
+
+    outputs:
+      - "src/commands/"
+      - "src/producers/"
+      - "tests/producers/"
+
+  - id: consumers
+    name: "Event Consumers"
+    description: "Event handlers, projections, and saga orchestrators"
+    order: 5
+    checkpoint: true
+    checkpoint_message: |
+      Consumers implemented. Review:
+      - Event handlers
+      - Projections (read models)
+      - Saga orchestration
+      - Error handling
+
+      Approve to proceed with CQRS.
+
+    steps:
+      - id: event_handlers
+        name: "Event Handlers"
+        agent: fullstack-developer
+        description: "Implement event consumers"
+
+      - id: projections
+        name: "Projections"
+        agent: fullstack-developer
+        description: "Build read model projections"
+
+      - id: saga_orchestrators
+        name: "Saga Orchestrators"
+        agent: fullstack-developer
+        description: "Implement saga patterns"
+
+      - id: error_handling
+        name: "Error Handling"
+        agent: fullstack-developer
+        description: "Retries, DLQ, compensation"
+
+      - id: consumer_tests
+        name: "Consumer Tests"
+        agent: tester
+        description: "Test event consumption"
+
+    outputs:
+      - "src/consumers/"
+      - "src/projections/"
+      - "src/sagas/"
+      - "tests/consumers/"
+
+  - id: cqrs
+    name: "CQRS Implementation"
+    description: "Query side APIs, read models, and eventual consistency"
+    order: 6
+    checkpoint: false
+
+    steps:
+      - id: read_models
+        name: "Read Models"
+        agent: fullstack-developer
+        description: "Design optimized read models"
+
+      - id: query_apis
+        name: "Query APIs"
+        agent: fullstack-developer
+        description: "Implement query endpoints"
+
+      - id: consistency_handling
+        name: "Consistency Handling"
+        agent: fullstack-developer
+        description: "Handle eventual consistency UX"
+
+      - id: cache_strategy
+        name: "Cache Strategy"
+        agent: fullstack-developer
+        description: "Cache read models if needed"
+
+    outputs:
+      - "src/queries/"
+      - "src/read-models/"
+
+  - id: monitoring
+    name: "Testing & Monitoring"
+    description: "Event flow testing, consumer lag monitoring, and observability"
+    order: 7
+    checkpoint: true
+    checkpoint_message: |
+      Monitoring complete. Review:
+      - Event flow tests
+      - Consumer lag alerts
+      - Schema evolution tests
+      - Observability dashboards
+
+      This is the final checkpoint.
+
+    steps:
+      - id: flow_tests
+        name: "Event Flow Tests"
+        agent: tester
+        description: "Test complete event flows"
+
+      - id: lag_monitoring
+        name: "Lag Monitoring"
+        agent: fullstack-developer
+        description: "Monitor consumer lag"
+
+      - id: schema_tests
+        name: "Schema Evolution Tests"
+        agent: tester
+        description: "Test schema compatibility"
+
+      - id: observability
+        name: "Observability"
+        agent: fullstack-developer
+        description: "Dashboards for events"
+
+      - id: replay_testing
+        name: "Replay Testing"
+        agent: tester
+        description: "Test event replay scenarios"
+
+    outputs:
+      - "tests/flows/"
+      - "monitoring/"
+      - "docs/"
+
+# Autonomy rules for this archetype
+autonomy_rules:
+  - pattern: "**/events/**"
+    level: 3
+    reason: "Event schemas are contracts"
+  - pattern: "**/schemas/**"
+    level: 3
+    reason: "Schema changes affect all consumers"
+  - pattern: "**/sagas/**"
+    level: 3
+    reason: "Saga logic is transaction-critical"
+  - pattern: "**/projections/**"
+    level: 2
+    reason: "Read model changes need review"
+  - pattern: "**/handlers/**"
+    level: 2
+    reason: "Event handling logic"
+  - pattern: "**/consumers/**"
+    level: 2
+    reason: "Consumer configuration"
+  - pattern: "kafka*.yaml"
+    level: 3
+    reason: "Broker configuration"
+  - pattern: "**/dlq/**"
+    level: 3
+    reason: "Dead letter queue handling"
+  - pattern: ".env*"
+    level: 4
+    reason: "Environment secrets"
+
+# Quality gates
+quality_gates:
+  after_feature:
+    - "npm test"
+    - "npm run lint"
+    - "schema compatibility check"
+  before_checkpoint:
+    - "all unit tests pass"
+    - "event flow tests pass"
+    - "no consumer lag issues"
+  before_deploy:
+    - "schema registry healthy"
+    - "replay tests pass"
+    - "monitoring configured"
+
+# Event-driven specific discovery questions
+discovery_additions:
+  - category: "Events"
+    questions:
+      - "What are the main domain events?"
+      - "Event sourcing needed or just messaging?"
+      - "Event replay requirements?"
+      - "Event retention period?"
+      - "Schema evolution strategy?"
+
+  - category: "Consistency"
+    questions:
+      - "Eventual consistency acceptable?"
+      - "Need distributed transactions (sagas)?"
+      - "Ordering requirements (strict or relaxed)?"
+      - "Exactly-once or at-least-once semantics?"
+
+  - category: "CQRS"
+    questions:
+      - "Separate read and write models?"
+      - "Query performance requirements?"
+      - "Real-time projections needed?"
+      - "Historical query needs?"
+
+  - category: "Infrastructure"
+    questions:
+      - "Message broker preference?"
+      - "Expected message throughput?"
+      - "Partition strategy?"
+      - "Multi-region requirements?"
+
+  - category: "Integration"
+    questions:
+      - "External systems to integrate?"
+      - "Legacy system events?"
+      - "Webhook requirements?"
+      - "CDC (Change Data Capture) needs?"

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: