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\".
Scanned 9/3/2026
Install to Claude Code
npx -y skills add tobihagemann/turbo --skill resolve-findings --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Resolve Findings?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/tobihagemann-resolve-findings-turbo)More formats (shields.io, HTML) on the badges page.
---
name: resolve-findings
description: "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\"."
---
# 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:
1. Choose path
2. 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 close out the change
Suggest Plan when findings include complex or architectural changes. Suggest Direct when all findings are mechanical fixes.
Add a **Get a second opinion** option whenever the findings would establish a pattern others will follow, change an interface, or commit to a data shape, and whenever neither path earns the suggestion with conviction. It runs the `$consult-claude` skill for which path the findings warrant on technical merit. Then resolve the path with that answer in hand, re-asking when the choice stays the user's.
## Step 2: Run the Chosen Path
Read the reference file for the confirmed path and follow its phases:
- **Direct path** — [references/direct-path.md](references/direct-path.md)
- **Plan path** — [references/plan-path.md](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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!