mcpbeat

Resolve Findings

tobihagemann/turbo-resolve-findings

Choose 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\", \"apply evaluated findings\", or \"dispatch findings to implementation\".

673 tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
398
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/tobihagemann/turbo --skill resolve-findings

The instruction itself

4 sections, as written by the author

Resolve Findings

Choose a path for evaluated findings and run it. Direct path applies fixes directly; plan path runs $turboplan.

Task Tracking

At the start, use update_plan to track each step, restating any remaining steps of a parent workflow alongside them:

  • 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 request_user_input to let the user choose:

  • Plan — Run $turboplan for drafting, refinement, approval, implementation, and finalize
  • Direct — Run $apply-findings, then $finalize

Suggest Plan when findings include complex or architectural changes. Suggest Direct when all findings are mechanical fixes.

Step 2: Run the Chosen Path

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

  • Direct path — references/direct-path.md
  • Plan path — references/plan-path.md

State the chosen path before continuing with the reference file.

Then call update_plan to mark this step completed and continue with the next step of the active workflow.

How to use it

Copy the folder

Take tobihagemann/turbo-resolve-findings from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.