draft-technical-ticketslisted

# Draft Technical Tickets Draft precise **engineering issues** that another coding agent can implement without guessing. Default destination is the **project host** (GitHub Issues or GitLab Issues) per [`config/tracker-profiles/`](../../config/tracker-profiles/README.md) and consumer `.skills/profile`. ClickUp is only for product features or tracking tickets when the user explicitly asks (`operations/create-tracking-ticket`). Read [`references/project-context.md`](references/project-context.md) when present as optional project hints — prefer the live repo `AGENTS.md` and docs over stale summaries. Use [`references/ticket-template.md`](references/ticket-template.md) for structure. ## Inputs Accept any of: - Approved Design Contract from [`design/product-design`](../../design/product-design/SKILL.md) - Feature description / PRD - ClickUp URL or task id (product context) - Target repository (path or remote) If the target repository is unclear, ask once before inspecting code. ## Workflow 1. Understand the requested outcome, user-visible behaviour, constraints, and non-goals. 2. Inspect product docs (ClickUp or repo) relevant to the request. Treat documented architecture decisions as authoritative unless the repository clearly shows they are obsolete. 3. Inspect the live repository. Read `AGENTS.md`, nearby implementation, tests, schemas, clients, and configuration. 4. Reconcile documentation with code. State material conflicts; do not silently invent behaviour. 5. Decid