Skip to content
Development
Skill

/resolve-open-items

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\".

From plugin
turbo
42074 skills

Claude Code

$ npx -y skills add tobihagemann/turbo --skill resolve-open-items --agent claude-code

SKILL.md

resolve-open-items.SKILL.md
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\"."

Resolve Open Items

Settle each open item with one question per item, acting on every answer before the next round.

Step 1: List the Open Items

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.

Step 2: Settle Each Item

Use `AskUserQuestion`, one question per item in the order `list` returns them, filling each call to its four-question limit:

  • **Header** — `#<id>`
  • **Question** — the item's line, plus whatever its detail adds that the answer depends on
  • **Options** — at most four, by the kind of item. Give each option a description saying what choosing it does and what it gives up.
  • **Decision**, where the detail names choices. Fill the four options in this order and leave out whatever does not fit:

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".

  • **Action**, where only the user can do it: **Done**, **Not yet**, and **Note for later**.
  • **Open question**, an item with no listed choices: the answers the conversation supports, then **Not yet** and **Note for later**, leaving out whatever does not fit and naming it in the question as available under "Other". When the conversation supports no answer, invite it 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.

  • **A choice** — carry it out, then call the tool with `action` set to `resolve` and the item's `id`.
  • **Done** — the user already did it. Acknowledge it and resolve the item without repeating the action.
  • **Note for later** — run the `/backlog` skill with the item. Resolve the item only when that skill wrote the entry. When it could only print the entry, leave the item open and say so.
  • **Not yet** — leave the item open.
  • **Get a second opinion** — run the `/consult-codex` skill. On a technical choice, ask for the soundest choice on technical merit alone, independent of how closely it conforms to the original scope, and carry any scope cost back with the answer. On a question of product intent, ask what each choice commits to, what reversing it costs, and what the prevailing convention is. Then ask about that item again with the answer in hand.
  • **An instruction or a question** — act on it. When that settles the item or makes it moot, resolve it. Ask about it again only while it stays open.

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.

Step 3: Report

Output, by `#<id>`, what was settled and what stays open. Then use the TaskList tool and proceed to any remaining task.

Read more
@tobihagemann
Ships withturbo

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.

Stars on GitHub

Momentum

stars in total
420
Star history of tobihagemann/turbo on GitHub, a chart by star-history.com

Other skills on turbo.

apply-turbo-handoffs

apply-turbo-handoffs

Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…

@tobihagemann@tobihagemannInstall Skill
apply-findings

apply-findings

Apply accepted review findings as code changes, escalating ambiguous ones to the user. Use when the user asks to \"apply…

@tobihagemann@tobihagemannInstall Skill
assess-technical-debt

assess-technical-debt

Assess project-wide technical debt (hotspots, deprecated APIs, duplication, low-value tests) into a ranked report. Use when the…

@tobihagemann@tobihagemannInstall Skill
backlog

backlog

Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user…

@tobihagemann@tobihagemannInstall Skill
code-style

code-style

Enforce existence, reuse, mirror, and symmetry principles so new code stays minimal and consistent. Use when writing, changing,…

@tobihagemann@tobihagemannInstall Skill

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills2w309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react6d252k
@facebook@facebookInstall Skill

Questions about resolve-open-items.

Which coding agents can use resolve-open-items?
resolve-open-items installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.