devops-needs-assessmentlisted

# DevOps Needs Assessment <!-- anthril-output-directive --> > **Output path directive (canonical — overrides in-body references).** > All file outputs from this skill MUST be written under `.anthril/reports/`. > Run `mkdir -p .anthril/reports` before the first `Write` call. > Primary artefact: `.anthril/reports/devops-needs-assessment.md`. > Do NOT write to the project root or to bare filenames at cwd. > Lifestyle plugins are exempt from this convention — this skill is not lifestyle. ## When to use Run this skill when the user asks: - "Do I need DevOps?" - "Is my app production-ready?" - "What DevOps work should I do first?" - Describes a new app and wants direction Scores nine dimensions — CI/CD, Infrastructure as Code, Containers, Kubernetes, Observability, Release process, Security, Reliability, Docs — on a four-point scale from *Not needed yet* to *Urgent*. Designed for founders, solo developers, and designers-turned-operators. ## Before You Start 1. **This is the plain-language entry point.** The user is probably not a DevOps engineer. Explain every recommendation in everyday English. Do not use jargon without defining it. Never say "you need to implement RBAC" — say "right now anyone with access to your cluster can do anything; you should restrict who can do what." 2. **You may not have access to the code.** If the user gave you a description rather than a repo, work from the description and the questionnaire. Do not fabricate signals. 3. **Three-mode support.** T