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.
이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.
에이전트 요청
Review the Skillstore skill "adapting-rvtf-to-agent-skills" from https://skillstore.io/skills/solohic-adapting-rvtf-to-agent-skills.md and its manifest at https://skillstore.io/api/skills/solohic-adapting-rvtf-to-agent-skills/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.
에이전트가 읽기 쉬운 리소스
AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.
"adapting-rvtf-to-agent-skills" 사용 중입니다. A request to add password reset with email delivery and audit logging.
예상 결과:
Requirements map: password reset flow, email delivery, audit event, and failure handling. Each item has acceptance checks, evidence requirements, and a named verification gate.
"adapting-rvtf-to-agent-skills" 사용 중입니다. A completed increment with unit tests passing but no current review receipt.
예상 결과:
Status: implementation evidence present; review remains pending. Action: obtain a current review receipt before claiming the increment is fully complete.
"adapting-rvtf-to-agent-skills" 사용 중입니다. A release plan that combines deployment with code review.
예상 결과:
Build completion is tracked separately from review approval.
Deployment and post-launch verification remain distinct release gates.
All 40 external-command detections are false positives caused by Markdown backticks around workflow names, field names, and status values. The system-reconnaissance detection is also a false positive because it describes evidence practices in prose; no executable security threat was evidenced in the supplied findings.
solohic. (2026). adapting-rvtf-to-agent-skills security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/solohic-adapting-rvtf-to-agent-skills/audits/1
BibTeX 인용
@techreport{solohic-solohic-adapting-rvtf-to-agent-skills-2026,
author = {solohic},
title = {adapting-rvtf-to-agent-skills security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/solohic-adapting-rvtf-to-agent-skills/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-agent-skills 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-agent-skills/audits/1"
identifiers:
- type: other
value: "skillstore:solohic-adapting-rvtf-to-agent-skills:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 점수
이 점수의 이유증거 신뢰도: 중간
55
아키텍처
85
유지보수성
87
콘텐츠
65
커뮤니티
91
사양 준수
만들 수 있는 것
Plan an agent-skill feature
Convert a feature brief into traceable requirements, acceptance items, increments, and verification gates.
Review incremental implementation
Check that each completed increment has current evidence, correct review status, and no unsupported completion claims.
Prepare a controlled release
Separate build completion from review, shipping, deployment, and post-launch verification before release decisions.
이 프롬프트를 사용해 보세요
Start a traceability plan
Turn this feature brief into requirements, acceptance items, user journeys, and verification steps. Keep each item uniquely identifiable.
Map one increment
For this increment, map every change to requirement IDs and acceptance item IDs. List the evidence needed before marking it complete.
Audit completion claims
Review these implementation and test receipts. Identify unsupported completion claims, stale evidence, missing review states, and required follow-up actions.
Define release boundaries
Create a traceability-aware release plan for this production change. Separate build, review, ship, deployment, and post-launch verification, and specify when to stop or await owner approval.
모범 사례
Use stable requirement and acceptance identifiers throughout planning, implementation, and review.
Record current evidence and host status separately from reusable historical evidence.
Make continuation actions explicit, and stop at host boundaries unless the user approved the scope.
피하기
Do not infer release completion from a finished task or passing local test.
Do not copy mutable host tracker status into a separate traceability document.
Do not silently translate review severities or omit required findings during synthesis.
자주 묻는 질문
What problem does this skill solve?
It keeps requirements connected to implementation, verification evidence, review state, and completion decisions.
Does it run builds or deployments?
No. It defines traceability and decision boundaries; the host tools perform execution.
When should I use it?
Use it when planning or reviewing multi-step agent-skill work with acceptance criteria and evidence requirements.
How does it handle stale evidence?
It keeps reused evidence separate and requires a fresh host gate or current status claim when needed.
Can it authorize automatic continuation?
Only an explicitly approved scope can permit continuation; otherwise the process records stop or await-owner.
Does completion imply release readiness?
No. Task and increment closure remain separate from review, shipping, deployment, and post-launch verification.