---
description: Execute a checked plan with LazyClaude start-work discipline.
argument-hint: '<plan-file>'
---

Use the `start-work` skill for the user's current plan file or command
arguments.

Before the first checkbox, bootstrap Claude Code-native workflow state:

- Use `get_goal` and `create_goal` only if model-facing goal tools are exposed.
- If goal tools are unavailable, ask the user to set a native `/goal` completion
  condition for the plan before multi-turn execution.
- For broad, risky, parallel, or long-running checkbox waves, call the
  `Workflow` tool when Claude Code exposes it.
- For isolated edit lanes, use `EnterWorktree` when exposed; otherwise launch
  or recommend `claude --worktree <short-name> --tmux`.

Then execute the first unchecked top-level checkbox with failing-test-first
implementation, automated verification, manual QA evidence, cleanup receipts,
and ledger updates.

For that checkbox, enforce `PIN -> RED -> GREEN -> VERIFY -> SURFACE -> REVIEW
-> CLEAN -> RECORD`:

- PIN the plan objective, selected checkbox, stale state, dirty worktree
  boundaries, resume checkpoint, commit/push approval, and publish approval.
- RED first for behavior changes, then GREEN with targeted and plan-level tests.
- SURFACE through the plan's Manual-QA channel with an artifact path.
- REVIEW broad, risky, shared, security-sensitive, or release-facing changes.
- CLEAN with bounded cleanup receipt for tmux sessions, servers, ports, browser
  contexts, temp directories, and child processes.

Stop rules: stop on malformed plan structure, missing acceptance criteria,
missing Manual-QA or cleanup requirements, contradictory live state, or
unapproved commit/push or publish.
