design-ask

Unpacks poorly written Jira or Azure DevOps tickets into design-relevant framing. Use this skill whenever a designer pastes in a ticket description, acceptance criteria, or any product/engineering requirement and wants to understand what the actual design work is. Trigger when someone says things like "can you help me understand this ticket," "what is this ticket actually asking for," "decode this ticket," "unpack this AC," "what design work does this require," or pastes raw ticket text and asks what to do with it. Also trigger when a designer mentions they're confused about scope, unclear on requirements, or trying to figure out if something is a content change vs. a flow vs. a new pattern. This skill is especially useful when tickets are written prescriptively (they specify a solution like "add a dropdown") instead of descriptively (explaining the user need), or when acceptance criteria are written from a dev/QA perspective with no design context.