[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F9ZH962BA0SABW0DKR0FAF":3,"skill-same:01M6F9ZH962BA0SABW0DKR0FAF":73},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":53,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":72},"01M6F9ZH962BA0SABW0DKR0FAF","wbs",null,"마일스톤 → WBS (Work Breakdown Structure) 분해. PM 핵심 산출물. team OKR 의 KR 을 분기→주→일 단위 작업으로 변환. dependency graph + critical path 식별.","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\u002Fwbs\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"structure","breakdown","path","manager","true","false","critical","decomposition","pm","planning","dependency graph","dependency","okr","work","schedule","leader","team","graph","product","2026-11-10 10:12:30",false,"---\nname: wbs\ndescription: 마일스톤 → WBS (Work Breakdown Structure) 분해. PM 핵심 산출물. team OKR 의 KR 을 분기→주→일 단위 작업으로 변환. dependency graph + critical path 식별.\nschema_version: 2\ntier: leader\nteam: _skill\ncategory: planning\nused_by: [\"product-manager\"]\ndev_capability: false\ntriggers:\n  keyword:\n    - \"wbs\"\n    - \"마일스톤\"\n    - \"일정\"\n    - \"schedule\"\n    - \"decomposition\"\npm_conventions:\n  anti_sycophancy: true\n  hard_gate: true\n  post_labeling: false\n  minimum_approaches: 1\n---\n\n# WBS Decomposition Skill\n\n> PM 의 마일스톤\u002FWBS 의사결정 영역 (Chief OKR 결정과 분리).\n\n## 입력\n\n- team OKR (특히 KR)\n- `prd` §6 Solution (recommended approach)\n- `hypothesis-design` recommended hypothesis\n\n## 분해 3단계\n\n```\nLevel 1: Milestone (분기 ~ 월)\n  Level 2: Workstream (주)\n    Level 3: Task (일)\n```\n\n## 형식\n\n```yaml\nmilestones:\n  - id: m1\n    title: \"lazy-create 패턴 도입\"\n    target_date: \"2026-06-14\"   # YYYY-MM-DD\n    okr_kr_ref: \"Q2-KR2\"\n    exit_criteria:\n      - \"discord-adapter 가 config 없을 때 자동 생성\"\n      - \"quality-assurance test 통과\"\n    workstreams:\n      - id: m1.w1\n        title: \"discord-adapter lazy-create\"\n        owner_specialist: \"backend-engineer\"\n        target_date: \"2026-06-07\"\n        tasks:\n          - { id: \"m1.w1.t1\", title: \"loadOrEmpty + mkdir 헬퍼\", estimate: \"2h\", depends_on: [] }\n          - { id: \"m1.w1.t2\", title: \"config.yaml schema validation\", estimate: \"1h\", depends_on: [\"m1.w1.t1\"] }\n          - { id: \"m1.w1.t3\", title: \"test 작성\", estimate: \"1h\", depends_on: [\"m1.w1.t1\"] }\n      - id: m1.w2\n        title: \"add-repo CLI seed\"\n        owner_specialist: \"frontend-engineer\"\n        ...\n\ndependency_graph:\n  # 의존성 시각화 (graphviz dot 또는 mermaid)\n  - \"m1.w1 → m1.w2\"\n  - \"m1.w2 → m2\"\n\ncritical_path:\n  - \"m1.w1.t1 → m1.w1.t2 → m1.w1.t3 → m1.w2 → m2\"\n  total_estimate: \"4 weeks\"\n```\n\n## HARD GATE: WBS 완료 조건\n\n- [ ] 모든 milestone 에 target_date + exit_criteria 명시\n- [ ] 모든 task 에 estimate + owner_specialist 명시\n- [ ] dependency_graph cycle 없음\n- [ ] critical_path 식별\n- [ ] team OKR 의 KR 과 milestone 의 1:N 매핑 확인\n\n## 입력 → 출력 흐름\n\n```\nPM 호출 wbs({\n  okr: \u003Cteam OKR>,\n  solution: \u003Cprd §6.recommended>,\n  hypothesis: \u003Chypothesis-design.recommended>\n})\n\n→ {\n  milestones: [...],\n  dependency_graph: [...],\n  critical_path: [...],\n  total_estimate: \"...\",\n  open_questions: [\n    \u002F\u002F capacity 미확인 (e.g. backend-engineer 가용 시간)\n    \u002F\u002F priority tie-break 필요\n  ]\n}\n```\n\n## Anti-Sycophancy\n\n- ❌ \"약 4주 정도 걸릴 것 같습니다\"\n- ✅ \"Critical path 추정 4주. backend-engineer task throughput 가정 5h\u002Fday. 가정 깨지면 6주.\"\n\n## Reference\n\n- IEEE 1490 (PMBOK) WBS 원칙\n- phuryn\u002Fpm-skills\u002Fpm-execution\u002Foutcome-roadmap\n- v1.1 PRD §6.4 (PM 마일스톤\u002FWBS 권한)\n","# WBS Decomposition Skill\n\n> PM 의 마일스톤\u002FWBS 의사결정 영역 (Chief OKR 결정과 분리).\n\n## 입력\n\n- team OKR (특히 KR)\n- `prd` §6 Solution (recommended approach)\n- `hypothesis-design` recommended hypothesis\n\n## 분해 3단계\n\n```\nLevel 1: Milestone (분기 ~ 월)\n  Level 2: Workstream (주)\n    Level 3: Task (일)\n```\n\n## 형식\n\n```yaml\nmilestones:\n  - id: m1\n    title: \"lazy-create 패턴 도입\"\n    target_date: \"2026-06-14\"   # YYYY-MM-DD\n    okr_kr_ref: \"Q2-KR2\"\n    exit_criteria:\n      - \"discord-adapter 가 config 없을 때 자동 생성\"\n      - \"quality-assurance test 통과\"\n    workstreams:\n      - id: m1.w1\n        title: \"discord-adapter lazy-create\"\n        owner_specialist: \"backend-engineer\"\n        target_date: \"2026-06-07\"\n        tasks:\n          - { id: \"m1.w1.t1\", title: \"loadOrEmpty + mkdir 헬퍼\", estimate: \"2h\", depends_on: [] }\n          - { id: \"m1.w1.t2\", title: \"config.yaml schema validation\", estimate: \"1h\", depends_on: [\"m1.w1.t1\"] }\n          - { id: \"m1.w1.t3\", title: \"test 작성\", estimate: \"1h\", depends_on: [\"m1.w1.t1\"] }\n      - id: m1.w2\n        title: \"add-repo CLI seed\"\n        owner_specialist: \"frontend-engineer\"\n        ...\n\ndependency_graph:\n  # 의존성 시각화 (graphviz dot 또는 mermaid)\n  - \"m1.w1 → m1.w2\"\n  - \"m1.w2 → m2\"\n\ncritical_path:\n  - \"m1.w1.t1 → m1.w1.t2 → m1.w1.t3 → m1.w2 → m2\"\n  total_estimate: \"4 weeks\"\n```\n\n## HARD GATE: WBS 완료 조건\n\n- [ ] 모든 milestone 에 target_date + exit_criteria 명시\n- [ ] 모든 task 에 estimate + owner_specialist 명시\n- [ ] dependency_graph cycle 없음\n- [ ] critical_path 식별\n- [ ] team OKR 의 KR 과 milestone 의 1:N 매핑 확인\n\n## 입력 → 출력 흐름\n\n```\nPM 호출 wbs({\n  okr: \u003Cteam OKR>,\n  solution: \u003Cprd §6.recommended>,\n  hypothesis: \u003Chypothesis-design.recommended>\n})\n\n→ {\n  milestones: [...],\n  dependency_graph: [...],\n  critical_path: [...],\n  total_estimate: \"...\",\n  open_questions: [\n    \u002F\u002F capacity 미확인 (e.g. backend-engineer 가용 시간)\n    \u002F\u002F priority tie-break 필요\n  ]\n}\n```\n\n## Anti-Sycophancy\n\n- ❌ \"약 4주 정도 걸릴 것 같습니다\"\n- ✅ \"Critical path 추정 4주. backend-engineer task throughput 가정 5h\u002Fday. 가정 깨지면 6주.\"\n\n## Reference\n\n- IEEE 1490 (PMBOK) WBS 원칙\n- phuryn\u002Fpm-skills\u002Fpm-execution\u002Foutcome-roadmap\n- v1.1 PRD §6.4 (PM 마일스톤\u002FWBS 권한)\n",{"name":5,"team":43,"tier":34,"used_by":44,"category":28,"triggers":46,"description":7,"dev_capability":39,"pm_conventions":50,"schema_version":53},"_skill",[45],"product-manager",{"keyword":47},[5,48,49,33,26],"마일스톤","일정",{"hard_gate":51,"post_labeling":39,"anti_sycophancy":51,"minimum_approaches":52},true,1,2,"main","d2bf4d7228eb31fd3ca7a4272e53054a97fabc42","skills\u002Fwbs","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad","https:\u002F\u002Fgithub.com\u002FAdelie-Squad","2026-11-13 01:15:27",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":51},[62,65,68],{"tool":63,"command":64},"npx","npx skills add Adelie-Squad\u002Fsolosquad --skill wbs",{"tool":66,"command":67},"bunx","bunx skills add Adelie-Squad\u002Fsolosquad --skill wbs",{"tool":69,"command":70},"pnpm","pnpm dlx skills add Adelie-Squad\u002Fsolosquad --skill wbs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fwbs\u002FSKILL.md",[],[74,89,109,129,143,156],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":38},"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",[],[81,82,37,83,84,22,23,85,86,24,87,88,34],"hypothesis","xyz hypothesis","definition","v1","segment","problem","chief","behavior",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":100,"publishedAt":38},"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",[95],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[101,102,103,34,23,24,104,105,106,87,107,108],"workflow","workflow refinement","refinement","stage","time","cycle","agile","handoff",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":38},"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",[115],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[22,117,101,118,119,37,120,23,34,121,87,122,123,124,24,104,125,126,127,128],"workflow manager","org","core","yaml","make","list","exit","show","solosquad","new","dag","validate",{"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":38},"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":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[131,23,137,138,24,139,87,140,141,142,34,119,101],"cron","Educational","classify","goal","nudge","knowledge",{"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":38},"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":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[151,103,152,107,23,153,24,87,154,34,155],"skill refinement","retrospective","ledger","question","open",{"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":38},"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":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[164,22,124,126,165,84,23,24,166,87,125,167,122,168,169,34,37,119,170,171,128,172],"skill manager","authority","authoring","new skill","eval","src","skill authoring","scaffold","bot"]