[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CHHQ4W7YQJ4K7F4VCGEEAS":3,"skill-same:01M6CHHQ4W7YQJ4K7F4VCGEEAS":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":26,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":56,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":75},"01M6CHHQ4W7YQJ4K7F4VCGEEAS","market-research",null,"멀티에이전트 병렬 시장 조사 프레임워크. 타깃 시장·경쟁사를 desk research 로 조사하고 인용\u002Fgroundedness 를 검증해 리포트(\u003Corg>\u002Freports\u002F)를 산출. v1.3.5 신규 — 현재 리포트 산출 skill 0 갭을 메움.","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\u002Fmarket-research\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"research","market research","Market","product","discovery","leader","reports","chief","false","org","true","manager","v1","competitor","skill 0","2026-11-10 10:12:30",false,"---\nname: market-research\ndescription: 멀티에이전트 병렬 시장 조사 프레임워크. 타깃 시장·경쟁사를 desk research 로 조사하고 인용\u002Fgroundedness 를 검증해 리포트(\u003Corg>\u002Freports\u002F)를 산출. v1.3.5 신규 — 현재 리포트 산출 skill 0 갭을 메움.\nschema_version: 2\ntier: leader\nteam: _skill\ncategory: discovery\nused_by: [\"product-manager\", \"chief\"]\ndev_capability: false\ntriggers:\n  keyword: [\"시장 조사\", \"market research\", \"경쟁사 분석\", \"competitor\"]\npm_conventions:\n  anti_sycophancy: true\n  hard_gate: false\n  post_labeling: true\n  minimum_approaches: 2\n---\n\n# Market Research — Multi-agent Desk Research + Report\n\n> **목적**: 타깃 시장·경쟁사를 병렬 desk research 로 조사하고, **모든 주장에 인용(evidence_ref)**\n> 을 달아 groundedness 를 검증한 뒤 리포트를 산출. 1인 초기엔 인터뷰 대신 desk research·시장 신호로\n> 보완하고 \"추후 인터뷰 계획\"을 명시(§3.6).\n> **합성 위치(v1.3.5):** market-research 서브워크플로(design\u002Fresearcher + product\u002Fbusiness-strategy).\n\n## 절차\n\n1. **질문 분해** — 타깃 시장(TAM\u002FSAM 신호)·경쟁사·대체재·가격·진입장벽으로 조사 질문을 나눈다.\n2. **병렬 조사** — 각 질문을 독립적으로 조사(멀티에이전트 가능). 출처 URL\u002F문서를 기록.\n3. **인용 검증(groundedness)** — 각 주장에 `evidence_ref`(출처) 부착. 출처 없는 주장은 **추측으로\n   표시**하거나 제거. 상충 출처는 병기.\n4. **리포트 산출** — `\u003Corg>\u002Freports\u002Fmarket-research-\u003Cslug>-\u003Cdate>.md` 작성(아래 구조).\n5. **요약 반환** — PRD §시장 에 들어갈 요약 + 리포트 경로(evidence_ref) 반환.\n\n## 리포트 구조\n\n```markdown\n# Market Research — \u003Ctopic> (\u003Cdate>)\n## 요약 (3–5줄)\n## 시장 규모 \u002F 신호        — 각 항목 [evidence_ref]\n## 경쟁사 \u002F 대체재         — 표: 이름·포지셔닝·강점·약점 [evidence_ref]\n## 기회 \u002F 차별화 가설\n## 미해결 질문 (open_questions[]) — 추후 인터뷰\u002F검증 계획\n## 출처\n```\n\n## Anti-Sycophancy\n\n낙관 편향 금지 — 시장 규모·수요는 출처로만 진술하고, 출처가 약하면 신뢰도를 낮춰 표기한다.\n최소 2개 시나리오(낙관\u002F보수)를 비교한다.\n","# Market Research — Multi-agent Desk Research + Report\n\n> **목적**: 타깃 시장·경쟁사를 병렬 desk research 로 조사하고, **모든 주장에 인용(evidence_ref)**\n> 을 달아 groundedness 를 검증한 뒤 리포트를 산출. 1인 초기엔 인터뷰 대신 desk research·시장 신호로\n> 보완하고 \"추후 인터뷰 계획\"을 명시(§3.6).\n> **합성 위치(v1.3.5):** market-research 서브워크플로(design\u002Fresearcher + product\u002Fbusiness-strategy).\n\n## 절차\n\n1. **질문 분해** — 타깃 시장(TAM\u002FSAM 신호)·경쟁사·대체재·가격·진입장벽으로 조사 질문을 나눈다.\n2. **병렬 조사** — 각 질문을 독립적으로 조사(멀티에이전트 가능). 출처 URL\u002F문서를 기록.\n3. **인용 검증(groundedness)** — 각 주장에 `evidence_ref`(출처) 부착. 출처 없는 주장은 **추측으로\n   표시**하거나 제거. 상충 출처는 병기.\n4. **리포트 산출** — `\u003Corg>\u002Freports\u002Fmarket-research-\u003Cslug>-\u003Cdate>.md` 작성(아래 구조).\n5. **요약 반환** — PRD §시장 에 들어갈 요약 + 리포트 경로(evidence_ref) 반환.\n\n## 리포트 구조\n\n```markdown\n# Market Research — \u003Ctopic> (\u003Cdate>)\n## 요약 (3–5줄)\n## 시장 규모 \u002F 신호        — 각 항목 [evidence_ref]\n## 경쟁사 \u002F 대체재         — 표: 이름·포지셔닝·강점·약점 [evidence_ref]\n## 기회 \u002F 차별화 가설\n## 미해결 질문 (open_questions[]) — 추후 인터뷰\u002F검증 계획\n## 출처\n```\n\n## Anti-Sycophancy\n\n낙관 편향 금지 — 시장 규모·수요는 출처로만 진술하고, 출처가 약하면 신뢰도를 낮춰 표기한다.\n최소 2개 시나리오(낙관\u002F보수)를 비교한다.\n",{"name":5,"team":47,"tier":32,"used_by":48,"category":31,"triggers":50,"description":7,"dev_capability":43,"pm_conventions":54,"schema_version":56},"_skill",[49,34],"product-manager",{"keyword":51},[52,28,53,40],"시장 조사","경쟁사 분석",{"hard_gate":43,"post_labeling":55,"anti_sycophancy":55,"minimum_approaches":56},true,2,"main","37b891996f0e5d7317b2abdd6e2a8acccdc94dff","skills\u002Fmarket-research","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad","https:\u002F\u002Fgithub.com\u002FAdelie-Squad","2026-11-12 01:51:16",{"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 market-research",{"tool":69,"command":70},"bunx","bunx skills add Adelie-Squad\u002Fsolosquad --skill market-research",{"tool":72,"command":73},"pnpm","pnpm dlx skills add Adelie-Squad\u002Fsolosquad --skill market-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fmarket-research\u002FSKILL.md",[],[77,90,106,125,146,160],{"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":42},"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",[],[84,85,32,86,39,38,37,87,88,35,34,89,30],"hypothesis","xyz hypothesis","definition","segment","problem","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":97,"publishedAt":42},"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":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[98,99,100,101,102,103,37,35,104,105,34,32],"workflow","refinement","workflow refinement","handoff","cycle","agile","stage","time",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":42},"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",[112],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[114,38,98,37,115,116,36,34,35,104,117,118,119,120,32,121,30,122,123,124],"workflow manager","new","make","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":42},"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,132,133,134,135,38,37,35,136,137,138,139,140,141,142,143,32,144,145,30],"planning","structure","breakdown","path","critical","decomposition","pm","dependency graph","dependency","okr","work","schedule","team","graph",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":42},"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",[152],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[148,124,37,154,35,155,34,156,157,158,32,159,98],"Educational","classify","goal","nudge","knowledge","cron",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":42},"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",[166],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[99,168,37,169,35,34,170,32,171,103,172],"skill refinement","ledger","question","open","retrospective"]