[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F9ZX66ETTM8NX73Z79MA21":3,"skill-same:01M6F9ZX66ETTM8NX73Z79MA21":67},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":47,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":66},"01M6F9ZX66ETTM8NX73Z79MA21","xyz-hypothesis",null,"검증 가능한 가설 프레임워크 — \"[X%] of [Y segment] will [Z behavior] within [T period], because [R]\". 입장+반증 조건 강제, 최소 2개 접근, V\u002FU\u002FV\u002FF 가정 분류. v1.3.5 에서 problem-definition P5 를 독립 skill 로 분리.","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\u002Fxyz-hypothesis\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"hypothesis","xyz hypothesis","product","leader","behavior","chief","false","problem","segment","true","manager","v1","definition","2026-11-10 10:12:30",false,"---\nname: xyz-hypothesis\ndescription: 검증 가능한 가설 프레임워크 — \"[X%] of [Y segment] will [Z behavior] within [T period], because [R]\". 입장+반증 조건 강제, 최소 2개 접근, V\u002FU\u002FV\u002FF 가정 분류. v1.3.5 에서 problem-definition P5 를 독립 skill 로 분리.\nschema_version: 2\ntier: leader\nteam: _skill\ncategory: problem-definition\nused_by: [\"product-manager\", \"chief\"]\ndev_capability: false\ntriggers:\n  keyword: [\"xyz hypothesis\", \"가설 수립\", \"검증 가능한 가설\", \"hypothesis\"]\npm_conventions:\n  anti_sycophancy: true\n  hard_gate: false\n  post_labeling: true\n  minimum_approaches: 2\n---\n\n# XYZ Hypothesis\n\n> 검증 가능한 가설 형식: **`[X%] of [Y segment] will [Z behavior] within [T period], because [R rationale]`**.\n> **합성 위치(v1.3.5):** 가설 수립 서브워크플로의 종착 렌즈(신규 구축·개선 두 메인이 공유).\n\n## 형식\n\n```yaml\nhypothesis:\n  x_percent: \"예: 80%\"\n  y_segment: \"예: 신규 org 를 추가하는 founder\"\n  z_behavior: \"예: 첫 messenger send 를 1회 시도 내 성공\"\n  t_period: \"예: org 추가 후 5분 이내\"\n  r_rationale: \"lazy-create 패턴 + post-add seed 가 wizard 와 동등한 보장 제공\"\nverification:\n  method: \"instrumentation 으로 retry 횟수 카운트\"\n  success_threshold: \"first-try 성공률 ≥ 80%\"\n  measurement_window: \"구현 후 30일\"\nconfidence: 75   # 0-100, RO-PNA Confidence Score\n```\n\n## Anti-Sycophancy 강제 (입장 + 반증)\n\n```yaml\nposition: \"lazy-create 도입 시 80% 첫시도 성공\"\nfalsification:\n  - \"first-try \u003C 50% → 다른 root cause (예: discord API 권한)\"\n  - \"100% 인데 사용자 보고 지속 → metric 정의가 wrong proxy\"\n```\n\n## ≥ 2 approaches 룰 (단일 가설 금지)\n\n항상 최소 2개 가설(approach·pros·cons) 제시 후 `recommended` 명시(근거 포함).\n\n## V\u002FU\u002FV\u002FF Assumption 분류\n\n각 가설 핵심 가정을 **V**alue \u002F **U**sability \u002F **V**iability \u002F **F**easibility 4영역으로 분류,\n가장 위험한 가정을 표시.\n","# XYZ Hypothesis\n\n> 검증 가능한 가설 형식: **`[X%] of [Y segment] will [Z behavior] within [T period], because [R rationale]`**.\n> **합성 위치(v1.3.5):** 가설 수립 서브워크플로의 종착 렌즈(신규 구축·개선 두 메인이 공유).\n\n## 형식\n\n```yaml\nhypothesis:\n  x_percent: \"예: 80%\"\n  y_segment: \"예: 신규 org 를 추가하는 founder\"\n  z_behavior: \"예: 첫 messenger send 를 1회 시도 내 성공\"\n  t_period: \"예: org 추가 후 5분 이내\"\n  r_rationale: \"lazy-create 패턴 + post-add seed 가 wizard 와 동등한 보장 제공\"\nverification:\n  method: \"instrumentation 으로 retry 횟수 카운트\"\n  success_threshold: \"first-try 성공률 ≥ 80%\"\n  measurement_window: \"구현 후 30일\"\nconfidence: 75   # 0-100, RO-PNA Confidence Score\n```\n\n## Anti-Sycophancy 강제 (입장 + 반증)\n\n```yaml\nposition: \"lazy-create 도입 시 80% 첫시도 성공\"\nfalsification:\n  - \"first-try \u003C 50% → 다른 root cause (예: discord API 권한)\"\n  - \"100% 인데 사용자 보고 지속 → metric 정의가 wrong proxy\"\n```\n\n## ≥ 2 approaches 룰 (단일 가설 금지)\n\n항상 최소 2개 가설(approach·pros·cons) 제시 후 `recommended` 명시(근거 포함).\n\n## V\u002FU\u002FV\u002FF Assumption 분류\n\n각 가설 핵심 가정을 **V**alue \u002F **U**sability \u002F **V**iability \u002F **F**easibility 4영역으로 분류,\n가장 위험한 가정을 표시.\n",{"name":5,"team":37,"tier":22,"used_by":38,"category":40,"triggers":41,"description":7,"dev_capability":33,"pm_conventions":45,"schema_version":47},"_skill",[39,24],"product-manager","problem-definition",{"keyword":42},[20,43,44,19],"가설 수립","검증 가능한 가설",{"hard_gate":33,"post_labeling":46,"anti_sycophancy":46,"minimum_approaches":47},true,2,"main","37b891996f0e5d7317b2abdd6e2a8acccdc94dff","skills\u002Fxyz-hypothesis","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad","https:\u002F\u002Fgithub.com\u002FAdelie-Squad","2026-11-12 01:51:16",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":46},[56,59,62],{"tool":57,"command":58},"npx","npx skills add Adelie-Squad\u002Fsolosquad --skill xyz-hypothesis",{"tool":60,"command":61},"bunx","bunx skills add Adelie-Squad\u002Fsolosquad --skill xyz-hypothesis",{"tool":63,"command":64},"pnpm","pnpm dlx skills add Adelie-Squad\u002Fsolosquad --skill xyz-hypothesis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fxyz-hypothesis\u002FSKILL.md",[],[68,88,108,129,143,156],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":32},"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",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[80,81,82,28,25,83,84,85,24,22,86,87],"workflow","refinement","workflow refinement","stage","time","cycle","agile","handoff",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":95,"publishedAt":32},"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",[94],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[29,80,96,97,21,98,99,100,101,28,102,22,103,104,25,83,24,105,106,107],"workflow manager","yaml","core","validate","dag","exit","new","make","org","solosquad","show","list",{"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":114,"publishedAt":32},"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",[],[110,115,116,117,118,119,29,120,121,28,122,123,25,124,125,22,126,21,127,128],"path","work","okr","breakdown","critical","dependency","dependency graph","structure","pm","decomposition","team","graph","planning","schedule",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":32},"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",[135],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[131,137,28,138,25,139,24,140,141,22,142,98,80],"nudge","Educational","classify","goal","knowledge","cron",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":32},"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",[149],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[81,151,152,86,153,22,28,154,25,24,155],"skill refinement","open","retrospective","ledger","question",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":32},"01M6F9Z654Q8647PBSK2WJB7NS","skill-manager","skill(SKILL.md)의 대화형 매니저이자 **작성 표준의 권위(authoring authority)**. 새 skill 생성·검토·개선을 Chief 세션 안에서 안내하고, 좋은 SKILL.md 작성 노하우(description 공식·정량 한도·번들 구조·eval 검증·frontmatter 필드 감사)를 보유한다. 결정적 동작(scaffold\u002Flist\u002Fshow\u002Fvalidate)은 `solosquad skill *` 헬퍼로 위임하고, 의도→초안·품질 검토·개선은 대화로 진행한다. 사용 시점 — skill 을 새로 만들 때, 기존 skill 을 고칠 때, 또는 다른 skill 의 작성 품질을 판단할 때. v1.3.6 — 코드 백엔드 `src\u002Fbot\u002Fskill-manager.ts` 위에 작성 권위를 얹음.","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fskill-manager\u002FSKILL.md",[162],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[29,164,165,102,166,30,28,25,167,24,105,106,107,168,169,22,21,98,170,171,99,172],"skill manager","new skill","authority","authoring","eval","src","skill authoring","scaffold","bot"]