Skills adapting-rvtf-to-openspec

📦

adapting-rvtf-to-openspec

Name: adapting-rvtf-to-openspec
Author: solohic

Content revision r1 Safe ⚙️ External commands🌐 Network access

Trace OpenSpec Changes to Verified Closure

OpenSpec tasks and archive states do not prove evidence-backed completion. This skill maps requirements, acceptance items, journeys, and gates into an auditable RVTF closure process.

Supports: Claude Codex Code(CC)

📊 74 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "adapting-rvtf-to-openspec" from https://skillstore.io/skills/solohic-adapting-rvtf-to-openspec.md and its manifest at https://skillstore.io/api/skills/solohic-adapting-rvtf-to-openspec/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/solohic-adapting-rvtf-to-openspec.md Signed manifest GET /api/skills/solohic-adapting-rvtf-to-openspec/manifest Signed lockfile GET /api/skills/solohic-adapting-rvtf-to-openspec/lockfile

Test it

Using "adapting-rvtf-to-openspec". All OpenSpec tasks are checked, but one mapped Acceptance Item has no target-specific evidence.

Expected outcome:

Keep the host progress, keep the affected Item implemented, and record an evidence gap with its owner. Do not close the Change.

Using "adapting-rvtf-to-openspec". The Change was archived before the RVTF disposition was complete.

Expected outcome:

Record the archived host state, preserve the prior RVTF disposition, and identify the continuation owner and entry condition.

Using "adapting-rvtf-to-openspec". A source file digest changed after the trace projection was created.

Expected outcome:

Reject the old projection for closure, reconcile stable IDs and mappings, assess affected evidence, and preserve only explicitly validated claims.

Security Audit

Safe

v1 • 9/19/2026 Open versioned report

All 39 static findings are false positives caused by Markdown code formatting, documentation examples, or a reference URL. No prompt injection, data-exfiltration intent, or unsafe execution behavior was found in the reviewed files.

Files scanned

322

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/solohic-adapting-rvtf-to-openspec/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/solohic-adapting-rvtf-to-openspec/security.svg)](https://skillstore.io/skills/solohic-adapting-rvtf-to-openspec?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/solohic-adapting-rvtf-to-openspec?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/solohic-adapting-rvtf-to-openspec/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/solohic-adapting-rvtf-to-openspec.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

solohic. (2026). adapting-rvtf-to-openspec security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/solohic-adapting-rvtf-to-openspec/audits/1

BibTeX citation

@techreport{solohic-solohic-adapting-rvtf-to-openspec-2026,
  author = {solohic},
  title = {adapting-rvtf-to-openspec security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/solohic-adapting-rvtf-to-openspec/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "adapting-rvtf-to-openspec security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "solohic"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/solohic-adapting-rvtf-to-openspec/audits/1"
identifiers:
  - type: other
    value: "skillstore:solohic-adapting-rvtf-to-openspec:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Audit a planned Change

Map requirements, scenarios, tasks, and acceptance evidence before implementation begins.

Review implementation readiness

Check source bindings, execution authority, mandatory gates, and evidence gaps before applying a Change.

Prepare a closure decision

Assess target-specific claims, Journey paths, findings, gaps, and final validation before declaring completion.

Try These Prompts

Beginner: Map a Change

Apply RVTF traceability to this OpenSpec Change. Identify its requirements, scenarios, tasks, acceptance items, and missing mappings.

Basic: Check Readiness

Review this OpenSpec Change for implementation readiness. Confirm the supported root and schema, sidecar requirements, task mappings, Journey applicability, and mandatory gates.

Advanced: Audit Evidence

Audit the Change evidence claim by claim. Reconcile source digest changes, separate Item evidence from Journey path evidence, preserve valid claims, and list exact gaps with owners.

Expert: Decide Closure

Produce a formal RVTF closure assessment for this OpenSpec Change. Verify host authority, source bindings, requirements, acceptance items, applicable Journeys, gates, findings, review state, Closure Packet fields, and final CLI validation.

Best Practices

Keep OpenSpec as authored truth and RVTF as the evidence and closure layer.
Use separate target-specific claims when one artifact supports multiple Requirements, Items, or Journeys.
Record exact gaps, owners, and entry conditions whenever a gate or evidence requirement is unsatisfied.

Avoid

Treating checked tasks, a clear verification report, sync, or archive as proof of RVTF closure.
Reinterpreting a custom schema or Store as the supported repo-local spec-driven workflow.
Allowing OpenSpec and a split-host method to schedule work or own lifecycle state simultaneously.

Frequently Asked Questions

What does this skill trace?

It traces one OpenSpec Change from authored requirements and scenarios to RVTF evidence, gates, review, and closure.

Does a checked task prove completion?

No. Checked tasks may support implemented status, but they do not produce verified evidence or complete RVTF closure.

When is a Scenario also a Journey?

Only when an actor, goal, and observable multi-step path require ordered path or outcome evidence.

What happens when source text changes?

The prior projection is rejected for closure until digests, stable IDs, mappings, and affected evidence are reconciled.

Can this skill support a custom OpenSpec schema?

No. Version one supports one repo-local Change using the built-in spec-driven schema.

Does the skill run validation commands?

No. It defines the required preflight and validation evidence; the host environment must run the commands and provide their results.

Developer Details

Author

solohic

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/solohic/rvtf-skills/tree/6a959384dd089c2f558482d7d70f869dbcaf3673/skills/adapting-rvtf-to-openspec

Ref

45ba6cfb7b3f812e89568524860ab3ab91f66f93

Maintenance freshness

9/19/2026

Usage

0 downloads · 0 views

File structure

📁 agents/

📄 openai.yaml

📁 references/

📄 pressure-scenarios.md

📄 SKILL.md

adapting-rvtf-to-openspec

Install with my Agent

Agent-readable resources

Test it

Security Audit

Risk Factors

Copy report link

Markdown badge

HTML badge

Embed card

APA citation

BibTeX citation

CITATION.cff

Skillstore Score

What You Can Build

Audit a planned Change

Review implementation readiness

Prepare a closure decision

Try These Prompts

Best Practices

Avoid

Frequently Asked Questions

Developer Details