Specification-driven development
SkillDev toolsRoute RIPDPI changes through the risk-based OpenSpec specification workflow.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Specification-driven development skill
What this skill tells your AI
The instructions your AI receives, as published by po4yka/ripdpi in .agents/skills/sdd/SKILL.md and read by ahel’s review.
Use OpenSpec for every feature, behavioral epic, user-visible change, breaking contract, protobuf/JNI/wire/storage/configuration schema, cross-module change, or security/network/protocol/service-lifecycle change.
- Create or find the portfolio task first with
./taskctl. - Use
$openspec-proposeto produce proposal, delta specs, design, mdtask tasks, and verification. - Use
$openspec-apply-changeonly after the planning artifacts pass strict validation. - Use
$openspec-archive-changeonly 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.
Signals
- GitHub stars
- 69
- Forks
- 4
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
sdd-po4yka- Source
- github.com/po4yka/ripdpi