What problem does it solve? Turning bugs, feature requests, and plans into trackable work items often produces inconsistent, vague tickets. This Skill enforces a strict frontmatter contract and body structure so every issue ticket is complete, prioritized, and machine-validatable. ## Core Features & Use Cases - Structured Ticket Generation: Creates markdown tickets in workspace/tickets/to-do with required fields like id, type, priority, dependencies, and acceptance criteria. - Automatic Validation: A PostToolUse hook runs a Node.js validator that checks frontmatter fields, required body sections, filename conventions, directory-status sync, duplicate IDs, and circular dependencies. - Priority and Type Rubrics: Built-in p0-p3 priority rubric and seven ticket types (feature, fix, improvement, chore, docs, refactor, perf) keep triage consistent. - Use Case: After a code review reveals an unauthenticated admin API route, ask the agent to file a ticket and receive a validated FG_001-p1 ticket with deterministic acceptance criteria and implementation steps. ## Quick Start Ask the agent to create a ticket for the bug or feature you describe, or say "break down this plan into tickets" to generate multiple validated issue tickets.
