Turbo resolve-findings

Choose an implementation path (trivial or standard) for evaluated findings and dispatch it. Trivial path applies fixes directly; standard path runs /turboplan. Use after /evaluate-findings has tagged findings and they need to be implemented, or when the user asks to \"resolve findings\", \"apply evaluated findings\", or \"dispatch findings to implementation\".

install

source · Clone the upstream repo

git clone https://github.com/tobihagemann/turbo

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/tobihagemann/turbo "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/resolve-findings" ~/.claude/skills/tobihagemann-turbo-resolve-findings && rm -rf "$T"

manifest: skills/resolve-findings/SKILL.md

Resolve Findings

Choose a path for evaluated findings and run it. Trivial path applies fixes directly; standard path runs

/turboplan

Task Tracking

At the start, use

TaskCreate

to create a task for each step:

Choose path
Run the chosen path

Step 1: Choose Path

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:

Standard — Run
```
/turboplan
```
for drafting, refinement, approval, implementation, and finalize
Trivial — Apply directly via
```
/apply-findings
```
, then
```
/finalize
```

Suggest Standard when findings include complex or architectural changes. Suggest Trivial when all findings are mechanical fixes.

Step 2: Run the Chosen Path

Read the reference file for the confirmed path and follow its phases:

Trivial path — references/trivial-path.md
Standard path — references/standard-path.md

State the chosen path before continuing with the reference file.

Then use the TaskList tool and proceed to any remaining task.