[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CHJ59352K23S9HBJ2GWFG2":3,"skill-same:01M6CHJ59352K23S9HBJ2GWFG2":71},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":51,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":70},"01M6CHJ59352K23S9HBJ2GWFG2","premortem",null,"출시 전 pre-mortem 분석. \"이미 실패했다고 가정하고 원인 역추적.\" launch checklist + release notes draft 자동 생성.","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\u002Fpremortem\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"chief","post-mortem","pre-mortem","manager","true","post","false","draft","launch checklist","launch","checklist","leader","release notes draft","product","release","planning","release notes","notes","2026-11-10 10:12:30",false,"---\nname: premortem\ndescription: 출시 전 pre-mortem 분석. \"이미 실패했다고 가정하고 원인 역추적.\" launch checklist + release notes draft 자동 생성.\nschema_version: 2\ntier: leader\nteam: _skill\ncategory: planning\nused_by: [\"product-manager\", \"chief\"]\ndev_capability: false\ntriggers:\n  keyword: [\"premortem\", \"pre-mortem\", \"런치 전 점검\", \"launch checklist\", \"post-mortem\"]\npm_conventions:\n  anti_sycophancy: true\n  hard_gate: true\n  post_labeling: true\n  minimum_approaches: 1\n---\n\n# Pre-Mortem Skill\n\n> Tier-2 (v1.1.x slot). Gary Klein 의 pre-mortem 기법. 출시 전 마지막 sanity check.\n\n## 진행 흐름\n\n### 1. Time Travel\n\"6개월 후. 이 프로젝트는 *실패* 했다. 사용자는 떠났고, OKR 미달.\"\n\n### 2. 실패 원인 brainstorm (≥10)\n가능한 모든 실패 시나리오를 나열. positive thinking 자제, 비관적으로.\n\n```yaml\nfailure_modes:\n  - id: f1\n    scenario: \"사용자가 첫 사용 후 다시 안 옴\"\n    likelihood: high | medium | low\n    impact: critical | major | minor\n    detection_lag: \"...\"  # 얼마나 늦게 알게 되나\n    early_signal: \"...\"   # 어떤 지표가 미리 알려주나\n    mitigation:\n      - \"...\"\n```\n\n### 3. 우선순위 매트릭스\n- (likelihood × impact) 곱으로 정렬\n- top 5 risk → 사전 mitigation 필수\n\n### 4. Launch Checklist 도출\n\n```markdown\n## Launch Checklist — {{project}}\n\n### Pre-launch (T-3d)\n- [ ] quality-assurance regression test 통과\n- [ ] infra 보안 audit (auth\u002Fdata 변경 시)\n- [ ] product-designer 검토 (정책 영향 시)\n- [ ] data-analyst instrumentation 검증\n- [ ] (premortem risks → 대응 완료 확인) × 5\n\n### Launch (T-0)\n- [ ] rollback plan 명시\n- [ ] monitoring dashboard 준비\n- [ ] support 응답 ready\n- [ ] release notes 작성 완료\n\n### Post-launch (T+24h)\n- [ ] leading indicator 5 지표 확인\n- [ ] guardrail metric 회귀 없는지\n- [ ] 사용자 피드백 1-pass\n- [ ] (premortem early signal 모니터링)\n```\n\n### 5. Release Notes Draft\n\n```markdown\n# {{Project}} — Release Notes\n\n## TL;DR\n{{1 line summary}}\n\n## What's New\n- ...\n\n## Why\n- {{problem this solves}}\n\n## How to Use\n- ...\n\n## Known Limitations\n- {{premortem 의 mitigated risks 일부 명시}}\n\n## Feedback\n- ...\n```\n\n## HARD GATE\n\n```markdown\n- [ ] failure modes ≥ 10 brainstorm\n- [ ] top 5 risk 모두 mitigation 완료\n- [ ] launch checklist 모든 항목 ✅\n- [ ] release notes 작성 완료\n- [ ] rollback plan 명시 + 실험\n```\n\n## Anti-Sycophancy\n\n비관적 사고 강제:\n- ❌ \"출시 준비가 잘 되었습니다\"\n- ✅ \"5 risk 중 3건 mitigated. risk #2 (적용 시 latency +200ms) 는 monitoring 만 완료. monitoring 발동 임계값 명시 필요.\"\n\n## Reference\n\n- Gary Klein \"Performing a Project Premortem\" (HBR)\n- phuryn\u002Fpm-skills\u002Fpm-execution\u002F{pre-mortem, release-notes}\n","# Pre-Mortem Skill\n\n> Tier-2 (v1.1.x slot). Gary Klein 의 pre-mortem 기법. 출시 전 마지막 sanity check.\n\n## 진행 흐름\n\n### 1. Time Travel\n\"6개월 후. 이 프로젝트는 *실패* 했다. 사용자는 떠났고, OKR 미달.\"\n\n### 2. 실패 원인 brainstorm (≥10)\n가능한 모든 실패 시나리오를 나열. positive thinking 자제, 비관적으로.\n\n```yaml\nfailure_modes:\n  - id: f1\n    scenario: \"사용자가 첫 사용 후 다시 안 옴\"\n    likelihood: high | medium | low\n    impact: critical | major | minor\n    detection_lag: \"...\"  # 얼마나 늦게 알게 되나\n    early_signal: \"...\"   # 어떤 지표가 미리 알려주나\n    mitigation:\n      - \"...\"\n```\n\n### 3. 우선순위 매트릭스\n- (likelihood × impact) 곱으로 정렬\n- top 5 risk → 사전 mitigation 필수\n\n### 4. Launch Checklist 도출\n\n```markdown\n## Launch Checklist — {{project}}\n\n### Pre-launch (T-3d)\n- [ ] quality-assurance regression test 통과\n- [ ] infra 보안 audit (auth\u002Fdata 변경 시)\n- [ ] product-designer 검토 (정책 영향 시)\n- [ ] data-analyst instrumentation 검증\n- [ ] (premortem risks → 대응 완료 확인) × 5\n\n### Launch (T-0)\n- [ ] rollback plan 명시\n- [ ] monitoring dashboard 준비\n- [ ] support 응답 ready\n- [ ] release notes 작성 완료\n\n### Post-launch (T+24h)\n- [ ] leading indicator 5 지표 확인\n- [ ] guardrail metric 회귀 없는지\n- [ ] 사용자 피드백 1-pass\n- [ ] (premortem early signal 모니터링)\n```\n\n### 5. Release Notes Draft\n\n```markdown\n# {{Project}} — Release Notes\n\n## TL;DR\n{{1 line summary}}\n\n## What's New\n- ...\n\n## Why\n- {{problem this solves}}\n\n## How to Use\n- ...\n\n## Known Limitations\n- {{premortem 의 mitigated risks 일부 명시}}\n\n## Feedback\n- ...\n```\n\n## HARD GATE\n\n```markdown\n- [ ] failure modes ≥ 10 brainstorm\n- [ ] top 5 risk 모두 mitigation 완료\n- [ ] launch checklist 모든 항목 ✅\n- [ ] release notes 작성 완료\n- [ ] rollback plan 명시 + 실험\n```\n\n## Anti-Sycophancy\n\n비관적 사고 강제:\n- ❌ \"출시 준비가 잘 되었습니다\"\n- ✅ \"5 risk 중 3건 mitigated. risk #2 (적용 시 latency +200ms) 는 monitoring 만 완료. monitoring 발동 임계값 명시 필요.\"\n\n## Reference\n\n- Gary Klein \"Performing a Project Premortem\" (HBR)\n- phuryn\u002Fpm-skills\u002Fpm-execution\u002F{pre-mortem, release-notes}\n",{"name":5,"team":42,"tier":30,"used_by":43,"category":34,"triggers":45,"description":7,"dev_capability":38,"pm_conventions":48,"schema_version":51},"_skill",[44,19],"product-manager",{"keyword":46},[5,21,47,27,20],"런치 전 점검",{"hard_gate":49,"post_labeling":49,"anti_sycophancy":49,"minimum_approaches":50},true,1,2,"main","d2bf4d7228eb31fd3ca7a4272e53054a97fabc42","skills\u002Fpremortem","https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad","https:\u002F\u002Fgithub.com\u002FAdelie-Squad","2026-11-13 01:15:27",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":49},[60,63,66],{"tool":61,"command":62},"npx","npx skills add Adelie-Squad\u002Fsolosquad --skill premortem",{"tool":64,"command":65},"bunx","bunx skills add Adelie-Squad\u002Fsolosquad --skill premortem",{"tool":67,"command":68},"pnpm","pnpm dlx skills add Adelie-Squad\u002Fsolosquad --skill premortem","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdelie-Squad\u002Fsolosquad\u002Fblob\u002Fmain\u002Fskills\u002Fpremortem\u002FSKILL.md",[],[72,86,106,126,146,160],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":37},"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",[],[79,80,30,81,82,22,23,83,84,25,19,85,32],"hypothesis","xyz hypothesis","definition","v1","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":97,"publishedAt":37},"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":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[98,99,100,101,102,103,23,25,104,105,19,30],"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":37},"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":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[114,22,98,23,115,116,117,19,25,104,118,119,120,121,30,122,32,123,124,125],"workflow manager","new","make","org","solosquad","show","exit","list","yaml","dag","validate","core",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":37},"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",[],[128,34,133,134,135,22,23,25,136,137,138,139,140,141,142,143,30,144,145,32],"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":37},"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":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[148,125,23,154,25,155,19,156,157,158,30,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":37},"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":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[99,168,23,169,25,19,170,30,171,103,172],"skill refinement","ledger","question","open","retrospective"]