nWave-ai/nWave / nWave/skills/nw-par-critique-dimensions
nw-par-critique-dimensions
VerifiedPlatform design review critique dimensions and severity levels. Load when reviewing CI/CD pipelines, infrastructure, deployment strategies, observability, or security designs.
Platform Design Critique Dimensions
Applicability is governed by the current authorized platform/rollout contract,
not a universal cloud/pipeline topology. Evaluate actual load-bearing gaps with
the consequences below; missing optional Kubernetes, vault, SBOM, tracing,
canary or DORA machinery is not itself a blocker. Existing project-native
equivalents are valid. Project-specific thresholds require observations; the
example durations/rates are not universal gates. Apply the platform dimensions
and complete role-owned assessment in nw-typesafe-system-one and scope rules
in nw-par-review-criteria; do not add another checklist or review phase.
Dimension 1: CI/CD Pipeline Completeness
Questions: Are applicable delivery stages and their genuine quality/security criteria explicit? Does failure recovery preserve the promised data/outcomes? Are caching/parallelism and environment parity appropriate to measured needs? Blocker: a missing required acceptance/security/safety obligation with evidence. Critical/high: concrete recovery, provenance or environment gaps whose consequence is grounded in the selected plan; elapsed time alone is not a finding. Medium: Inconsistent naming | missing documentation for manual steps.
Dimension 2: Infrastructure as Code Quality
Questions: Infrastructure fully codified? Modules reusable and parameterized? State management secure (encrypted, locked)? Security best practices (least privilege, encryption)? Idempotent and reproducible?
Blocker: Secrets in version control | no state management | production credentials in code. Critical: No encryption at rest | overly permissive IAM | missing network security. High: Hardcoded values | missing resource tagging | no cost estimation. Medium: Inconsistent module structure | missing input variable validation.
Dimension 3: Deployment Strategy Risk
Questions: Strategy appropriate for risk profile? Rollback documented? Health checks and readiness probes defined? Gradual traffic shifting with automatic rollback? Database migrations backward compatible?
Blocker: No rollback strategy | no health checks | breaking changes without safeguards. Critical: Single-shot deployment for critical services | no canary/blue-green for high-traffic | missing pod disruption budgets. High: Rollback not tested | no gradual traffic shifting | no pre-deployment validation. Medium: Incomplete manual step documentation | no feature flags for risky features.
Dimension 4: Observability and SLO Alignment
Questions: SLOs defined with specific targets? All four golden signals monitored? Distributed tracing configured? Alerts SLO burn-rate based? Dashboards for investigation?
Blocker: No SLOs defined | no error rate monitoring | no alerting strategy. Critical: No latency monitoring (p50/p90/p99) | symptom-based alerts | no log-metric-trace correlation. High: Incomplete metric coverage | alert thresholds misaligned with SLOs | no runbook links. Medium: Unclear dashboard organization | missing error budget tracking.
Dimension 5: Pipeline and Infrastructure Security
Questions: SAST in commit stage? DAST before production? SCA configured? Secrets management using external vault? SBOM generated and signed?
Blocker: leaked credentials or a required security control absent at its real boundary. Critical/high: evidenced permission, dependency, network or artifact risk without the promised mitigation. Environment variables are not automatically credential leaks; evaluate actual exposure. Do not demand all listed tools for every stack.
Dimension 6: DORA Metrics Enablement
Questions: Design enables multiple deployments/day? Lead time < 1 hour achievable? Change failure rate tracking in place? Time to restore measurable with SLOs?
Critical: Manual steps preventing daily deployments | no automated testing for fast feedback | no deployment failure tracking. High: Pipeline > 1 hour for full deployment | no post-deployment validation | missing deployment frequency metrics.
Dimension 7: Priority and Constraint Validation
Questions: Design addresses largest bottleneck first? Simpler alternatives documented and rejected with evidence? Constraint prioritization correct? Complexity justified?
Critical: Design addresses secondary concern while larger exists | no measurement data | simple alternatives not documented. High: Constraint prioritization not explicit | over-engineered for stated requirements.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |