Agent skill · aiskillstore

adapting-rvtf-to-superpowers

Use when applying requirements-to-verification traceability to Superpowers workflows, including brainstorming, writing plans, subagent-driven development, review, verification, branch finishing, or skill writing.

What it needs

About 6k tokens when loaded.

What this skill does

Adapting RVTF To Superpowers REQUIRED BACKGROUND: Use tracing-requirements-to-verification. Host Contract Snapshot Host repo/method: Superpowers writing-plans, subagent-driven-development, executing-plans, verification-before-completion, and finishing-a-development-branch. Branch: main. Revision: b36e0829c6d0140e93cfef2ca599b1b07d4a7797. This mapping is pinned to that exact host revision. Re-audit it before use if Superpowers task, review, verification, or branch-finishing behavior changes. Principle Do not replace Superpowers. Add RVTF as the evidence thread running through the existing Superpowers lifecycle. RVTF defines Requirement, canonical Acceptance Item, Journey, evidence, gap, and closure semantics; Superpowers still decides task grouping, implementer/reviewer roles, and whether or how to delegate work. Shared RVTF Boundary Use the required core Skill's schema, gate, and review-governance references for detailed fields and algorithms; this adapter only maps host boundaries. Use goal, milestone, and unit only for containment. Use deliverygroups with executionbatch, verificationbatch, or reviewbatch for execution, verification, and review grouping; group or Unit completion never auto-closes a parent Milestone or Goal. Effective gates are the union of host-native mandatory gates and RVTF-required gates. Reused evidenceclaims[].validity.status: valid may avoid only gates whose freshness policy permits reuse; it never erases a fresh/full host gate or supports a current-test claim. Keep hostgatestatus and currentteststatusclaim separate. Keep implementer self-check, verification, and formal review distinct. Review dimensions do not imply reviewer or batch count. Parent coverage is future work recorded as reviewstate: pendingatparent, never pre-recorded review evidence. Preserve strict independence from the implementer and every required specialist or segregation-of-duties fan-out. Review batches keep their subject revision immutable. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills aiskillstore/adapting-rvtf-to-superpowers

View the source on GitHub

Browse the @skills marketplace