[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F9Z12P42PVFF4M2T5M699K":3,"skill-same:01M6F9Z12P42PVFF4M2T5M699K":70},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":50,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":69},"01M6F9Z12P42PVFF4M2T5M699K","prioritization",null,"9 framework (RICE\u002FICE\u002FKano\u002FOpportunity Score\u002FMoSCoW\u002FWeighted\u002FEisenhower\u002FValue-vs-Effort\u002FCost-of-Delay) 비교 후 컨텍스트 맞춤 selection + 계산.","Adelie-Squad\u002Fsolosquad","Adelie-Squad","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269218606?v=4","01M6CHETAA89FK6KREADPVEF4T","SaPN","01M6CHETE7QEKZW6FK52137ZBP",25,"MIT","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fprioritization\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32],"planning","product","framework","leader","rice","cost","selection","chief","opportunity","false","true","manager","Kano","value","2026-11-10 10:12:30",false,"---\nname: prioritization\ndescription: 9 framework (RICE\u002FICE\u002FKano\u002FOpportunity Score\u002FMoSCoW\u002FWeighted\u002FEisenhower\u002FValue-vs-Effort\u002FCost-of-Delay) 비교 후 컨텍스트 맞춤 selection + 계산.\nschema_version: 2\ntier: leader\nteam: _skill\ncategory: planning\nused_by: [\"product-manager\", \"chief\"]\ndev_capability: false\ntriggers:\n  keyword:\n    - \"우선순위\"\n    - \"prioritization\"\n    - \"rice\"\n    - \"ice\"\n    - \"kano\"\n    - \"moscow\"\npm_conventions:\n  anti_sycophancy: true\n  hard_gate: false\n  post_labeling: true\n  minimum_approaches: 1\n---\n\n# Prioritization Skill\n\n## 9 Framework 매트릭스\n\n| Framework | 형식 | 적용 컨텍스트 |\n|---|---|---|\n| **RICE** | (Reach × Impact × Confidence) \u002F Effort | 분기 로드맵, 기능 우선순위 |\n| **ICE** | (Impact + Confidence + Ease) \u002F 3 | 빠른 직관 비교, ≤10 후보 |\n| **Kano** | Must-have \u002F Performance \u002F Excitement \u002F Indifferent \u002F Reverse | 신규 기능 분류 |\n| **Opportunity Score** | Importance × (1 - Satisfaction) | Discovery 단계, unmet need |\n| **MoSCoW** | Must \u002F Should \u002F Could \u002F Won't | Release 단위 분류 |\n| **Weighted** | Σ (weight × score) | 다기준 의사결정 (technical + business) |\n| **Eisenhower** | Urgent × Important 2×2 | Solo founder 일정 |\n| **Value vs Effort** | 2×2 matrix | quick wins 식별 |\n| **Cost of Delay** | $$ \u002F week | 의존성 \u002F 시간민감 작업 |\n\n## Framework 선택 가이드 (post-labeling)\n\nPM 이 후보 framework 를 직접 처방하지 않고, 컨텍스트에서 *어떤 분류가 자연스러운지* 식별:\n\n- 후보가 N≥20 → **RICE**\n- 후보가 N≤10 + 빠른 비교 → **ICE**\n- discovery 단계, unmet need 발굴 → **Opportunity Score**\n- release scope 결정 → **MoSCoW**\n- 신규 vs 기존 mix → **Kano**\n- 시간 민감 \u002F 의존성 → **Cost of Delay**\n\n## 계산 예시 (RICE)\n\n```yaml\ncandidates:\n  - title: \"feature A\"\n    reach: 1000        # 분기 영향 사용자 수\n    impact: 2          # 0.25 \u002F 0.5 \u002F 1 \u002F 2 \u002F 3 scale\n    confidence: 0.7    # 0-1\n    effort: 2          # person-month\n    rice_score: 700    # (1000 * 2 * 0.7) \u002F 2\n\n  - title: \"feature B\"\n    reach: 500\n    impact: 3\n    confidence: 0.5\n    effort: 1\n    rice_score: 750\n```\n\n## 출력\n\n```json\n{\n  \"framework_used\": \"RICE\",\n  \"framework_rationale\": \"후보 23개 → RICE 적합\",\n  \"ranked\": [\n    { \"id\": \"feature-B\", \"score\": 750, \"rank\": 1 },\n    { \"id\": \"feature-A\", \"score\": 700, \"rank\": 2 }\n  ],\n  \"recommended\": [\"feature-B\"],\n  \"deferred\": [\"feature-X\"]\n}\n```\n\n## Anti-Sycophancy\n\n- ❌ \"feature B 가 더 좋아 보입니다\"\n- ✅ \"feature B 가 RICE 750 으로 1위. effort \u003C 2 인 조건에서. effort 가 1.5 이상으로 재추정되면 feature A 가 1위로 역전.\"\n\n## Reference\n\n- phuryn\u002Fpm-skills\u002Fpm-execution\u002Fprioritization-frameworks (9 framework)\n- Intercom RICE framework\n- Kano model\n","# Prioritization Skill\n\n## 9 Framework 매트릭스\n\n| Framework | 형식 | 적용 컨텍스트 |\n|---|---|---|\n| **RICE** | (Reach × Impact × Confidence) \u002F Effort | 분기 로드맵, 기능 우선순위 |\n| **ICE** | (Impact + Confidence + Ease) \u002F 3 | 빠른 직관 비교, ≤10 후보 |\n| **Kano** | Must-have \u002F Performance \u002F Excitement \u002F Indifferent \u002F Reverse | 신규 기능 분류 |\n| **Opportunity Score** | Importance × (1 - Satisfaction) | Discovery 단계, unmet need |\n| **MoSCoW** | Must \u002F Should \u002F Could \u002F Won't | Release 단위 분류 |\n| **Weighted** | Σ (weight × score) | 다기준 의사결정 (technical + business) |\n| **Eisenhower** | Urgent × Important 2×2 | Solo founder 일정 |\n| **Value vs Effort** | 2×2 matrix | quick wins 식별 |\n| **Cost of Delay** | $$ \u002F week | 의존성 \u002F 시간민감 작업 |\n\n## Framework 선택 가이드 (post-labeling)\n\nPM 이 후보 framework 를 직접 처방하지 않고, 컨텍스트에서 *어떤 분류가 자연스러운지* 식별:\n\n- 후보가 N≥20 → **RICE**\n- 후보가 N≤10 + 빠른 비교 → **ICE**\n- discovery 단계, unmet need 발굴 → **Opportunity Score**\n- release scope 결정 → **MoSCoW**\n- 신규 vs 기존 mix → **Kano**\n- 시간 민감 \u002F 의존성 → **Cost of Delay**\n\n## 계산 예시 (RICE)\n\n```yaml\ncandidates:\n  - title: \"feature A\"\n    reach: 1000        # 분기 영향 사용자 수\n    impact: 2          # 0.25 \u002F 0.5 \u002F 1 \u002F 2 \u002F 3 scale\n    confidence: 0.7    # 0-1\n    effort: 2          # person-month\n    rice_score: 700    # (1000 * 2 * 0.7) \u002F 2\n\n  - title: \"feature B\"\n    reach: 500\n    impact: 3\n    confidence: 0.5\n    effort: 1\n    rice_score: 750\n```\n\n## 출력\n\n```json\n{\n  \"framework_used\": \"RICE\",\n  \"framework_rationale\": \"후보 23개 → RICE 적합\",\n  \"ranked\": [\n    { \"id\": \"feature-B\", \"score\": 750, \"rank\": 1 },\n    { \"id\": \"feature-A\", \"score\": 700, \"rank\": 2 }\n  ],\n  \"recommended\": [\"feature-B\"],\n  \"deferred\": [\"feature-X\"]\n}\n```\n\n## Anti-Sycophancy\n\n- ❌ \"feature B 가 더 좋아 보입니다\"\n- ✅ \"feature B 가 RICE 750 으로 1위. effort \u003C 2 인 조건에서. effort 가 1.5 이상으로 재추정되면 feature A 가 1위로 역전.\"\n\n## Reference\n\n- phuryn\u002Fpm-skills\u002Fpm-execution\u002Fprioritization-frameworks (9 framework)\n- Intercom RICE framework\n- Kano model\n",{"name":5,"team":38,"tier":22,"used_by":39,"category":19,"triggers":41,"description":7,"dev_capability":34,"pm_conventions":47,"schema_version":50},"_skill",[40,26],"product-manager",{"keyword":42},[43,5,23,44,45,46],"우선순위","ice","kano","moscow",{"hard_gate":34,"post_labeling":48,"anti_sycophancy":48,"minimum_approaches":49},true,1,2,"main","37b891996f0e5d7317b2abdd6e2a8acccdc94dff","skills\u002Fprioritization","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad","https:\u002F\u002Fgithub.com\u002FAdelie-Squad","2026-11-12 01:51:16",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":48},[59,62,65],{"tool":60,"command":61},"npx","npx skills add Adelie-Squad\u002Fsolosquad --skill prioritization",{"tool":63,"command":64},"bunx","bunx skills add Adelie-Squad\u002Fsolosquad --skill prioritization",{"tool":66,"command":67},"pnpm","pnpm dlx skills add Adelie-Squad\u002Fsolosquad --skill prioritization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fprioritization\u002FSKILL.md",[],[71,85,105,125,145,159],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":33},"01M6F9ZX66ETTM8NX73Z79MA21","xyz-hypothesis","검증 가능한 가설 프레임워크 — \"[X%] of [Y segment] will [Z behavior] within [T period], because [R]\". 입장+반증 조건 강제, 최소 2개 접근, V\u002FU\u002FV\u002FF 가정 분류. v1.3.5 에서 problem-definition P5 를 독립 skill 로 분리.","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fxyz-hypothesis\u002FSKILL.md",[],[78,79,22,80,81,30,29,82,83,28,26,84,20],"hypothesis","xyz hypothesis","definition","v1","segment","problem","behavior",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":96,"publishedAt":33},"01M6F9ZSHR17J5CH16AQAK0ER0","workflow-refinement","Workflow 종료 시 개선 제안. stage 의존성 \u002F handoff 효율 \u002F 평균 cycle time 분석. Chief 가 RETROSPECT 에서 호출.","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-refinement\u002FSKILL.md",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[97,98,99,100,101,102,29,28,103,104,26,22],"workflow","refinement","workflow refinement","handoff","cycle","agile","stage","time",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":33},"01M6F9ZKZJB8H3GWFJ95P6398V","workflow-manager","workflow(org 단위 조립물 — stage DAG 가 워크스페이스의 skill·agent 를 참조)의 대화형 매니저이자 작성 표준의 권위. 의도에서 workflow YAML 을 합성·검토·개선하도록 안내하고, 좋은 워크플로 노하우(본질 원칙=목표·근거·방법→결론·핸드오프 \u002F DAG 무순환 \u002F exit_criteria measurable \u002F 기획 3대 편향 가드)를 보유한다. 결정적 동작(new\u002Flist\u002Fshow\u002Fvalidate)은 solosquad workflow * 헬퍼로 위임. 사용 시점 — 워크플로를 새로 만들·고칠 때, 또는 다른 워크플로의 작성 품질을 판단할 때.","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-manager\u002FSKILL.md",[111],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[113,30,97,29,114,115,116,26,28,103,117,118,119,120,22,121,20,122,123,124],"workflow manager","new","make","org","solosquad","show","exit","list","yaml","dag","validate","core",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":33},"01M6F9ZH962BA0SABW0DKR0FAF","wbs","마일스톤 → WBS (Work Breakdown Structure) 분해. PM 핵심 산출물. team OKR 의 KR 을 분기→주→일 단위 작업으로 변환. dependency graph + critical path 식별.","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fwbs\u002FSKILL.md",[],[127,19,132,133,134,30,29,28,135,136,137,138,139,140,141,142,22,143,144,20],"structure","breakdown","path","critical","decomposition","pm","dependency graph","dependency","okr","work","schedule","team","graph",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":33},"01M6F9ZE85QYBBX4XMM0W71YN3","triage","Chief 의 과제 분류 도구. 사용자 입력을 4-way 분류 (discussion \u002F workflow \u002F cron \u002F goal) + Educational Nudge (불명확 시 KNOWLEDGE 가이드 선제시).","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[151],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[147,124,29,153,28,154,26,155,156,157,22,158,97],"Educational","classify","goal","nudge","knowledge","cron",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":166,"publishedAt":33},"01M6F9ZAFACH7XZ8KMFK9TKARX","skill-refinement","Skill 사용 후 개선 제안. ledger 분석으로 어느 skill 이 자주 실패 \u002F open_question 다발 \u002F 비효율인지 식별. Chief 가 retrospective 후 호출.","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fskill-refinement\u002FSKILL.md",[165],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[98,167,29,168,28,26,169,22,170,102,171],"skill refinement","ledger","question","open","retrospective"]