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.
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.
エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
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.
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形式の引用
@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 スコア
このスコアの理由証拠の信頼度: 中
41
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
83
仕様準拠
作成できるもの
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.
これらのプロンプトを試す
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.
ベストプラクティス
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.
回避
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.
よくある質問
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.