$npx -y skills add tobihagemann/turbo --skill resolve-findingsChoose an implementation path (direct or plan) for evaluated findings and dispatch it. Direct path applies fixes directly; plan path runs /turboplan. Use after /evaluate-findings has tagged findings and they need to be implemented, or when the user asks to \"resolve findings\", \
| 1 | # Resolve Findings |
| 2 | |
| 3 | Choose a path for evaluated findings and run it. Direct path applies fixes directly; plan path runs `/turboplan`. |
| 4 | |
| 5 | ## Task Tracking |
| 6 | |
| 7 | At the start, use `TaskCreate` to create a task for each step: |
| 8 | |
| 9 | 1. Choose path |
| 10 | 2. Run the chosen path |
| 11 | |
| 12 | ## Step 1: Choose Path |
| 13 | |
| 14 | Present a summary of accepted findings (Apply verdict): count by complexity (mechanical fixes vs. architectural or design changes). Then use `AskUserQuestion` to let the user choose: |
| 15 | |
| 16 | - **Plan** — Run `/turboplan` for drafting, refinement, approval, implementation, and finalize |
| 17 | - **Direct** — Run `/apply-findings`, then `/finalize` |
| 18 | |
| 19 | Suggest Plan when findings include complex or architectural changes. Suggest Direct when all findings are mechanical fixes. |
| 20 | |
| 21 | ## Step 2: Run the Chosen Path |
| 22 | |
| 23 | Read the reference file for the confirmed path and follow its phases: |
| 24 | |
| 25 | - **Direct path** — [references/direct-path.md](references/direct-path.md) |
| 26 | - **Plan path** — [references/plan-path.md](references/plan-path.md) |
| 27 | |
| 28 | State the chosen path before continuing with the reference file. |
| 29 | |
| 30 | Then use the TaskList tool and proceed to any remaining task. |