Four steps, sprint-ready work

Overcut identifies the relevant repos, clones them for context, checks the ticket has enough detail, then splits it into structured sub-tickets along natural boundaries.

The edge cases, covered

It validates before it acts and splits along real technical seams, so you get usable sub-tickets instead of busywork.

Gates on readiness

Checks for sufficient requirements or design content first, and exits early with guidance when a ticket isn't ready.

Splits along real boundaries

Decomposes by component, feature, dependency layer, or risk — using your actual codebase structure.

Maps dependencies

Posts a dependency map and a suggested implementation order back on the original ticket.

Carries context forward

Each sub-ticket includes scope, acceptance criteria, technical notes, and inherited labels.

Integrates with your stack

Reads and writes issues in your tracker and pulls context straight from your repositories.

Running from day one

Triggers automatically when a ticket is labeled needs-breakdown, or on demand with /breakdown on any issue.