omgkit 2.13.0 → 2.15.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +93 -10
- package/package.json +2 -2
- package/plugin/agents/api-designer.md +5 -0
- package/plugin/agents/architect.md +8 -0
- package/plugin/agents/brainstormer.md +4 -0
- package/plugin/agents/cicd-manager.md +6 -0
- package/plugin/agents/code-reviewer.md +6 -0
- package/plugin/agents/copywriter.md +2 -0
- package/plugin/agents/data-engineer.md +255 -0
- package/plugin/agents/database-admin.md +10 -0
- package/plugin/agents/debugger.md +10 -0
- package/plugin/agents/devsecops.md +314 -0
- package/plugin/agents/docs-manager.md +4 -0
- package/plugin/agents/domain-decomposer.md +181 -0
- package/plugin/agents/embedded-systems.md +397 -0
- package/plugin/agents/fullstack-developer.md +12 -0
- package/plugin/agents/game-systems-designer.md +375 -0
- package/plugin/agents/git-manager.md +10 -0
- package/plugin/agents/journal-writer.md +2 -0
- package/plugin/agents/ml-engineer.md +284 -0
- package/plugin/agents/observability-engineer.md +353 -0
- package/plugin/agents/oracle.md +9 -0
- package/plugin/agents/performance-engineer.md +290 -0
- package/plugin/agents/pipeline-architect.md +6 -0
- package/plugin/agents/planner.md +12 -0
- package/plugin/agents/platform-engineer.md +325 -0
- package/plugin/agents/project-manager.md +3 -0
- package/plugin/agents/researcher.md +5 -0
- package/plugin/agents/scientific-computing.md +426 -0
- package/plugin/agents/scout.md +3 -0
- package/plugin/agents/security-auditor.md +7 -0
- package/plugin/agents/sprint-master.md +17 -0
- package/plugin/agents/tester.md +10 -0
- package/plugin/agents/ui-ux-designer.md +12 -0
- package/plugin/agents/vulnerability-scanner.md +6 -0
- package/plugin/commands/data/pipeline.md +47 -0
- package/plugin/commands/data/quality.md +49 -0
- package/plugin/commands/domain/analyze.md +34 -0
- package/plugin/commands/domain/map.md +41 -0
- package/plugin/commands/game/balance.md +56 -0
- package/plugin/commands/game/optimize.md +62 -0
- package/plugin/commands/iot/provision.md +58 -0
- package/plugin/commands/ml/evaluate.md +47 -0
- package/plugin/commands/ml/train.md +48 -0
- package/plugin/commands/perf/benchmark.md +54 -0
- package/plugin/commands/perf/profile.md +49 -0
- package/plugin/commands/platform/blueprint.md +56 -0
- package/plugin/commands/security/audit.md +54 -0
- package/plugin/commands/security/scan.md +55 -0
- package/plugin/commands/sre/dashboard.md +53 -0
- package/plugin/registry.yaml +711 -0
- package/plugin/skills/ai-ml/experiment-tracking/SKILL.md +338 -0
- package/plugin/skills/ai-ml/feature-stores/SKILL.md +340 -0
- package/plugin/skills/ai-ml/llm-ops/SKILL.md +454 -0
- package/plugin/skills/ai-ml/ml-pipelines/SKILL.md +390 -0
- package/plugin/skills/ai-ml/model-monitoring/SKILL.md +398 -0
- package/plugin/skills/ai-ml/model-serving/SKILL.md +386 -0
- package/plugin/skills/event-driven/cqrs-patterns/SKILL.md +348 -0
- package/plugin/skills/event-driven/event-sourcing/SKILL.md +334 -0
- package/plugin/skills/event-driven/kafka-deep/SKILL.md +252 -0
- package/plugin/skills/event-driven/saga-orchestration/SKILL.md +335 -0
- package/plugin/skills/event-driven/schema-registry/SKILL.md +328 -0
- package/plugin/skills/event-driven/stream-processing/SKILL.md +313 -0
- package/plugin/skills/game/game-audio/SKILL.md +446 -0
- package/plugin/skills/game/game-networking/SKILL.md +490 -0
- package/plugin/skills/game/godot-patterns/SKILL.md +413 -0
- package/plugin/skills/game/shader-programming/SKILL.md +492 -0
- package/plugin/skills/game/unity-patterns/SKILL.md +488 -0
- package/plugin/skills/iot/device-provisioning/SKILL.md +405 -0
- package/plugin/skills/iot/edge-computing/SKILL.md +369 -0
- package/plugin/skills/iot/industrial-protocols/SKILL.md +438 -0
- package/plugin/skills/iot/mqtt-deep/SKILL.md +418 -0
- package/plugin/skills/iot/ota-updates/SKILL.md +426 -0
- package/plugin/skills/microservices/api-gateway-patterns/SKILL.md +201 -0
- package/plugin/skills/microservices/circuit-breaker-patterns/SKILL.md +246 -0
- package/plugin/skills/microservices/contract-testing/SKILL.md +284 -0
- package/plugin/skills/microservices/distributed-tracing/SKILL.md +246 -0
- package/plugin/skills/microservices/service-discovery/SKILL.md +304 -0
- package/plugin/skills/microservices/service-mesh/SKILL.md +181 -0
- package/plugin/skills/mobile-advanced/mobile-ci-cd/SKILL.md +407 -0
- package/plugin/skills/mobile-advanced/mobile-security/SKILL.md +403 -0
- package/plugin/skills/mobile-advanced/offline-first/SKILL.md +473 -0
- package/plugin/skills/mobile-advanced/push-notifications/SKILL.md +494 -0
- package/plugin/skills/mobile-advanced/react-native-deep/SKILL.md +374 -0
- package/plugin/skills/simulation/numerical-methods/SKILL.md +434 -0
- package/plugin/skills/simulation/parallel-computing/SKILL.md +382 -0
- package/plugin/skills/simulation/physics-engines/SKILL.md +377 -0
- package/plugin/skills/simulation/validation-verification/SKILL.md +479 -0
- package/plugin/skills/simulation/visualization-scientific/SKILL.md +365 -0
- package/plugin/workflows/ai-engineering/agent-development.md +3 -3
- package/plugin/workflows/ai-engineering/fine-tuning.md +3 -3
- package/plugin/workflows/ai-engineering/model-evaluation.md +3 -3
- package/plugin/workflows/ai-engineering/prompt-engineering.md +2 -2
- package/plugin/workflows/ai-engineering/rag-development.md +4 -4
- package/plugin/workflows/ai-ml/data-pipeline.md +188 -0
- package/plugin/workflows/ai-ml/experiment-cycle.md +203 -0
- package/plugin/workflows/ai-ml/feature-engineering.md +208 -0
- package/plugin/workflows/ai-ml/model-deployment.md +199 -0
- package/plugin/workflows/ai-ml/monitoring-setup.md +227 -0
- package/plugin/workflows/api/api-design.md +1 -1
- package/plugin/workflows/api/api-testing.md +2 -2
- package/plugin/workflows/content/technical-docs.md +1 -1
- package/plugin/workflows/database/migration.md +1 -1
- package/plugin/workflows/database/optimization.md +1 -1
- package/plugin/workflows/database/schema-design.md +3 -3
- package/plugin/workflows/development/bug-fix.md +3 -3
- package/plugin/workflows/development/code-review.md +2 -1
- package/plugin/workflows/development/feature.md +3 -3
- package/plugin/workflows/development/refactor.md +2 -2
- package/plugin/workflows/event-driven/consumer-groups.md +190 -0
- package/plugin/workflows/event-driven/event-storming.md +172 -0
- package/plugin/workflows/event-driven/replay-testing.md +186 -0
- package/plugin/workflows/event-driven/saga-implementation.md +206 -0
- package/plugin/workflows/event-driven/schema-evolution.md +173 -0
- package/plugin/workflows/fullstack/authentication.md +4 -4
- package/plugin/workflows/fullstack/full-feature.md +4 -4
- package/plugin/workflows/game-dev/content-pipeline.md +218 -0
- package/plugin/workflows/game-dev/platform-submission.md +263 -0
- package/plugin/workflows/game-dev/playtesting.md +237 -0
- package/plugin/workflows/game-dev/prototype-to-production.md +205 -0
- package/plugin/workflows/microservices/contract-first.md +151 -0
- package/plugin/workflows/microservices/distributed-tracing.md +166 -0
- package/plugin/workflows/microservices/domain-decomposition.md +123 -0
- package/plugin/workflows/microservices/integration-testing.md +149 -0
- package/plugin/workflows/microservices/service-mesh-setup.md +153 -0
- package/plugin/workflows/microservices/service-scaffolding.md +151 -0
- package/plugin/workflows/omega/1000x-innovation.md +2 -2
- package/plugin/workflows/omega/100x-architecture.md +2 -2
- package/plugin/workflows/omega/10x-improvement.md +2 -2
- package/plugin/workflows/quality/performance-optimization.md +2 -2
- package/plugin/workflows/research/best-practices.md +1 -1
- package/plugin/workflows/research/technology-research.md +1 -1
- package/plugin/workflows/security/penetration-testing.md +3 -3
- package/plugin/workflows/security/security-audit.md +3 -3
- package/plugin/workflows/sprint/sprint-execution.md +2 -2
- package/plugin/workflows/sprint/sprint-retrospective.md +1 -1
- package/plugin/workflows/sprint/sprint-setup.md +1 -1
|
@@ -0,0 +1,149 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Comprehensive integration testing for microservices architecture
|
|
3
|
+
triggers:
|
|
4
|
+
- manual
|
|
5
|
+
- ci:integration
|
|
6
|
+
agents:
|
|
7
|
+
- tester
|
|
8
|
+
- fullstack-developer
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
# Integration Testing Workflow
|
|
12
|
+
|
|
13
|
+
Test service interactions and system behavior.
|
|
14
|
+
|
|
15
|
+
## Prerequisites
|
|
16
|
+
- [ ] Services deployed to test environment
|
|
17
|
+
- [ ] Test data prepared
|
|
18
|
+
- [ ] External dependencies mockable
|
|
19
|
+
|
|
20
|
+
## Phase 1: Test Environment Setup
|
|
21
|
+
|
|
22
|
+
### Step 1.1: Provision Test Infrastructure
|
|
23
|
+
```yaml
|
|
24
|
+
agent: fullstack-developer
|
|
25
|
+
action: setup
|
|
26
|
+
using: docker_compose
|
|
27
|
+
services:
|
|
28
|
+
- service_under_test
|
|
29
|
+
- dependencies
|
|
30
|
+
- databases
|
|
31
|
+
- message_brokers
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
### Step 1.2: Seed Test Data
|
|
35
|
+
```yaml
|
|
36
|
+
agent: tester
|
|
37
|
+
action: seed_data
|
|
38
|
+
strategies:
|
|
39
|
+
- fixtures
|
|
40
|
+
- factories
|
|
41
|
+
- snapshots
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
## Phase 2: Service Integration Tests
|
|
45
|
+
|
|
46
|
+
### Step 2.1: API Integration Tests
|
|
47
|
+
```yaml
|
|
48
|
+
agent: tester
|
|
49
|
+
action: test
|
|
50
|
+
type: api_integration
|
|
51
|
+
coverage:
|
|
52
|
+
- happy_paths
|
|
53
|
+
- error_handling
|
|
54
|
+
- authentication
|
|
55
|
+
- authorization
|
|
56
|
+
- pagination
|
|
57
|
+
- rate_limiting
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
### Step 2.2: Database Integration Tests
|
|
61
|
+
```yaml
|
|
62
|
+
agent: tester
|
|
63
|
+
action: test
|
|
64
|
+
type: database_integration
|
|
65
|
+
coverage:
|
|
66
|
+
- CRUD_operations
|
|
67
|
+
- transactions
|
|
68
|
+
- migrations
|
|
69
|
+
- constraints
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
## Phase 3: Service-to-Service Testing
|
|
73
|
+
|
|
74
|
+
### Step 3.1: Synchronous Communication
|
|
75
|
+
```yaml
|
|
76
|
+
agent: tester
|
|
77
|
+
action: test
|
|
78
|
+
type: service_communication
|
|
79
|
+
patterns:
|
|
80
|
+
- REST_calls
|
|
81
|
+
- gRPC_calls
|
|
82
|
+
- circuit_breaker_behavior
|
|
83
|
+
- retry_logic
|
|
84
|
+
- timeout_handling
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
### Step 3.2: Asynchronous Communication
|
|
88
|
+
```yaml
|
|
89
|
+
agent: tester
|
|
90
|
+
action: test
|
|
91
|
+
type: async_communication
|
|
92
|
+
patterns:
|
|
93
|
+
- message_publishing
|
|
94
|
+
- message_consumption
|
|
95
|
+
- dead_letter_handling
|
|
96
|
+
- ordering_guarantees
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
## Phase 4: End-to-End Scenarios
|
|
100
|
+
|
|
101
|
+
### Step 4.1: Business Flow Tests
|
|
102
|
+
```yaml
|
|
103
|
+
agent: tester
|
|
104
|
+
action: test
|
|
105
|
+
type: e2e_flows
|
|
106
|
+
scenarios:
|
|
107
|
+
- user_journey_1
|
|
108
|
+
- user_journey_2
|
|
109
|
+
- failure_recovery
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
### Step 4.2: Chaos Testing
|
|
113
|
+
```yaml
|
|
114
|
+
agent: tester
|
|
115
|
+
action: test
|
|
116
|
+
type: chaos
|
|
117
|
+
scenarios:
|
|
118
|
+
- service_failure
|
|
119
|
+
- network_partition
|
|
120
|
+
- database_unavailable
|
|
121
|
+
- slow_dependencies
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
## Phase 5: Reporting
|
|
125
|
+
|
|
126
|
+
### Step 5.1: Generate Reports
|
|
127
|
+
```yaml
|
|
128
|
+
agent: tester
|
|
129
|
+
action: report
|
|
130
|
+
outputs:
|
|
131
|
+
- test_results
|
|
132
|
+
- coverage_report
|
|
133
|
+
- performance_metrics
|
|
134
|
+
- failure_analysis
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
## Outputs
|
|
138
|
+
- [ ] Test suites (integration, e2e)
|
|
139
|
+
- [ ] Test environment configuration
|
|
140
|
+
- [ ] Test data fixtures
|
|
141
|
+
- [ ] Test reports
|
|
142
|
+
- [ ] Coverage metrics
|
|
143
|
+
|
|
144
|
+
## Quality Gates
|
|
145
|
+
- All integration tests pass
|
|
146
|
+
- Coverage > 70% for critical paths
|
|
147
|
+
- No flaky tests
|
|
148
|
+
- Performance within SLA
|
|
149
|
+
- All failure scenarios handled
|
|
@@ -0,0 +1,153 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Configure service mesh for traffic management and security
|
|
3
|
+
triggers:
|
|
4
|
+
- manual
|
|
5
|
+
- infrastructure:mesh
|
|
6
|
+
agents:
|
|
7
|
+
- platform-engineer
|
|
8
|
+
- site-reliability-engineer
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
# Service Mesh Setup Workflow
|
|
12
|
+
|
|
13
|
+
Deploy and configure service mesh infrastructure.
|
|
14
|
+
|
|
15
|
+
## Prerequisites
|
|
16
|
+
- [ ] Kubernetes cluster available
|
|
17
|
+
- [ ] Services containerized
|
|
18
|
+
- [ ] Network policies defined
|
|
19
|
+
|
|
20
|
+
## Phase 1: Mesh Installation
|
|
21
|
+
|
|
22
|
+
### Step 1.1: Choose and Install Mesh
|
|
23
|
+
```yaml
|
|
24
|
+
agent: platform-engineer
|
|
25
|
+
action: install
|
|
26
|
+
options:
|
|
27
|
+
- Istio
|
|
28
|
+
- Linkerd
|
|
29
|
+
- Consul Connect
|
|
30
|
+
configuration:
|
|
31
|
+
- control_plane
|
|
32
|
+
- data_plane_sidecars
|
|
33
|
+
- ingress_gateway
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
### Step 1.2: Configure Namespace Injection
|
|
37
|
+
```yaml
|
|
38
|
+
agent: platform-engineer
|
|
39
|
+
action: configure
|
|
40
|
+
namespaces:
|
|
41
|
+
- production
|
|
42
|
+
- staging
|
|
43
|
+
settings:
|
|
44
|
+
- auto_sidecar_injection: true
|
|
45
|
+
- mtls_mode: STRICT
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
## Phase 2: Traffic Management
|
|
49
|
+
|
|
50
|
+
### Step 2.1: Configure Virtual Services
|
|
51
|
+
```yaml
|
|
52
|
+
agent: platform-engineer
|
|
53
|
+
action: create
|
|
54
|
+
resources:
|
|
55
|
+
- VirtualService
|
|
56
|
+
- DestinationRule
|
|
57
|
+
features:
|
|
58
|
+
- traffic_routing
|
|
59
|
+
- load_balancing
|
|
60
|
+
- retries
|
|
61
|
+
- timeouts
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
### Step 2.2: Configure Traffic Policies
|
|
65
|
+
```yaml
|
|
66
|
+
agent: platform-engineer
|
|
67
|
+
action: configure
|
|
68
|
+
policies:
|
|
69
|
+
- circuit_breaker:
|
|
70
|
+
consecutive_errors: 5
|
|
71
|
+
interval: 30s
|
|
72
|
+
ejection_time: 30s
|
|
73
|
+
- rate_limit:
|
|
74
|
+
requests_per_second: 100
|
|
75
|
+
- retry:
|
|
76
|
+
attempts: 3
|
|
77
|
+
per_try_timeout: 2s
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
## Phase 3: Security Configuration
|
|
81
|
+
|
|
82
|
+
### Step 3.1: mTLS Setup
|
|
83
|
+
```yaml
|
|
84
|
+
agent: platform-engineer
|
|
85
|
+
action: configure
|
|
86
|
+
security:
|
|
87
|
+
- peer_authentication: STRICT
|
|
88
|
+
- certificate_rotation: automatic
|
|
89
|
+
- trust_domain: cluster.local
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
### Step 3.2: Authorization Policies
|
|
93
|
+
```yaml
|
|
94
|
+
agent: platform-engineer
|
|
95
|
+
action: create
|
|
96
|
+
resources:
|
|
97
|
+
- AuthorizationPolicy
|
|
98
|
+
rules:
|
|
99
|
+
- service_to_service_access
|
|
100
|
+
- namespace_isolation
|
|
101
|
+
- deny_by_default
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
## Phase 4: Observability Integration
|
|
105
|
+
|
|
106
|
+
### Step 4.1: Configure Telemetry
|
|
107
|
+
```yaml
|
|
108
|
+
agent: site-reliability-engineer
|
|
109
|
+
action: configure
|
|
110
|
+
integrations:
|
|
111
|
+
- prometheus_metrics
|
|
112
|
+
- jaeger_tracing
|
|
113
|
+
- kiali_dashboard
|
|
114
|
+
- access_logging
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
### Step 4.2: Create Dashboards
|
|
118
|
+
```yaml
|
|
119
|
+
agent: site-reliability-engineer
|
|
120
|
+
action: create
|
|
121
|
+
dashboards:
|
|
122
|
+
- service_mesh_overview
|
|
123
|
+
- traffic_flow
|
|
124
|
+
- error_rates
|
|
125
|
+
- latency_distribution
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
## Phase 5: Testing and Validation
|
|
129
|
+
|
|
130
|
+
### Step 5.1: Verify Mesh Functionality
|
|
131
|
+
```yaml
|
|
132
|
+
agent: site-reliability-engineer
|
|
133
|
+
action: test
|
|
134
|
+
validations:
|
|
135
|
+
- mtls_working
|
|
136
|
+
- traffic_routing
|
|
137
|
+
- circuit_breaker
|
|
138
|
+
- observability_data
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
## Outputs
|
|
142
|
+
- [ ] Service mesh installation
|
|
143
|
+
- [ ] Traffic management rules
|
|
144
|
+
- [ ] Security policies
|
|
145
|
+
- [ ] Observability dashboards
|
|
146
|
+
- [ ] Runbooks
|
|
147
|
+
|
|
148
|
+
## Quality Gates
|
|
149
|
+
- All sidecars healthy
|
|
150
|
+
- mTLS verified between services
|
|
151
|
+
- Traffic routing working
|
|
152
|
+
- Observability data flowing
|
|
153
|
+
- Rollback plan documented
|
|
@@ -0,0 +1,151 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Scaffold a new microservice with standard structure and infrastructure
|
|
3
|
+
triggers:
|
|
4
|
+
- manual
|
|
5
|
+
- command:scaffold-service
|
|
6
|
+
agents:
|
|
7
|
+
- fullstack-developer
|
|
8
|
+
- cicd-manager
|
|
9
|
+
- database-admin
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
# Service Scaffolding Workflow
|
|
13
|
+
|
|
14
|
+
Create a production-ready microservice from scratch.
|
|
15
|
+
|
|
16
|
+
## Prerequisites
|
|
17
|
+
- [ ] Service name and ownership defined
|
|
18
|
+
- [ ] API contract (OpenAPI/AsyncAPI)
|
|
19
|
+
- [ ] Database requirements
|
|
20
|
+
- [ ] Target runtime environment
|
|
21
|
+
|
|
22
|
+
## Phase 1: Project Structure
|
|
23
|
+
|
|
24
|
+
### Step 1.1: Initialize Repository
|
|
25
|
+
```yaml
|
|
26
|
+
agent: fullstack-developer
|
|
27
|
+
action: scaffold
|
|
28
|
+
template: microservice
|
|
29
|
+
structure:
|
|
30
|
+
- src/
|
|
31
|
+
- domain/ # Business logic
|
|
32
|
+
- application/ # Use cases
|
|
33
|
+
- infrastructure/ # External adapters
|
|
34
|
+
- api/ # HTTP/gRPC handlers
|
|
35
|
+
- tests/
|
|
36
|
+
- unit/
|
|
37
|
+
- integration/
|
|
38
|
+
- e2e/
|
|
39
|
+
- docs/
|
|
40
|
+
- scripts/
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
### Step 1.2: Configure Build System
|
|
44
|
+
```yaml
|
|
45
|
+
agent: fullstack-developer
|
|
46
|
+
action: configure
|
|
47
|
+
files:
|
|
48
|
+
- package.json / pom.xml / go.mod
|
|
49
|
+
- Dockerfile
|
|
50
|
+
- docker-compose.yml
|
|
51
|
+
- Makefile
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
## Phase 2: Core Infrastructure
|
|
55
|
+
|
|
56
|
+
### Step 2.1: Database Setup
|
|
57
|
+
```yaml
|
|
58
|
+
agent: database-admin
|
|
59
|
+
action: setup
|
|
60
|
+
artifacts:
|
|
61
|
+
- schema_migrations
|
|
62
|
+
- seed_data
|
|
63
|
+
- connection_config
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
### Step 2.2: Observability Setup
|
|
67
|
+
```yaml
|
|
68
|
+
agent: fullstack-developer
|
|
69
|
+
action: configure
|
|
70
|
+
components:
|
|
71
|
+
- structured_logging
|
|
72
|
+
- metrics_endpoint
|
|
73
|
+
- health_checks
|
|
74
|
+
- trace_instrumentation
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
## Phase 3: API Implementation
|
|
78
|
+
|
|
79
|
+
### Step 3.1: Generate API Stubs
|
|
80
|
+
```yaml
|
|
81
|
+
agent: fullstack-developer
|
|
82
|
+
action: generate
|
|
83
|
+
from: openapi_spec
|
|
84
|
+
outputs:
|
|
85
|
+
- handlers
|
|
86
|
+
- request_validators
|
|
87
|
+
- response_types
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
### Step 3.2: Implement Business Logic
|
|
91
|
+
```yaml
|
|
92
|
+
agent: fullstack-developer
|
|
93
|
+
action: implement
|
|
94
|
+
patterns:
|
|
95
|
+
- Clean Architecture
|
|
96
|
+
- Dependency Injection
|
|
97
|
+
- Repository Pattern
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
## Phase 4: CI/CD Pipeline
|
|
101
|
+
|
|
102
|
+
### Step 4.1: Create Pipeline
|
|
103
|
+
```yaml
|
|
104
|
+
agent: cicd-manager
|
|
105
|
+
action: create
|
|
106
|
+
stages:
|
|
107
|
+
- lint
|
|
108
|
+
- test
|
|
109
|
+
- build
|
|
110
|
+
- security_scan
|
|
111
|
+
- deploy_staging
|
|
112
|
+
- integration_test
|
|
113
|
+
- deploy_production
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
### Step 4.2: Configure Deployment
|
|
117
|
+
```yaml
|
|
118
|
+
agent: cicd-manager
|
|
119
|
+
action: configure
|
|
120
|
+
artifacts:
|
|
121
|
+
- kubernetes_manifests
|
|
122
|
+
- helm_chart
|
|
123
|
+
- terraform_module
|
|
124
|
+
```
|
|
125
|
+
|
|
126
|
+
## Phase 5: Documentation
|
|
127
|
+
|
|
128
|
+
### Step 5.1: Generate Docs
|
|
129
|
+
```yaml
|
|
130
|
+
agent: fullstack-developer
|
|
131
|
+
action: document
|
|
132
|
+
outputs:
|
|
133
|
+
- README.md
|
|
134
|
+
- API_DOCS.md
|
|
135
|
+
- CONTRIBUTING.md
|
|
136
|
+
- ADR_TEMPLATE.md
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
## Outputs
|
|
140
|
+
- [ ] Runnable service codebase
|
|
141
|
+
- [ ] Docker configuration
|
|
142
|
+
- [ ] CI/CD pipeline
|
|
143
|
+
- [ ] Kubernetes manifests
|
|
144
|
+
- [ ] Documentation
|
|
145
|
+
|
|
146
|
+
## Quality Gates
|
|
147
|
+
- All tests pass
|
|
148
|
+
- Code coverage > 80%
|
|
149
|
+
- No security vulnerabilities
|
|
150
|
+
- API matches contract
|
|
151
|
+
- Health endpoints working
|
|
@@ -9,9 +9,9 @@ agents:
|
|
|
9
9
|
- vulnerability-scanner
|
|
10
10
|
- researcher
|
|
11
11
|
skills:
|
|
12
|
-
- owasp
|
|
13
|
-
- defense-in-depth
|
|
14
|
-
- security-hardening
|
|
12
|
+
- security/owasp
|
|
13
|
+
- methodology/defense-in-depth
|
|
14
|
+
- security/security-hardening
|
|
15
15
|
commands:
|
|
16
16
|
- /quality:security-scan
|
|
17
17
|
- /planning:research
|
|
@@ -11,9 +11,9 @@ agents:
|
|
|
11
11
|
- fullstack-developer
|
|
12
12
|
- docs-manager
|
|
13
13
|
skills:
|
|
14
|
-
- owasp
|
|
15
|
-
- security-hardening
|
|
16
|
-
- defense-in-depth
|
|
14
|
+
- security/owasp
|
|
15
|
+
- security/security-hardening
|
|
16
|
+
- methodology/defense-in-depth
|
|
17
17
|
commands:
|
|
18
18
|
- /quality:security-scan
|
|
19
19
|
- /dev:fix
|