DevOps Engineer — Document Workflow¶
Description: Generate documentation summary
When to Use¶
Use the document workflow when you need to generate documentation summary.
Input Requirements¶
- Infrastructure topology diagrams and resource inventories
- Monitoring and alerting configurations
- Incident reports and post-mortem analyses
- Capacity forecasts and resource utilization metrics
- Service level objectives (SLOs) and error budgets
Process¶
- Initialize — Set up the document context for DevOps Engineer
- Execute — Perform the document operation following DevOps Engineer's style
- Validate — Check output against quality gates
- Handoff — Deliver results to downstream personas
Output¶
- Infrastructure as code definitions for all environments
- Monitoring and alerting configuration with SLO-based thresholds
- Incident response playbooks with escalation procedures
- Capacity planning reports with growth projections
- Post-mortem templates and improvement tracking
Quality Gates¶
- Infrastructure changes must be defined as code, never manual
- Observability instrumentation required for all production services
- Runbook documentation mandatory for all operational procedures
- Incident response procedures must include post-mortem requirements
- Capacity planning must project at least 90 days ahead