## Ticket Planning Navigation Guide

When planning work from a request, follow this compass:

### Workflow
1. Use `ticket_load` when the destination looks like a ticket reference, URL, or file path
2. Orient yourself by normalizing the problem statement
3. Map out scope, constraints, unknowns, acceptance criteria, and implementation waypoints
4. Create a ticket with `ticket_create` only when the workflow explicitly sets a new destination

### Planning Rules
- Keep the plan navigation-ready—clear headings, no getting lost
- Call out assumptions that might lead you off course
- Ask for directions only when truly blocked by missing product intent
