What problem does it solve? Filing GitHub issues by hand produces story-style write-ups that repeat metadata, lack acceptance criteria, and ignore the labeling scheme the repository already uses, leaving later planning work without a spec to build against. ## Core Features & Use Cases - Spec-shaped issue bodies: Writes every issue in a Spec or Report structure with outcome, done-when criteria, and references, in the language of the repository's existing issues. - Repository vocabulary detection: Runs a script that reads labels, issue types, milestones, and project fields through the gh CLI, reusing what exists and creating default labels only when the repository defines none. - Deterministic sizing: Derives size, estimate, and priority from path and acceptance-criteria counts so two sessions produce the same values. - Use Case: Ask to split a feature request into a parent issue plus sub-issues; the skill grounds references in real code paths, creates the issues in dependency order with labels and project fields set, and reads each one back with its URL. ## Quick Start Ask the assistant to file a GitHub issue describing the outcome you want, for example to open an issue for adding rate limiting to the API endpoints.