---
name: kd-verify
description: Kingdee Harness Engineering verification phase for build, tests, checks, UAT evidence, and residual risk.
---

# Kingdee Verify Phase

Use this skill after implementation.

Goal:

- Run planned validation commands.
- For Cangqiong/Xinghan/Flagship Java projects, run the planned Gradle command to catch syntax/compile errors, for example `.\gradlew.bat build`, `./gradlew build`, or a narrow `:module:build` task.
- For C#/Enterprise projects, run `dotnet build` or `dotnet build <.sln/.csproj>` to catch syntax/compile errors.
- Run `kd_check` when code is available.
- Record the completed validation command through `kd_verify_result` with the real command, exit code, and useful output summary.
- Record failures, fixes, skipped checks, and residual risk.

Rules:

- Passing unit tests is not enough if acceptance criteria require workflow behavior.
- If validation cannot run, state the exact blocker.
- Do not hand-edit `VERIFY.md` as the primary result path; `kd_verify_result` owns pass/failure evidence and the repair loop.
- Do not ship while verification evidence is missing.
- Do not convert skipped external/BOS/manual validation into a pass. Record user-provided evidence source, test data, environment, and result.
- If validation fails, keep the run in the repair loop; do not summarize delivery or mark residual risk as low.