gs-openspec-to-tickets
Installation
SKILL.md
OpenSpec to Tickets
Break OpenSpec changes into tickets: tracer-bullet vertical slices, each declaring the tickets that block it, published to the project's tracker under one parent ticket per change.
Input
/gs-openspec-to-tickets <change> [<change> ...]
Also accept a prose list of change names. When no change is named, run openspec list --json and ask which active changes to ticket (several may be picked). A name that is not an active change is reported as not found; continue with the rest.
The user may also pass an existing tracker issue as the parent for a change. Use it as that change's parent and leave its body, labels, and state untouched.
Process
1. Gate each change
For each named change: