SkillAgentSearch skills...

nw-devops

Establishes durable deployment, environment, observability, recovery, and CI constraints when platform risk requires the DEVOPS lens.

Install / Use

npx skills add nWave-ai/nWave --skill nw-devops

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Claude Code

Our assessment of nw-devops

nw-devops scores 92/100 on our quality scale, 295th of 950 AI & Machine Learning skills we index (top 32%).

Its SKILL.md is 20 KB long, well organised into 35 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

It has 617 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so nw-devops is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-08. Automated pattern scan on 2026-10-08. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

nw-devops compared with similar skills

All 4 of these similar skills score higher than nw-devops; compare them before choosing.

SkillScoreStarsUpdatedFormat
nw-devops (this skill)by nWave-ai926172mo agoSKILL.md
claude-memby thedotmack100117.9ktodayCLAUDE.md
Understand-Anythingby Egonex-AI10093.0k2d agoCLAUDE.md
headroomby headroomlabs-ai10079.9ktodayCLAUDE.md
CowAgentby zhayujie10048.0ktodayCLAUDE.md

Frequently asked questions

How do I install nw-devops?
Run npx skills add nWave-ai/nWave --skill nw-devops. The install tabs above show the steps for each supported agent.
Which AI agents does nw-devops work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is nw-devops safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is nw-devops still maintained?
The repository was last updated about 2 months ago, so nw-devops is actively maintained.

name: nw-devops description: "Designs CI/CD pipelines, infrastructure, observability, and deployment strategy. Use when preparing platform readiness for a feature." user-invocable: true argument-hint: '[deployment-target] - Optional: --environment=[staging|production] --validation=[full|smoke]'

NW-DEVOPS: Platform Readiness and Infrastructure Design

Wave: DEVOPS (wave 4 of 6) | Agent: Apex (nw-platform-architect) | Command: /nw-devops

Overview

Execute DEVOPS wave: platform readiness|CI/CD pipeline setup|observability design|infrastructure preparation. Positioned between DESIGN and DISTILL (DISCOVER > DISCUSS > SPIKE > DESIGN > DEVOPS > DISTILL > DELIVER), ensures infrastructure is ready before acceptance tests and code.

Apex translates DESIGN architecture decisions into operational infrastructure: CI/CD pipelines|logging|monitoring|alerting|observability.

Output Tiers (per D2)

Provenance: feature lean-wave-documentation — D2 (schema-typed sections), D10 (one-line expansion descriptions). Tier-1 [REF] sections (always emitted) + Tier-2 EXPANSION CATALOG items (lazy, on-demand) are the two output bands. Full contract: nWave/skills/nw-density-resolution-contract/SKILL.md.

Tier-1 [REF] — always emitted

Under ## Wave: DEVOPS / [REF] <Section> headings:

  • Environment matrix — table of target environments with platform + preconditions
  • CI/CD pipeline outline — stage list with trigger rules per branch
  • Monitoring contracts — KPI-to-instrument mapping (one row per outcome KPI)
  • Deployment strategy — chosen strategy + rollback contract (one paragraph)
  • Mutation testing strategy — selected mode (per-feature/nightly-delta/pre-release/disabled)
  • Observability stack — chosen tools per signal class (logs/metrics/traces)
  • Branching strategy — selected model + CI trigger alignment
  • Coexistence matrix — tools that must continue to work alongside deployment
  • Pre-requisites — DESIGN constraints the platform must satisfy

Tier-2 EXPANSION CATALOG — lazy, on-demand (per D10)

Rendered under ## Wave: DEVOPS / [WHY|HOW] <Section> only when requested via --expand <id> (DDD-2), the broad wave-end menu (expansion_prompt = "ask"), a declared trigger under expansion_prompt = "ask-intelligent", mode = "full" auto-expansion, or an ad-hoc user request mid-session.

| Expansion ID | Tier label | One-line description | |---|---|---| | infra-cost-analysis | [WHY] | Per-environment monthly cost estimate with vendor pricing assumptions | | alternative-deploy-targets | [WHY] | Cloud/on-prem/hybrid options weighed and rejected with one-paragraph reason | | observability-deep-dive | [HOW] | Detailed metric/log/trace schemas, alert thresholds, dashboard layouts | | runbook-drafts | [HOW] | Incident response runbooks for the top failure modes | | kpi-instrumentation-recipes | [HOW] | Per-KPI data collection recipe (event names, log fields, metric labels) | | ci-pipeline-yaml | [HOW] | Full CI/CD pipeline YAML with comments per stage | | disaster-recovery-plan | [HOW] | Backup, restore, and DR procedures with RPO/RTO targets | | expansion-catalog-rationale | [WHY] | Why this set of expansions, why these defaults, why D10 enforces one-line descriptions |

