القائمة
Applies MoSCoW prioritization method to categorize requirements by importance. Use for scope negotiations, release planning, or stakeholder alignment on priorities.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Drafts or converts documents into Product Requirements Documents (PRD). Supports two modes - (1) Create new PRD from initiative documents and research, or (2) Convert existing documents to PRD format using standard or daily iteration templates.
Generates new feature ideas based on user feedback, internal notes, and historical PRDs using advanced pattern recognition and semantic analysis. Use when planning quarterly roadmaps, responding to accumulated user feedback, identifying next features after major releases, or conducting strategic planning sessions.
Analyzes market opportunity and sizing using TAM/SAM/SOM framework with supporting data research. Use when evaluating market potential, creating business cases for new products, preparing investor presentations, or assessing business opportunities.
Creates a new product initiative document using Socratic questioning and guided discovery. Use when starting a new product feature, clarifying vague product ideas, structuring informal concepts into formal proposals, or aligning stakeholders on initiative scope and goals.
Applies first principles thinking to break down complex problems to fundamental truths and reconstruct innovative solutions. Use when facing seemingly impossible challenges, when existing solutions are too costly or complex, when innovative breakthroughs are needed, or when challenging industry assumptions.
Applies the Five Whys root cause analysis method to identify underlying causes of problems through systematic questioning. Use when problems recur despite fixes, surface solutions fail, systematic improvement is needed, or team alignment on root causes is required.
| name | niopd-st-moscow |
| description | Applies MoSCoW prioritization method to categorize requirements by importance. Use for scope negotiations, release planning, or stakeholder alignment on priorities. |
This skill applies the MoSCoW method to systematically categorize requirements, helping teams focus on what's truly essential.
MoSCoW was developed by Dai Clegg at Oracle in 1994 as part of the Dynamic Systems Development Method (DSDM). The name is an acronym for the four priority categories.
| Category | Meaning | Criteria |
|---|---|---|
| Must Have | Critical–no viable product without | Non-negotiable |
| Should Have | Important but not vital | High value, not critical |
| Could Have | Desirable if time permits | Nice to have |
| Won't Have | Explicitly excluded (this time) | Out of scope |
At most 60% of effort should go to Must Haves, ensuring buffer for the unexpected.
List all features/requirements from:
Clarify with stakeholders:
For each requirement:
Challenge each "Must Have":
Calculate effort distribution:
File path: 02-reports/[YYYYMMDD]-moscow-priorities-v0.md
Format:
## Must Have
- [Requirement]: [Rationale]
## Should Have
- [Requirement]: [Rationale]
## Could Have
- [Requirement]: [Rationale]
## Won't Have (This Release)
- [Requirement]: [Why excluded]
[YYYYMMDD]-moscow-priorities-v0.md02-reports/references/moscow-template.mdniopd-st-rice: Quantitative prioritizationniopd-ur-kano: Satisfaction-based categorizationniopd-pd-roadmap: Roadmap planningniopd-pm-release: Release planning