open-ticketlisted

# Open Ticket — Issue Creation with Spec This skill creates a new GitHub issue with proper labels and epic assignment, then automatically runs the `/write-spec` skill to post a requirements specification as a comment. ## Step 0: Gather Information If a title was provided as an argument, use it. Otherwise, ask the user for: - **Title**: Short, descriptive issue title - **Description**: What is this feature/bug/refactor? (can be brief — the spec will expand it) ``` REPO="nick-pape/grackle" ``` ## Step 1: Fetch Available Labels Fetch the repository's labels to select the right ones: ```bash gh label list -R $REPO --limit 100 --json name --jq '.[].name' ``` ## Step 2: Fetch Open Epics Fetch the current epic issues to find the right parent: ```bash gh issue list -R $REPO --state open --search "Epic:" --json number,title --jq '.[] | "\(.number): \(.title)"' ``` Key epics to know: - **#270** — Epic: Orchestration (multi-agent coordination, swarming, reconciliation, escalation) - **#272** — Epic: Web UI features (all frontend/UX work) - **#271** — Epic: Code quality and refactoring - **#273** — Epic: Rushstack tooling adoption (build infra) ## Step 3: Classify the Issue Based on the title and description, determine: ### Labels (select all that apply): - **Type**: `feature`, `bug`, `refactor`, `infra` - **Packages**: `web`, `server`, `cli`, `powerline`, `common` (based on which packages are affected) - **Domain**: `orchestration` (if related to multi-agent, swarming,