Breakdown Perps Tickets

Turn one perps product requirement into the minimum set of technical tickets, each routed to the right layer and written for direct agent ingestion. You have codebase access — use it to decide the split from the actual code, not guesswork.

When To Use

• A PM (e.g. via a codebase-aware Claude) has a perps bug or feature and wants tickets engineering can dispatch as-is.
• A requirement may span Core logic and one or both clients, and you need it split correctly instead of filed as one vague ticket against one repo.

This is the second pass: the PM states what's broken / expected (no implementation); this skill does the technical breakdown + routing. It converts a bug or EPIC into engineering task tickets — it does not author initiatives/EPICs.

Not for: pure investigation/spikes (narrow to a concrete behavior first), or non-perps work.