[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CHHCVJGMSF4D780S83XSPC":3,"skill-same:01M6CHHCVJGMSF4D780S83XSPC":76},{"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":28,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":56,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":75},"01M6CHHCVJGMSF4D780S83XSPC","hypothesis-design",null,"XYZ hypothesis + If-Then-Because + V\u002FU\u002FV\u002FF assumption 분류. PM 자체 reasoning. ≥2 approaches 비교 강제.","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\u002Fhypothesis-design\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40],"design","hypothesis","hypothesis design","planning","reasoning","product","leader","pm","false","xyz hypothesis","true","manager","2026-11-10 10:12:30",false,"---\nname: hypothesis-design\ndescription: XYZ hypothesis + If-Then-Because + V\u002FU\u002FV\u002FF assumption 분류. PM 자체 reasoning. ≥2 approaches 비교 강제.\nschema_version: 2\ntier: leader\nteam: _skill\ncategory: planning\nused_by: [\"product-manager\"]\ndev_capability: false\ntriggers:\n  keyword:\n    - \"가설\"\n    - \"hypothesis\"\n    - \"실험 가설\"\n    - \"if then because\"\npm_conventions:\n  anti_sycophancy: true\n  hard_gate: true\n  post_labeling: true\n  minimum_approaches: 2\n---\n\n# Hypothesis Design Skill\n\n## XYZ Hypothesis\n\n```\n[X%] of [Y segment] will [Z behavior] within [T period], because [R rationale]\n```\n\n상세 schema 는 `skills\u002Fproblem-definition\u002Fassets\u002F05-xyz-hypothesis.md` 참조 (cross-reference).\n\n## If-Then-Because\n\n```\nIf [intervention] is delivered to [segment]\nThen [measurable result] within [period]\nBecause [causal mechanism]\n```\n\nXYZ 보다 가벼운 형식. early-stage exploration 시 사용.\n\n## V\u002FU\u002FV\u002FF Assumption Classifier\n\n각 가설의 핵심 가정을 4 카테고리로 분류 후 위험도 평가:\n\n| 카테고리 | 질문 | 위험 시 검증 방법 |\n|---|---|---|\n| **V**alue | 사용자가 이 변화로 가치를 얻는가? | concierge MVP, fake door |\n| **U**sability | 사용자가 발견\u002F사용 가능한가? | usability test, prototype |\n| **V**iability | 비즈니스 \u002F 운영 가능한가? | financial model, capacity check |\n| **F**easibility | 기술적으로 가능한가? | technical spike, prototype |\n\n가장 risky assumption 부터 experiment 우선순위 결정.\n\n## ≥ 2 approaches 룰\n\n```yaml\nhypotheses:\n  - id: h1\n    xyz: \"...\"\n    pros: [...]\n    cons: [...]\n    v_u_v_f_risk: { v: high, u: low, v2: low, f: low }\n  - id: h2\n    xyz: \"...\"\n    pros: [...]\n    cons: [...]\n    v_u_v_f_risk: { v: low, u: high, v2: low, f: medium }\nrecommended: h1\nrecommendation_rationale: \"h1 의 V 위험이 더 testable. h1 fail 시 h2 로 pivot.\"\n```\n\n## HARD GATE: hypothesis → experiment-design 진입 조건\n\n- [ ] ≥2 hypotheses 비교\n- [ ] 각 hypothesis 의 V\u002FU\u002FV\u002FF risk 평가\n- [ ] recommended + falsification 명시\n- [ ] confidence ≥ 60\n\n## Reference\n\n- RO-PNA XYZ format\n- David Bland \"Testing Business Ideas\" — V\u002FU\u002FV\u002FF (V=Value, U=Usability, V=Viability, F=Feasibility)\n- gstack approaches ≥2 rule\n","# Hypothesis Design Skill\n\n## XYZ Hypothesis\n\n```\n[X%] of [Y segment] will [Z behavior] within [T period], because [R rationale]\n```\n\n상세 schema 는 `skills\u002Fproblem-definition\u002Fassets\u002F05-xyz-hypothesis.md` 참조 (cross-reference).\n\n## If-Then-Because\n\n```\nIf [intervention] is delivered to [segment]\nThen [measurable result] within [period]\nBecause [causal mechanism]\n```\n\nXYZ 보다 가벼운 형식. early-stage exploration 시 사용.\n\n## V\u002FU\u002FV\u002FF Assumption Classifier\n\n각 가설의 핵심 가정을 4 카테고리로 분류 후 위험도 평가:\n\n| 카테고리 | 질문 | 위험 시 검증 방법 |\n|---|---|---|\n| **V**alue | 사용자가 이 변화로 가치를 얻는가? | concierge MVP, fake door |\n| **U**sability | 사용자가 발견\u002F사용 가능한가? | usability test, prototype |\n| **V**iability | 비즈니스 \u002F 운영 가능한가? | financial model, capacity check |\n| **F**easibility | 기술적으로 가능한가? | technical spike, prototype |\n\n가장 risky assumption 부터 experiment 우선순위 결정.\n\n## ≥ 2 approaches 룰\n\n```yaml\nhypotheses:\n  - id: h1\n    xyz: \"...\"\n    pros: [...]\n    cons: [...]\n    v_u_v_f_risk: { v: high, u: low, v2: low, f: low }\n  - id: h2\n    xyz: \"...\"\n    pros: [...]\n    cons: [...]\n    v_u_v_f_risk: { v: low, u: high, v2: low, f: medium }\nrecommended: h1\nrecommendation_rationale: \"h1 의 V 위험이 더 testable. h1 fail 시 h2 로 pivot.\"\n```\n\n## HARD GATE: hypothesis → experiment-design 진입 조건\n\n- [ ] ≥2 hypotheses 비교\n- [ ] 각 hypothesis 의 V\u002FU\u002FV\u002FF risk 평가\n- [ ] recommended + falsification 명시\n- [ ] confidence ≥ 60\n\n## Reference\n\n- RO-PNA XYZ format\n- David Bland \"Testing Business Ideas\" — V\u002FU\u002FV\u002FF (V=Value, U=Usability, V=Viability, F=Feasibility)\n- gstack approaches ≥2 rule\n",{"name":5,"team":46,"tier":35,"used_by":47,"category":32,"triggers":49,"description":7,"dev_capability":42,"pm_conventions":54,"schema_version":56},"_skill",[48],"product-manager",{"keyword":50},[51,30,52,53],"가설","실험 가설","if then because",{"hard_gate":55,"post_labeling":55,"anti_sycophancy":55,"minimum_approaches":56},true,2,"main","37b891996f0e5d7317b2abdd6e2a8acccdc94dff","skills\u002Fhypothesis-design","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad","https:\u002F\u002Fgithub.com\u002FAdelie-Squad","2026-11-13 01:15:27",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":55},[65,68,71],{"tool":66,"command":67},"npx","npx skills add Adelie-Squad\u002Fsolosquad --skill hypothesis-design",{"tool":69,"command":70},"bunx","bunx skills add Adelie-Squad\u002Fsolosquad --skill hypothesis-design",{"tool":72,"command":73},"pnpm","pnpm dlx skills add Adelie-Squad\u002Fsolosquad --skill hypothesis-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fhypothesis-design\u002FSKILL.md",[],[77,90,108,128,147,161],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":41},"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",[],[30,38,35,84,85,40,39,86,87,37,88,89,34],"definition","v1","segment","problem","chief","behavior",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":99,"publishedAt":41},"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",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[100,101,102,103,104,105,39,37,106,107,88,35],"workflow","refinement","workflow refinement","handoff","cycle","agile","stage","time",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":41},"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",[114],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},[116,40,100,39,117,118,119,88,37,106,120,121,122,123,35,124,34,125,126,127],"workflow manager","new","make","org","solosquad","show","exit","list","yaml","dag","validate","core",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":41},"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",[],[130,32,135,136,137,40,39,37,138,139,36,140,141,142,143,144,35,145,146,34],"structure","breakdown","path","critical","decomposition","dependency graph","dependency","okr","work","schedule","team","graph",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":41},"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",[153],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},[149,127,39,155,37,156,88,157,158,159,35,160,100],"Educational","classify","goal","nudge","knowledge","cron",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":41},"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",[167],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},[101,169,39,170,37,88,171,35,172,105,173],"skill refinement","ledger","question","open","retrospective"]