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.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "tracing-requirements-to-verification" from https://skillstore.io/skills/solohic-tracing-requirements-to-verification.md and its manifest at https://skillstore.io/api/skills/solohic-tracing-requirements-to-verification/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 "tracing-requirements-to-verification". A checkout change has three requirements, six acceptance items, one missing end-to-end path test, and a review finding about rollback evidence.
Expected outcome:
The requirements may remain implemented, but delivery is incomplete. Add the missing journey evidence, classify rollback evidence as a cross-cutting constraint, assign an owner, and rerun the completion gate.
Using "tracing-requirements-to-verification". A team has passing unit tests and a host status of shipped, but no target-specific evidence for two acceptance items.
Expected outcome:
Using "tracing-requirements-to-verification". A reviewer proposes an unrelated reporting improvement during a release review.
Expected outcome:
Classify it as an optional enhancement unless an owner accepts a scope amendment. Keep it out of the current closure decision.
All 220 static findings are false positives caused by documentation syntax and ordinary governance language. The reviewed files contain no executable shell usage, network reconnaissance, or prompt-injection instructions; no net-new semantic security finding was identified.
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-tracing-requirements-to-verification/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/solohic-tracing-requirements-to-verification?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/solohic-tracing-requirements-to-verification?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/solohic-tracing-requirements-to-verification/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/solohic-tracing-requirements-to-verification.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). tracing-requirements-to-verification security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/solohic-tracing-requirements-to-verification/audits/1@techreport{solohic-solohic-tracing-requirements-to-verification-2026,
author = {solohic},
title = {tracing-requirements-to-verification security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/solohic-tracing-requirements-to-verification/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: "tracing-requirements-to-verification security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "solohic"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/solohic-tracing-requirements-to-verification/audits/1"
identifiers:
- type: other
value: "skillstore:solohic-tracing-requirements-to-verification:audit:1"
description: "Skillstore immutable audit report identifier"
Turn feature requirements into acceptance items, verification methods, implementation mappings, and explicit delivery gaps.
Audit evidence, journeys, review coverage, unresolved gaps, and completion gates before a release decision.
Keep scope, ownership, evidence, review state, and continuation conditions consistent across parallel contributors.
Map these requirements to acceptance criteria, implementation tasks, verification methods, and known evidence gaps: [paste requirements].
Review this delivery scope and decide whether an actor journey is required. Explain the path dependencies and required evidence: [paste scope].
Classify each review finding as required-gap, evidence-gap, cross-cutting-constraint, scope-amendment, optional-enhancement, or quality-defect. Link each finding to affected trace objects: [paste findings].
Audit this closure packet against the completion gate. Check required children, requirement evidence, journey evidence, review governance, effective gates, gaps, and continuation. State the supported disposition and missing actions: [paste packet].
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
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.
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 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.
Track Long Tasks With a Portable State Ledger
by glenskii
Long technical tasks lose decisions, evidence, and next actions across sessions. This skill maintains a concise Markdown state file with reviewed local evidence references.
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.