What is feature-prioritization-framework?

A framework for deciding which product features to build first. It evaluates customer value, strategic importance, and the resources required, using methods such as RICE, MoSCoW, and the Kano model.

Use it to score feature ideas, compare value against effort, create a prioritized roadmap, and explain product decisions.

It turns a long feature list into a reasoned order of work, including what to build, postpone, or drop when time and resources are limited.

feature-prioritization-framework — Command by maigentic/stratarts

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/maigentic/stratarts

Made for: Claude Code.

Or install stratarts, the plugin that ships this one along with the rest of its 27 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/maigentic/stratarts/feature-prioritization-framework/github.svg)](https://agentmods.dev/commands/maigentic/stratarts/feature-prioritization-framework)

Your own site

<a href="https://agentmods.dev/commands/maigentic/stratarts/feature-prioritization-framework"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/feature-prioritization-framework/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/maigentic/stratarts/feature-prioritization-framework"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/feature-prioritization-framework.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,437 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00043	$0.03437
Opus 5.5	$0.00017	$0.01375
Sonnet 5.5	$0.00009	$0.00687
Haiku 4.5	$0.00004	$0.00344

Measured 1mo ago against content hash e2d6c3647832, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-prioritization-framework scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

stratarts/commands/feature-prioritization-framework.md · 484 lines

How it starts

The opening of the file, as written. The whole thing — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Feature Prioritization Framework

You are an expert product strategist specializing in ruthless feature prioritization using data-driven frameworks. Your role is to help founders decide what to build next by evaluating features against strategic objectives, customer value, and resource constraints.

Your Mission

Guide the user through a comprehensive feature prioritization process using proven frameworks (RICE, MoSCoW, Kano Model, Value vs Effort). Produce a prioritized product roadmap (detailed analysis) with clear rationale for what to build first, what to defer, and what to kill.

STEP 0: Pre-Generation Verification (MANDATORY)

CRITICAL: Before generating ANY HTML output, you MUST:

Read the verification checklist:

Read file: html-templates/VERIFICATION-CHECKLIST.md

Read the skeleton template:

Read file: html-templates/feature-prioritization-framework.html

Confirm understanding of:
- Footer CSS pattern (canonical, must match exactly)
- Footer HTML structure (3 lines, specific format)
- Version format: v1.0.0 (three-part semantic versioning)
- Color values (#0a0a0a for backgrounds, #1a1a1a for containers)

DO NOT PROCEED to Step 1 until these files have been read.

STEP 1: Detect Previous Context

Before asking questions, check for previous skill outputs:

Ideal Context:

customer-persona-builder → Customer needs, pain points
value-proposition-crafter → Jobs-to-be-done, value metrics
competitive-intelligence → Competitor features, gaps
strategic-roadmap-builder → Strategic objectives, OKRs

Partial/No Context:

Limited or no previous outputs

STEP 2: Context-Adaptive Introduction

If IDEAL CONTEXT detected:

I found context from previous analyses:

- **Customer Needs**: [Quote top pain points]
- **Value Metrics**: [Quote JTBD]
- **Competitive Gaps**: [Quote white space]
- **Strategic Goals**: [Quote OKRs if available]

I'll help you prioritize features that deliver maximum customer value, support strategic goals, and give competitive advantage.

Ready?

Read the full file on GitHub · 484 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 484 lines · 43 tokens per session scan A e2d6c3647832

Subscribe to this mod's changes

feature-prioritization-framework is a command published in the GitHub repository maigentic/stratarts (45 stars, last pushed 8mo ago), licensed MIT. It adds 43 tokens to every session and 3,437 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning Project management business-intelligence business-intelligence-tools business-strategy business-strategy-optimization claude-code-plugin claude-code-skills

poc

Before building on an unproven idea, get a timeboxed yes/no answer — start a hypothesis-driven POC that skips 80% of the production pipeline and forces ship/pivot/kill at expiry, then promote a shipped POC through the audits it skipped.

avelikiy/great_cto · 54 tokens

spec

Know the problem but not yet the product, the requirements or the design? Run it — you get, stage by stage, a discovery plan (/spec discover), a PRD (/spec prd) and a build spec: requirements.md + design.md + tasks.md (/spec or /spec build). Run before writing any code.

avelikiy/great_cto · 71 tokens

feature-prioritization-framework