mg-tickets

Creates Linear epics and phase-labeled tickets from approved minigame specifications via MCP.

1|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/Bornqazaq/sleepover --skill mg-tickets-bornqazaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mg-tickets
Source: https://github.com/Bornqazaq/sleepover/tree/main/.claude/skills/mg-tickets
Command: npx skills add https://github.com/Bornqazaq/sleepover --skill mg-tickets-bornqazaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved minigame design spec into actionable Linear tickets is repetitive and error-prone: tickets get duplicated, phases get mixed, and art subphases get skipped. This Skill automates slicing a finalized spec into a structured epic with properly labeled, dependency-linked tickets in Linear. ## Core Features & Use Cases - Epic and ticket creation via Linear MCP: Checks for existing draft epics to avoid duplicates, then creates or updates the parent epic and child tickets using mcp__linear__save_issue and related tools. - Fixed phase breakdown: Generates tickets across four phases (skeleton, network, art, playtest) with dedicated labels, priorities, and statuses, including one ticket per art subphase (4.0–4.6). - Governance rules: Enforces ticket templates, blocks ticket creation when the spec has open questions, and isolates Core changes and animator edits into separately flagged tickets. - Use Case: After finalizing a party-game spec with /mg-spec, run this Skill to produce a complete Linear epic where every ticket can be picked up and implemented without further clarification. ## Quick Start Run the mg-tickets skill with the minigame name to create the Linear epic and phase tickets from the approved spec in docs/minigames.

Frequently Asked Questions about mg-tickets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Linear tickets from a game design spec?

Run this Skill with the minigame name after the spec is approved. It reads docs/minigames/<game>.md, creates or updates the parent epic, and generates child tickets per phase using Linear MCP tools like save_issue.

How are minigame tickets split into phases in Linear?

Tickets are split into four fixed phases: skeleton, network, art, and playtest. Each ticket gets a phase label, a priority (High for skeleton and network, Medium for art and playtest), and a parentId linking it to the epic.

Does this Skill avoid creating duplicate Linear epics?

Yes. It first searches existing issues by game name with list_issues, then updates and rewrites existing draft epics instead of creating duplicates.

When should tickets not be created from a spec?

Tickets must not be created when the spec still has open questions in its unresolved section. The workflow requires returning to the spec phase until all questions are resolved.

Why does each art subphase need its own ticket?

Bundling art into a few large tickets previously caused sound work to be skipped and baking to be missed entirely. One ticket per subphase (4.0–4.6) ensures no art step is dropped from the build.