Open Ticket

Create one remote tracker ticket from a brand-new idea. Take the user's idea, turn it into a ticket title and a body that captures the idea, create the ticket in the single owning tracker, and surface the created ticket's URL/identifier back to the user. That URL is what a local thread later links from its seed's External: line.

Procedure

1. Preflight first, before any substantive execution. Run both gates from ## Prerequisite Preflight. If either fails, stop and refuse without drafting or creating anything, ending with exactly one terminal line: Outcome: REFUSED — <what is missing and how to supply it>.

2. Draft the ticket from the idea. Compose the title and body described in ## Drafting the Ticket From the Idea.

3. Create the ticket — once — in the owning tracker. Use the tracker's CLI/API to create exactly one ticket, per ## The Only Tracker Write, Made Once and ## Single Ownership of Work-Item Status.

4. Surface the result. Return the created ticket's URL/identifier to the user plainly, so it can seed a thread's External: line. No preamble, no closing remark. End with exactly one terminal line: Outcome: DONE — Ticket created: <URL/identifier>.

The Only Tracker Write, Made Once

Being invoked here is the sole authorization to create a ticket: in this workflow exactly one skill writes to the tracker, and it is this one. Its only write anywhere is that single remote ticket — it touches no repo file and no git (no staging, committing, pushing, or branching).

The skill creates the ticket, hands back its URL, and stops. There is no ongoing sync between the repo and the tracker — two systems kept in continuous step always rot — so once the ticket exists the skill leaves it in place: it does not poll, re-sync, write repo state back onto the ticket, update it, re-run to refresh it, or close it. Any comment, transition, or close on a ticket happens only when the user explicitly asks.