phxwork

# Work Execute tasks from a plan file with checkpoint tracking and verification. ## Usage ``` /phx:work .claude/plans/user-auth/plan.md /phx:work .claude/plans/user-auth/plan.md --from P2-T3 /phx:work --skip-blockers /phx:work # Resumes most recent plan ``` ## Arguments - `<plan-file>` -- Path to plan file (optional, auto-detects recent) - `--from <task-id>` -- Resume from specific task (e.g., `P2-T3`) - `--skip-blockers` -- Continue past blocked tasks - `--continue` -- Resume IN_PROGRESS plan from checkboxes ## Iron Laws (NON-NEGOTIABLE) 1. **NEVER auto-proceed** to /phx:review or any next workflow phase -- always ask the user what to do next 2. **AUTO-CONTINUE between plan phases** -- when Phase N completes, immediately start Phase N+1. Do NOT stop or ask for permission between phases. Only stop at BLOCKERS or when ALL phases are done. 3. **Plan checkboxes ARE the state** -- `[x]` = done, `[ ]` = pending. No separate JSON state files. Resume by reading the plan. 4. **Verify after EVERY task** -- never skip verification 5. **Max 3 retries then BLOCKER** -- don't keep retrying forever 6. **Stage specific files** -- never use `git add -A` or `git add .` 7. **Read scratchpad BEFORE implementing** -- scratchpad has dead-ends and decisions that prevent rework. Step 2 is not optional. 8. **Clarify ambiguous tasks** -- ask the user rather than guessing when a plan task's intent is unclear ## Step 1: Research Decision Ask the user for plans with >3 tasks:...