do-it-for-me

do-it-for-me (difm)

The user is telling you to stop handing a step back and do it yourself. It usually fires right after you reported a block ("denied", "needs your approval") or offered a command for the user to run.

When this fires

• The keyword difm or do it for me, bare or slashed.
• Close variants aimed at a step you just reported blocked or handed back: "you run it", "run it yourself".

What it grants

Authority to run the specific step that was just blocked or handed back. Each new blocked step needs its own difm. It does not lift the prohibited-action rules.

Procedure

1. Name the step in one clause: the exact command or action.
2. Run it as one command, exactly as before. A classifier denial is a sample, not a wall. The mechanics and limits are in ask-for-manual-approval: retry the identical command once, never rephrased.
3. If it is denied again, turn auto mode off for this step, when the switch conditions hold. Check the switch conditions in ask-for-manual-approval's "When to switch or ask" first: a dispatched subagent reports up its dispatch chain instead, and in an away session, or a CI or @claude run, record a pending decision instead. For a merge, an action any allow route in that section covers, or one where the settings files and hooks that apply do not let you tell, never switch yourself: ask the user to switch out of auto mode. Otherwise, when mcp__ccd_session_mgmt__set_session_permission_mode is available, read the original mode with mcp__ccd_session_mgmt__get_session, switch the session to default, and run the command once. Restore the original mode right after that one step, even if a command failed or timed out: difm covers one step, so the stretch that ask-for-manual-approval's "Say when it is over" ends is that step alone. When that tool is not available, ask the user to switch out of auto mode, naming the refused command and its stated reason. When you asked the user to switch, tell them right after the step that they can switch back. The self-switch, the stop conditions, and the managed-settings exception are in ask-for-manual-approval. How a standing grant interacts with a denial is in default-to-action-grants.
4. Verify and report in the past tense: what ran, the read-back or exit status, and, when you switched modes yourself, that the original mode was restored. Count attempts honestly: "denied N times, succeeded on run N+1", never "cannot".

What it does not grant

• A standing change to permission mode: auto mode is off for one step only.
• A wider step: same command, same target, nothing extra.
• Edits to settings files or allow rules: ask the user to add one if it would help.

Relationship to other skills

• dmmhyh makes you ask less. difm carries out a step already blocked or handed back.
• daytb decides a pending question. difm carries out a pending action.

Anti-patterns

• Rephrasing the denied command instead of re-running it identically.
• Leaving auto mode off after the step.
• Offering a one-liner for the user to run when you can run it.