ticket

Topics in the source

• Ticket
• 1. Project and board
• 2. Pick the ticket
• 3. Claim
• 4. Branch (git only)
• 5. Import
• 6. Route
• 7. Handoff

/ticket [KEY-12|12] starts one ticket: claim it on the project's board, cut its branch, import it to ticket.md, write the handoff, then print the route and start it. /send ships the work later. The steps are the same on every board. What a board does at a step lives in its board file, read once in step 1: | Board | Board file | | --- | --- | | Vault Kanban file (board: vault) | ${CLAUDESKILLDIR}/VAULT.md | | Jira (board: jira-candidate, or a link on an Atlassian site) | ${CLAUDESKILLDIR}/JIRA.md | | Any other link or text, e.g. Azure DevOps | ${CLAUDESKILLDIR}/OTHER.md | The vault path and the projects root are set in /.claude/CLAUDE.md (a project CLAUDE.md may replace them). Run: project: none → stop and print its reason:. Then follow ${CLAUDESKILLDIR}/BOARD.md to get the board (on a Jira candidate it checks the key first), and read its board file. is the dir: line: the main checkout, or the project folder without git. Git means git -C rev-parse succeeds; without git, skip every git step and write no branch anywhere. Done when: project, , board and git-or-not are known, and the board file is read. $ARGUMENTS matches [A-Z][A-Z0-9]+-[0-9]+ → that id. Digits only → on a number-only t

This is an excerpt. Refer to the complete source and its current requirements.