adf-result-normalization

Original：🇨🇳 Chinese

Translated

Transform different representations into comparable semantic results based on approved MIG-*.

2installs

Sourcechungtsai/adf-framework

Added on2026-10-02

NPX Install

npx skill4agent add chungtsai/adf-framework adf-result-normalization

SKILL.md Content (Chinese)

View Translation Comparison →

ADF Result Normalization

Purpose

Only APPROVED Migration Rule may participate in Normalization; Normalization must not be used to conceal genuine Business Difference.

ADF Common Invariants

Work Type may only use
```
NEW
```
,
```
CHANGE
```
, and
```
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-*
```
.
Behavior that cannot be proven must be marked as
```
UNKNOWN
```
or
```
REVIEW_REQUIRED
```
.
Expected Result must not be weakened to obtain a
```
PASS
```
.
Project-wide Standards are stored in
```
standards/
```
.

Evidence-Guided Q&A

Parse the single official source under

adf-project-install/references/

, including interactive-review, question-schema, approval-gate, and terminology, and follow its rules. If the source is missing or its version is incompatible, stop any Stage that requires Review; do not maintain a local copy.

v5.1 Resources and Legacy Project Compatibility

The sole location of official resources is defined by
```
adf-project-install/references/resources.json
```
; do not copy them to the project’s
```
.adf/templates/
```
or use custom templates.
Resolve sources from this project’s
```
.agents/skills/
```
or
```
.claude/skills/
```
. The installed Skill’s
```
scripts/project.mjs resolve <project> <resource-key>
```
command may be used. If the versions or content of the two locations conflict, stop; do not fall back to global resources.
If the official resource source Skill is not installed or its version is incompatible, prompt the user to install the applicable official version at the project level using
```
npx skills
```
. Review cannot be skipped.
Read the project’s
```
standards/
```
and approved Evidence first; examples in official standards are not project-approved standards and are not applied automatically.
Retain v5.0 Module documentation, completion status, and approval records. Fields or documentation missing from the new version should be listed as remediation recommendations and must not automatically revoke approvals. Remediation must follow the separate CHANGE process.
For legacy Modules that have not adopted the new Gate, list only Functional Scenario or specification differences. Check new-version requirements only for work that has explicitly adopted them.