[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70NF3ZAZ5X9P0TK7YVRZBEW":3,"skill-same:01M70NF3ZAZ5X9P0TK7YVRZBEW":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M70NF3ZAZ5X9P0TK7YVRZBEW","feature-prioritization",null,"RICE, MoSCoW, Kano, and value-effort prioritization frameworks with scoring methodologies and decision documentation. Use when prioritizing features, evaluating competing initiatives, creating roadmaps, or making build vs defer decisions.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Ffeature-prioritization\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"prioritization","feature","feature prioritization","Kano","build","with","decisions","use","frameworks","value","rice","features","documentation","prioritization frameworks","scoring","when","decision","2026-11-10 10:12:30",false,"---\nname: feature-prioritization\ndescription: RICE, MoSCoW, Kano, and value-effort prioritization frameworks with scoring methodologies and decision documentation. Use when prioritizing features, evaluating competing initiatives, creating roadmaps, or making build vs defer decisions.\n---\n\n# Prioritization Framework Application\n\nSystematic frameworks for making objective prioritization decisions that balance value, effort, and strategic alignment.\n\n## When to Activate\n\n- Prioritizing feature backlogs\n- Evaluating competing initiatives\n- Making build vs defer decisions\n- Creating product roadmaps\n- Allocating limited resources\n- Justifying prioritization decisions to stakeholders\n\n## RICE Framework\n\nQuantitative scoring for comparing initiatives objectively.\n\n### Formula\n\n```\nRICE Score = (Reach × Impact × Confidence) \u002F Effort\n```\n\n### Components\n\n| Factor | Description | Scale |\n|--------|-------------|-------|\n| **Reach** | How many users affected per quarter | Actual number (100, 1000, 10000) |\n| **Impact** | Effect on each user | 0.25 (Minimal) to 3 (Massive) |\n| **Confidence** | How sure are we | 50% (Low) to 100% (High) |\n| **Effort** | Person-months required | Actual estimate (0.5, 1, 3, 6) |\n\n### Impact Scale\n\n| Score | Label | Description |\n|-------|-------|-------------|\n| 3 | Massive | Life-changing for users, core workflow transformation |\n| 2 | High | Major improvement, significant time savings |\n| 1 | Medium | Noticeable improvement, minor friction reduction |\n| 0.5 | Low | Slight improvement, nice-to-have |\n| 0.25 | Minimal | Barely noticeable difference |\n\n### Confidence Scale\n\n| Score | Label | Basis |\n|-------|-------|-------|\n| 100% | High | User research + validated data + successful tests |\n| 80% | Medium | Some data + team experience + analogous examples |\n| 50% | Low | Intuition only, no supporting data |\n\n### Example Calculation\n\n```\nFeature: One-click reorder\n\nReach: 5,000 (customers who reorder monthly)\nImpact: 2 (High - saves significant time)\nConfidence: 80% (Based on support ticket analysis)\nEffort: 1 person-month\n\nRICE = (5000 × 2 × 0.8) \u002F 1 = 8000\n\nFeature: Dark mode\n\nReach: 20,000 (all active users)\nImpact: 0.5 (Low - preference, not productivity)\nConfidence: 50% (No data, user requests only)\nEffort: 2 person-months\n\nRICE = (20000 × 0.5 × 0.5) \u002F 2 = 2500\n\nDecision: One-click reorder scores higher, prioritize first\n```\n\n### RICE Template\n\n| Feature | Reach | Impact | Confidence | Effort | Score | Rank |\n|---------|-------|--------|------------|--------|-------|------|\n| Feature A | 5000 | 2 | 80% | 1 | 8000 | 1 |\n| Feature B | 20000 | 0.5 | 50% | 2 | 2500 | 2 |\n\n## Value vs Effort Matrix\n\nVisual framework for quick categorization.\n\n### The Matrix\n\n```\n              High Value\n                   │\n    ┌──────────────┼──────────────┐\n    │              │              │\n    │  QUICK WINS  │  STRATEGIC   │\n    │  Do First    │  Plan & Do   │\n    │              │              │\n    ├──────────────┼──────────────┤ High\nLow │              │              │ Effort\nEffort             │              │\n    │  FILL-INS    │  TIME SINKS  │\n    │  If Spare    │  Avoid       │\n    │  Capacity    │              │\n    │              │              │\n    └──────────────┼──────────────┘\n                   │\n              Low Value\n```\n\n### Quadrant Actions\n\n| Quadrant | Characteristics | Action |\n|----------|-----------------|--------|\n| **Quick Wins** | High value, low effort | Do immediately |\n| **Strategic** | High value, high effort | Plan carefully, staff appropriately |\n| **Fill-Ins** | Low value, low effort | Do when nothing else is ready |\n| **Time Sinks** | Low value, high effort | Don't do (or simplify drastically) |\n\n### Estimation Guidance\n\n**Value Assessment:**\n- Revenue impact\n- Cost reduction\n- User satisfaction improvement\n- Strategic alignment\n- Risk reduction\n\n**Effort Assessment:**\n- Development time\n- Design complexity\n- Testing requirements\n- Deployment complexity\n- Ongoing maintenance\n\n## Kano Model\n\nCategorize features by their impact on satisfaction.\n\n### Categories\n\n```\nSatisfaction\n     ▲\n     │         ╱ Delighters\n     │       ╱   (Unexpected features)\n     │     ╱\n─────┼────●──────────────────────────► Feature\n     │    │╲                           Implementation\n     │    │  ╲ Performance\n     │    │    (More is better)\n     │    │\n     │    └── Must-Haves\n     │         (Expected, dissatisfaction if missing)\n     ▼\n```\n\n### Category Definitions\n\n| Category | Present | Absent | Example |\n|----------|---------|--------|---------|\n| **Must-Have** | Neutral | Very dissatisfied | Login functionality |\n| **Performance** | More = better | Less = worse | Page load speed |\n| **Delighter** | Very satisfied | Neutral | Personalized recommendations |\n| **Indifferent** | No effect | No effect | Backend tech choice |\n| **Reverse** | Dissatisfied | Satisfied | Forced tutorials |\n\n### Kano Survey Questions\n\nFor each feature, ask two questions:\n\n```\nFunctional: \"If [feature] were present, how would you feel?\"\nDysfunctional: \"If [feature] were absent, how would you feel?\"\n\nAnswer Options:\n1. I like it\n2. I expect it\n3. I'm neutral\n4. I can tolerate it\n5. I dislike it\n```\n\n### Interpretation Matrix\n\n|  | Like | Expect | Neutral | Tolerate | Dislike |\n|--|------|--------|---------|----------|---------|\n| **Like** | Q | A | A | A | O |\n| **Expect** | R | I | I | I | M |\n| **Neutral** | R | I | I | I | M |\n| **Tolerate** | R | I | I | I | M |\n| **Dislike** | R | R | R | R | Q |\n\nKey: M=Must-Have, O=One-dimensional, A=Attractive, I=Indifferent, R=Reverse, Q=Questionable\n\n## MoSCoW Method\n\nSimple categorization for scope definition.\n\n### Categories\n\n| Category | Definition | Negotiability |\n|----------|------------|---------------|\n| **Must** | Critical for success, release blocked without | Non-negotiable |\n| **Should** | Important but not critical | Can defer to next release |\n| **Could** | Nice to have, minor impact | First to cut if needed |\n| **Won't** | Explicitly excluded from scope | Not this release |\n\n### Application Rules\n\n```\nBudget Allocation (Recommended):\n- Must: 60% of capacity\n- Should: 20% of capacity\n- Could: 20% of capacity (buffer)\n- Won't: 0% (explicitly excluded)\n\nWhy the buffer matters:\n- Must items often take longer than estimated\n- Should items may become Must if requirements change\n- Could items fill capacity at sprint end\n```\n\n### Example\n\n```\nFeature: User Registration\n\nMUST:\n✓ Email\u002Fpassword signup\n✓ Email verification\n✓ Password requirements enforcement\n\nSHOULD:\n○ Social login (Google)\n○ Remember me functionality\n○ Password strength indicator\n\nCOULD:\n◐ Social login (Facebook, Apple)\n◐ Profile picture upload\n◐ Username suggestions\n\nWON'T (this release):\n✗ Two-factor authentication\n✗ SSO integration\n✗ Biometric login\n```\n\n## Cost of Delay\n\nPrioritize by economic impact of waiting.\n\n### CD3 Formula\n\n```\nCD3 = Cost of Delay \u002F Duration\n\nCost of Delay: Weekly value lost by not having the feature\nDuration: Weeks to implement\n```\n\n### Delay Cost Types\n\n| Type | Description | Calculation |\n|------|-------------|-------------|\n| **Revenue** | Sales not captured | Lost deals × average value |\n| **Cost** | Ongoing expenses | Weekly operational cost |\n| **Risk** | Penalty or loss potential | Probability × impact |\n| **Opportunity** | Market window | Revenue × time sensitivity |\n\n### Urgency Profiles\n\n```\n                Value\n                  │\nStandard:         │────────────────\n                  │\n                  └──────────────────► Time\n\nUrgent:           │╲\n                  │  ╲\n                  │    ╲──────────\n                  │\n                  └──────────────────► Time\n\nDeadline:         │\n                  │────────┐\n                  │        │\n                  │        └─ (drops to zero)\n                  └──────────────────► Time\n```\n\n### Example\n\n```\nFeature A: New payment method\n- Cost of Delay: $10,000\u002Fweek (lost sales to competitor)\n- Duration: 4 weeks\n- CD3 = 10000 \u002F 4 = 2500\n\nFeature B: Admin dashboard redesign\n- Cost of Delay: $2,000\u002Fweek (support inefficiency)\n- Duration: 2 weeks\n- CD3 = 2000 \u002F 2 = 1000\n\nFeature C: Compliance update (deadline in 6 weeks)\n- Cost of Delay: $50,000\u002Fweek after deadline (fines)\n- Duration: 4 weeks\n- CD3 = 50000 \u002F 4 = 12500 (if started now, 0 if after deadline)\n\nPriority: C (deadline), then A (highest CD3), then B\n```\n\n## Weighted Scoring\n\nCustom scoring for organization-specific criteria.\n\n### Building a Weighted Model\n\n```\nStep 1: Define Criteria\n- Strategic alignment\n- Revenue potential\n- User demand\n- Technical feasibility\n- Competitive advantage\n\nStep 2: Assign Weights (total = 100%)\n| Criterion | Weight |\n|-----------|--------|\n| Strategic | 30% |\n| Revenue | 25% |\n| User demand | 20% |\n| Feasibility | 15% |\n| Competitive | 10% |\n\nStep 3: Score Each Feature (1-5 scale)\n| Feature | Strategic | Revenue | Demand | Feasible | Competitive | Total |\n|---------|-----------|---------|--------|----------|-------------|-------|\n| A | 5 | 4 | 3 | 4 | 2 | 3.95 |\n| B | 3 | 5 | 5 | 3 | 3 | 3.90 |\n| C | 4 | 3 | 4 | 5 | 4 | 3.85 |\n```\n\n### Calculation\n\n```\nScore = Σ (criterion_score × criterion_weight)\n\nFeature A:\n= (5 × 0.30) + (4 × 0.25) + (3 × 0.20) + (4 × 0.15) + (2 × 0.10)\n= 1.5 + 1.0 + 0.6 + 0.6 + 0.2\n= 3.9\n```\n\n## Decision Documentation\n\n### Priority Decision Record\n\n```markdown\n# Priority Decision: [Feature\u002FInitiative]\n\n## Date: [YYYY-MM-DD]\n## Decision: [Prioritize \u002F Defer \u002F Reject]\n\n## Context\n[What prompted this decision?]\n\n## Evaluation\n\n### Framework Used: [RICE \u002F Kano \u002F MoSCoW \u002F Weighted]\n\n### Scores\n[Show calculations or categorization]\n\n### Trade-offs Considered\n- Option A: [description] - [pros\u002Fcons]\n- Option B: [description] - [pros\u002Fcons]\n\n## Decision Rationale\n[Why this priority over alternatives?]\n\n## Stakeholders\n- Agreed: [names]\n- Disagreed: [names, reasons documented]\n\n## Review Date\n[When to revisit if deferred]\n```\n\n## Framework Selection Guide\n\n| Situation | Recommended Framework |\n|-----------|----------------------|\n| Comparing many similar features | RICE (quantitative) |\n| Quick triage of backlog | Value vs Effort |\n| Understanding user expectations | Kano Model |\n| Defining release scope | MoSCoW |\n| Time-sensitive decisions | Cost of Delay |\n| Organization-specific criteria | Weighted Scoring |\n\n## Anti-Patterns\n\n| Anti-Pattern | Problem | Solution |\n|--------------|---------|----------|\n| **HiPPO** | Highest-paid person's opinion wins | Use data-driven frameworks |\n| **Recency Bias** | Last request gets priority | Systematic evaluation of all options |\n| **Squeaky Wheel** | Loudest stakeholder wins | Weight by strategic value |\n| **Analysis Paralysis** | Over-analyzing decisions | Time-box evaluation |\n| **Sunken Cost** | Continuing failed initiatives | Evaluate future value only |\n| **Feature Factory** | Shipping without measuring | Tie features to outcomes |\n\n## Best Practices\n\n1. **Use multiple frameworks** - Validate with different approaches\n2. **Document decisions** - Enable future learning\n3. **Revisit regularly** - Priorities change as context evolves\n4. **Include stakeholders** - Ensure buy-in\n5. **Measure outcomes** - Validate prioritization quality\n\n## References\n\n- [RICE Scoring Template](examples\u002Frice-template.md) - Spreadsheet template\n- [Prioritization Workshop Guide](reference.md) - Facilitation guide\n","# Prioritization Framework Application\n\nSystematic frameworks for making objective prioritization decisions that balance value, effort, and strategic alignment.\n\n## When to Activate\n\n- Prioritizing feature backlogs\n- Evaluating competing initiatives\n- Making build vs defer decisions\n- Creating product roadmaps\n- Allocating limited resources\n- Justifying prioritization decisions to stakeholders\n\n## RICE Framework\n\nQuantitative scoring for comparing initiatives objectively.\n\n### Formula\n\n```\nRICE Score = (Reach × Impact × Confidence) \u002F Effort\n```\n\n### Components\n\n| Factor | Description | Scale |\n|--------|-------------|-------|\n| **Reach** | How many users affected per quarter | Actual number (100, 1000, 10000) |\n| **Impact** | Effect on each user | 0.25 (Minimal) to 3 (Massive) |\n| **Confidence** | How sure are we | 50% (Low) to 100% (High) |\n| **Effort** | Person-months required | Actual estimate (0.5, 1, 3, 6) |\n\n### Impact Scale\n\n| Score | Label | Description |\n|-------|-------|-------------|\n| 3 | Massive | Life-changing for users, core workflow transformation |\n| 2 | High | Major improvement, significant time savings |\n| 1 | Medium | Noticeable improvement, minor friction reduction |\n| 0.5 | Low | Slight improvement, nice-to-have |\n| 0.25 | Minimal | Barely noticeable difference |\n\n### Confidence Scale\n\n| Score | Label | Basis |\n|-------|-------|-------|\n| 100% | High | User research + validated data + successful tests |\n| 80% | Medium | Some data + team experience + analogous examples |\n| 50% | Low | Intuition only, no supporting data |\n\n### Example Calculation\n\n```\nFeature: One-click reorder\n\nReach: 5,000 (customers who reorder monthly)\nImpact: 2 (High - saves significant time)\nConfidence: 80% (Based on support ticket analysis)\nEffort: 1 person-month\n\nRICE = (5000 × 2 × 0.8) \u002F 1 = 8000\n\nFeature: Dark mode\n\nReach: 20,000 (all active users)\nImpact: 0.5 (Low - preference, not productivity)\nConfidence: 50% (No data, user requests only)\nEffort: 2 person-months\n\nRICE = (20000 × 0.5 × 0.5) \u002F 2 = 2500\n\nDecision: One-click reorder scores higher, prioritize first\n```\n\n### RICE Template\n\n| Feature | Reach | Impact | Confidence | Effort | Score | Rank |\n|---------|-------|--------|------------|--------|-------|------|\n| Feature A | 5000 | 2 | 80% | 1 | 8000 | 1 |\n| Feature B | 20000 | 0.5 | 50% | 2 | 2500 | 2 |\n\n## Value vs Effort Matrix\n\nVisual framework for quick categorization.\n\n### The Matrix\n\n```\n              High Value\n                   │\n    ┌──────────────┼──────────────┐\n    │              │              │\n    │  QUICK WINS  │  STRATEGIC   │\n    │  Do First    │  Plan & Do   │\n    │              │              │\n    ├──────────────┼──────────────┤ High\nLow │              │              │ Effort\nEffort             │              │\n    │  FILL-INS    │  TIME SINKS  │\n    │  If Spare    │  Avoid       │\n    │  Capacity    │              │\n    │              │              │\n    └──────────────┼──────────────┘\n                   │\n              Low Value\n```\n\n### Quadrant Actions\n\n| Quadrant | Characteristics | Action |\n|----------|-----------------|--------|\n| **Quick Wins** | High value, low effort | Do immediately |\n| **Strategic** | High value, high effort | Plan carefully, staff appropriately |\n| **Fill-Ins** | Low value, low effort | Do when nothing else is ready |\n| **Time Sinks** | Low value, high effort | Don't do (or simplify drastically) |\n\n### Estimation Guidance\n\n**Value Assessment:**\n- Revenue impact\n- Cost reduction\n- User satisfaction improvement\n- Strategic alignment\n- Risk reduction\n\n**Effort Assessment:**\n- Development time\n- Design complexity\n- Testing requirements\n- Deployment complexity\n- Ongoing maintenance\n\n## Kano Model\n\nCategorize features by their impact on satisfaction.\n\n### Categories\n\n```\nSatisfaction\n     ▲\n     │         ╱ Delighters\n     │       ╱   (Unexpected features)\n     │     ╱\n─────┼────●──────────────────────────► Feature\n     │    │╲                           Implementation\n     │    │  ╲ Performance\n     │    │    (More is better)\n     │    │\n     │    └── Must-Haves\n     │         (Expected, dissatisfaction if missing)\n     ▼\n```\n\n### Category Definitions\n\n| Category | Present | Absent | Example |\n|----------|---------|--------|---------|\n| **Must-Have** | Neutral | Very dissatisfied | Login functionality |\n| **Performance** | More = better | Less = worse | Page load speed |\n| **Delighter** | Very satisfied | Neutral | Personalized recommendations |\n| **Indifferent** | No effect | No effect | Backend tech choice |\n| **Reverse** | Dissatisfied | Satisfied | Forced tutorials |\n\n### Kano Survey Questions\n\nFor each feature, ask two questions:\n\n```\nFunctional: \"If [feature] were present, how would you feel?\"\nDysfunctional: \"If [feature] were absent, how would you feel?\"\n\nAnswer Options:\n1. I like it\n2. I expect it\n3. I'm neutral\n4. I can tolerate it\n5. I dislike it\n```\n\n### Interpretation Matrix\n\n|  | Like | Expect | Neutral | Tolerate | Dislike |\n|--|------|--------|---------|----------|---------|\n| **Like** | Q | A | A | A | O |\n| **Expect** | R | I | I | I | M |\n| **Neutral** | R | I | I | I | M |\n| **Tolerate** | R | I | I | I | M |\n| **Dislike** | R | R | R | R | Q |\n\nKey: M=Must-Have, O=One-dimensional, A=Attractive, I=Indifferent, R=Reverse, Q=Questionable\n\n## MoSCoW Method\n\nSimple categorization for scope definition.\n\n### Categories\n\n| Category | Definition | Negotiability |\n|----------|------------|---------------|\n| **Must** | Critical for success, release blocked without | Non-negotiable |\n| **Should** | Important but not critical | Can defer to next release |\n| **Could** | Nice to have, minor impact | First to cut if needed |\n| **Won't** | Explicitly excluded from scope | Not this release |\n\n### Application Rules\n\n```\nBudget Allocation (Recommended):\n- Must: 60% of capacity\n- Should: 20% of capacity\n- Could: 20% of capacity (buffer)\n- Won't: 0% (explicitly excluded)\n\nWhy the buffer matters:\n- Must items often take longer than estimated\n- Should items may become Must if requirements change\n- Could items fill capacity at sprint end\n```\n\n### Example\n\n```\nFeature: User Registration\n\nMUST:\n✓ Email\u002Fpassword signup\n✓ Email verification\n✓ Password requirements enforcement\n\nSHOULD:\n○ Social login (Google)\n○ Remember me functionality\n○ Password strength indicator\n\nCOULD:\n◐ Social login (Facebook, Apple)\n◐ Profile picture upload\n◐ Username suggestions\n\nWON'T (this release):\n✗ Two-factor authentication\n✗ SSO integration\n✗ Biometric login\n```\n\n## Cost of Delay\n\nPrioritize by economic impact of waiting.\n\n### CD3 Formula\n\n```\nCD3 = Cost of Delay \u002F Duration\n\nCost of Delay: Weekly value lost by not having the feature\nDuration: Weeks to implement\n```\n\n### Delay Cost Types\n\n| Type | Description | Calculation |\n|------|-------------|-------------|\n| **Revenue** | Sales not captured | Lost deals × average value |\n| **Cost** | Ongoing expenses | Weekly operational cost |\n| **Risk** | Penalty or loss potential | Probability × impact |\n| **Opportunity** | Market window | Revenue × time sensitivity |\n\n### Urgency Profiles\n\n```\n                Value\n                  │\nStandard:         │────────────────\n                  │\n                  └──────────────────► Time\n\nUrgent:           │╲\n                  │  ╲\n                  │    ╲──────────\n                  │\n                  └──────────────────► Time\n\nDeadline:         │\n                  │────────┐\n                  │        │\n                  │        └─ (drops to zero)\n                  └──────────────────► Time\n```\n\n### Example\n\n```\nFeature A: New payment method\n- Cost of Delay: $10,000\u002Fweek (lost sales to competitor)\n- Duration: 4 weeks\n- CD3 = 10000 \u002F 4 = 2500\n\nFeature B: Admin dashboard redesign\n- Cost of Delay: $2,000\u002Fweek (support inefficiency)\n- Duration: 2 weeks\n- CD3 = 2000 \u002F 2 = 1000\n\nFeature C: Compliance update (deadline in 6 weeks)\n- Cost of Delay: $50,000\u002Fweek after deadline (fines)\n- Duration: 4 weeks\n- CD3 = 50000 \u002F 4 = 12500 (if started now, 0 if after deadline)\n\nPriority: C (deadline), then A (highest CD3), then B\n```\n\n## Weighted Scoring\n\nCustom scoring for organization-specific criteria.\n\n### Building a Weighted Model\n\n```\nStep 1: Define Criteria\n- Strategic alignment\n- Revenue potential\n- User demand\n- Technical feasibility\n- Competitive advantage\n\nStep 2: Assign Weights (total = 100%)\n| Criterion | Weight |\n|-----------|--------|\n| Strategic | 30% |\n| Revenue | 25% |\n| User demand | 20% |\n| Feasibility | 15% |\n| Competitive | 10% |\n\nStep 3: Score Each Feature (1-5 scale)\n| Feature | Strategic | Revenue | Demand | Feasible | Competitive | Total |\n|---------|-----------|---------|--------|----------|-------------|-------|\n| A | 5 | 4 | 3 | 4 | 2 | 3.95 |\n| B | 3 | 5 | 5 | 3 | 3 | 3.90 |\n| C | 4 | 3 | 4 | 5 | 4 | 3.85 |\n```\n\n### Calculation\n\n```\nScore = Σ (criterion_score × criterion_weight)\n\nFeature A:\n= (5 × 0.30) + (4 × 0.25) + (3 × 0.20) + (4 × 0.15) + (2 × 0.10)\n= 1.5 + 1.0 + 0.6 + 0.6 + 0.2\n= 3.9\n```\n\n## Decision Documentation\n\n### Priority Decision Record\n\n```markdown\n# Priority Decision: [Feature\u002FInitiative]\n\n## Date: [YYYY-MM-DD]\n## Decision: [Prioritize \u002F Defer \u002F Reject]\n\n## Context\n[What prompted this decision?]\n\n## Evaluation\n\n### Framework Used: [RICE \u002F Kano \u002F MoSCoW \u002F Weighted]\n\n### Scores\n[Show calculations or categorization]\n\n### Trade-offs Considered\n- Option A: [description] - [pros\u002Fcons]\n- Option B: [description] - [pros\u002Fcons]\n\n## Decision Rationale\n[Why this priority over alternatives?]\n\n## Stakeholders\n- Agreed: [names]\n- Disagreed: [names, reasons documented]\n\n## Review Date\n[When to revisit if deferred]\n```\n\n## Framework Selection Guide\n\n| Situation | Recommended Framework |\n|-----------|----------------------|\n| Comparing many similar features | RICE (quantitative) |\n| Quick triage of backlog | Value vs Effort |\n| Understanding user expectations | Kano Model |\n| Defining release scope | MoSCoW |\n| Time-sensitive decisions | Cost of Delay |\n| Organization-specific criteria | Weighted Scoring |\n\n## Anti-Patterns\n\n| Anti-Pattern | Problem | Solution |\n|--------------|---------|----------|\n| **HiPPO** | Highest-paid person's opinion wins | Use data-driven frameworks |\n| **Recency Bias** | Last request gets priority | Systematic evaluation of all options |\n| **Squeaky Wheel** | Loudest stakeholder wins | Weight by strategic value |\n| **Analysis Paralysis** | Over-analyzing decisions | Time-box evaluation |\n| **Sunken Cost** | Continuing failed initiatives | Evaluate future value only |\n| **Feature Factory** | Shipping without measuring | Tie features to outcomes |\n\n## Best Practices\n\n1. **Use multiple frameworks** - Validate with different approaches\n2. **Document decisions** - Enable future learning\n3. **Revisit regularly** - Priorities change as context evolves\n4. **Include stakeholders** - Ensure buy-in\n5. **Measure outcomes** - Validate prioritization quality\n\n## References\n\n- [RICE Scoring Template](examples\u002Frice-template.md) - Spreadsheet template\n- [Prioritization Workshop Guide](reference.md) - Facilitation guide\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Ffeature-prioritization",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill feature-prioritization",{"tool":57,"command":58},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill feature-prioritization",{"tool":60,"command":61},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill feature-prioritization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Ffeature-prioritization\u002FSKILL.md",true,[],[66,75,83,91,99,107],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":74},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":74},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":74},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":74},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":74},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":74},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]