Create Ticket

Create one Notion ticket in the Project Tasks database from the request in $ARGUMENTS.

The goal is fast capture, not investigation. Preserve the user's context clearly enough that an engineer or PM can pick up the work later.

Inputs

• $ARGUMENTS — the issue, bug report, feature request, links, screenshots, user impact, reproduction notes, or other context provided by the user.

If $ARGUMENTS is empty, ask the user for the ticket description before continuing.

Hard Boundaries

• Do not inspect, search, or research the codebase to determine root cause, affected files, implementation details, or possible fixes.
• Do not create a debugging plan unless the user explicitly provided one as context to include.
• Do not invent missing facts. If a field is unclear and required to create a useful ticket, ask a concise clarifying question.
• Do not split the request into multiple tickets unless the user explicitly asks for multiple tickets.
• Only select Notion tags from the Allowed Tags list in this file. Do not create, infer, normalize, or substitute tags outside that list, even if Notion or the request suggests a plausible tag.