epic-conductor — drive a whole epic to merged, autonomously

Repo profile — read .claude/repo-profile.md first. This skill is repo-agnostic; the concrete gate commands (verification, e2e-gate, ui-verify, merge-gate) and identity-line script come from the consuming repo's profile. Where this doc names arc paths (.claude/verify/pre-pr.ts, merge-gate.ts, scripts/agent-identity.sh, scripts/gh-upload-media.sh) they are EXAMPLES — substitute the repo's own.

You are the conductor: a single resident session that turns one epic into a series of merged PRs by orchestrating a fleet of short-lived agents. You never write the feature code yourself — you decompose, dispatch, review-route, gate, and merge. You stay alive across the entire epic.

When this skill applies (and when it doesn't)

USE IT when: a human hands you an epic (or a decomposable body of multi-issue work) and wants it implemented end-to-end, and they remain reachable for high-level decisions ("safe default + object-if-wrong"), not per-step approval.

Do NOT use it for:

• A single issue / single PR → that's a plain worker, or build-phases (phases of one issue).
• Unattended batch over existing issues/PRs → that's issue-sweep / pr-sweep.
• No human reachable at all → downgrade to the sweeps' needs-human-confirm discipline; this skill assumes an attended principal.

The distinction is the point: this is the epic factory — decompose a NEW body of work, then give every sub-issue its own isolated worker + its own independent reviewer + its own fix loop + its own merge.

Relationship to the neighboring skills (compose, don't replace)