open-ticketlisted

# Open Ticket Turn a user's rough idea into one ticket in the project's tracker. You interpret the raw input, compose a title and a body, confirm both with the user, and file the ticket. What makes this worth a deliberate operation is the body. A ticket filed here is written so that whoever later opens a thread from it can take the body as the thread's genesis narrative unchanged, instead of mining intent out of a half-specification. You write nothing to disk. The ticket in the tracker and the URL you report are the whole result. ## Read the repository's conventions Do this first, before composing: a convention can decide the title's shape, and a title composed without it has to be rewritten. Read `references/repository-conventions.md` and apply what it says about a ticket. It carries where a project states such a convention, which parts of it bind you, and what to do when it leaves a choice the user's idea does not settle. ## Compose the ticket Compose two things from the user's idea. **The title** — one human-readable line naming the subject, in the register a person would use when speaking about the work. Where the project prescribes no title shape, that register means prose, with no bracketed prefix and no kebab-case identifier. **The body** — a self-contained **problem statement**: what triggered the work and what outcome is wanted, written so a reader with no memory of the conversation understands why the ticket exists. Restraint is the point — a problem state