Specs → Tickets

human-only. Start this only when a human asks for it by name. If you arrived here from another skill, stop and get explicit confirmation before running any step.

Downstream of /decisions-to-specs. That skill settled a wayfinder map's decisions into repo spec files and recorded them on the map under ## Specs settled. This skill reads those notes and produces the implementation tickets — by handing each spec to Matt's /to-tickets.

This is the boundary where planning becomes building: the decision issues and the specs are behind you; from here it's tracer-bullet tickets → /implement.

Approvals go on the tracker. The scope confirmed at step 2 and the granularity settled at step 3 are the human's calls, and both get lost the moment this session ends. Follow the approval-policy skill: record them where it says — the map for what the run decided, the ticket for what shapes one slice — never as a note in a spec file.

Process

1. Load the map and its settled specs

Resolve the map from the argument (issue URL or number). Read the ## Specs settled section written by /decisions-to-specs — the list of spec files with their disposition (new / updated / ADR).

If the section is missing, stop and tell the user to run /decisions-to-specs <map> first — there are no settled specs to slice.

Done when: you have the list of spec files and their dispositions.