| name | zl-execute-phase |
| description | Zhulong phase execution workflow grounded in task state, source/test evidence, optional documents, code-map impact, and evidence writeback. |
Zhulong Execute Phase
Use this when the user invokes /zl-execute-phase or asks Zhulong to execute a
planned change.
Treat the user text after /zl-execute-phase as the execution request.
Required Flow
-
From the repository root, run:
{{ZL_CLI}} workflow run execute-phase --target . "$ARGUMENTS"
-
Read the generated .planning/context/*execute*.md packet and handoff.
-
Read active phase, issue, debug, and plan records before editing.
-
Verify expected behavior from the plan, active records, source, and tests.
Query local documents only when relevant sources exist; use RAG only when
rag_backend is not none and the backend is approved.
-
Verify likely impact with code-map artifacts before editing. Refresh the graph
with {{ZL_CLI}} graph build --target . --run only when direct graph
execution is approved for the project.
-
Implement the smallest coherent change, following the existing project style.
-
Run focused tests and any required build, lint, typecheck, or manual checks.
-
If code structure changed and direct graph execution is approved, run:
{{ZL_CLI}} graph build --target . --run
{{ZL_CLI}} graph diff --target . --details
-
Record evidence with {{ZL_CLI}} evidence record --target . ... --writeback <active-record>.
-
Follow core/workflows/execute-phase.md and execute inline with the same
gates.
Keep the user-facing workflow name /zl-execute-phase. When suggesting next
commands to the user, suggest /zl-* commands, never /gsd-* commands.