Density resolution (per D12)

Call resolve_density(global_config) from scripts/shared/density_config.py after reading ~/.nwave/global-config.json (missing/malformed = empty dict). Returns mode ("lean" | "full") + expansion_prompt ("ask" | "ask-intelligent" | "always-skip" | "always-expand" | "smart") per the D12 cascade (resolver-internal, DDD-5 — do NOT replicate locally). Branch on density.mode for what to emit; branch on density.expansion_prompt at wave end for menu behaviour. DEVOPS declares no ask-intelligent triggers: emit no menu and the shared-contract no-trigger skip event; do not invent triggers. Full cascade detail, branch semantics, ad-hoc override workflow: nWave/skills/nw-density-resolution-contract/SKILL.md.

Telemetry (per D4 + DDD-6)

Every expansion choice emits a DocumentationDensityEvent (dataclass at src/des/domain/telemetry/documentation_density_event.py) via event.to_audit_event() → JsonlAuditLogWriter().log_event(...). Schema fields per D4: feature_id, wave, expansion_id, choice, timestamp. For this wave the schema declares "wave": "DEVOPS". Use helper scripts/shared/telemetry.py:write_density_event(...) — do NOT write JSONL directly.

Wave-specific signal: DISTILL consuming a lean DEVOPS environment matrix — downstream --expand requests for runbook drafts or alternative deploy targets indicate the [REF] baseline was insufficient. Full emission rules: nWave/skills/nw-density-resolution-contract/SKILL.md.

Interactive Decision Points

Before proceeding, the orchestrator asks:

Decision 1: Deployment Target

Question: What is the deployment target? Options:

  1. Cloud-native -- AWS, GCP, Azure managed services
  2. On-premise -- self-hosted infrastructure
  3. Hybrid -- mix of cloud and on-premise
  4. Edge -- distributed edge deployment
  5. Other -- user provides custom input

Decision 2: Container Orchestration

Question: Container orchestration approach? Options:

  1. Kubernetes -- full orchestration
  2. Docker Compose -- lightweight container management
  3. Serverless -- function-as-a-service, no containers
  4. None -- bare metal or VM-based deployment

Decision 3: CI/CD Platform

Question: CI/CD platform preference? Options:

  1. GitHub Actions
  2. GitLab CI
  3. Jenkins
  4. Azure DevOps
  5. Other -- user provides custom input

Decision 4: Existing Infrastructure

Question: Is there existing infrastructure or CI/CD to integrate with? Options:

  1. Yes, both -- describe existing infrastructure and CI/CD (user provides details)
  2. Existing infra only -- infrastructure exists, CI/CD is greenfield
  3. Existing CI/CD only -- CI/CD exists, infrastructure is greenfield
  4. No -- greenfield, design everything from scratch

Decision 5: Observability and Logging

Question: What observability and logging approach? Options:

  1. Prometheus + Grafana (metrics) with structured JSON logs
  2. Datadog (full-stack observability including logs)
  3. ELK stack (Elasticsearch, Logstash, Kibana for logs and metrics)
  4. OpenTelemetry (vendor-agnostic telemetry) with provider of choice
  5. CloudWatch (AWS-native metrics and logging)
  6. Custom -- user provides details
  7. None -- defer observability setup

Decision 6: Deployment Strategy

Question: What deployment strategy? Options:

  1. Blue-green -- zero-downtime with environment swap
  2. Canary -- gradual traffic shifting
  3. Rolling -- incremental pod/instance replacement
  4. Recreate -- simple stop-and-replace

Decision 7: Continuous Learning (conditional)

Question: Is there existing monitoring/alerting infrastructure in place? Options:

  1. Yes -- include continuous learning and experimentation capabilities
  2. No -- focus on foundational monitoring setup first

