apply-turbo-handoffs
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Walk the open items listed above the prompt and settle each through AskUserQuestion. Use when the user asks to \"resolve open items\", \"walk the open items\", or \"what's waiting on me\".
Claude Code
$ npx -y skills add tobihagemann/turbo --skill resolve-open-items --agent claude-code
Codex
$ npx skills add tobihagemann/turbo --skill resolve-open-items -a codex -y
Cursor
$ npx skills add tobihagemann/turbo --skill resolve-open-items -a cursor -y
Gemini CLI
$ npx skills add tobihagemann/turbo --skill resolve-open-items -a gemini-cli -y
GitHub Copilot
$ npx skills add tobihagemann/turbo --skill resolve-open-items -a github-copilot -y
OpenCode
$ npx skills add tobihagemann/turbo --skill resolve-open-items -a opencode -y
Windsurf
$ npx skills add tobihagemann/turbo --skill resolve-open-items -a windsurf -y
name: resolve-open-items description: "Walk the open items listed above the prompt and settle each through AskUserQuestion. Use when the user asks to \"resolve open items\", \"walk the open items\", or \"what's waiting on me\"."
Settle each open item with one question per item, acting on every answer before the next round.
Call the `mcp__turbo__open-items` tool with `action` set to `list`. When it answers that there are no open items, present "No open items." Then use the TaskList tool and proceed to any remaining task.
Use `AskUserQuestion`, one question per item in the order `list` returns them, filling each call to its four-question limit:
1. The choice the detail recommends, with "(Recommended)" appended and the reason in its description. When no choice earns it with conviction, the most likely choice, unlabeled. 2. **Get a second opinion**, when the decision is costly to reverse (it establishes a pattern others will follow, defines an interface, commits to a data shape, or imports a pattern the codebase has not used) or no choice earns "(Recommended)" with conviction. Leave it out when asking about an item again after a consultation. 3. The other choices, most likely first. 4. **Not yet**, then **Note for later**.
End the question by naming each choice or deferral left out as available under "Other".
After each call, act on its answers before the next call. An answer given under "Other" that names a choice, "not yet", or "note for later" takes that option's branch.
Before the next call, resolve any unasked item that earlier answers settled or made moot, and leave it out of the call. Repeat until no item remains to ask. Then call the tool with `list` again, and settle any item it shows that this walk has not asked about, except an action this walk itself added, which stays open.
Output, by `#<id>`, what was settled and what stays open. Then use the TaskList tool and proceed to any remaining task.
A human-gated agentic software factory for Claude Code and Codex: you decide what to build and judge the result; skills shape, build, polish, ship, and learn.
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Apply accepted review findings as code changes, escalating ambiguous ones to the user. Use when the user asks to \"apply…
Assess project-wide technical debt (hotspots, deprecated APIs, duplication, low-value tests) into a ranked report. Use when the…
Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user…
Shared changelog conventions and formatting rules. Not typically invoked directly.
Enforce existence, reuse, mirror, and symmetry principles so new code stays minimal and consistent. Use when writing, changing,…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.