一键导入
assumption-grading
Assess assumptions on certainty and risk to prioritize validation efforts. Use at project start or before phase transitions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Assess assumptions on certainty and risk to prioritize validation efforts. Use at project start or before phase transitions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Test whether assumptions are true before making commitments. Use when assumptions have low certainty and high risk.
Create structured visualizations of stakeholder perspectives (says, thinks, does, feels) to build deep understanding. Use when conducting user research or validating assumptions.
Assess solution ideas on impact and feasibility to prioritize prototyping. Use during Ideate phase when deciding which ideas to pursue.
Transform raw research into actionable insights that inform design decisions. Use during Define phase after completing research.
Distinguish user wants from underlying needs to guide solution design. Use when stakeholders make feature requests or during Define phase.
Create clear leadership presentations that communicate findings and enable good decisions. Use at end of each phase or before major commitments.
| name | assumption-grading |
| description | Assess assumptions on certainty and risk to prioritize validation efforts. Use at project start or before phase transitions. |
Systematically assess assumptions to identify which ones need validation and prioritize research efforts.
Identify what you're assuming to be true. Common sources:
Assess on two dimensions:
CERTAINTY — How confident are we this is true?
RISK — What's the impact if we're wrong?
Focus on assumptions that are:
For each high-priority assumption, define:
Record each assumption with:
{
"id": "a1",
"description": "Users want automated reporting",
"certainty": "low",
"risk": "high",
"validation_plan": "Interview 5 users about reporting needs and current workflows",
"status": "open"
}
Assumption: "Users will adopt mobile app over desktop"
Assumption: "API can handle 1000 requests/second"
Assumption: "Users understand technical jargon"