kiro-agent-team 1.0.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/.kiro/README.md +228 -0
- package/.kiro/agents/backend-engineer.json +6 -0
- package/.kiro/agents/backend-engineer.md +643 -0
- package/.kiro/agents/database-specialist.json +6 -0
- package/.kiro/agents/database-specialist.md +390 -0
- package/.kiro/agents/development-logger.json +6 -0
- package/.kiro/agents/development-logger.md +265 -0
- package/.kiro/agents/devops-engineer.json +6 -0
- package/.kiro/agents/devops-engineer.md +287 -0
- package/.kiro/agents/frontend-architect.json +6 -0
- package/.kiro/agents/frontend-architect.md +1032 -0
- package/.kiro/agents/hooks/backend-engineer-hooks.yaml +540 -0
- package/.kiro/agents/hooks/database-specialist-hooks.yaml +488 -0
- package/.kiro/agents/hooks/development-logger-hooks.yaml +361 -0
- package/.kiro/agents/hooks/devops-engineer-hooks.yaml +345 -0
- package/.kiro/agents/hooks/frontend-architect-hooks.yaml +521 -0
- package/.kiro/agents/hooks/project-manager-hooks.yaml +513 -0
- package/.kiro/agents/hooks/security-specialist-hooks.yaml +358 -0
- package/.kiro/agents/hooks/test-orchestrator-hooks.yaml +380 -0
- package/.kiro/agents/hooks/ui-ux-designer-hooks.yaml +353 -0
- package/.kiro/agents/project-manager.json +6 -0
- package/.kiro/agents/project-manager.md +344 -0
- package/.kiro/agents/prompts/backend-engineer-system.md +815 -0
- package/.kiro/agents/prompts/database-specialist-system.md +332 -0
- package/.kiro/agents/prompts/development-logger-system.md +232 -0
- package/.kiro/agents/prompts/devops-engineer-system.md +260 -0
- package/.kiro/agents/prompts/frontend-architect-system.md +305 -0
- package/.kiro/agents/prompts/project-manager-system.md +285 -0
- package/.kiro/agents/prompts/security-specialist-system.md +231 -0
- package/.kiro/agents/prompts/test-orchestrator-system.md +214 -0
- package/.kiro/agents/prompts/ui-ux-designer-system.md +270 -0
- package/.kiro/agents/security-specialist.json +6 -0
- package/.kiro/agents/security-specialist.md +277 -0
- package/.kiro/agents/test-orchestrator.json +6 -0
- package/.kiro/agents/test-orchestrator.md +266 -0
- package/.kiro/agents/ui-ux-designer.json +6 -0
- package/.kiro/agents/ui-ux-designer.md +284 -0
- package/.kiro/devlog/00-START-HERE.md +444 -0
- package/.kiro/devlog/COMPLETE-WORKFLOW.md +553 -0
- package/.kiro/devlog/DEVLOG-INTEGRATION.md +413 -0
- package/.kiro/devlog/DEVLOG-PROCESS-FLOWS.md +484 -0
- package/.kiro/devlog/DEVLOG-QUICK-REF.md +299 -0
- package/.kiro/devlog/DEVLOG.md +22 -0
- package/.kiro/devlog/IMPLEMENTATION-COMPLETE.txt +434 -0
- package/.kiro/devlog/IMPLEMENTATION-SUMMARY.md +358 -0
- package/.kiro/devlog/README.md +363 -0
- package/.kiro/devlog/devlog-update.bat +136 -0
- package/.kiro/devlog/devlog-update.sh +275 -0
- package/.kiro/devlog/feature-completion-hook.bat +78 -0
- package/.kiro/devlog/feature-completion-hook.sh +84 -0
- package/.kiro/documentation/cli.md +31 -0
- package/.kiro/documentation/docs_cli.md +41 -0
- package/.kiro/documentation/docs_cli_authentication.md +43 -0
- package/.kiro/documentation/docs_cli_autocomplete.md +132 -0
- package/.kiro/documentation/docs_cli_billing.md +31 -0
- package/.kiro/documentation/docs_cli_billing_contact-support.md +43 -0
- package/.kiro/documentation/docs_cli_billing_managing-taxes.md +67 -0
- package/.kiro/documentation/docs_cli_billing_related-questions.md +49 -0
- package/.kiro/documentation/docs_cli_billing_subscription-portal.md +31 -0
- package/.kiro/documentation/docs_cli_chat.md +84 -0
- package/.kiro/documentation/docs_cli_chat_configuration.md +40 -0
- package/.kiro/documentation/docs_cli_chat_context.md +258 -0
- package/.kiro/documentation/docs_cli_chat_git-aware-selection.md +41 -0
- package/.kiro/documentation/docs_cli_chat_images.md +53 -0
- package/.kiro/documentation/docs_cli_chat_manage-prompts.md +216 -0
- package/.kiro/documentation/docs_cli_chat_model-selection.md +153 -0
- package/.kiro/documentation/docs_cli_chat_permissions.md +68 -0
- package/.kiro/documentation/docs_cli_chat_planning-agent.md +230 -0
- package/.kiro/documentation/docs_cli_chat_responding.md +123 -0
- package/.kiro/documentation/docs_cli_chat_security.md +87 -0
- package/.kiro/documentation/docs_cli_chat_subagents.md +77 -0
- package/.kiro/documentation/docs_cli_code-intelligence.md +251 -0
- package/.kiro/documentation/docs_cli_custom-agents.md +37 -0
- package/.kiro/documentation/docs_cli_custom-agents_configuration-reference.md +941 -0
- package/.kiro/documentation/docs_cli_custom-agents_creating.md +93 -0
- package/.kiro/documentation/docs_cli_custom-agents_examples.md +360 -0
- package/.kiro/documentation/docs_cli_custom-agents_troubleshooting.md +180 -0
- package/.kiro/documentation/docs_cli_enterprise_billing.md +33 -0
- package/.kiro/documentation/docs_cli_enterprise_concepts.md +34 -0
- package/.kiro/documentation/docs_cli_enterprise_getting-started.md +19 -0
- package/.kiro/documentation/docs_cli_enterprise_iam.md +251 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track.md +15 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track_dashboard.md +62 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track_prompt-logging.md +165 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track_user-activity.md +123 -0
- package/.kiro/documentation/docs_cli_enterprise_settings.md +15 -0
- package/.kiro/documentation/docs_cli_enterprise_subscribe.md +36 -0
- package/.kiro/documentation/docs_cli_enterprise_subscription-management.md +55 -0
- package/.kiro/documentation/docs_cli_enterprise_supported-regions.md +39 -0
- package/.kiro/documentation/docs_cli_experimental.md +282 -0
- package/.kiro/documentation/docs_cli_experimental_checkpointing.md +439 -0
- package/.kiro/documentation/docs_cli_experimental_delegate.md +422 -0
- package/.kiro/documentation/docs_cli_experimental_knowledge-management.md +449 -0
- package/.kiro/documentation/docs_cli_experimental_tangent-mode.md +357 -0
- package/.kiro/documentation/docs_cli_experimental_thinking.md +331 -0
- package/.kiro/documentation/docs_cli_experimental_todo-lists.md +385 -0
- package/.kiro/documentation/docs_cli_hooks.md +207 -0
- package/.kiro/documentation/docs_cli_installation.md +235 -0
- package/.kiro/documentation/docs_cli_mcp.md +106 -0
- package/.kiro/documentation/docs_cli_mcp_configuration.md +294 -0
- package/.kiro/documentation/docs_cli_mcp_examples.md +273 -0
- package/.kiro/documentation/docs_cli_mcp_governance.md +436 -0
- package/.kiro/documentation/docs_cli_mcp_security.md +77 -0
- package/.kiro/documentation/docs_cli_migrating-from-q.md +129 -0
- package/.kiro/documentation/docs_cli_privacy-and-security.md +83 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_compliance-validation.md +17 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_data-protection.md +104 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_firewalls.md +26 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_infrastructure-security.md +10 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_vpc-endpoints.md +41 -0
- package/.kiro/documentation/docs_cli_reference_built-in-tools.md +624 -0
- package/.kiro/documentation/docs_cli_reference_cli-commands.md +689 -0
- package/.kiro/documentation/docs_cli_reference_settings.md +294 -0
- package/.kiro/documentation/docs_cli_reference_slash-commands.md +559 -0
- package/.kiro/documentation/docs_cli_steering.md +84 -0
- package/.kiro/guides/AGENT_WORKFLOW_GUIDE.md +294 -0
- package/.kiro/guides/DEVLOG.md +882 -0
- package/.kiro/guides/IMPLEMENTATION_EXAMPLES.md +611 -0
- package/.kiro/guides/PIV Loop.md +122 -0
- package/.kiro/guides/PIV Loop.png +0 -0
- package/.kiro/guides/PIVLoop.png +0 -0
- package/.kiro/guides/QUICK_REFERENCE.md +202 -0
- package/.kiro/guides/README.md +149 -0
- package/.kiro/guides/advanced-patterns.md +514 -0
- package/.kiro/guides/agent-coordination.md +434 -0
- package/.kiro/guides/core-workflows.md +409 -0
- package/.kiro/guides/emergency-procedures.md +414 -0
- package/.kiro/guides/project-evaluation.md +534 -0
- package/.kiro/guides/quality-assurance.md +431 -0
- package/.kiro/guides/quick-start.md +235 -0
- package/.kiro/guides/troubleshooting.md +575 -0
- package/.kiro/guides/walkthroughs.md +711 -0
- package/.kiro/prompts/add-to-devlog.md +263 -0
- package/.kiro/prompts/code-review-fix.md +18 -0
- package/.kiro/prompts/code-review-hackathon.md +167 -0
- package/.kiro/prompts/code-review-security.md +454 -0
- package/.kiro/prompts/code-review.md +113 -0
- package/.kiro/prompts/create-prd.md +151 -0
- package/.kiro/prompts/execute-backend.md +257 -0
- package/.kiro/prompts/execute-frontend.md +438 -0
- package/.kiro/prompts/execute-logging.md +491 -0
- package/.kiro/prompts/execute-security.md +482 -0
- package/.kiro/prompts/execute-testing.md +528 -0
- package/.kiro/prompts/execute.md +101 -0
- package/.kiro/prompts/execution-report.md +72 -0
- package/.kiro/prompts/implement-fix.md +228 -0
- package/.kiro/prompts/plan-feature.md +433 -0
- package/.kiro/prompts/prime.md +73 -0
- package/.kiro/prompts/quality-metrics.md +622 -0
- package/.kiro/prompts/quickstart.md +318 -0
- package/.kiro/prompts/rca.md +220 -0
- package/.kiro/prompts/system-review.md +189 -0
- package/README.md +32 -0
- package/bin/cli.js +97 -0
- package/package.json +33 -0
|
@@ -0,0 +1,345 @@
|
|
|
1
|
+
# DevOps Engineer Agent Hooks Configuration
|
|
2
|
+
# Automated infrastructure and deployment workflows
|
|
3
|
+
|
|
4
|
+
agent_name: "DevOps Engineer"
|
|
5
|
+
agent_role: "Infrastructure, Deployment & CI/CD Automation Expert"
|
|
6
|
+
version: "1.0"
|
|
7
|
+
|
|
8
|
+
hooks:
|
|
9
|
+
# Infrastructure and Deployment Triggers
|
|
10
|
+
- name: "systematic_infrastructure_implementation"
|
|
11
|
+
description: "Execute systematic infrastructure development using standardized framework"
|
|
12
|
+
trigger:
|
|
13
|
+
type: "user_command"
|
|
14
|
+
conditions:
|
|
15
|
+
- command: "execute"
|
|
16
|
+
- agent: "devops-engineer"
|
|
17
|
+
action:
|
|
18
|
+
type: "execute_prompt"
|
|
19
|
+
prompt: "execute.md"
|
|
20
|
+
message: "Executing systematic infrastructure development with comprehensive deployment validation and monitoring setup..."
|
|
21
|
+
agent: "devops-engineer"
|
|
22
|
+
include_context:
|
|
23
|
+
- infrastructure_requirements: true
|
|
24
|
+
- deployment_strategy: true
|
|
25
|
+
- monitoring_needs: true
|
|
26
|
+
- security_requirements: true
|
|
27
|
+
|
|
28
|
+
- name: "deployment_pipeline_trigger"
|
|
29
|
+
description: "Trigger deployment pipeline setup when new services are added"
|
|
30
|
+
trigger:
|
|
31
|
+
type: "file_change"
|
|
32
|
+
patterns:
|
|
33
|
+
- "backend/package.json"
|
|
34
|
+
- "frontend/package.json"
|
|
35
|
+
- "docker-compose.yml"
|
|
36
|
+
- "Dockerfile"
|
|
37
|
+
- ".github/workflows/*.yml"
|
|
38
|
+
action:
|
|
39
|
+
type: "agent_message"
|
|
40
|
+
message: |
|
|
41
|
+
🚀 DEPLOYMENT PIPELINE REVIEW
|
|
42
|
+
|
|
43
|
+
Infrastructure or deployment configuration changes detected. Use @execute for systematic deployment pipeline optimization.
|
|
44
|
+
|
|
45
|
+
**Pipeline Assessment Areas:**
|
|
46
|
+
- CI/CD workflow optimization and automation
|
|
47
|
+
- Container configuration and orchestration
|
|
48
|
+
- Environment management and provisioning
|
|
49
|
+
- Deployment strategies and rollback procedures
|
|
50
|
+
- Infrastructure as Code implementation
|
|
51
|
+
|
|
52
|
+
Use @execute to implement systematic deployment improvements with comprehensive validation.
|
|
53
|
+
|
|
54
|
+
- name: "infrastructure_scaling_trigger"
|
|
55
|
+
description: "Trigger infrastructure review when performance issues are detected"
|
|
56
|
+
trigger:
|
|
57
|
+
type: "manual"
|
|
58
|
+
description: "Manual trigger for performance issues or scaling needs"
|
|
59
|
+
action:
|
|
60
|
+
type: "agent_message"
|
|
61
|
+
message: |
|
|
62
|
+
📈 INFRASTRUCTURE SCALING ASSESSMENT
|
|
63
|
+
|
|
64
|
+
Performance or scaling concerns detected. Let me help optimize your infrastructure.
|
|
65
|
+
|
|
66
|
+
**Scaling Assessment Areas:**
|
|
67
|
+
- Current resource utilization and bottlenecks
|
|
68
|
+
- Auto-scaling configuration and triggers
|
|
69
|
+
- Load balancing and traffic distribution
|
|
70
|
+
- Database performance and scaling strategies
|
|
71
|
+
- CDN and caching optimization
|
|
72
|
+
|
|
73
|
+
**Performance Analysis Questions:**
|
|
74
|
+
1. What performance issues are you experiencing? (Slow response times, high CPU, memory issues, database bottlenecks)
|
|
75
|
+
2. What's your current traffic patterns and expected growth? (Peak usage, geographic distribution, seasonal patterns)
|
|
76
|
+
3. What's your performance targets? (Response time, throughput, concurrent users)
|
|
77
|
+
4. What's your budget constraints for scaling? (Cost optimization priorities, resource limits)
|
|
78
|
+
5. What's your preferred scaling approach? (Vertical scaling, horizontal scaling, auto-scaling)
|
|
79
|
+
6. Do you need multi-region deployment or CDN optimization?
|
|
80
|
+
|
|
81
|
+
I'll analyze your infrastructure and recommend scaling strategies that balance performance and cost.
|
|
82
|
+
|
|
83
|
+
- name: "environment_provisioning_trigger"
|
|
84
|
+
description: "Trigger environment setup when new environments are needed"
|
|
85
|
+
trigger:
|
|
86
|
+
type: "file_change"
|
|
87
|
+
patterns:
|
|
88
|
+
- "terraform/*.tf"
|
|
89
|
+
- "cloudformation/*.yml"
|
|
90
|
+
- "k8s/*.yaml"
|
|
91
|
+
- "ansible/*.yml"
|
|
92
|
+
action:
|
|
93
|
+
type: "agent_message"
|
|
94
|
+
message: |
|
|
95
|
+
🏗️ ENVIRONMENT PROVISIONING REVIEW
|
|
96
|
+
|
|
97
|
+
Infrastructure as Code changes detected. Let me help with environment provisioning and management.
|
|
98
|
+
|
|
99
|
+
**Environment Management Areas:**
|
|
100
|
+
- Infrastructure as Code best practices and validation
|
|
101
|
+
- Environment consistency and configuration management
|
|
102
|
+
- Resource provisioning and cost optimization
|
|
103
|
+
- Security and access control implementation
|
|
104
|
+
- Backup and disaster recovery procedures
|
|
105
|
+
|
|
106
|
+
**Environment Planning Questions:**
|
|
107
|
+
1. What environments are you provisioning? (Development, staging, production, testing)
|
|
108
|
+
2. What's your infrastructure requirements? (Compute, storage, networking, databases)
|
|
109
|
+
3. What's your security and compliance requirements? (Network isolation, encryption, access controls)
|
|
110
|
+
4. What's your backup and disaster recovery needs? (RTO, RPO, data retention)
|
|
111
|
+
5. What's your cost optimization priorities? (Resource sizing, auto-shutdown, reserved instances)
|
|
112
|
+
6. What monitoring and alerting do you need for these environments?
|
|
113
|
+
|
|
114
|
+
I'll help ensure your infrastructure is reliable, secure, and cost-effective.
|
|
115
|
+
|
|
116
|
+
# Monitoring and Alerting Triggers
|
|
117
|
+
- name: "monitoring_setup_trigger"
|
|
118
|
+
description: "Trigger monitoring configuration when new services are deployed"
|
|
119
|
+
trigger:
|
|
120
|
+
type: "file_change"
|
|
121
|
+
patterns:
|
|
122
|
+
- "backend/src/server.ts"
|
|
123
|
+
- "frontend/src/App.tsx"
|
|
124
|
+
- "docker-compose.yml"
|
|
125
|
+
- "k8s/deployment.yaml"
|
|
126
|
+
action:
|
|
127
|
+
type: "agent_message"
|
|
128
|
+
message: |
|
|
129
|
+
📊 MONITORING & OBSERVABILITY SETUP
|
|
130
|
+
|
|
131
|
+
New service deployment detected. Let me help set up comprehensive monitoring and observability.
|
|
132
|
+
|
|
133
|
+
**Monitoring Setup Areas:**
|
|
134
|
+
- Application performance monitoring (APM)
|
|
135
|
+
- Infrastructure monitoring and alerting
|
|
136
|
+
- Log aggregation and analysis
|
|
137
|
+
- Error tracking and debugging
|
|
138
|
+
- User experience and synthetic monitoring
|
|
139
|
+
|
|
140
|
+
**Monitoring Requirements Questions:**
|
|
141
|
+
1. What metrics are most important to monitor? (Performance, availability, errors, business metrics)
|
|
142
|
+
2. What's your alerting preferences? (Email, Slack, PagerDuty, SMS)
|
|
143
|
+
3. What's your incident response process? (On-call rotation, escalation procedures)
|
|
144
|
+
4. What's your log retention and analysis needs? (Compliance, debugging, analytics)
|
|
145
|
+
5. What's your monitoring budget and tool preferences? (Open source, SaaS, enterprise)
|
|
146
|
+
6. Do you need custom dashboards or reporting? (Executive dashboards, team dashboards, customer-facing status)
|
|
147
|
+
|
|
148
|
+
I'll design a monitoring strategy that provides visibility without overwhelming your team with noise.
|
|
149
|
+
|
|
150
|
+
- name: "incident_response_trigger"
|
|
151
|
+
description: "Trigger incident response when system alerts are detected"
|
|
152
|
+
trigger:
|
|
153
|
+
type: "manual"
|
|
154
|
+
description: "Manual trigger for system incidents or outages"
|
|
155
|
+
action:
|
|
156
|
+
type: "agent_message"
|
|
157
|
+
message: |
|
|
158
|
+
🚨 INCIDENT RESPONSE COORDINATION
|
|
159
|
+
|
|
160
|
+
System incident or outage detected. Initiating incident response procedures.
|
|
161
|
+
|
|
162
|
+
**Immediate Response Actions:**
|
|
163
|
+
- Assess incident severity and impact scope
|
|
164
|
+
- Coordinate incident response team and communication
|
|
165
|
+
- Implement immediate mitigation and recovery procedures
|
|
166
|
+
- Document incident timeline and actions taken
|
|
167
|
+
- Prepare stakeholder communication and updates
|
|
168
|
+
|
|
169
|
+
**Critical Information Needed:**
|
|
170
|
+
1. What type of incident occurred? (Service outage, performance degradation, security breach, data loss)
|
|
171
|
+
2. What services or systems are affected? (Frontend, backend, database, third-party integrations)
|
|
172
|
+
3. What's the business impact? (User-facing, internal systems, revenue impact)
|
|
173
|
+
4. When did the incident start and what triggered it?
|
|
174
|
+
5. What immediate actions have been taken? (Rollbacks, scaling, service restarts)
|
|
175
|
+
6. Who needs to be notified? (Internal team, customers, stakeholders, compliance)
|
|
176
|
+
|
|
177
|
+
I'll coordinate the incident response and help restore service as quickly as possible.
|
|
178
|
+
|
|
179
|
+
# CI/CD and Automation Triggers
|
|
180
|
+
- name: "cicd_optimization_trigger"
|
|
181
|
+
description: "Trigger CI/CD pipeline optimization when build times increase"
|
|
182
|
+
trigger:
|
|
183
|
+
type: "schedule"
|
|
184
|
+
schedule: "weekly"
|
|
185
|
+
action:
|
|
186
|
+
type: "agent_message"
|
|
187
|
+
message: |
|
|
188
|
+
⚡ CI/CD PIPELINE OPTIMIZATION REVIEW
|
|
189
|
+
|
|
190
|
+
Weekly CI/CD pipeline performance and optimization review.
|
|
191
|
+
|
|
192
|
+
**Pipeline Optimization Areas:**
|
|
193
|
+
- Build time analysis and optimization
|
|
194
|
+
- Test execution parallelization and efficiency
|
|
195
|
+
- Deployment speed and reliability improvements
|
|
196
|
+
- Resource utilization and cost optimization
|
|
197
|
+
- Pipeline security and compliance validation
|
|
198
|
+
|
|
199
|
+
**Optimization Assessment Questions:**
|
|
200
|
+
1. Are you experiencing any CI/CD performance issues? (Slow builds, test timeouts, deployment delays)
|
|
201
|
+
2. What's your current build and deployment frequency? (Multiple daily, daily, weekly)
|
|
202
|
+
3. What's your pipeline resource constraints? (Build agents, concurrent jobs, cost limits)
|
|
203
|
+
4. What optimizations would provide the most value? (Speed, reliability, cost, security)
|
|
204
|
+
5. Are there any new requirements or changes needed? (New environments, testing strategies, compliance)
|
|
205
|
+
|
|
206
|
+
Let's identify opportunities to make your CI/CD pipeline faster, more reliable, and cost-effective.
|
|
207
|
+
|
|
208
|
+
- name: "backup_recovery_check"
|
|
209
|
+
description: "Regular backup and disaster recovery validation"
|
|
210
|
+
trigger:
|
|
211
|
+
type: "schedule"
|
|
212
|
+
schedule: "monthly"
|
|
213
|
+
action:
|
|
214
|
+
type: "agent_message"
|
|
215
|
+
message: |
|
|
216
|
+
💾 BACKUP & DISASTER RECOVERY VALIDATION
|
|
217
|
+
|
|
218
|
+
Monthly backup and disaster recovery testing and validation.
|
|
219
|
+
|
|
220
|
+
**Backup & Recovery Areas:**
|
|
221
|
+
- Database backup integrity and restoration testing
|
|
222
|
+
- Application data backup and recovery procedures
|
|
223
|
+
- Infrastructure backup and disaster recovery validation
|
|
224
|
+
- Recovery time objective (RTO) and recovery point objective (RPO) testing
|
|
225
|
+
- Documentation and runbook updates
|
|
226
|
+
|
|
227
|
+
**Recovery Planning Questions:**
|
|
228
|
+
1. What's your current backup strategy and schedule? (Automated, manual, frequency)
|
|
229
|
+
2. When was the last successful recovery test? (Database, application, full system)
|
|
230
|
+
3. What's your RTO and RPO requirements? (Minutes, hours, days)
|
|
231
|
+
4. What disaster scenarios should we test? (Data corruption, service outage, regional failure)
|
|
232
|
+
5. Are your recovery procedures documented and up-to-date?
|
|
233
|
+
6. Do you need cross-region or multi-cloud disaster recovery?
|
|
234
|
+
|
|
235
|
+
Let's ensure your backup and recovery procedures are reliable and meet your business continuity needs.
|
|
236
|
+
|
|
237
|
+
- name: "cost_optimization_review"
|
|
238
|
+
description: "Regular infrastructure cost analysis and optimization"
|
|
239
|
+
trigger:
|
|
240
|
+
type: "schedule"
|
|
241
|
+
schedule: "monthly"
|
|
242
|
+
action:
|
|
243
|
+
type: "agent_message"
|
|
244
|
+
message: |
|
|
245
|
+
💰 INFRASTRUCTURE COST OPTIMIZATION REVIEW
|
|
246
|
+
|
|
247
|
+
Monthly infrastructure cost analysis and optimization opportunities.
|
|
248
|
+
|
|
249
|
+
**Cost Optimization Areas:**
|
|
250
|
+
- Resource utilization analysis and rightsizing
|
|
251
|
+
- Reserved instance and savings plan optimization
|
|
252
|
+
- Auto-scaling configuration and efficiency
|
|
253
|
+
- Storage optimization and lifecycle management
|
|
254
|
+
- Network and data transfer cost optimization
|
|
255
|
+
|
|
256
|
+
**Cost Analysis Questions:**
|
|
257
|
+
1. What's your current monthly infrastructure spend and budget? (Actual vs. budgeted costs)
|
|
258
|
+
2. What services are consuming the most resources and cost? (Compute, storage, networking, databases)
|
|
259
|
+
3. What's your usage patterns and growth trends? (Peak usage, seasonal variations, growth rate)
|
|
260
|
+
4. What cost optimization priorities do you have? (Immediate savings, long-term efficiency, performance balance)
|
|
261
|
+
5. Are you using reserved instances, savings plans, or spot instances effectively?
|
|
262
|
+
6. What monitoring and alerting do you have for cost management?
|
|
263
|
+
|
|
264
|
+
I'll analyze your infrastructure costs and recommend optimization strategies that maintain performance while reducing expenses.
|
|
265
|
+
|
|
266
|
+
# Integration Hooks with Other Agents
|
|
267
|
+
integration_hooks:
|
|
268
|
+
- agent: "Backend Engineer"
|
|
269
|
+
trigger: "API deployment and scaling needs"
|
|
270
|
+
message: "DevOps Engineer available for backend service deployment and infrastructure scaling"
|
|
271
|
+
|
|
272
|
+
- agent: "Frontend Architect"
|
|
273
|
+
trigger: "Frontend deployment and CDN optimization"
|
|
274
|
+
message: "DevOps Engineer ready to assist with frontend deployment and performance optimization"
|
|
275
|
+
|
|
276
|
+
- agent: "Database Specialist"
|
|
277
|
+
trigger: "Database infrastructure and backup management"
|
|
278
|
+
message: "DevOps Engineer available for database infrastructure provisioning and backup automation"
|
|
279
|
+
|
|
280
|
+
- agent: "Security Specialist"
|
|
281
|
+
trigger: "Infrastructure security and compliance"
|
|
282
|
+
message: "DevOps Engineer ready to collaborate on secure infrastructure and DevSecOps implementation"
|
|
283
|
+
|
|
284
|
+
- agent: "Test Orchestrator"
|
|
285
|
+
trigger: "Testing infrastructure and CI/CD integration"
|
|
286
|
+
message: "DevOps Engineer available to integrate testing into deployment pipelines and provision test environments"
|
|
287
|
+
|
|
288
|
+
# Consultation Triggers
|
|
289
|
+
consultation_triggers:
|
|
290
|
+
- name: "infrastructure_requirements_gathering"
|
|
291
|
+
description: "Comprehensive infrastructure consultation for new projects"
|
|
292
|
+
message: |
|
|
293
|
+
🏗️ INFRASTRUCTURE REQUIREMENTS CONSULTATION
|
|
294
|
+
|
|
295
|
+
Starting infrastructure planning for reliable and scalable deployment strategy.
|
|
296
|
+
|
|
297
|
+
**Key Areas to Discuss:**
|
|
298
|
+
1. **Scalability Requirements**: What are your expected traffic patterns and growth projections?
|
|
299
|
+
2. **Deployment Strategy**: What's your preferred deployment approach and release frequency?
|
|
300
|
+
3. **Environment Needs**: How many environments do you need and what are their requirements?
|
|
301
|
+
4. **Budget Constraints**: What's your infrastructure budget and cost optimization priorities?
|
|
302
|
+
5. **Technology Preferences**: What cloud platforms, tools, and technologies do you prefer?
|
|
303
|
+
|
|
304
|
+
Let's design infrastructure that balances performance, reliability, and cost-effectiveness.
|
|
305
|
+
|
|
306
|
+
- name: "deployment_strategy_consultation"
|
|
307
|
+
description: "Comprehensive deployment strategy and CI/CD consultation"
|
|
308
|
+
message: |
|
|
309
|
+
🚀 DEPLOYMENT STRATEGY CONSULTATION
|
|
310
|
+
|
|
311
|
+
Planning deployment pipeline and CI/CD strategy for reliable software delivery.
|
|
312
|
+
|
|
313
|
+
**Deployment Questions:**
|
|
314
|
+
1. **Release Frequency**: How often do you want to deploy? (Multiple daily, daily, weekly, on-demand)
|
|
315
|
+
2. **Deployment Strategy**: What approach fits best? (Blue-green, canary, rolling, immediate)
|
|
316
|
+
3. **Rollback Requirements**: What's your rollback strategy and recovery time needs?
|
|
317
|
+
4. **Testing Integration**: How should testing be integrated into the deployment pipeline?
|
|
318
|
+
5. **Environment Management**: What environments do you need and how should they be managed?
|
|
319
|
+
|
|
320
|
+
I'll help design a deployment strategy that balances speed, reliability, and risk management.
|
|
321
|
+
|
|
322
|
+
- name: "quality_metrics_collection"
|
|
323
|
+
description: "Collect infrastructure and deployment quality metrics"
|
|
324
|
+
trigger:
|
|
325
|
+
type: "deployment_completion"
|
|
326
|
+
conditions:
|
|
327
|
+
- deployment_type: ["staging", "production"]
|
|
328
|
+
action:
|
|
329
|
+
type: "execute_prompt"
|
|
330
|
+
prompt: "quality-metrics.md"
|
|
331
|
+
message: "Collecting infrastructure quality metrics: deployment success, performance, and reliability..."
|
|
332
|
+
agent: "devops-engineer"
|
|
333
|
+
include_context:
|
|
334
|
+
- deployment_metrics: true
|
|
335
|
+
- infrastructure_performance: true
|
|
336
|
+
- reliability_indicators: true
|
|
337
|
+
|
|
338
|
+
# Notification Settings
|
|
339
|
+
notifications:
|
|
340
|
+
deployment_alerts: "immediate"
|
|
341
|
+
performance_issues: "immediate"
|
|
342
|
+
cost_alerts: "daily"
|
|
343
|
+
backup_failures: "immediate"
|
|
344
|
+
security_incidents: "immediate"
|
|
345
|
+
maintenance_windows: "24_hours_advance"
|