---
description: Plan LazyClaude work with explicit goal, Dynamic workflow, and QA criteria.
argument-hint: '<planning brief>'
---

Use the `ulw-plan` skill for the user's current planning brief or command
arguments.

The plan must include Claude Code-native bootstrap steps:

- If model-facing goal tools are exposed, use `get_goal`, `create_goal`, and
  delayed `update_goal` exactly as native goal state, not as slash-command text.
- If goal tools are unavailable, include the exact user-visible `/goal`
  completion condition to bind before execution.
- For independent, risky, parallel, or long-running work, include when Claude
  should call the `Workflow` tool and how each lane proves its evidence.
- For isolated edit lanes, include when to use `EnterWorktree`; if only the CLI
  surface is available, include `claude --worktree <short-name> --tmux`, plus
  evidence paths and cleanup.

Write the plan under `plans/` and keep it executable: concrete files, tests,
manual QA, cleanup, and publish/remote-mutation guardrails.
