What problem does it solve? Teams routinely file tickets, issues, and stories that lack context or testable acceptance criteria, forcing triagers and engineers to chase clarification. This Skill drafts well-formed work items with a consistent structure and observable acceptance criteria, and tightens existing items that are missing pieces. ## Core Features & Use Cases - Structured drafting: Produces work items with a framing section (Context, Observed Symptoms, or Steps to reproduce), optional Root cause or Plan, and mandatory testable acceptance criteria. - Standalone vs. child logic: Determines whether an item is standalone or a child of a parent, and only adds acceptance criteria to child items that are independently verifiable. - Tracker-agnostic creation: Creates or updates the item in whatever tracker is connected at runtime, such as Jira via MCP, GitHub via gh issue create, Azure DevOps, or Linear. - Use Case: A user says "log a bug for the 502 errors on the orders API" and receives a complete defect ticket with observed symptoms, impact, and acceptance criteria, ready to file in Jira. ## Quick Start Ask the assistant to draft a work item for the bug you just found, including acceptance criteria, and create it in your connected tracker.
