| name | zl-plan-phase |
| description | Zhulong native phase planning command for Codex. Use when the user invokes $zl-plan-phase or asks Zhulong Project Intelligence Kit to plan work with task/source evidence, optional documents, code-map context, verification expectations, and evidence writeback. |
Zhulong Plan Phase
This is the Codex runtime entrypoint for $zl-plan-phase.
Invocation
- Treat all user text after
$zl-plan-phase as ZL_ARGS.
- Preserve
$zl-plan-phase in user-facing notes.
- Treat GSD commands such as
$gsd-plan-phase 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 plan-phase --target "$PWD" "<ZL_ARGS>"
- Read the generated plan context packet and handoff under
.planning/context/.
- Confirm requirements, scope, acceptance criteria, API, data, UI, and test
assumptions from the request, active records, source, and tests. Query local
documents only when relevant sources exist; use
zl-docs-query --rag only
when rag_backend is not none and the backend is approved.
- Check code-map context for likely impacted entry points, modules, coupling,
and risky areas.
- Follow
core/workflows/plan-phase.md as the Zhulong native workflow contract.
- Produce a plan that names evidence, impact surface, verification commands,
risks, rollback strategy, and follow-ups.
- Record durable evidence or planning decisions when the phase plan materially
changes project direction. Use
--writeback or --phase when a phase
record exists.
Fallback
GSD is reference design only. Continue inline using the Zhulong packet and write the
plan into the relevant .planning/phases/ or issue record.
