Forge-Prioritisation

Ranks and sequences proposed work items by value, risk, dependencies, and strategic importance.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-prioritisation-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Prioritisation
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/01-Product/Forge-Prioritisation
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-prioritisation-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often face competing features, technical tasks, and improvements with limited resources, making it unclear what to build first. This Skill provides a structured method to evaluate, compare, and sequence work so engineering effort goes to the highest-value outcomes with documented reasoning. ## Core Features & Use Cases - Work Item Evaluation: Assesses candidate features, user stories, improvements, and technical tasks against value, urgency, risk reduction, dependencies, and effort. - Prioritisation Assessment Output: Produces ranked work items, decision criteria, trade-offs, recommendations, and outstanding decisions using the Prioritisation-Matrix template. - Use Case: When a release backlog contains twenty competing items and scope must be reduced, apply this Skill to rank items by business impact and dependencies, then feed the ordering into the roadmap and task routing. ## Quick Start Ask the AI to apply Forge-Prioritisation to evaluate and rank the listed backlog items by value, risk, and dependencies, and produce a prioritisation assessment with a recommended ordering.

Frequently Asked Questions about Forge-Prioritisation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize a product backlog with competing features?▼

Gather candidate work items, assess each for value, urgency, risk reduction, dependencies, and effort, then compare options using a method like value versus effort. Document the recommended ordering, reasoning, and trade-offs in a prioritisation matrix.

What criteria should I use for feature prioritisation?▼

Use five criteria: value (user and business benefit), urgency (deadlines and commitments), risk reduction (security or technical exposure), dependencies (blocking relationships), and effort and complexity (development and maintenance cost).

When should I not use a prioritisation process?▼

Skip prioritisation when there is only one clearly defined task, requirements are not yet understood, technical investigation is still required, or a defect needs immediate resolution. Prioritisation adds overhead only worthwhile when multiple items compete.

How does prioritisation connect to roadmaps and task routing?▼

Prioritisation outcomes feed the roadmap template for release planning and guide task routing to determine execution order. Requirements analysis and user story definition supply the analysed work items that prioritisation ranks.

Does prioritisation replace product strategy or effort estimation?▼

No. Prioritisation does not make business decisions without stakeholder input, replace product strategy, define technical implementation, or estimate exact development effort. It only makes sequencing reasoning visible and records decisions.