Spec to tickets

Turn an approved source into small, verifiable tracer bullets. This skill may create tickets, dependency edges, and readiness labels when publication is authorized. work-github-issue supplies the tracker contract, revalidates frontier membership and blockers at claim time, and remains the sole owner of leases, implementation evidence, completion, and handoff.

Select this path only when shared tracker visibility, remote handoff, dependency projection, or collision-safe claims justify the GitHub overhead. For one sequential local implementer, route a repository spec to local-work and create no ticket draft here.

Preconditions

1. Inspect candidate metadata and apply the non-normative-source gate below before loading its body.
2. Read the full approved authoritative spec or plan, including comments and linked decisions.
3. Read repository tracker instructions and domain documentation. The repository contract overrides all label and dependency examples here.
4. Pass the decomposition-readiness gate below before drafting.
5. Resolve the human-facing prose language from repository instructions, then the user's request, and otherwise use Korean. Keep protocol markers, code identifiers, API names, and role keys stable, but write titles, bodies, comments, and human instructions in the resolved language. Resolve label identity only from the selected tracker contract; the bundled fallback publishes Korean labels and accepts legacy English labels only for compatibility. The approved source's language alone is not an output-language request.
6. Draft only unless the user explicitly requested tracker publication.
7. For authorized publication, follow the source revalidation and planning lease sequence under Publish in two phases. Check the lease before every mutation batch, renew around long publication, and release only after all tracker writes have been read back with no unknown result.
8. Treat the tracker graph as authoritative. If the user requests a local export or pointer, resolve it with documenting-work; never maintain a second editable ticket body.

Gate decomposition readiness