What problem does it solve? Filing well-formed tickets on a GitHub Projects board is repetitive and error-prone: IDs collide across parallel sessions, field and option IDs drift when hardcoded, and board listings silently truncate. This Skill turns a title into a board-ready issue with consistent Status, Priority, Type, labels, and a stable AREA-NNN-slug identifier. ## Core Features & Use Cases - Suggestion-first interactive flow: Proposes home repo, AREA prefix, Type, Priority, labels, and the next free NNN, then confirms with the human via AskUserQuestion before creating anything. - Deterministic board setup: Creates the issue with gh, adds it to the project, resolves field/option IDs at runtime, and sets Status, Priority, Type, and the ID text field. - Concurrency and verification hardening: Re-scans issue titles via paginated REST before creating, verifies results by node ID instead of truncated board listings, and defines yield rules for duplicate-ID collisions. - Use Case: You spot out-of-scope work mid-change and say "file an issue on the board" — the Skill proposes HARNESS-017-ticket-templates as a P2 chore in dotfiles, you confirm, and the ticket lands on the bitácora with all fields set. ## Quick Start Ask the agent to create a new ticket for the issue you found, for example by saying "new ticket: fix the drift assertion on Windows setup".