skills.rest
wfukatsu
wfukatsuCOMMUNITY
Explore all skills by this author →
GitHub

define-scope

Normalize constraints and apply MoSCoW and RICE criteria to define product scope.

12|1|Updated Mar 23, 2026
Search Tags:#project planning#MoSCoW#RICE#product scope#constraint normalization
One-click install
npx skills add https://github.com/wfukatsu/nexus-architect --skill define-scope-wfukatsu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: define-scope
Source: https://github.com/wfukatsu/nexus-architect/tree/main/skills/product/define-scope
Command: npx skills add https://github.com/wfukatsu/nexus-architect --skill define-scope-wfukatsu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in defining the scope of a product by normalizing constraints and using MoSCoW and RICE criteria, ensuring that the product's capabilities and limitations are clearly outlined.

Core Features & Use Cases

  • Constraint Normalization: Takes in constraints and normalizes them for clarity.
  • Scope Definition: Determines what the product will and will not do, using MoSCoW and RICE methods.
  • Deliverables: Produces a report detailing constraints and scope definition.
  • Use Case: When starting a new project, use this Skill to define the scope, ensuring that all stakeholders have a clear understanding of the project's boundaries.

Quick Start

Use the /product:define-scope command to initiate the scope definition process.

Frequently Asked Questions about define-scope

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

FAQPage Schema
How do I define product scope using MoSCoW and RICE criteria?▼

To define product scope, normalize your project constraints and analyze vision, success metrics, and constraints to apply MoSCoW and RICE criteria, generating a report of in-scope and out-of-scope items.

What is constraint normalization in project planning?▼

Constraint normalization in project planning standardizes project limitations for clarity before applying MoSCoW and RICE criteria to determine final product scope and boundaries.

How do I prioritize product features with RICE scores and MoSCoW classification?▼

Prioritize product features by analyzing vision, success metrics, and constraints, then apply MoSCoW classification to categorize requirements and RICE scores to quantify their overall priority.

What inputs do I need to determine in-scope and out-of-scope product items?▼

Determining in-scope and out-of-scope product items requires analyzing your product vision, success metrics, and constraints, which are then normalized and evaluated using MoSCoW and RICE methods.

Can I use this product scope definition approach for any project scale?▼

Yes, constraint normalization and MoSCoW and RICE criteria can be applied to any project scale to clearly outline capabilities and limitations for stakeholders during project planning.

When should I not use MoSCoW and RICE for product scope definition?▼

Avoid using MoSCoW and RICE for product scope definition if you lack clear vision, success metrics, or constraints, as these inputs are required to normalize constraints and generate accurate scope reports.

Related Skills

Explore More Product & Management Skills→
dangelesdangeles
6

experimental-planner

Design experimental protocols with success criteria, controls, and prioritized experiments.

Community
Advanced
rafazshrafazsh

project-planner

Break down complex projects into tasks, timelines, dependencies, and milestones.

Community
Intermediate
Dev-Dennis-040Dev-Dennis-040
10

product-sprint-prioritizer

Automate backlog prioritization for sprint planning using RICE, MoSCoW, and Kano scoring.

Community
Advanced
menkesumenkesu
389

prioritization-craft

Prioritize backlog items using RICE scoring, Value vs Effort, and Kano modeling.

Community
Intermediate