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\".
How to install resolve-findings?
tobihagemann/turbo/resolve-findings
$npx -y skills add tobihagemann/turbo --skill resolve-findingsInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/tobihagemann/turbo" --skill "tobihagemann/turbo/resolve-findings"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/tobihagemann/turbo" that are relevant to the current task. Run `npx skills add "https://github.com/tobihagemann/turbo"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- gpt-image-2Create or edit images with Pilio GPT Image 2 through the unified Pilio developer API.Jul 2026
- spec-driven-implementationDrive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs…Jul 2026
- review-prReview a pull request diff and write structured feedback to review.json for the workflow to publish.Jul 2026
- write-product-specWrite a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation.Jul 2026
- write-tech-specWrite a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints.Jul 2026
- fix-errorsFix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests.Jul 2026
