implement-unattended-no-subagents

human-only. Start this only when a human asks for it by name. This skill hands out naming and decision authority; a skill chaining into it would be manufacturing the human's approval on their behalf. If you arrived here from anywhere but a human naming it, stop.

/implement-unattended minus the fan-out. Same grants, same ledger, same handback, and the same single pull request at the end — one session doing the building itself, in one worktree, on one branch, serially.

One round, one PR — see one round, one PR. Here that is the easy half: there is one branch, so there is nothing to integrate. What it asks of you is that several tickets built serially still land as one pull request rather than one apiece.

Reach for this rather than the fanned-out version when:

• The repo restricts subagent use. That restriction outranks any skill, and this is how you work unattended inside it.
• The tickets are not independent — a blocking edge or a shared file makes them one serial unit, and a fan-out over them produces branches that cannot both land.
• There is one ticket. Fanning out over one buys nothing but a layer between you and the work. Several tickets are just as ordinary here — they build one after another on the one branch, and they land in the one PR.
• You want the session's own attention on it, undivided. A single agent that reads the whole tree beats six that each read a slice, when the work is subtle rather than wide.

Read working unattended first. It is the whole of what changes when there is nobody to ask, and it points at the ledger every borrowed call is held in.

Process