Write Perps Ticket

Turn a raw perps observation, idea, or goal into one clean, complete ticket the product team can file and engineering can break down as-is. You describe what and what's expected — never how.

When To Use

• A PM (or a Claude acting for one) reports a perps bug, proposes a feature, or frames a strategic goal and wants a well-formed ticket.
• The input is raw: a Slack message, a screenshot, a one-line idea.

This is the first (product) pass. The technical split — which repos/layers change, dependency order, component routing — is the engineer's job and lives in perps-breakdown-tickets. Do not do it here.

Not for: engineering task breakdown, or routing a ticket across Core/clients (→ perps-breakdown-tickets).