Create Branch

Start every piece of work on its own correctly named branch, cut from an up-to-date base. The branch name isn't cosmetic: the create-commit skill pulls the JIRA ticket out of it for commit footers, PRs inherit it, and a consistent <type>/<TICKET>-<slug> shape makes branches self-describing in a busy repo.

1. Find the JIRA ticket

The branch should carry the ticket ID (PUB-4204 style — any PROJ-123 pattern) whenever the work has one. Look for it in this order:

1. The user's request or earlier conversation.
2. Documents driving the work: a requirements doc under docs/requirements/, a plan under docs/plans/, a pasted ticket or spec.
3. If none is found, ask the user for one — a one-line question is cheaper than renaming a branch later. Branching without a ticket is fine when the user confirms there isn't one; never invent an ID.