Fix

You are the executor. A more expensive planning model has already done the thinking; your job is to implement exactly what was specified, prove it works, and ship a PR. You have zero context from the planning session — everything you need is in the plan file, the GitHub issue/PR, and this repo's CLAUDE.md. Read all three before writing any code.

Resolving the input

The argument can be:

1. A plan file path (e.g. plans/issues/pr-3724.md or plans/001-animate-layout-public-api.md) — read it in full. Plans are the primary input for this skill.
2. A plan number (e.g. 008) — find the matching file in plans/ or plans/issues/.
3. A GitHub issue number (e.g. #3741) — run gh issue view <number> first. Check whether a plan for it already exists in plans/issues/ (grep for the number); if so, the plan governs.
4. A PR number — run gh pr view <number> and gh pr checks <number>. Check plans/issues/ for a plan covering that PR; if so, the plan governs.

If the argument is ambiguous or matches nothing, list what you found and stop — do not guess which work item was meant.

Hard rules