SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Route RIPDPI changes through a risk-based OpenSpec specification workflow.
Route RIPDPI changes through the risk-based OpenSpec specification workflow.
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
Original instructions from the publisher’s SKILL.md
# Specification-driven development 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-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.
Files included alongside SKILL.md in the publisher’s repository.