Create a Clanker Ship ticket
A ticket is one unit of work on one team, such as WEB-31. Its summary says what
is wrong or missing and why; its plan, written later, says how to do it. Each team
keeps ticket instructions: a template, guidance and defaults. Follow the live
instructions every time. Do not reuse ones from earlier in the conversation.
Steps
- Find the team. If the person did not name one,
read_settingsgives their default team, whichcreate_ticketuses when you name none. Calllist_teamsand ask only when the work clearly belongs to another team. - Call
get_agent_instructionswithkind: "ticket"and the team's key. - Read the guidance and follow it. Ask the person before guessing at anything it says to confirm.
- Write the summary from the template. When the ticket will carry a tag that has its own template, start from that one.
- Call
create_ticketwith the team, a short title, the summary, and any status, tags, owner or project the person named. Leave the rest out: the instructions' defaults fill them, including you as the owner when the team wants that. - Tell the person the new ticket's ID and title, and link it.
Use only tags that list_tags returns for the team. Give each ticket one outcome:
when the request holds two, propose two tickets.