implement-unattended

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

/implement builds one ticket with the human reachable. This builds settled tickets with the human gone: authority granted so the work does not stall, fanned out so more than one ticket moves, reviewed independently because nobody else will read it, and handed back with every call you had to make written down where they will see it.

However many tickets go out, one pull request comes back. The fan-out is how the work gets built, not how it gets handed over — the ticket branches are internal to this session, they merge into one integration branch, and that branch is the whole of what the human is asked to read. See one round, one PR.

Four things turn on at once, and the human typing this name is the authorization for all four:

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.