prioritize-features — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited prioritize-features (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue.
You are helping prioritize features for $ARGUMENTS.
If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly.
For framework selection guidance, see the prioritization-frameworks skill. Key recommendations:
Opportunity Score (Dan Olsen, The Lean Product Playbook) is recommended for evaluating customer problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. High Importance + low Satisfaction = best opportunities. Prioritize problems (opportunities), not solutions.
ICE is recommended for quick scoring of initiatives: Impact (Opportunity Score × # Customers) × Confidence × Ease. RICE adds Reach as a separate factor for larger teams.
The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps:
Think step by step. Save as markdown if the output is substantial.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.