Claude Write Ticket

write-ticket — how to use it

For the team. This is the human guide; the files next to it are for Claude.

The skill turns a description of some work into a backlog ticket, saves it as a markdown file you review, and then — only after you say yes — creates the ClickUp task.

You do not have to read `SKILL.md`. Claude reads that.

---

One-time setup

You need two things: Claude Code open in this repository, and a ClickUp token.

**The token.** Each person uses their own — it is a personal token, not a shared one. Get it from ClickUp → **Settings → Apps → API Token**. It starts with `pk_`.

You do not have to set it up in advance. The first time you push a ticket, Claude checks for a token and asks you for one if it is missing. If you would rather do it now:

cd .claude/skills/write-ticket/scripts
python token_setup.py --status

That tells you whether you already have a working token and where it is. To store one:

CLICKUP_TOKEN_INPUT=pk_your_token python token_setup.py --save --target user

`--target user` puts it in `~/.claude/clickup.env`, outside the repository. That is the recommended place: the token is yours, the repository is shared, and a file outside the repo cannot be committed by mistake. Use `--target repo-env` instead if you prefer it in the repo-root `.env` next to the database settings.

The script checks the token against ClickUp before saving it, and refuses to write it anywhere git would track. It never prints your token.

**Python.** The scripts need Python 3 and nothing else — no `pip install`. They use only the standard library.

---

Writing a ticket

Type `/write-ticket` and describe the work, or just describe the work and ask for a ticket. Both reach the same place.

/write-ticket add an endpoint that returns the customer's saved addresses

we need a ticket for the bug where the cart total ignores the coupon after
the user changes the quantity

Then Claude does five things. You are involved in t