nWave/skills/nw-production-readiness/SKILL.md
Monitoring, observability, operational procedures, CI/CD lessons learned, and quality gate definitions. Load when assessing production readiness or validating operational excellence.
npx skillsauth add nwave-ai/nwave nw-production-readinessInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Server/container health and resource utilization | Network performance and connectivity | Storage capacity and I/O performance | Security event detection.
| Tier | Condition | Response | |------|-----------|----------| | Page | Service down, data loss risk, security breach | Immediate response | | Urgent | Error rate >2x baseline, latency SLA breach | Response within 15 min | | Warning | Capacity >80%, error rate trending up | Response within 1 hour | | Info | Deployment complete, metric threshold crossed | Review next business day |
Regular update and patching schedule | Backup verification (test restores quarterly) | Security vulnerability scanning (automated, weekly) | Performance baseline recalibration (after major changes).
Operational runbooks for common procedures | Architecture documentation with system diagrams | Deployment procedures and configuration management | Troubleshooting guides for known failure modes.
Before declaring production-ready, all must pass:
For CI/CD architecture lessons and measurement coupling pitfalls, see cicd-and-deployment skill.
testing
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
testing
Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation
testing
Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation
development
Design mandates for acceptance tests - hexagonal boundary, business language abstraction, user journey completeness, pure function extraction, 3 Pillars (domain language / chained narrative / production composition), and the layered ATD discipline (Universe-bound assertion, layer-dependent PBT mode, two-tier acceptance, example-based sad paths)