abhsin/designskills

Overview

This skill extracts fuzzy product ideas and turns them into crisp, actionable problem statements, target user definitions, and jobs-to-be-done. It’s designed to be used when an idea exists but the problem, audience, or assumptions are unclear. The output is structured so coding and product teams can act with fewer clarifying questions and less rework.

How this skill works

You provide any form of raw input—notes, a voice dump, or a short pitch—and the skill runs a conversational question flow to clarify intent. It asks one focused question at a time, probes vague answers, and reflects back to confirm understanding. From the clarified context it produces a standardized problem-framing document that highlights the problem statement, target user, jobs-to-be-done, current alternatives, trigger moments, key assumptions, success criteria, and open questions. The result is a concise artifact you can share with coding agents or stakeholders to reduce misalignment.

When to use it

• You have a raw idea but can’t clearly state the problem or who it’s for.
• You want to hand context to a coding agent to build features with fewer iterations.
• Early discovery sessions to quickly test whether an idea is worth scoping.
• When prepping a brief for a designer, engineer, or product manager.
• Before running user interviews or validation experiments.

Best practices

• Share whatever raw material you have—drafts, voice notes, or bullet points—to speed clarification.
• Answer questions specifically; avoid “everyone” or vague groups—name roles, environments, and constraints.
• Be honest about assumptions and current workarounds; exposing risks early saves time.
• Focus on measurable success criteria so engineering and analytics can validate outcomes.
• Iterate the framing with short follow-up questions rather than trying to perfect it in one go.

Example use cases

• Turn a founder’s 2-minute pitch into a single-sentence problem statement and clear target user.
• Refine a feature idea into functional, emotional, and social jobs-to-be-done for product requirements.
• Translate customer complaints into trigger moments and measurable success criteria for an experiment.
• Document key assumptions and open questions before handing work to a development team.
• Prepare a concise brief that reduces ‘that’s not what I meant’ iterations when working with coding agents.