To Tickets Break plan/spec/conversation into tickets — tracer-bullet vertical slices, each declaring tickets that block it. Publish per consumer repo's tracker conventions (AGENTS.md). Reproducibility invariant Full issue set, replayed in dependency order — features and bugfixes alike — must build roughly same application, regardless of who or what implements. Issue stream = buildable spec. Every rule below serves this. Self-containedness Every outcome-shaping decision lives in issue itself , or durable docs it references — ADRs ( ), glossary terms ( ). Never conversation context, tribal know…