To Tasks

A ticket from to-tickets is a tracer bullet: one end-to-end behaviour, deliberately layer-agnostic. Implementing it usually means creating or editing files across several projects at once, and that is where a small model in a long session drifts. This skill turns each ticket into tasks: implementation slices whose footprint (the projects they write to) is at most two projects, ordered along the dependency graph, each a short step the ticket's worker finishes, validates, and commits before starting the next.

Tasks nest under their ticket:

ticket 01
├─ task 01
├─ task 02
└─ task 03

This skill writes task files only. It ends when the tree is published.

1. Establish the input

The input is a feature directory holding the tickets and design.md. Accept it as a path or infer it from the conversation; when the conversation already holds the tickets and the design, work from that.