[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JSEH2VXWRMD2SFF0ZZ10D":3,"skill-same:01M71JSEH2VXWRMD2SFF0ZZ10D":88},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M71JSEH2VXWRMD2SFF0ZZ10D","pmstudio-arb",null,"Generate an Architecture Review Board (ARB) presentation in a standard 11-slide format. Use when someone asks to \"create an ARB deck\", \"architecture review presentation\", \"prepare for architecture review board\", \"ARB slides\", or needs to present a product\u002Fplatform architecture for sign-off. Reads PRD, architecture maps, and project memory to pre-fill technical content. Produces a self-contained HTML slide deck.","coco-research\u002Fcoco","coco-research","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F68911604?v=4","01M71JRE9C4NM4NSZM4JD0BJTB","Coco Research","01M71JREA0ZMR0PMH3CKA99SN1",631,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Farb-review\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"pmstudio arb","create","deck","for","platform","slides","presentation","html","present","generate","product","self","review","maps","architecture","when","project","memory","architecture review","project memory","2026-11-10 10:12:30",false,"---\nname: pmstudio-arb\ndescription: Generate an Architecture Review Board (ARB) presentation in a standard 11-slide format. Use when someone asks to \"create an ARB deck\", \"architecture review presentation\", \"prepare for architecture review board\", \"ARB slides\", or needs to present a product\u002Fplatform architecture for sign-off. Reads PRD, architecture maps, and project memory to pre-fill technical content. Produces a self-contained HTML slide deck.\ndomain: ops\n---\n\n# ARB Review — Architecture Review Board Presentation\n\n## Purpose\n\nGenerates an 11-slide architecture review presentation following Coco Inc's standard ARB format. Used when a product needs architecture sign-off for a new instance, major integration, platform migration, or periodic review.\n\n## Process\n\n### Step 1: Read Context\n\n**Required sources (read all that exist):**\n- `CLAUDE.local.md` — project context, architecture decisions, stakeholders, ProdID\n- `PRD\u002F*.html` or `PRD\u002F*.md` — requirements, NFRs, technical considerations, integrations, data model\n- `Architecture\u002F` or `*Architecture*.html` — existing diagrams, maps\n\n**Optional sources:**\n- `.sync-watch.json` — project name\n- `Operational\u002FDR-Plan*.html` — RTO\u002FRPO targets (for slide 8)\n- `Data\u002FStakeholder-Directory.*` — presenter and audience names\n\n### Step 2: Ask Discovery Questions\n\nOnly ask what cannot be inferred from context:\n\n1. **Review type?** New Product \u002F Major Change \u002F Periodic Review \u002F Decommission\n2. **Data classification?** Purple \u002F Red \u002F Yellow \u002F Green (if not in PRD)\n3. **Audience?** Firm-level ARB \u002F Department-level \u002F Technical review\n4. **Known constraints or mandates?** (e.g., \"must use existing Snowflake instance\")\n5. **Decision you need?** Approve \u002F Approve-with-conditions \u002F Defer — what specifically?\n\n### Step 3: Generate 11-Slide Deck\n\n**Output:** `Presentations\u002FARB-Review-{ProductName}-{Date}.html`\n\nSelf-contained HTML file with:\n- System fonts (no CDN dependencies)\n- Click\u002Fkeyboard navigation between slides\n- Print CSS for PDF export\n- Mermaid.js (CDN) for architecture diagrams\n\n**Slide structure — see `references\u002Farb-format.md` for section details:**\n\n| # | Slide | Key Content |\n|---|-------|-------------|\n| 1 | Title & Context | Product name, ProdID, review type, date, presenters |\n| 2 | Business Context | Problem statement, strategic alignment, sponsor |\n| 3 | Current State | AS-IS architecture (Mermaid diagram), pain points |\n| 4 | Proposed Architecture | TO-BE architecture (Mermaid diagram), what changes |\n| 5 | Data Architecture | Data classification, flows, retention, residency |\n| 6 | Security & Access | AuthN\u002FAuthZ, RBAC, encryption, CUECs |\n| 7 | Integration Points | Upstream\u002Fdownstream, protocols, error handling |\n| 8 | NFRs & SLAs | Performance, availability, RTO\u002FRPO, scalability |\n| 9 | Risk Assessment | Architecture risks, mitigations, residual acceptance |\n| 10 | Implementation Plan | Phases, timeline, rollback, blast radius |\n| 11 | Decision Request | What you need from the board, options, recommendation |\n\n### Step 4: Populate Content\n\nFor each slide, pull from project sources:\n\n- **Slide 1**: Product name and ProdID from CLAUDE.local.md. Review type from Step 2. Presenters from stakeholder directory.\n- **Slides 3-4**: Generate Mermaid diagrams from PRD architecture section and Architecture maps. If current-state diagram exists, use it. If not, build from PRD integrations and technical considerations.\n- **Slide 5**: Data classification from PRD or discovery. Data flows from integrations section. Retention from NFRs.\n- **Slide 6**: RBAC from PRD. CUECs from operationalization section. SSO\u002FAuthN from technical considerations.\n- **Slide 7**: Extract all integration points from PRD. Add protocol, frequency, error handling.\n- **Slide 8**: Pull NFRs directly from PRD table. RTO\u002FRPO from DR plan if it exists.\n- **Slide 9**: Pull risks from PRD risk section. Add architecture-specific risks.\n- **Slide 10**: Pull timeline from PRD. Add rollback strategy.\n- **Slide 11**: Decision request from Step 2. Frame options with recommendation.\n\n### Step 5: Present for Review\n\nShow the deck outline with key content per slide. Ask:\n- \"Does this cover the right scope?\"\n- \"Any slides that need different emphasis?\"\n- \"Who are the presenters for slide 1?\"\n\nApply feedback, then write the file.\n\n## Critical Rules\n\n1. **Mermaid diagrams are mandatory** for slides 3 and 4. Architecture reviews without diagrams fail.\n2. **Data classification must be explicit.** If unknown, mark as \"TBD — requires classification\" in red. Never assume.\n3. **Slide 11 must have a clear ask.** Not \"please review\" but \"approve this architecture for production deployment\" or \"approve with condition: validate cascading before Phase 2.\"\n4. **No implementation details on architecture slides.** Show components, interfaces, and data flows — not code, configs, or step-by-step procedures.\n5. **Keep it to 11 slides.** If more content is needed, add appendix slides clearly labeled \"APPENDIX\" after slide 11.\n","# ARB Review — Architecture Review Board Presentation\n\n## Purpose\n\nGenerates an 11-slide architecture review presentation following Coco Inc's standard ARB format. Used when a product needs architecture sign-off for a new instance, major integration, platform migration, or periodic review.\n\n## Process\n\n### Step 1: Read Context\n\n**Required sources (read all that exist):**\n- `CLAUDE.local.md` — project context, architecture decisions, stakeholders, ProdID\n- `PRD\u002F*.html` or `PRD\u002F*.md` — requirements, NFRs, technical considerations, integrations, data model\n- `Architecture\u002F` or `*Architecture*.html` — existing diagrams, maps\n\n**Optional sources:**\n- `.sync-watch.json` — project name\n- `Operational\u002FDR-Plan*.html` — RTO\u002FRPO targets (for slide 8)\n- `Data\u002FStakeholder-Directory.*` — presenter and audience names\n\n### Step 2: Ask Discovery Questions\n\nOnly ask what cannot be inferred from context:\n\n1. **Review type?** New Product \u002F Major Change \u002F Periodic Review \u002F Decommission\n2. **Data classification?** Purple \u002F Red \u002F Yellow \u002F Green (if not in PRD)\n3. **Audience?** Firm-level ARB \u002F Department-level \u002F Technical review\n4. **Known constraints or mandates?** (e.g., \"must use existing Snowflake instance\")\n5. **Decision you need?** Approve \u002F Approve-with-conditions \u002F Defer — what specifically?\n\n### Step 3: Generate 11-Slide Deck\n\n**Output:** `Presentations\u002FARB-Review-{ProductName}-{Date}.html`\n\nSelf-contained HTML file with:\n- System fonts (no CDN dependencies)\n- Click\u002Fkeyboard navigation between slides\n- Print CSS for PDF export\n- Mermaid.js (CDN) for architecture diagrams\n\n**Slide structure — see `references\u002Farb-format.md` for section details:**\n\n| # | Slide | Key Content |\n|---|-------|-------------|\n| 1 | Title & Context | Product name, ProdID, review type, date, presenters |\n| 2 | Business Context | Problem statement, strategic alignment, sponsor |\n| 3 | Current State | AS-IS architecture (Mermaid diagram), pain points |\n| 4 | Proposed Architecture | TO-BE architecture (Mermaid diagram), what changes |\n| 5 | Data Architecture | Data classification, flows, retention, residency |\n| 6 | Security & Access | AuthN\u002FAuthZ, RBAC, encryption, CUECs |\n| 7 | Integration Points | Upstream\u002Fdownstream, protocols, error handling |\n| 8 | NFRs & SLAs | Performance, availability, RTO\u002FRPO, scalability |\n| 9 | Risk Assessment | Architecture risks, mitigations, residual acceptance |\n| 10 | Implementation Plan | Phases, timeline, rollback, blast radius |\n| 11 | Decision Request | What you need from the board, options, recommendation |\n\n### Step 4: Populate Content\n\nFor each slide, pull from project sources:\n\n- **Slide 1**: Product name and ProdID from CLAUDE.local.md. Review type from Step 2. Presenters from stakeholder directory.\n- **Slides 3-4**: Generate Mermaid diagrams from PRD architecture section and Architecture maps. If current-state diagram exists, use it. If not, build from PRD integrations and technical considerations.\n- **Slide 5**: Data classification from PRD or discovery. Data flows from integrations section. Retention from NFRs.\n- **Slide 6**: RBAC from PRD. CUECs from operationalization section. SSO\u002FAuthN from technical considerations.\n- **Slide 7**: Extract all integration points from PRD. Add protocol, frequency, error handling.\n- **Slide 8**: Pull NFRs directly from PRD table. RTO\u002FRPO from DR plan if it exists.\n- **Slide 9**: Pull risks from PRD risk section. Add architecture-specific risks.\n- **Slide 10**: Pull timeline from PRD. Add rollback strategy.\n- **Slide 11**: Decision request from Step 2. Frame options with recommendation.\n\n### Step 5: Present for Review\n\nShow the deck outline with key content per slide. Ask:\n- \"Does this cover the right scope?\"\n- \"Any slides that need different emphasis?\"\n- \"Who are the presenters for slide 1?\"\n\nApply feedback, then write the file.\n\n## Critical Rules\n\n1. **Mermaid diagrams are mandatory** for slides 3 and 4. Architecture reviews without diagrams fail.\n2. **Data classification must be explicit.** If unknown, mark as \"TBD — requires classification\" in red. Never assume.\n3. **Slide 11 must have a clear ask.** Not \"please review\" but \"approve this architecture for production deployment\" or \"approve with condition: validate cascading before Phase 2.\"\n4. **No implementation details on architecture slides.** Show components, interfaces, and data flows — not code, configs, or step-by-step procedures.\n5. **Keep it to 11 slides.** If more content is needed, add appendix slides clearly labeled \"APPENDIX\" after slide 11.\n",{"name":5,"domain":57,"description":7},"ops","main","cd89f013b617f7eea982a9bbc60e992974fda2aa","skills\u002Farb-review",15,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco","https:\u002F\u002Fcocoresearch.org\u002Fcoco\u002F","https:\u002F\u002Fgithub.com\u002Fcoco-research","https:\u002F\u002Fcocoresearch.org","Local-first, open-source tools for people who work with AI agents: governed memory, agents that check their own work, and data that stays on your machine.","2026-11-11 12:18:13",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add coco-research\u002Fcoco --skill pmstudio-arb",{"tool":74,"command":75},"bunx","bunx skills add coco-research\u002Fcoco --skill pmstudio-arb",{"tool":77,"command":78},"pnpm","pnpm dlx skills add coco-research\u002Fcoco --skill pmstudio-arb","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Farb-review\u002FSKILL.md",true,[82],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Farb-format.md","REFERENCE","参考文档",4214,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Farb-review\u002Freferences\u002Farb-format.md",[89,114,124,140,172,191],{"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":96,"publishedAt":52},"01M71KEJXF9KMT0BWCMRSRFA4M","trading-super-intelligence","Trading Super Intelligence Team. Named real-world personas across 8 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Ftrading\u002FSKILL.md",[95],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113],"super","trading super intelligence","intelligence","trading","validator","personas","local","composites","studio","team","across","world","first","gated","2026","lm studio","local-first",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":52},"01M71KEFWS3CMAP7DF1P0FWTDE","strategy-super-intelligence","Strategy Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fstrategy\u002FSKILL.md",[120],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[122,97,123,99,101,102,103,104,105,106,107,108,109,110,111,112,113],"strategy","strategy super intelligence",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":134,"publishedAt":52},"01M71KED56ZEPK2QE84QSQPMT0","risk-compliance-super-intelligence","Risk & Compliance (GRC) Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Frisk-compliance\u002FSKILL.md",[130,131],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":132,"categoryName":133,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000037","律师与法务",[135,97,136,137,138,99,101,102,103,104,139,105,106,107,108,109,110,111,112,113],"risk","risk compliance super intelligence","compliance","risk compliance","grc",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":157,"publishedAt":52},"01M71KE9A2FWSC74VA96W1EZSN","product-design-super-intelligence","Your product + design brain trust and decision partner. Named personas across 8 cells spanning product strategy, discovery\u002Fresearch, growth\u002Fmetrics, design foundations\u002Fusability, design leadership\u002Fcraft, UX\u002Fcontent, design systems, and a…","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fproduct-design\u002FSKILL.md",[146,149,152,153,154],{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},{"categoryNo":155,"categoryName":156,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师",[158,42,99,159,97,160,161,162,163,164,165,106,107,166,167,111,168,169,170,171],"design","product design","product design super intelligence","foundations","product-design","decision","design systems","usability","leadership","ux","brain","craft","metrics","trust",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":180,"publishedAt":52},"01M71KE6H9FPSD9TECYFBPXZ8Y","legal-ip-super-intelligence","Your legal, IP, and regulatory brain trust. 31 named personas across 7 cells covering patent strategy, tech licensing, regulatory litigation, AI governance, open-source compliance, privacy law, and antitrust.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Flegal-ip\u002FSKILL.md",[178,179],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":132,"categoryName":133,"taxonomyType":29,"taxonomyTypeDesc":30},[181,97,182,99,183,184,171,185,102,186,187,188,122,106,107,189,137,190,111,168],"ip","legal ip super intelligence","legal","sep","tech","litigation","ai governance","open","open-source","governance",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":198,"publishedAt":52},"01M71KE36QRY610V6YVB9JWRND","healthcare-life-sciences-super-intelligence","Your healthcare and life sciences brain trust. 25 named personas across 7 cells covering drug discovery, medtech, biotech strategy, health policy, genomics, clinical trials, and healthcare economics.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fhealthcare-life-sciences\u002FSKILL.md",[197],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[199,97,200,201,99,184,171,202,203,102,204,205,122,106,107,206,207,208,209,111],"healthcare","healthcare life sciences super intelligence","life","economics","discovery","policy","clinical","clinical trials","health","trials","genomics"]