[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QZAF57EJRZ84NQQGHAS643":3,"skill-same:01M6QZAF57EJRZ84NQQGHAS643":81},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6QZAF57EJRZ84NQQGHAS643","revops-pipeline-schema",null,"RevOps 파이프라인 스키마·위생 가이드 — 세일즈 stage 와 forecast_category enum 을 정의하고(references\u002Fpipeline-enums.json 이 게이트가 읽는 정본), 위생 룰셋(amount>0·open 딜 close_date 미래성·stale 체류일)을 references\u002Fhygiene-rules.md 로 집약한다. gate-pipeline-hygiene.sh 가 이 enum 을 상대경로로 참조하며 하드코딩하지 않는다.\nUse when: 파이프라인 감사 스키마 확인, stage\u002Fforecast_category enum 참조, CRM export 정규화, \u002Fpipeline-audit 작성 시.\nRevOps pipeline schema and hygiene guide defining the sales stage and forecast_category enums (references\u002Fpipeline-enums.json is the source the gate reads) and the hygiene ruleset; gate-pipeline-hygiene reads the enum by relative path rather than hardcoding.\nUse when: normalizing a CRM export, referencing pipeline enums, or auditing pipeline hygiene.","Dokkabei97\u002Fdokkabei-harness","Dokkabei97","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69792585?v=4","01M6QYPVTYK6CGF609W541QNSD","JangMK","01M6QYPVYXBP1GRYHZ7ZABCZC6",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Farchive\u002Fscaleup\u002Fskills\u002Frevops-pipeline-schema\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"revops pipeline schema","pipeline","revops","schema","stale","when","close","hygiene","stage","crm","references","gate","forecast","export","use","sales","Rules","json","open","audit","2026-11-10 10:12:30",false,"---\nname: revops-pipeline-schema\ndescription: |\n  RevOps 파이프라인 스키마·위생 가이드 — 세일즈 stage 와 forecast_category enum 을 정의하고(references\u002Fpipeline-enums.json 이 게이트가 읽는 정본), 위생 룰셋(amount>0·open 딜 close_date 미래성·stale 체류일)을 references\u002Fhygiene-rules.md 로 집약한다. gate-pipeline-hygiene.sh 가 이 enum 을 상대경로로 참조하며 하드코딩하지 않는다.\n  Use when: 파이프라인 감사 스키마 확인, stage\u002Fforecast_category enum 참조, CRM export 정규화, \u002Fpipeline-audit 작성 시.\n  RevOps pipeline schema and hygiene guide defining the sales stage and forecast_category enums (references\u002Fpipeline-enums.json is the source the gate reads) and the hygiene ruleset; gate-pipeline-hygiene reads the enum by relative path rather than hardcoding.\n  Use when: normalizing a CRM export, referencing pipeline enums, or auditing pipeline hygiene.\nmetadata:\n  version: 1.0.0\n  category: scaleup\n---\n\n# RevOps Pipeline Schema — 파이프라인 스키마·위생\n\n파이프라인 감사(`gtm\u002Fpipeline\u002FYYYY-MM-DD-audit.json`)의 스키마와 위생 룰. **enum 정본은 [references\u002Fpipeline-enums.json](references\u002Fpipeline-enums.json)** — gate-pipeline-hygiene.sh 가 상대경로로 읽으므로 게이트·스킬·데이터 파일 3자가 항상 일치해야 한다(값 변경 시 이 문서와 JSON 동기화).\n\n## enum (정본 = references\u002Fpipeline-enums.json)\n\n**stage** (세일즈 단계):\n`prospecting` → `qualification` → `proposal` → `negotiation` → `closed_won` | `closed_lost`\n\n**forecast_category** (포캐스트 카테고리):\n`pipeline` · `best_case` · `commit` · `closed_won` · `closed_lost` · `omitted`\n\n- **open 딜** = forecast_category ∉ {`closed_won`,`closed_lost`}(= pipeline\u002Fbest_case\u002Fcommit\u002Fomitted). 위생 룰의 close_date·stale 검사는 open 딜에만 적용.\n\n## audit.json 스키마\n\n```json\n{\n  \"audited_at\": \"YYYY-MM-DD\",\n  \"stale_max_days\": 30,\n  \"deals\": [\n    {\"id\",\"stage\",\"amount\":\u003Cnum>,\"close_date\":\"YYYY-MM-DD\",\"forecast_category\",\"last_activity\":\"YYYY-MM-DD\"}\n  ]\n}\n```\n\n## 위생 룰셋\n\n상세는 [references\u002Fhygiene-rules.md](references\u002Fhygiene-rules.md). 요약(gate-pipeline-hygiene 계약):\n1. stage·forecast_category ∈ enum\n2. amount > 0 전건\n3. open 딜 close_date ≥ TODAY (마감일 도과 미갱신 = 위생 위반)\n4. open 딜 last_activity 경과 ≤ stale_max_days(기본 30)\n\n## 정규화 (jq)\n\nCRM export(CSV\u002FJSON)를 위 스키마로 jq 정규화한다. 비표준 stage\u002Fforecast 값은 정규화 단계에서 enum 으로 매핑하고, 매핑 불가 값은 그대로 두어 게이트가 잡게 한다(은폐 금지).\n\n## Boundaries\n\n**Will:** stage\u002Fforecast enum·audit 스키마·위생 룰 제공(gate 계약 정본), export 정규화 가이드.\n**Will Not:** SaaS CRM API 연동(export 입력만), 매출 수치 재무 검증(→finance), 딜 자격 판정(→meddpicc-qualification\u002Fdeal-qualifier).\n","# RevOps Pipeline Schema — 파이프라인 스키마·위생\n\n파이프라인 감사(`gtm\u002Fpipeline\u002FYYYY-MM-DD-audit.json`)의 스키마와 위생 룰. **enum 정본은 [references\u002Fpipeline-enums.json](references\u002Fpipeline-enums.json)** — gate-pipeline-hygiene.sh 가 상대경로로 읽으므로 게이트·스킬·데이터 파일 3자가 항상 일치해야 한다(값 변경 시 이 문서와 JSON 동기화).\n\n## enum (정본 = references\u002Fpipeline-enums.json)\n\n**stage** (세일즈 단계):\n`prospecting` → `qualification` → `proposal` → `negotiation` → `closed_won` | `closed_lost`\n\n**forecast_category** (포캐스트 카테고리):\n`pipeline` · `best_case` · `commit` · `closed_won` · `closed_lost` · `omitted`\n\n- **open 딜** = forecast_category ∉ {`closed_won`,`closed_lost`}(= pipeline\u002Fbest_case\u002Fcommit\u002Fomitted). 위생 룰의 close_date·stale 검사는 open 딜에만 적용.\n\n## audit.json 스키마\n\n```json\n{\n  \"audited_at\": \"YYYY-MM-DD\",\n  \"stale_max_days\": 30,\n  \"deals\": [\n    {\"id\",\"stage\",\"amount\":\u003Cnum>,\"close_date\":\"YYYY-MM-DD\",\"forecast_category\",\"last_activity\":\"YYYY-MM-DD\"}\n  ]\n}\n```\n\n## 위생 룰셋\n\n상세는 [references\u002Fhygiene-rules.md](references\u002Fhygiene-rules.md). 요약(gate-pipeline-hygiene 계약):\n1. stage·forecast_category ∈ enum\n2. amount > 0 전건\n3. open 딜 close_date ≥ TODAY (마감일 도과 미갱신 = 위생 위반)\n4. open 딜 last_activity 경과 ≤ stale_max_days(기본 30)\n\n## 정규화 (jq)\n\nCRM export(CSV\u002FJSON)를 위 스키마로 jq 정규화한다. 비표준 stage\u002Fforecast 값은 정규화 단계에서 enum 으로 매핑하고, 매핑 불가 값은 그대로 두어 게이트가 잡게 한다(은폐 금지).\n\n## Boundaries\n\n**Will:** stage\u002Fforecast enum·audit 스키마·위생 룰 제공(gate 계약 정본), export 정규화 가이드.\n**Will Not:** SaaS CRM API 연동(export 입력만), 매출 수치 재무 검증(→finance), 딜 자격 판정(→meddpicc-qualification\u002Fdeal-qualifier).\n",{"name":5,"metadata":44,"description":47},{"version":45,"category":46},"1.0.0","scaleup","RevOps 파이프라인 스키마·위생 가이드 — 세일즈 stage 와 forecast_category enum 을 정의하고(references\u002Fpipeline-enums.json 이 게이트가 읽는 정본), 위생 룰셋(amount>0·open 딜 close_date 미래성·stale 체류일)을 references\u002Fhygiene-rules.md 로 집약한다. gate-pipeline-hygiene.sh 가 이 enum 을 상대경로로 참조하며 하드코딩하지 않는다.\nUse when: 파이프라인 감사 스키마 확인, stage\u002Fforecast_category enum 참조, CRM export 정규화, \u002Fpipeline-audit 작성 시.\nRevOps pipeline schema and hygiene guide defining the sales stage and forecast_category enums (references\u002Fpipeline-enums.json is the source the gate reads) and the hygiene ruleset; gate-pipeline-hygiene reads the enum by relative path rather than hardcoding.\nUse when: normalizing a CRM export, referencing pipeline enums, or auditing pipeline hygiene.\n","main","e9f37e996e3d2b1b6ac9c879e9dfba1223b597c3","archive\u002Fscaleup\u002Fskills\u002Frevops-pipeline-schema",0,"https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness","https:\u002F\u002Fdokkabei97.github.io\u002Fdokkabei-harness\u002F","https:\u002F\u002Fgithub.com\u002FDokkabei97","Contact: wkdrn970@gmail.com","2026-10-29 06:49:16",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add Dokkabei97\u002Fdokkabei-harness --skill revops-pipeline-schema",{"tool":63,"command":64},"bunx","bunx skills add Dokkabei97\u002Fdokkabei-harness --skill revops-pipeline-schema",{"tool":66,"command":67},"pnpm","pnpm dlx skills add Dokkabei97\u002Fdokkabei-harness --skill revops-pipeline-schema","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Farchive\u002Fscaleup\u002Fskills\u002Frevops-pipeline-schema\u002FSKILL.md",true,[71,77],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fhygiene-rules.md","REFERENCE","参考文档",1719,"https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Farchive\u002Fscaleup\u002Fskills\u002Frevops-pipeline-schema\u002Freferences\u002Fhygiene-rules.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fpipeline-enums.json",627,"https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Farchive\u002Fscaleup\u002Fskills\u002Frevops-pipeline-schema\u002Freferences\u002Fpipeline-enums.json",[82,112,143,166,187,208],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":93,"publishedAt":39},"01M6QZQTNF815AWYMAMJ3B25GY","sync-claude-md","커밋·푸시·PR\u002FMR 직전에 이번 변경이 프로젝트 CLAUDE.md 를 낡게 만드는지 검토하고, 필요할 때만 갱신 diff 를 제안한다 — 아키텍처·디렉터리 구조, 새 통합\u002FMCP, 컨벤션, 빌드·CI·도구, 주요 의존성 변화가 대상. 해당 없으면 한 줄로 끝낸다.\nReviews whether pending changes make the project CLAUDE.md stale (architecture, integrations, conventions, build\u002FCI\u002Ftooling, major dependencies) and proposes a minimal update diff only when needed.\nUse when: \"CLAUDE.md 갱신 필요해?\", \"CLAUDE.md 동기화\", 커밋\u002F푸시\u002FMR 전에 구조·도구가 바뀐 변경을 정리할 때, sync CLAUDE.md, check CLAUDE.md before commit or PR.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fsync-claude-md\u002FSKILL.md",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[94,95,96,97,98,99,100,101,102,103,33,104,105,106,107,108,109,110,111,24],"sync","claude md","sync claude md","MCP","commit","architecture","pr","update","ci","integrations","diff","only","minimal","project","make","reviews","pending","mr",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":124,"publishedAt":39},"01M6QZQEK94G00N955VQH9EFQN","spec-driven-dev","새 기능·프로젝트·큰 변경을 코드보다 스펙 먼저로 진행하는 게이트 워크플로(SPECIFY → PLAN → TASKS → IMPLEMENT) — 가정 명시, 측정 가능한 성공 기준, Always\u002FAsk\u002FNever 경계, 단계별 사람 검토로 범위 이탈과 재작업을 줄인다.\nSpec-before-code gated workflow for new features or significant changes: explicit assumptions, measurable success criteria, boundaries, and a human review between stages.\nUse when: \"스펙 먼저\", \"기능 명세\", \"요구사항 정리\", starting a new feature or project, a significant change with vague requirements. 단순 버그 수정·1~2줄 변경엔 불필요.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fspec-driven-dev\u002FSKILL.md",[118,119],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[125,126,127,128,129,130,131,132,133,134,135,136,137,138,107,139,140,141,142,24],"spec","spec driven","dev","spec driven dev","driven","review","workflow","change","tasks","code","plan","ask","never","human","feature","for","vague","features",{"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":149,"publishedAt":39},"01M6QZQA9F6QVGTVDMJ28YQGDV","shipping-guide","프로덕션 배포 전후 가이드 — 배포 전 체크리스트, 피처 플래그 수명주기, 단계적 롤아웃과 진행\u002F보류\u002F롤백 임계값, 롤백 계획 템플릿, 배포 후 모니터링.\nProduction shipping guide: pre-launch checklist, feature-flag lifecycle, staged rollout with go\u002Fhold\u002Frollback thresholds, rollback plan template, post-launch monitoring.\nUse when: \"배포 준비\", \"릴리즈 전 점검\", \"롤아웃 계획\", \"롤백 계획\", preparing a production deploy, staged rollout, feature flags.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fshipping-guide\u002FSKILL.md",[],[150,151,152,153,154,155,156,135,157,158,33,159,160,139,161,162,163,164,165,24],"shipping","guide","shipping guide","launch","monitoring","lifecycle","feature flags","template","rollback","rollout","flags","thresholds","post","with","pre-launch","rollback plan",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":39},"01M6QZQ3M962PCWYM6YH62D76Z","retro","세션 회고·교훈 컴파운딩 — 이번 세션의 교정·실수·발견을 추출해 품질 기준(재현·일반화·판정 가능성)으로 거르고, 컨벤션 변화는 sync-claude-md 위임, 반복 실수는 tasks\u002Flessons.md(#가드-훅-후보 태그), 스킬 지식 갱신은 수정 제안으로 나눈다. 모든 적용은 승인 후.\nSession retrospective that turns corrections, mistakes, and discoveries into vetted lessons routed to CLAUDE.md sync, tasks\u002Flessons.md, or skill-edit proposals, with user approval before any write.\nUse when: \"회고\", \"레트로\", \"교훈 정리\", \"같은 실수 반복\", \"재발 방지 규칙\", retrospective, lessons learned, wrapping up a task, review, or loop. 여러 실행에 걸친 하네스 개선은 harness:evolve.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fretro\u002FSKILL.md",[],[168,130,94,133,173,174,175,176,177,178,179,180,105,181,182,183,184,185,186,24],"run","harness","loop","evolve","write","edit","proposals","session","up","dry","learned","Session Retrospective","lessons","mistakes",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":194,"publishedAt":39},"01M6QZPPDATJ7DAGNP0JCXFGRV","project-rules","현재 프로젝트의 스택(빌드 파일 버전, 마이그레이션 도구, ORM 유무, ES 사용, git 호스트)을 감지해 프로젝트 루트 AGENTS.md 의 마커 블록(스택 사실 + 항상 적용되는 스페셜리스트 핵심 ≤15줄 — Claude Code·Codex·Antigravity 공통)과 CLAUDE.md 의 `@AGENTS.md` 연결, Claude 전용 경로 한정 .claude\u002Frules\u002F\u003Cstack>-specialist.md(해당 버전에 실제로 맞는 상세 함정)를 diff 로 제안하고, 스택 플러그인을 런타임별로 프로젝트 범위에서 켜는 법을 안내한다. 이전 버전 출력(CLAUDE.md 블록·specialist-core.md)은 AGENTS.md 로 이전을 제안. --check 는 버전 불일치·사라진 ID·크기 한도·연결 누락을 점검.\nDetects the project's stack and proposes a cross-runtime AGENTS.md block (stack facts + always-on specialist core) linked from CLAUDE.md via @AGENTS.md, plus Claude-only path-scoped specialist rules; migrates the older CLAUDE.md-block layout; --check audits drift.\nUse when: \"이 프로젝트 세팅\", \"프로젝트 규칙 생성\", \"AGENTS.md\u002FCLAUDE.md 점검\", project setup, generate project rules, audit AGENTS.md or CLAUDE.md drift.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fproject-rules\u002FSKILL.md",[193],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},[35,107,195,196,197,134,198,38,199,200,104,105,201,202,203,204,205,206,207,24],"project rules","core","generate","git","stack","orm","es","drift","layout","runtime","-specialist","path","scoped",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":218,"publishedAt":39},"01M6QZPF3S8YAM27F297F6GVD7","post-merge","MR 머지 완료 후 Plane 이슈 종료와 Outline 문서 업데이트를 자동으로 처리하는 오케스트레이터 스킬입니다.\nissue-tracker와 document-latest 스킬을 연계 실행하여 머지 후 후속 작업을 일괄 처리합니다.\nOrchestrates post-merge follow-up after an MR is merged: chains the issue-tracker and document-latest skills to close the Plane issue and update Outline wiki docs in a single batch. Use when: an MR was just merged, closing tickets and syncing documentation after a merge, post-merge cleanup.","https:\u002F\u002Fgithub.com\u002FDokkabei97\u002Fdokkabei-harness\u002Fblob\u002Fmain\u002Fplugins\u002Fworkflow\u002Fskills\u002Fpost-merge\u002FSKILL.md",[214,217],{"categoryNo":215,"categoryName":216,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},[219,220,162,221,222,101,223,224,225,181,226,227,25,228,229,230,231,232,111,24],"merge","post merge","documentation","cleanup","batch","wiki","just","issue","tracker","closing","follow-up","true","plane","single"]