Route RIPDPI VPN deployment changes through the risk-based OpenSpec specification workflow.
Scanned 9/12/2026
Install to Claude Code
Skills Directorynpx -y skills add po4yka/ripdpi-vpn-deploy --skill sdd --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Sdd?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/po4yka-sdd)More formats (shields.io, HTML) on the badges page.
---
name: sdd
description: Route RIPDPI VPN deployment changes through the risk-based OpenSpec specification workflow.
---
# Specification-driven development
Use OpenSpec for every feature, behavioral epic, operator-visible change, breaking contract, Terraform or Ansible runtime change, secrets/configuration schema, public `vpnd` CLI change, cross-layer or cross-repository contract, or security/network/deployment-lifecycle change.
- Create or find the portfolio task first with `./taskctl`.
- Use `$openspec-propose` to produce proposal, delta specs, design, mdtask tasks, and verification.
- Use `$openspec-apply-change` only after the planning artifacts pass strict validation.
- Use `$openspec-archive-change` only after review and complete evidence.
Narrow single-module regression fixes, tests, docs, dependency-only work, mechanical refactors, tooling, and research may use `spec_mode: not-required` with an allowed reason. Features and epics cannot waive OpenSpec.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
