adf-retrofit-verification

Original：🇨🇳 Chinese

Translated

Perform follow-up semantic verification for Targets that have completed migration while Legacy still exists.

2installs

Sourcechungtsai/adf-framework

Added on2026-10-02

NPX Install

npx skill4agent add chungtsai/adf-framework adf-retrofit-verification

SKILL.md Content (Chinese)

View Translation Comparison →

ADF Retrofit Verification

Purpose

VERIFY ONLY by default; analyze Legacy and Target, use the same cases for Golden/Dual Execution, Normalization, Comparison, and Traceability; after Human Review, open a separate CHANGE for any defects.

ADF Common Invariants

Work Type may only use
```
NEW
```
,
```
CHANGE
```
, or
```
MIGRATION
```
.
Each Module may have only one Active Work Item at a time; the Module is the primary isolation boundary.

Compact Artifacts are used by default:

requirements.md

,

rules.md

,

standards.md

,

design.md

,

test-cases.md

, and

traceability.md

.

The existence of a file does not mean that the Stage is complete.
Stable identifiers remain in English:
```
REQ-*
```
,
```
BR-*
```
,
```
VAL-*
```
,
```
Q-*
```
,
```
UI-*
```
,
```
DEV-*
```
, and
```
MIG-*
```
.
Any behavior that cannot be proven must be marked
```
UNKNOWN
```
or
```
REVIEW_REQUIRED
```
.
Expected Result must not be weakened merely to obtain a
```
PASS
```
.
Project-wide Standards are stored in
```
standards/
```
.

Verify Only

The first phase prohibits automatic modification of the Target. When differences are discovered, first preserve the Evidence and classify it; after confirming that the difference is a

MIGRATION_DEFECT

, the Human Gate determines whether to create an independent

CHANGE

for remediation and Re-Verify.

Evidence-Guided Q&A

Parse the interactive-review, question-schema, approval-gate, and terminology from the single official source under

adf-project-install/references/

, and follow their rules. If the source is missing or version-incompatible, stop any phase that requires Review; do not maintain a local copy.

v5.1 Resource and Legacy Project Compatibility

The sole authoritative location for official resources is
```
adf-project-install/references/resources.json
```
; do not copy them into the project’s
```
.adf/templates/
```
directory or use custom templates.
Parse sources from the project’s
```
.agents/skills/
```
or
```
.claude/skills/
```
; the installed Skill’s
```
scripts/project.mjs resolve <project> <resource-key>
```
may be used. If the versions or content conflict between the two locations, stop and do not fall back to the global location.
If the Skill that provides the official resources is not installed or is version-incompatible, prompt the user to install the applicable official version at the project level using
```
npx skills
```
. Review cannot be skipped.
First read the project’s
```
standards/
```
and approved Evidence; examples in the official specification are not project-approved standards and are not automatically applied.
Retain v5.0 Module documents, completion statuses, and approval records; fields or documents missing from the new version are listed as follow-up recommendations, and approvals are not automatically revoked. Any follow-up work must go through a separate
```
CHANGE
```
.
For legacy Modules that have not yet adopted the new Gate, list only Functional Scenario or specification differences; check the new-version requirements only for newly adopted work.