[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F9ZE85QYBBX4XMM0W71YN3":3,"skill-same:01M6F9ZE85QYBBX4XMM0W71YN3":69},{"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":23,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":49,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":68},"01M6F9ZE85QYBBX4XMM0W71YN3","triage",null,"Chief 의 과제 분류 도구. 사용자 입력을 4-way 분류 (discussion \u002F workflow \u002F cron \u002F goal) + Educational Nudge (불명확 시 KNOWLEDGE 가이드 선제시).","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\u002Ftriage\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35],"workflow","core","cron","leader","knowledge","nudge","goal","chief","classify","false","Educational","true","2026-11-10 10:12:30",false,"---\nname: triage\ndescription: Chief 의 과제 분류 도구. 사용자 입력을 4-way 분류 (discussion \u002F workflow \u002F cron \u002F goal) + Educational Nudge (불명확 시 KNOWLEDGE 가이드 선제시).\nschema_version: 2\ntier: leader\nteam: _skill\ncategory: core\nused_by: [\"chief\"]\ndev_capability: false\ntriggers:\n  keyword: [\"triage\", \"분류\", \"classify\"]\npm_conventions:\n  anti_sycophancy: true\n  hard_gate: false\n  post_labeling: true\n  minimum_approaches: 1\n---\n\n# Triage Skill\n\n> Chief 가 매 turn TRIAGE stage 에서 호출. Chief 의 의사결정 권한 (Task 분류) 의 reasoning 도구.\n\n## 4-Way 분류\n\n| 분류 | 정의 | 예시 |\n|---|---|---|\n| **discussion** | 대화 자체로 종결. clarification \u002F status check \u002F light reply | \"어떻게 지내?\", \"지금 진행 중인 게 뭐야?\" |\n| **workflow** | 일회성 chain (PRD → 분해 → 실행 → 보고) | \"X 기능 만들자\", \"캠페인 준비해줘\" |\n| **cron** | 반복 (cron 등록) | \"매일 아침 brief 보여줘\", \"주간 회고 자동화\" |\n| **goal** | 자율 실행 (metric 기반 keep\u002Fdiscard) | \"Y 지표를 Z 까지 올리는 방법 찾아줘\" |\n\n## Triage Stage 0 — Educational Nudge\n\n사용자 입력이 막연하면 PM\u002Fspecialist spawn **전에** KNOWLEDGE 가이드 선제시:\n\n```\n조건: 4-way 신뢰도 \u003C 60%\n→ team KNOWLEDGE.md 의 가장 정합 높은 playbook 1~2개 표시\n→ \"어느 단계에서 시작할까요?\" 또는 \"처음부터 가설 정의가 필요하신가요?\"\n→ 사용자 응답 기다림\n```\n\n**원칙: 사후 라벨링** — 프레임워크 선처방 X. 사용자 의도가 모이면 사후 label.\n\n## 출력\n\n```yaml\nclassification: discussion | workflow | cron | goal\nconfidence: 0-100\neducational_nudge:\n  needed: true | false\n  candidate_playbooks: [\"...\"]\nreasoning: \"string\"\nnext_stage: DECOMPOSE | reply_directly | await_user\n```\n\n## Confidence 임계값\n\n- ≥80: 즉시 다음 stage (DECOMPOSE)\n- 60~79: Educational Nudge 권고\n- \u003C60: 명시적 clarification 1회 (사용자에게 1-2 짧은 질문)\n\n## ≥ 2 approaches (Educational Nudge 시)\n\nKNOWLEDGE 가이드 제시는 ≥ 2 playbook 후보. 단일 강요 X.\n\n## Anti-Sycophancy\n\n- ❌ \"흥미로운 요청이네요. 어떻게 시작할까요?\"\n- ✅ \"이 요청은 workflow(60%) 와 goal(40%) 사이입니다. KNOWLEDGE 에 두 playbook 있어요: X \u002F Y. 어느 쪽?\"\n\n## Reference\n\n- v1.1 PRD §5.2 (TRIAGE stage), §5.4 (Educational Nudge)\n- Harness Report §7.5 권고 (Educational Nudge)\n","# Triage Skill\n\n> Chief 가 매 turn TRIAGE stage 에서 호출. Chief 의 의사결정 권한 (Task 분류) 의 reasoning 도구.\n\n## 4-Way 분류\n\n| 분류 | 정의 | 예시 |\n|---|---|---|\n| **discussion** | 대화 자체로 종결. clarification \u002F status check \u002F light reply | \"어떻게 지내?\", \"지금 진행 중인 게 뭐야?\" |\n| **workflow** | 일회성 chain (PRD → 분해 → 실행 → 보고) | \"X 기능 만들자\", \"캠페인 준비해줘\" |\n| **cron** | 반복 (cron 등록) | \"매일 아침 brief 보여줘\", \"주간 회고 자동화\" |\n| **goal** | 자율 실행 (metric 기반 keep\u002Fdiscard) | \"Y 지표를 Z 까지 올리는 방법 찾아줘\" |\n\n## Triage Stage 0 — Educational Nudge\n\n사용자 입력이 막연하면 PM\u002Fspecialist spawn **전에** KNOWLEDGE 가이드 선제시:\n\n```\n조건: 4-way 신뢰도 \u003C 60%\n→ team KNOWLEDGE.md 의 가장 정합 높은 playbook 1~2개 표시\n→ \"어느 단계에서 시작할까요?\" 또는 \"처음부터 가설 정의가 필요하신가요?\"\n→ 사용자 응답 기다림\n```\n\n**원칙: 사후 라벨링** — 프레임워크 선처방 X. 사용자 의도가 모이면 사후 label.\n\n## 출력\n\n```yaml\nclassification: discussion | workflow | cron | goal\nconfidence: 0-100\neducational_nudge:\n  needed: true | false\n  candidate_playbooks: [\"...\"]\nreasoning: \"string\"\nnext_stage: DECOMPOSE | reply_directly | await_user\n```\n\n## Confidence 임계값\n\n- ≥80: 즉시 다음 stage (DECOMPOSE)\n- 60~79: Educational Nudge 권고\n- \u003C60: 명시적 clarification 1회 (사용자에게 1-2 짧은 질문)\n\n## ≥ 2 approaches (Educational Nudge 시)\n\nKNOWLEDGE 가이드 제시는 ≥ 2 playbook 후보. 단일 강요 X.\n\n## Anti-Sycophancy\n\n- ❌ \"흥미로운 요청이네요. 어떻게 시작할까요?\"\n- ✅ \"이 요청은 workflow(60%) 와 goal(40%) 사이입니다. KNOWLEDGE 에 두 playbook 있어요: X \u002F Y. 어느 쪽?\"\n\n## Reference\n\n- v1.1 PRD §5.2 (TRIAGE stage), §5.4 (Educational Nudge)\n- Harness Report §7.5 권고 (Educational Nudge)\n",{"name":5,"team":41,"tier":27,"used_by":42,"category":25,"triggers":43,"description":7,"dev_capability":37,"pm_conventions":46,"schema_version":49},"_skill",[31],{"keyword":44},[5,45,32],"분류",{"hard_gate":37,"post_labeling":47,"anti_sycophancy":47,"minimum_approaches":48},true,1,2,"main","37b891996f0e5d7317b2abdd6e2a8acccdc94dff","skills\u002Ftriage","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad","https:\u002F\u002Fgithub.com\u002FAdelie-Squad","2026-11-12 01:51:16",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":47},[58,61,64],{"tool":59,"command":60},"npx","npx skills add Adelie-Squad\u002Fsolosquad --skill triage",{"tool":62,"command":63},"bunx","bunx skills add Adelie-Squad\u002Fsolosquad --skill triage",{"tool":65,"command":66},"pnpm","pnpm dlx skills add Adelie-Squad\u002Fsolosquad --skill triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[],[70,86,101,120,141,154],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":36},"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",[],[77,78,79,80,81,82,35,83,84,33,31,85,27],"xyz hypothesis","hypothesis","product","definition","v1","manager","segment","problem","behavior",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":93,"publishedAt":36},"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",[92],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,94,95,35,33,96,97,98,31,27,99,100],"workflow refinement","refinement","stage","time","cycle","agile","handoff",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":36},"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",[107],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,82,109,31,110,96,33,111,112,35,113,114,115,27,116,79,25,117,118,119],"workflow manager","show","org","make","solosquad","exit","list","yaml","validate","dag","new",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":36},"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",[],[122,127,35,128,82,33,129,130,131,132,133,134,135,136,137,27,138,139,79,140],"breakdown","schedule","critical","decomposition","pm","structure","dependency graph","dependency","okr","work","path","team","graph","planning",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":148,"publishedAt":36},"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",[147],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[95,149,150,99,151,27,35,152,33,31,153],"skill refinement","open","retrospective","ledger","question",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":161,"publishedAt":36},"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",[160],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[82,162,163,119,164,81,35,33,165,31,113,110,115,166,167,27,79,25,168,169,117,170],"skill manager","new skill","authority","authoring","eval","src","skill authoring","scaffold","bot"]