Skill

Skill: release-scope

Define and structure the scope of an upcoming release using MoSCoW prioritization. Helps delivery managers align teams around what's in, what's out, and what's deferred.

Install

npx claudepluginhub devmuslim/pdm-skills --plugin pdm-release-planning

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Define and structure the scope of an upcoming release using MoSCoW prioritization. Helps delivery managers align teams around what's in, what's out, and what's deferred.

SKILL.md

Similar Skills

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.8k

startup-financial-modeling

Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.

startup-business-analyst

32.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Skill: release-scope

Purpose

Define and structure the scope of an upcoming release using MoSCoW prioritization. Helps delivery managers align teams around what's in, what's out, and what's deferred.

When to Use

Starting a new release planning cycle
Scope is unclear or contested across teams
Need to communicate scope decisions to stakeholders

Framework: Structured Scope Definition

Step 1 — Gather Inputs

Ask for:

List of features/requirements proposed for the release
Target release date or sprint count
Team size and composition
Any non-negotiable items (regulatory, contractual, dependencies)

Step 2 — Apply MoSCoW

Classify each item:

Must Have — Release fails without this. Non-negotiable.
Should Have — High value, but workarounds exist. Include if capacity allows.
Could Have — Nice-to-have. First to cut under pressure.
Won't Have (this time) — Explicitly out of scope for this release.

Step 3 — Scope Summary Table

Output a table:

Item	Category	Rationale	Owner	Estimated Effort
...	Must	...	...	...

Step 4 — Scope Risks

Flag items where:

Effort is uncertain (spike needed)
External dependency exists
Two teams need to coordinate

Step 5 — Scope Statement

Write a 2-sentence scope statement suitable for stakeholder communication:

"Release X will deliver [Must Haves] enabling [business outcome]. The following items are explicitly deferred to Release Y: [Won't Haves]."

Output Format

MoSCoW table
Scope risks list
Scope statement (stakeholder-ready)
Suggested next command: /map-dependencies or /assess-readiness