What problem does it solve? Teams often force non-narrative work (like "set up security protocols") into fake user stories, or skip ticketing it entirely so real work becomes invisible. This Skill decides whether work qualifies as a task and writes a properly shaped, typed, and parented ticket for it. ## Core Features & Use Cases - Task vs. plan discrimination: Applies the sparse rule — goals become tickets, plan line items are refused and routed to plan-mode notes on the story. - Typed ticket shaping: Assigns exactly one of six types (Foundation, Improvement, Bug, Decision, Research) with a two-to-four-word lowercase title, concrete body, and checkable acceptance criteria. - Mandatory parenting: Places every task under a story or epic so it never floats untracked. - Use Case: When a build surfaces work like "core security setup" that no story owns, use this Skill to ticket it as a Foundation task directly under the epic. ## Quick Start Ask the agent to ticket the named work that isn't a story, for example by saying "this isn't a story, ticket it" or invoking /task-writer.
