---
description: Verify and run LazyClaude Dynamic workflow delegation.
argument-hint: '<objective>'
---

Use the `ulw-loop` skill for the user's current objective, with this
Dynamic-workflow bootstrap first.

1. Inspect native goal state when model-facing tools are exposed: call
   `get_goal`, call `create_goal` only when no matching active goal exists, and
   reserve `update_goal` for verified completion or a genuine blocker. If only
   the user-visible goal surface is available, ask for one exact
   `/goal <completion condition>` instead of claiming LazyClaude set it.
2. Run `lazyclaude-ai workflow-check --json` when the package CLI is available.
   Treat a failing check as BLOCKED until the missing route, command, or
   subagent delegation surface is fixed.
3. For broad, risky, parallel, or long-running work, call the `Workflow` tool
   when Claude Code exposes it. Bind each lane to success criteria, evidence
   artifacts, and cleanup receipts.
4. Use subagent delegation where available:
   - `prometheus-planner` for read-only planning and dependency ordering.
   - `boulder-executor` for implementation against a checked plan.
   - `oracle-verifier` for evidence and acceptance verification.
   - `qa-runner` for tmux/manual-QA scenarios and cleanup receipts.
   - `quality-reviewer` for code-quality and security findings.
   - `librarian-researcher` for local-first context mining.
5. For isolated edit lanes, use `EnterWorktree` when exposed. If only the CLI
   surface exists, use or recommend `claude --worktree <short-name> --tmux`.

Do not auto-type `/goal`, do not echo or execute prompt text, and do not mutate
remote state. Continue through the normal LazyClaude evidence loop:
`PIN -> RED -> GREEN -> VERIFY -> SURFACE -> REVIEW -> CLEAN -> RECORD`.
