| name | zl-verify-work |
| description | Zhulong public work verification command for Codex. Use when the user invokes $zl-verify-work or asks Zhulong Project Intelligence Kit to verify completed work with task/source evidence, optional documents, code-map checks, test/build/manual validation, risk notes, rollback, and evidence writeback. |
Zhulong Verify Work
This is the Codex runtime entrypoint for $zl-verify-work.
Invocation
- Treat all user text after
$zl-verify-work as ZL_ARGS.
- Preserve
$zl-verify-work in user-facing notes.
- Treat GSD commands such as
$gsd-verify-work as reference design only.
- When suggesting next commands to the user, suggest
zl-* commands, never
$gsd-* commands.
Required Flow
- Resolve the project root from the current working directory.
- Run the deterministic Zhulong preflight:
{{ZL_CLI}} workflow run verify-work --target "$PWD" "<ZL_ARGS>"
- Read the generated verification context packet and handoff under
.planning/context/.
- Confirm the claimed change against the request, active records, source files,
code-map impact, tests, build checks, logs, and manual checks. Query optional
documents when present; use
zl-docs-query --rag only when rag_backend is
not none and the backend is approved.
- Follow
core/workflows/verify-work.md as the Zhulong native workflow contract.
- If structural relationships changed and direct graph refresh is approved,
run
zl-graph-build --run and inspect zl-graph-diff.
- Record durable evidence with
zl-evidence-record, including remaining
risk and rollback notes. Use --writeback, --issue, --debug, or
--phase when a backend record exists.
- Clearly state what was verified, what was not verified, and what remains
risky.
Fallback
GSD is reference design only. Verify inline using the Zhulong packet and write
evidence under .planning/evidence/.
