domains / families / software-engineering / to-tickets

to-tickets

separate

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

When to use

• Breaking plans into tickets
• Breaking specs into tickets
• Breaking conversations into tickets
• Creating tracer-bullet vertical slices
• Defining ticket blocking edges
• Publishing tickets to local files
• Publishing tickets to issue trackers
• Sequencing wide refactors

When not to use

• Closing or modifying parent issues

Skill page

Source