| name | zl-plan-phase |
| description | Zhulong native phase planning workflow with task/source evidence, optional documents, code-map context, planning, and verification gates. |
Zhulong Plan Phase
Use this when the user invokes /zl-plan-phase or asks Zhulong to plan a phase.
Treat the user text after /zl-plan-phase as the planning request.
Required Flow
-
From the repository root, run:
{{ZL_CLI}} workflow run plan-phase --target . "$ARGUMENTS"
-
Read the generated .planning/context/*plan*.md packet and handoff.
-
Confirm current project state in .planning/STATE.md, .planning/ROADMAP.md,
and active phase or issue records.
-
Confirm requirements from the request, active records, source, and tests.
Query local documents only when relevant sources exist; use
{{ZL_CLI}} docs query --target . --rag "<question>" only when
rag_backend is not none and the backend is approved.
-
Query code-map context for likely impact areas:
{{ZL_CLI}} graph status --target .
{{ZL_CLI}} graph query --target . "<module or symbol>"
-
Follow core/workflows/plan-phase.md and create the plan inline while
preserving Zhulong evidence and verification gates.
-
Write planning decisions, source references, risks, and open questions back
to the relevant .planning/phases/ or .planning/issues/ record.
Keep the user-facing workflow name /zl-plan-phase; GSD is reference design
only. When suggesting next commands to the user, suggest /zl-* commands,
never /gsd-* commands.
