Writing issues REQUIRED BACKGROUND: the skill (hard rules, truth rules, style). Overview Core principle: write issues so they survive without you. State the outcome, include the acceptance check that decides Done, link the evidence behind every decision, and name the owner of every open part. When to invoke, and not Invoke when writing or editing tracker items, filing a bug, splitting work into tickets, or writing acceptance criteria. Do NOT invoke for weighing alternatives: when an issue needs a design argued, that is ; the issue links the design doc and never inlines it. This skill covers t…