Before you build a new feature, it pays to challenge your own thinking. Many ideas fail because of hidden assumptions that nobody noticed. This skill helps you find those risky assumptions early. It looks at your feature idea from three different viewpoints: a Product Manager, a Designer, and an Engineer. Each one sees different problems.
The analysis covers four key areas. First, does the feature create real value for customers? Second, can people actually use it without confusion? Third, can the business support it with marketing, sales, and legal? Fourth, can your team build it with the technology you have today. For each possible risk, you get a confidence score and a way to test it.
The goal is not to kill your idea. The goal is to make it stronger by fixing weak spots before you spend time and money. Product managers, designers, and engineers can all use this approach to avoid surprises later.
Global
mkdir -p ~/.claude/skills/identify-assumptions-existingProject
mkdir -p .claude/skills/identify-assumptions-existingSource Repository
Lark Calendarlarksuite/cli
View, create, and update calendar events and book meeting rooms
Lark Tasklarksuite/cli
Create, assign, track, and manage Feishu tasks, lists, and agents efficiently
Lark Workflow Standup Reportlarksuite/cli
Lark workflow creates a daily standup report from your calendar and tasks
Lark Attendancelarksuite/cli
See your daily attendance clock-in and clock-out times with lark-cli
Lark Okrlarksuite/cli
Set and track OKRs in Lark with easy commands
Caveman Helpjuliusbrussee/caveman
A quick reference for all Caveman modes, skills, and commands
Writing Plansobra/superpowers
Create comprehensive bite-sized implementation plans for any multi-step task
Site Architecturecoreyhaines31/marketingskills
Plan your website structure for clear navigation and better search rankings