From product-skills
Generates concise actionable problem statements for issues/features and guides solution exploration with strategic levers and UX principles. Useful for feature planning and issue triage.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-skills:draft-specThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
*Updated: @today's date in MM/DD/YY*
Updated: @today's date in MM/DD/YY
Write one actionable but concise problem statement paragraph behind the issue and its underlying motivation, clearly articulating the core problems this issue aims to solve or opportunities that are unlocked by building this feature. What's the marketing statement for this feature? Why are we building it now? Why do we deserve to win with this feature? This problem statement must be detailed and actionable enough to stand alone without additional context and still convey ALL the key takeaways but be limited to 3 concise sentences MAXIMUM. Lead with the most relevant customer persona making the request (ex: "Business owners need...") but NEVER use exact person and company names in the overview paragraph.
Explore the solution space before committing to a direction. Consider multiple candidate solutions and evaluate them against strategic and experience lenses.
Identify which of these strategic levers matter most for this solution and go deep on them:
When designing a simple and delightful user experience, try and employ some of these principles when designing the user flow:
Simplify relentlessly — remove unnecessary steps or features to deliver an intuitive, minimalistic experience. Every element must earn its place.
Maintain seamless continuity — guide users naturally from start to finish with minimal cognitive load and no dead ends.
Sweat the details — typography, transitions, spacing, and copy should all reflect meticulous craftsmanship. Balance functionality and beauty in a unified, consistent brand feel at every touchpoint.
Delight with thoughtful touches — add small but memorable details that elevate the experience beyond functional.
When unclear how to design a SaaS component, copy Linear on how a design or component should work.
Do not explicitly mention these principles when talking through the solution - just incorporate it into your rationale when exploring then deciding on and explaining the best solution.
After exploring the solution space and identifying the best strategy, provide a concise walkthrough of what the feature does, how it solves the user's pain points, and how it delights the user — written tightly, without unnecessary preamble.
Remember: the best solutions maximize ICE: impact, confidence, and effort. The higher the impact, the higher the confidence, and lower the effort - the better the solution.
Break the solution walkthrough into focused and concise paragraphs separated by line breaks — one aspect of the experience per paragraph.
Each criterion must describe a specific, testable condition with a clear expected outcome. Criteria describe desired outcomes, not implementation choices. Criteria should be MECE — mutually exclusive and collectively exhaustive — covering all conditions required for the work to be complete.
Functional:
Edge cases and error handling:
Out of scope:
npx claudepluginhub amplitude/builder-skills --plugin product-skillsDefine a clear, evidence-based problem statement that frames customer pain without prescribing solutions. Use when discovering unmet customer needs, validating market problems, or prioritizing discovery research.
Frames product design problems before solutions exist through research synthesis, opportunity sizing, hypothesis definition, project scoping, and customer journey mapping.
Defines feature specifications with user stories, acceptance criteria, backlog prioritization, and business discovery (hypothesis validation, MVP, monetization, AARRR metrics). Use when writing product requirements or planning new features.