- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill discuss-change -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill discuss-change -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill discuss-change -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill discuss-change -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/tobihagemann/turbo/tree/HEAD/claude/skills/discuss-changeFrom the publisher
Escalate open decisions, agree on the implementation shape, then implement.
Use TaskCreate to create a task for each step:
/implement skillAbsorb the request without interrupting. Take the task from the user's request, or from conversation context when the task was already established. Restate the goal in one or two sentences and confirm.
Identify product or design decisions the request did not resolve. Escalate these via AskUserQuestion before any code is written. Read the code the change would touch before judging whether a bullet matches. Skip when no bullet below matches the change.
Escalate when:
Do not escalate technical decisions the agent can make autonomously: which data structure, which existing pattern to follow, internal implementation approach. The boundary is product intent.
Confirm external constraints before escalating. When an option depends on a third-party API, service, or platform behaving a particular way, query documentation MCP tools (or WebSearch as a fallback) and drop the option unless current documentation confirms that behavior.
Look up a named precedent before escalating. When the request, or a document it points to, names a precedent the change is meant to follow, such as an existing product, a protocol, or a standard, look up how it behaves on the points the change touches, and frame options against what the lookup found. Mark as unverified only a claim about it that the lookup could not settle.
Observe existing surfaces before escalating. When an option concerns how an existing surface looks, observe it as it currently renders, by running the app from the current code, or from a screenshot requested from the user, and drop any option its rendered state rules out.
Read the code an option's benefit lands in before escalating. When an option is justified by what it lets code outside the change do, such as the caller of an interface or the consumer of an output, or by what it does for data already stored, read that code, or every path that has written that data, and follow the benefit through what you read. Confirm the code or data needs what the option provides and does not already get it another way. Drop a benefit the reading does not bear out.
Apply the UX lens before escalating. When a decision concerns what the software does for the person using it, including a default, a control, or a setting in a public interface, run the /user-experience skill on it first, and state each option as the behavior that person gets and the goal it serves. For software that other code consumes, that person is the developer integrating it and the user behind them. Leave the mechanism behind each behavior to Step 3.
Output what is at stake as text first, even when the reading it came from is fresh in this conversation. When the decision turns on a failure or misuse scenario, that means the invariant the change would protect, what makes that scenario reachable given the existing guards, whether that scenario has been observed or is derived from reading, and the failure modes the new guard itself adds. Establish that reachability by tracing every path that can produce the state the scenario needs, including the code's inputs, its public interface, and data already stored, rather than inferring it from the proposed guard's purpose. When no path can produce that state and the scenario has never been observed, drop it as grounds for any option. When the scenario has never been observed, offer leaving the guard out as one of the options. Then use AskUserQuestion to present the decision as a concise trade-off with options. Keep each option's description to the decision being asked and its trade-off. When an option would also commit to a design choice the question does not ask about, ask that choice on its own or state it in the shape Step 4 confirms. Mark the strongest option "(Recommended)" and place it first. Treat the work of departing from the codebase's existing structure as a cost to state beside the option that incurs it, with no bearing on which option is strongest.
Offer a Get a second opinion option whenever 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), and whenever no option earns "(Recommended)" with conviction. It runs the /consult-codex skill for what each option commits to, what reversing it costs, and what the prevailing convention is. Hold the concrete options to three so the question stays within the four-option limit. Then resolve the decision with that answer in hand, re-asking when the choice stays the user's.
Interview the user about the implementation shape until you reach shared understanding. Use AskUserQuestion in rounds: put every question whose answer depends on nothing still open into one call, up to its four-question limit, and hold a question that depends on an open answer for a later round. Cover whichever of these matter for the task. Do not present a rigid checklist. Skip when the request and the resolved decisions already name the files to touch, the existing code to build on, and the tests to write.
/consult-codex skill for the soundest answer on technical merit alone, independent of the task's original scope; on a question of product intent, run it for what each answer commits to and what reversing it costs. Then resolve the question with that answer in hand, re-asking when the choice stays the user's./prototype skill on that unknown, then asks the question again with the prototype in hand./user-experience skill on it before framing options, and state each option as the behavior that person gets and the goal it serves. For software that other code consumes, that person is the developer integrating it and the user behind them.Output the agreed shape as text, short enough to read at a glance: what the change does, where it lands, the decisions resolved in Steps 2 and 3, how to tell it worked, and anything deliberately deferred. Label any consistency or durability machinery the shape adds (a lease, lock, queue, versioning scheme, or new persistent entity) as machinery. For each, name the stated requirement or user decision that demands it, or say that none does, and state what dropping it would give up. For each deferred item, including an addition the user declined earlier, state the user story it serves, or what it simplifies when it is a technical item, and recommend noting it for later or dropping it. Recommend noting only an item that serves a goal the person using the software actually has or that simplifies existing code. This text is the change description Step 6 implements, so keep it concrete enough to act on. Before outputting it, confirm each claim the shape makes about how existing code behaves, such as what a mechanism covers, which inputs reach it, or which dependents exist, by reading the code that decides it rather than its comment or name. Drop a claim the reading does not bear out, or re-ask the decision that rests on it.
Close with how to reply: approve the shape as settled, or describe what to change. When the shape defers items, add that an approval notes the ones recommended for noting and drops the rest, and can flip any of them. When an unknown that only a built artifact settles is still open, also offer prototyping it first, and recommend that over approving, since a surface or interaction pattern that is still unproven cannot be judged from the shape description.
Then end the turn.
/prototype skill, then fold what it settled into the shape. Then confirm each claim the revised shape newly makes about existing code as Step 4 does, re-present it, close with Step 4's reply guidance, and end the turn again./backlog skill once for each deferred item settled as noted. Once every such item is noted, continue to Step 6./implement SkillRun the /implement skill. The shape the user approved is the change it applies.
Then use the TaskList tool and proceed to any remaining task.
/turbo:plan for plan mode.Align on the shape of a change through an interview, then implement it. Use when the user asks to \"discuss this change\", \"ask me questions first\", or \"agree on the approach before coding\".
---name: discuss-changedescription: Align on the shape of a change through an interview, then implement it. Use when the user asks to \"discuss…---# claude/skills/discuss-change/SKILL.mdFAQ
Download claude/skills/discuss-change/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/tobihagemann/turbo.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.