nWave-ai/nWave / nWave/skills/nw-devops
nw-devops
UnverifiedEstablishes durable deployment, environment, observability, recovery, and CI constraints when platform risk requires the DEVOPS lens.
NW-DEVOPS
Read ~/.claude/skills/nw-human-collaboration/SKILL.md to offer and conduct
interactive refinement with the human. Honor an already selected final-review
or full-delegation mode; the LLM manages the dialogue and progression.
The installed nw-platform-architect supplies semantic platform facts to the
solution architect. Keep operational advice in the coherent design authority,
not a separate constructor or sidecar.
When the platform role reads this skill, it applies only the semantic workflow and returns its findings and human questions to its caller; it never invokes itself or writes generated authority.
Purpose
Apply the platform lens only when infrastructure, deployment, recovery, observability or environment risk is material. Update existing durable platform architecture, environment inventory and ADRs; do not create a per-delivery narrative.
Workflow
- Read stable product KPI identities and durable architecture decisions.
- Inventory actual environments, toolchains, trust boundaries and ownership.
- Define deployment and rollback observations, health signals, SLOs and alert ownership.
- Model infrastructure/recovery outcomes explicitly: timeout, unavailable, partial success, retryable, permanent refusal, replay and operator action. Ensure the application/port contract cannot silently ignore a required failure mode.
- Define literal environment-native verification commands and dependency
ownership. Never substitute an ambient
.venvor assume a language. - Return platform constraints, decisions and evidence to the solution architect
through
--root-context. That owner incorporates relevant facts in the current design payload; do not create a parallel operational authority. - When independent operational review is selected, follow
nw-role-invocation's selected-review branch: the native caller invokesnw-platform-architect-revieweron the current constructed authority, bound facts, scope and observations, then consumes its actual result. Keep review outside the closed constructor JSON. Required revisions return to the platform authority owner; construction alone is not completion of an enabled selected review. No unselected review turn or live rollout is implied.
DEVOPS does not author a handover, feature directory, rollout ledger or CI status copy. A downstream operational contradiction returns to the platform authority; software re-derives any needed execution facts.
Integration and lifecycle
Keep platform review replies verbatim. The host invokes models, runs native checks and retains actual output. Declared operational facts and rendered documents do not deploy or verify infrastructure.
Guidance, not enforced by nwdes: when a design declares an auto-deploy target, the architect should record in the shared DESIGN constraint the target, its trigger and its health endpoint, and should record as a slice verification command a deploy probe the host can run against that target or a faithful mirror. nwdes does not check that the probe ran or that its output exists; a close with --outcome indeterminate --diagnostic TEXT that names the missing probe is the honest outcome when it cannot run.
Before creating or inheriting a lane, or finalizing/resuming cleanup, apply
the worktree lifecycle in nw-throughput. The feature's handoff and product
brief are its record; there is no separate evolution constructor.
Human-readable authority
Use current full briefs and HTML with nw-doc-as-artifact for human review.
Rendering introduces no density preference or automatic expansion-offer mechanism.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |
| paperclip-pagepaperclipai/paperclipPublish static HTML pages and asset folders to the Paperclip S3/CloudFront page host. Use when asked to deploy, host, or share a persistent page, viewer, prototype, report, or static site without here.now. | Stars: 114k | Updated | Claude CodeCodex | Verified | Install |