implement-plan

# Implement Plan Execute an implementation plan file. ## Task Tracking At the start, use `TaskCreate` to create a task for each step: 1. Resolve and read the plan file 2. Run `/code-style` skill 3. Read relevant files and load task-specific skills 4. Execute implementation steps 5. Run `/finalize` skill ## Step 1: Resolve and Read the Plan File Determine which plan file to implement using these rules in order: 1. **Explicit path** — If an absolute or relative path was passed, use it 2. **Explicit slug** — If a slug was passed (e.g., `add-image-cache`), resolve to `.turbo/plans/<slug>.md` 3. **Single file** — Glob `.turbo/plans/*.md`, excluding shell files (see shell detection below). If exactly one non-shell file exists, use it 4. **Most recent** — If multiple non-shell files exist, use the most recently modified 5. **Legacy fallback** — If `.turbo/plans/` does not exist but `.turbo/plan.md` exists, use it 6. **Nothing found** — If no plan file exists, tell the user to run `/turboplan` (for a new task) or `/pick-next-prompt` (for an existing prompt plan) and stop If multiple files exist and the most-recent choice is non-obvious (e.g., several plans were modified within the same minute), use `AskUserQuestion` to let the user pick from the candidates. ### Shell Detection A file is a **shell** when it contains `## Produces`, `## Consumes`, and `## Covers Spec Requirements` AND does NOT contain `## Pattern Survey`. If the resolved file is a shell, halt with: > `<path>...