subagent-implement

human-only. Start this only when a human asks for it by name. If you arrived here from another skill, stop and get explicit confirmation before running any step.

/implement builds one settled ticket. This builds several at once, one subagent per ticket, where the tickets are genuinely independent of each other. Everything /implement says about the work still holds — this skill only changes who does it and how they are kept apart.

The parallelism is the risk, not the feature. Two agents that share a checkout corrupt it; two tickets that share a file produce two branches that cannot both land. Step 1 is where this skill earns its keep, and it is not setup to hurry through.

How a fan-out is run — isolation, the shell hazard, the brief, the prohibitions, and how results are verified — is subagent dispatch, shared with subagent-review. Read it before dispatching anything.

Process

1. Establish independence — before anything is created

A set of tickets is only parallel if none of them needs another's result and none of them will fight another for a file. Both have to be checked; neither is visible from inside a subagent.

Read every ticket in full, then check three things: