identify-assumptions-existing

Describe your product, objective, market segment, and feature idea, and the Skill analyzes it from Product Manager, Designer, and Engineer perspectives. It surfaces assumptions across value, usability, viability, and feasibility, each with a confidence rating and a suggested test.

The four risk areas are Value (does it solve a real customer problem), Usability (can users figure it out), Viability (can the business support it), and Feasibility (can it be built with existing technology). This framework comes from product discovery practice.

Yes. If you provide supporting files such as designs, PRDs, or research documents, the Skill reads them first and grounds the assumption analysis in that material rather than relying only on your description.

Run it before committing engineering effort to a feature, when stress-testing an idea, or when preparing an assumption mapping session. It works best for features in an existing product where context about users and systems is available.

Assumption identification surfaces what could go wrong and rates your confidence in each assumption. Assumption testing is the follow-up step where you run experiments to validate or invalidate the highest-risk assumptions this analysis produces.