---
name: ticketing
description: Use to create or organize requested issues into independently verifiable work, without mandatory tracking machinery.
---

# Ticketing

Tracking is optional. Prefer local decomposition unless the user or project
requests issues. Inspect existing work to avoid duplicates. Each useful ticket
states the problem, scope, acceptance evidence and dependencies without
prescribing speculative implementation details.

Use `tracker-operator` for native operations. Preserve project-specific metadata;
do not impose a universal label taxonomy, ownership claim or lifecycle state.
Create only the requested scope, update it as facts change, and report links.
Do not treat issue creation as permission to push, merge or publish code.