If Yes to Decision 7: Follow-up: Which continuous learning capabilities to include? Options:

  1. A/B testing framework
  2. Feature flags (LaunchDarkly, Unleash, custom)
  3. Canary analysis (automated rollback on metrics)
  4. Progressive rollout (percentage-based deployment)
  5. All of the above

Decision 8: Git Branching Strategy

Question: What Git branching strategy should the project follow? Options:

  1. Trunk-Based Development -- single main branch, short-lived feature branches (<1 day), continuous integration. Requires robust CI gates on every commit.
  2. GitHub Flow -- feature branches from main, pull requests, merge to main after review. Balanced CI with PR-triggered pipelines.
  3. GitFlow -- develop/main branches, feature/release/hotfix branches, formal release process. Requires branch-specific pipelines (develop CI, release candidate, hotfix fast-track).
  4. Release Branching -- long-lived release branches, cherry-pick fixes between branches. Requires per-branch pipelines and cross-branch validation.
  5. Other -- user provides custom strategy

This directly influences CI/CD pipeline design: trigger rules|branch protection|environment promotion|release automation.

Decision 9: Mutation Testing Strategy

Question: When should mutation testing run? Options:

  1. per-feature (default) -- Runs after each feature delivery (refactoring + review), scoped to modified files. Best for small/medium projects where per-feature overhead is acceptable. Fastest feedback loop but adds ~5-15 min per delivery.
  2. nightly-delta -- Runs in CI nightly on files modified that day. Best for large projects where per-feature mutation testing is too slow. Delays feedback but keeps delivery fast.
  3. pre-release -- Runs before each release on the entire solution. Best for projects with long release cycles where comprehensive mutation coverage matters most at release boundaries. Slowest feedback but most thorough.
  4. disabled -- No mutation testing. Only appropriate for prototypes, spikes, or projects where test quality is validated through other means.

After selection, Apex asks permission to write to project CLAUDE.md under ## Mutation Testing Strategy:

per-feature: This project uses **per-feature** mutation testing. Runs after refactoring during each delivery, scoped to modified files. Kill rate gate: >= 80%.

nightly-delta: This project uses **nightly-delta** mutation testing. CI runs on files modified each day. NOT run during feature delivery.

pre-release: This project uses **pre-release** mutation testing. Runs on entire solution before each release. Delivery not blocked.

disabled: Mutation testing is **disabled**. Test quality validated through code review and CI coverage.

Default if not chosen: per-feature.

Prior Wave Consultation

Before beginning DEVOPS work, read targeted prior wave artifacts:

  1. DISCOVER (skip): DESIGN already synthesizes DISCOVER+DISCUSS into architecture. Not needed for infrastructure design.
  2. DISCUSS (KPIs only): Read docs/feature/{feature-id}/discuss/outcome-kpis.md — drives observability and instrumentation design.
  3. DESIGN (primary input): Read all files in docs/feature/{feature-id}/design/ — architecture drives infrastructure decisions.

READING ENFORCEMENT: Read every file listed above using the Read tool before proceeding. After reading, output a confirmation checklist (✓ {file} for each read, ⊘ {file} (not found) for missing). Do NOT skip files that exist — skipping causes infrastructure decisions disconnected from architecture.

After reading, check whether any DEVOPS decisions would contradict DESIGN architecture. Flag contradictions and resolve with user before proceeding. Example: DESIGN specifies "single-region deployment" but DEVOPS discovers latency requirements from outcome-kpis.md that demand multi-region — this must be resolved.

Document Update (Back-Propagation)

When DEVOPS decisions change assumptions from prior waves:

  1. Document change — Add a ## Changed Assumptions section at the end of the affected DEVOPS artifact. Gate: section present in artifact.
  2. Reference original — Quote the original prior-wave document and the original assumption. Gate: quote included.
  3. State new assumption — Write the new assumption and rationale for the change. Gate: rationale documented.
  4. Flag upstream changes — If infrastructure constraints require architecture changes, write them to docs/feature/{feature-id}/devops/upstream-changes.md for the architect to review. Gate: file created if architecture impact exists.

Agent Invocation

  1. Dispatch — Invoke @nw-platform-architect with the feature-id and configuration below. Gate: agent accepts invocation.
  2. Provide context — Pass all prior wave consultation files (see Prior Wave Consultation). Gate: context files attached.
  3. Pass configuration — Includ

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars617
CategoryAI
Updated2mo ago
Forks63

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions