What problem does it solve? Decisions made during brainstorming and planning sessions get lost or arrive at implementation as vague, unestimated tickets that force follow-up questions. This Skill turns an approved spec, plan, or design decision into a tracker ticket an implementation agent can execute with zero clarification. ## Core Features & Use Cases - Ingest-first ticket creation: Pulls scope from existing specs, plans, ADRs, and conversation decisions instead of inventing scope, including first-class support for forge-generated specs. - Required-slot enforcement: Every ticket must include title, context, scope, technical specs, acceptance criteria, definition of done, edge cases, TDD mode, and native tracker fields (estimate, labels, parent epic, dependencies, priority). - Duplicate detection: Searches the tracker by subject across multiple phrasings, including closed tickets, before creating anything, then either enriches an existing ticket or creates a linked one. - Multi-ticket programme handoff: Generates a .void/program.md descriptor with tracker-agnostic routing frontmatter for ticket pools spanning multiple sessions. - Use Case: After a planning session approves a spec for a new webhook retry system, invoke this Skill to produce a fully estimated, labeled ticket with acceptance criteria, edge cases, and declared runner passes, ready for void-implement to execute. ## Quick Start Ask the agent to create a ticket from the approved spec at docs/specs/webhook-retry.md and log it in the project tracker with an estimate and labels.
