メニュー
Assess solution ideas on impact and feasibility to prioritize prototyping. Use during Ideate phase when deciding which ideas to pursue.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Assess assumptions on certainty and risk to prioritize validation efforts. Use at project start or before phase transitions.
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.
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 | idea-evaluation |
| description | Assess solution ideas on impact and feasibility to prioritize prototyping. Use during Ideate phase when deciding which ideas to pursue. |
Systematically assess solution ideas to prioritize which ones to pursue through prototyping.
IMPACT — How much value would this create?
FEASIBILITY — How realistic is this to build/implement?
FEASIBILITY
Low Med High
┌─────────────────────┐
H │ │ B │ A │
I │ │ │ │
M ├───────┼─────┼──────┤
P │ │ C │ B │
A │ │ │ │
C ├───────┼─────┼──────┤
T │ D │ D │ C │
└─────────────────────┘
A tier: High impact, High feasibility → Prioritize B tier: High impact, Med feasibility OR Med impact, High feasibility → Consider C tier: Med impact, Med feasibility OR Low impact, High feasibility → Maybe later D tier: Low feasibility or Low impact → Park or discard
Beyond impact/feasibility:
For each tier:
A tier: "Prototype immediately. This addresses [key insight] with clear path forward."
B tier: "Strong candidate. Needs [feasibility spike / user validation / resource check] before committing."
C tier: "Interesting but not priority. Revisit if A/B tier ideas fail or after launch."
D tier: "Park for now. [Technical barriers / unclear value / other ideas are stronger]."
{
"id": "idea1",
"title": "Offline data capture",
"description": "Allow field techs to log data without connection, sync when back online",
"impact": "high",
"feasibility": "high",
"status": "ideated",
"idea_doc_link": "ideas/offline_capture.md"
}
Idea: "AI-powered predictive maintenance alerts"
Idea: "Quick-capture field form"