Ad-hoc task

Command: /adhoc-flow · ← All scenarios · User guide

For small or unusual tasks that don’t fit a fixed workflow. The agent assembles a custom plan from reusable building blocks, reviews it, and executes with tracking.

Use this when the task spans several concerns or doesn’t match any specific scenario: lightweight docs, build scripts, cross-cutting chores, syncing, or one-off tooling.

Not for: real coding features/fixes (Write or change code), requirements (Author requirements), or codebase analysis (Analyze a codebase) — use the dedicated scenario, which is more thorough.

Running it

/adhoc-flow Write a quick script to parse these CSV files
/adhoc-flow Refactor logging across the payments, orders, and billing services
/adhoc-flow Sync the CHANGELOG with the last 10 merged PRs

How it works

Instead of a fixed set of phases, it composes one from building blocks (discovery, planning, execution, review, validation, and so on) sized to the task, then loops through the plan — adapting it as it learns.

flowchart TB
    Start(["/adhoc-flow + request"]) --> Triv{"Trivial <br>one-liner?"}
    Triv -->|yes| Do["Just do it"]
    Do --> Done(["Task done"])
    Triv -->|no| Build["Build a plan from building blocks"]
    Build --> Size{"Medium <br>or large?"}
    Size -->|yes| RevPlan["Plan review"]
    RevPlan --> G1{"You approve <br>the plan"}
    Size -->|no| Exec["Execute step by step"]
    G1 -->|request changes| Build
    G1 -->|approve| Exec
    Exec --> More{"More steps?"}
    More -->|yes| Exec
    More -->|no| Intent{"Matches <br>your intent?"}
    Intent -->|no| Exec
    Intent -->|yes| Done

    classDef step fill:#dae8ff,stroke:#3674b5,color:#102a43;
    classDef gate fill:#fff2cc,stroke:#b58b00,color:#493800;
    classDef done fill:#e5f7e8,stroke:#35834a,color:#153b20;
    class Do,Build,RevPlan,Exec step;
    class Triv,Size,G1,More,Intent gate;
    class Start,Done done;

For a genuinely trivial one-liner it can just do the task after confirming it’s trivial; anything bigger gets a plan, and medium or large work stops for your approval before execution. The plan is a living artifact — the agent updates it mid-run as things change.

What you’ll be asked to do

For medium and large tasks, approve the plan before execution. Keep your intent clear, and flag it if a discovery should change the scope.

What it creates

A living plan plus a state file under agents/TEMP/<feature>/; other artifacts depend on which building blocks the plan uses.

Any of the dedicated scenarios if your task actually fits one — they’re more thorough. Get help if you’re unsure.

Sources