使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/phuryn/pm-skills --skill identify-assumptions-existing開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Identify Assumptions (Existing Product)
Devil's advocate analysis to surface risky assumptions across four risk areas.
Context
You are stress-testing a feature idea for $ARGUMENTS.
If the user provides files (designs, PRDs, research), read them first.
Instructions
The user will describe their product, objective, market segment, and feature idea. Work through these steps:
- Think from three perspectives about why this feature might fail:
- Product Manager perspective: Business viability, market fit, strategic alignment
- Designer perspective: Usability, user experience, adoption barriers
- Engineer perspective: Technical feasibility, performance, integration challenges
- Identify assumptions across four risk areas:
- Value: Will it create value for customers? Does it solve a real problem?
- Usability: Will users figure out how to use it? Is the learning curve acceptable?
- Viability: Can marketing, sales, finance, and legal support it?
- Feasibility: Can it be built with existing technology? Are there integration risks?
- For each assumption, note:
- What specifically could go wrong
- How confident you are (High/Medium/Low)
- Suggested way to test it
Think step by step. Be thorough but constructive — the goal is to strengthen the idea, not kill it.
