create-tracking-ticketlisted

Create a ClickUp tracking ticket when the user requests work that has no product feature ticket and no engineering issue yet. Use when the user asks to track ad-hoc work in ClickUp for visibility, then optionally file a host engineering issue (GitHub or GitLab) from that tracking ticket.
singleton-sd/ai-plattform-skills · ★ 0 · AI & Automation · score 68

Install: claude install-skill singleton-sd/ai-plattform-skills

# Create Tracking Ticket Use when the user wants **ClickUp visibility** for work that is not yet (or may never become) a formal product feature, and may or may not need an engineering issue on the project host. ## Ownership | System | Role here | |--------|-----------| | **ClickUp** | Optional tracking ticket (this skill) | | **GitHub / GitLab Issues** | Engineering work — only create if the user wants implementation tracking on the host | Do **not** use ClickUp Delivery / claim tokens for engineering execution. Read [`config/tracker-profiles/README.md`](../../config/tracker-profiles/README.md) and the consumer `.skills/profile` when present. ## When to use - User asks to "create a ClickUp ticket" / "track this" without an existing feature. - User describes ad-hoc ops/chore work and wants a ClickUp breadcrumb. - User has no ClickUp product feature and no host issue yet. ## When not to use - Engineering-ready work with clear acceptance criteria → file a **host issue** (`task-management` / `draft-technical-tickets`) instead of or in addition to tracking. - User already has a ClickUp **product feature** → refine that; do not duplicate. - Skills-repo skill authoring → use `operations/skill-authoring-workflow` and the Skills Product Backlog list in [`config/clickup-defaults.json`](../../config/clickup-defaults.json). ## Workflow 1. Confirm destination list from consumer `.skills/profile.clickup.trackingList` (or ask once). Fall back to Ideas & Discovery style list