Turn a plan into a GitHub ticket backlog

Take a superpowers spec + implementation plan (the docs/superpowers/specs/... + docs/superpowers/plans/... pair from brainstorming and writing-plans) and file a GitHub backlog: an epic issue for the spec/plan, plus ticket sub-issues — each tagged with a complexity, an abstract model tier, a priority, and its dependencies on other tickets. The bundled scripts/create-tickets.sh does the mechanical GitHub work; it is idempotent (finds an existing epic/tickets by a hidden marker and updates them instead of duplicating).

This skill never dispatches, assigns, or monitors work — it stops once the backlog exists.

When this applies