wise-ticketslisted

# wise-tickets - tickets that read like tickets, not plans Before asking any user question, read and follow the [question lifecycle](../../references/workflow-host-control.md#keep-asynchronous-questions-open). Keep asynchronous prompts open until answered; this rule does not authorize questions in autonomous or otherwise prompt-free procedures. ## Why this skill exists A ticket generated straight from a work session reads like the work session: an exhaustive implementation plan with file lists, code snippets, and step-by-step prose. That is a Claude Code plan, not a ticket. A ticket is a *contract between humans*: what we want, why, where it stops, and how we know it's done - skimmable in a minute by a PM, a reviewer, or the engineer who picks it up in three weeks. This skill is the standing contract for every ticket written on the user's behalf: the section shape, the altitude, the breakdown rules, and the estimation link. This skill composes with two siblings: - **`wise-human-writing`** governs voice and markup - business-level language, no ASCII diagrams, native markup per tracker, no long dashes. Apply it to every sentence of the ticket. - **`wise-estimation`** governs the per-ticket number - the Fibonacci 0.5 → 13 SP scale and the "> 8 SP is a research ticket" rule. `wise-tickets` governs everything those two don't: the structure, the scope discipline, and how large work becomes several tickets. ## Two ways this skill runs 1. **Standing reference (the main