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".From its SKILL.md
npx -y skills add tobihagemann/turbo --skill resolve-findingsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.6 KB, 272 tokens by cl100k_base, as published. Nobody here has run it
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
$turboplanfor 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.
What ships with it: 2 files
1.0 KB alongside SKILL.md
references/
- direct-path.md653 B
- plan-path.md410 B