GSD progress can hide missing evidence, journey gaps, and unresolved review findings. This skill maps RVTF traceability and closure controls onto GSD planning and shipping.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "adapting-rvtf-to-gsd" from https://skillstore.io/skills/solohic-adapting-rvtf-to-gsd.md and its manifest at https://skillstore.io/api/skills/solohic-adapting-rvtf-to-gsd/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.
All 57 static findings are false positives caused by Markdown inline-code formatting, text fences, and a documented configuration identifier. The reviewed files contain no executable command behavior, prompt injection, data exfiltration intent, or system reconnaissance instructions.
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.
solohic. (2026). adapting-rvtf-to-gsd security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/solohic-adapting-rvtf-to-gsd/audits/1
BibTeX citation
@techreport{solohic-solohic-adapting-rvtf-to-gsd-2026,
author = {solohic},
title = {adapting-rvtf-to-gsd security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/solohic-adapting-rvtf-to-gsd/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-gsd 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-gsd/audits/1"
identifiers:
- type: other
value: "skillstore:solohic-adapting-rvtf-to-gsd:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this scoreEvidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance
What You Can Build
Validate a Phase Plan
Map planned work to requirements, acceptance items, journeys, and evidence before execution begins.
Audit Verification Coverage
Separate completed implementation from verified outcomes and expose missing item or journey evidence.
Prepare a Shipping Decision
Review host gates, formal reviews, waivers, unresolved gaps, and closure evidence before shipping.
Try These Prompts
Check a Phase Plan
Review this GSD phase plan with RVTF. Identify mapped requirements, acceptance items, journeys, missing links, and the next verification actions.
Find Verification Gaps
Assess this GSD phase evidence. Separate implementation progress from canonical verification, then list item evidence gaps and journey path gaps.
Design Traceability Coverage
Create an RVTF traceability approach for this GSD phase. Include scope mappings, delivery groups, review batches, evidence expectations, and closure conditions.
Assess Release Readiness
Evaluate this GSD release for RVTF closure. Reconcile host gates, review epochs, state conflicts, waivers, continuation ownership, and unresolved residual risk.
Best Practices
Use stable requirement, acceptance item, journey, and step identifiers throughout planning and verification.
Keep host gate status, current test claims, review coverage, and RVTF closure separate.
Re-audit the adapter whenever the pinned GSD planning, review, verification, or shipping contracts change.
Avoid
Do not treat completed tasks, plans, summaries, or pushed branches as verified outcomes.
Do not infer review coverage from configured capabilities or failed reviewer lanes.
Do not merge conflicting planning roots or allow parallel workers to update shared continuation state.
Frequently Asked Questions
What does this skill add to GSD?
It adds auditable links among requirements, acceptance items, journeys, evidence, reviews, and gaps while preserving GSD lifecycle authority.
Does this skill run GSD commands?
No. It provides declarative mapping and decision guidance without invoking plans, shipping workflows, or other GSD commands.
Can task completion close a GSD phase?
No. Canonical phase verification must pass, and required item and journey evidence must support RVTF closure.
How are human checks handled?
Route required human checks through UAT and owner decisions, then resume the remaining verification and closure gates.
What happens when planning state conflicts?
Treat the conflict as an integrity gap, reconcile phase artifacts and ownership, restore one writer, and then resume.
When should the adapter be reviewed again?
Review it when the pinned GSD revision changes or when planning, review, verification, workspace, isolation, or shipping contracts change.