Write tickets that make sense without you.
Guides issue writing so tickets state an outcome, testable acceptance checks, supporting evidence, and ownership of open questions.
When to use it
Use when writing or editing tracker items, filing bugs, splitting work into tickets, or writing acceptance criteria, not when weighing design alternatives.
It changes how the agent writes and refines tracker issues, requiring self-contained outcomes, evidence, testable acceptance checks, and explicitly owned gaps.
Requires technical-writing as background for its hard rules, truth rules, and style.
This skill
tracker
Files and updates tracker issues (irreversible)