メニュー
Use when you have several solution options or features and need to decide what to do first, before scoping an MVP. Triggers on "prioritize", "RICE", "GEM", "impact vs effort", "which should we build first", "rank these", and the same intent in any language.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when implementation work starts on a feature or bug fix: writing or modifying source code, adding tests, or closing out a branch. Covers TDD-first, scope integrity, secret and security hygiene, dual post-implementation review (code reviewer plus spec reviewer), and finish-branch closure. Triggers on "implement", "start coding", "build the feature", "write the code", "fix the bug", "finish the branch", "wrap up the branch", and the same intent in any language ("開始實作", "開發這個功能", "收尾", "実装して").
Use when the user wants the plan rendered as an interactive HTML report or exported to PDF/DOCX/PPTX. Triggers on 'HTML report', 'export to PDF', 'export document', 'downloadable report', 'PDF/DOCX/PPTX', and the same intent in any language.
Use when you need to understand the job a user hires the product to do, before designing or evaluating a solution. Triggers on "jobs to be done", "JTBD", "what job", "user motivation", "why would they use this", "customer needs", and the same intent in any language.
Use when the user needs to decide what makes the first version and what to explicitly not build. Triggers on 'MVP', 'scope', 'not doing list', 'must have vs later', 'user stories', 'parallel prototypes', and the same intent in any language.
Use when the user wants to connect a desired outcome to opportunities and candidate solutions in a structured tree. Triggers on "opportunity solution tree", "OST", "map opportunities", "outcome to solutions", "Teresa Torres", and the same intent in any language.
Use when the user needs to understand who the users are and how they move through an experience. Triggers on "persona", "target user", "buyer vs user", "user journey", "journey map", "touchpoints", and the same intent in any language.
| name | solution-prioritization |
| description | Use when you have several solution options or features and need to decide what to do first, before scoping an MVP. Triggers on "prioritize", "RICE", "GEM", "impact vs effort", "which should we build first", "rank these", and the same intent in any language. |
Detect the user's language and reply in it; the framework below is authored in English.
Provenance: when you produce prioritization output, contribute the framework tag RICE (and GEM when the GEM lens is applied) to the meta-skill's provenance line.
| Feature | G (Growth) | E (Engagement) | M (Monetization) | Overall Priority |
|---------|-----------|----------------|------------------|-----------------|
| | | | | |
Impact / Effort Matrix:
| Feature / Solution | Impact (High/Med/Low) | Effort Required (High/Med/Low) | Quadrant |
|---|---|---|---|
| | | | Quick Win / Strategic / Fill-in / Avoid |
RICE Score = (Reach × Impact × Confidence) / Effort
| Feature | Reach (users impacted/mo) | Impact (0.25/0.5/1/2/3) | Confidence (%) | Effort (person-months) | RICE Score |
|---------|--------------------------|------------------------|----------------|----------------------|------------|
| | | | | | |
Impact Scale Definitions:
| Score | Level | Criteria |
|---|---|---|
| 3 | Massive | Fundamentally changes the user experience; directly solves the core JTBD |
| 2 | High | Significantly improves user experience; clear positive impact on the North Star Metric |
| 1 | Medium | Noticeable improvement; helpful for some users or some scenarios |
| 0.5 | Low | Minor improvement; nice-to-have |
| 0.25 | Minimal | Barely noticeable difference; maintenance-level work |
Confidence Judgment Reference:
"Don't prioritize features — prioritize problems. Features are solutions, and they only matter after you've confirmed the priority of the problems." — Shreyas Doshi