Map BMAD Work to Verified Evidence
BMAD work can lose traceability between requirements, reviews, tests, and closure decisions. This skill maps BMAD artifacts to RVTF records while preserving host ownership, evidence quality, and review boundaries.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "adapting-rvtf-to-bmad" from https://skillstore.io/skills/solohic-adapting-rvtf-to-bmad.md and its manifest at https://skillstore.io/api/skills/solohic-adapting-rvtf-to-bmad/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.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "adapting-rvtf-to-bmad". A Story has passing tests but no journey-step evidence.
Expected outcome:
The tests may support acceptance-item evidence, but journey coverage remains unproven. Record a verification gap and narrow the closure claim.
Using "adapting-rvtf-to-bmad". A retrospective proposes fixes for an unfinished Story.
Expected outcome:
Keep the Story unfinished and the machine verdict rejected. Treat the fixes as proposals until an authorized owner routes them.
Using "adapting-rvtf-to-bmad". A direct change has no resolved Story key.
Expected outcome:
Map the actual change to one RVTF Unit. Do not update arbitrary sprint status or invent Story ownership.
All 36 static matches are false positives caused by Markdown inline-code spans or fenced documentation examples in SKILL.md. The skill contains no executable command mechanism, prompt injection attempt, or separate intent-level security issue.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/solohic-adapting-rvtf-to-bmad/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/solohic-adapting-rvtf-to-bmad?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/solohic-adapting-rvtf-to-bmad?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/solohic-adapting-rvtf-to-bmad/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/solohic-adapting-rvtf-to-bmad.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>solohic. (2026). adapting-rvtf-to-bmad security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/solohic-adapting-rvtf-to-bmad/audits/1@techreport{solohic-solohic-adapting-rvtf-to-bmad-2026,
author = {solohic},
title = {adapting-rvtf-to-bmad security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/solohic-adapting-rvtf-to-bmad/audits/1},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "adapting-rvtf-to-bmad 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-bmad/audits/1"
identifiers:
- type: other
value: "skillstore:solohic-adapting-rvtf-to-bmad:audit:1"
description: "Skillstore immutable audit report identifier"
Map a BMAD Story and its acceptance criteria to RVTF requirements, journeys, verification methods, and evidence targets before implementation.
Check whether adversarial, edge-case, and verification-gap reviews preserve finding identity, required roles, evidence, and host triage decisions.
Evaluate a BMAD retrospective using declared criteria, Story status, revisions, runtime evidence, gaps, and the RVTF completion gate.
Map this BMAD Story to RVTF requirements, acceptance items, journeys, and journey steps. Identify missing IDs and evidence targets.
Review this Story acceptance evidence. Separate item evidence from path evidence, identify unsupported claims, and list the smallest verification gaps.
Audit this BMAD review record for untraced scope, unsupported verified claims, missing review-batch coverage, lost deferred gaps, and unauthorized remediation.
Assess this Epic or direct change against RVTF closure rules. Preserve host status, distinguish proposed actions from approved work, and report evidence gaps and required owner decisions.
Author
solohicLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
45ba6cfb7b3f812e89568524860ab3ab91f66f93
Maintenance freshness
9/19/2026
Usage
0 downloads · 0 views
File structure
Trace Requirements to Verified Delivery
Teams can lose requirements when agent-skill work moves from planning to implementation and review. This skill keeps requirements, acceptance evidence, review state, and completion claims connected through a clear traceability process.
Trace Requirements Across Superpowers Workflows
Development teams can lose requirement evidence across planning, implementation, review, and release. This skill adds RVTF traceability while preserving Superpowers task boundaries and control.
Apply RVTF Traceability to GSD Workflows
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.
Trace Requirements to Verified Delivery
Teams often declare work complete without proving every requirement, path, review, and gap. This skill creates a traceable chain from intent to evidence and a defensible delivery decision.
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.
Create Verifiable Agent Loop Specs
by zhangzeyu99-web
Vague coding-agent tasks drift, repeat work, and report success without evidence. Ariadne Loop turns them into bounded loop specs with verifiers, stop rules, and human gates.
Verify Agent Completion With Evidence
by CleanExpo
AI agents can mark work complete without proof, which creates false completion risk. This skill requires independent evidence before task completion is accepted.
Create Focused Implementation Plans
by sickn33
Multi-step coding work can become vague, large, and hard to verify. This skill helps Claude, Codex, and Claude Code create short plans with clear tasks, order, and checks.
Execute Implementation Plans with Checkpoints
by obra
Implementation plans can lose focus when work moves into a separate AI session. This skill guides Claude, Codex, and Claude Code through batch execution, verification, and review checkpoints.
Verify Completion Claims Before Reporting
by CodingCossack
Completion claims can be wrong when agents rely on memory or confidence. This skill requires fresh evidence before reporting success.
Verify Acceptance Criteria and Stop
by juliusbrussee
Verification tasks often expand beyond their acceptance criteria. This skill selects sufficient checks, reports exact outcomes, and stops when proof is complete.