[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JWH14P2EK0RX1J33SZWEN":3,"skill-same:01M71JWH14P2EK0RX1J33SZWEN":83},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M71JWH14P2EK0RX1J33SZWEN","pmstudio-irp",null,"Use when the user asks for an incident response plan, IRP, escalation matrix or incident playbook. Writes an offline HTML plan with severities, escalation contacts and comms; DR restores service, IRP runs the incident.","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\u002Firp\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"pmstudio irp","html","dr","html plan","incident response plan","with","escalation matrix","ops","use","for","escalation","comms","offline","matrix","playbook","plan","contacts","incident response","when","incident","2026-11-10 10:12:30",false,"---\nname: pmstudio-irp\ndescription: \"Use when the user asks for an incident response plan, IRP, escalation matrix or incident playbook. Writes an offline HTML plan with severities, escalation contacts and comms; DR restores service, IRP runs the incident.\"\ndomain: ops\n---\n\n# IRP — Incident Response Plan\n\n## Purpose\n\nGenerates an Incident Response Plan specific to the product\u002Fplatform. Not a generic IT incident template — this plan is scoped to the product, uses its real stakeholders as escalation contacts, and ties severity to its data classification.\n\n## Process\n\n### Step 1: Read Context\n\n**Read all that exist:**\n- `CLAUDE.local.md` — architecture, stakeholders, vendor contacts, data classification\n- `PRD\u002F*.html` or `PRD\u002F*.md` — security section, RBAC, NFRs, integrations\n- `Data\u002FStakeholder-Directory.*` — escalation contacts with roles and emails\n- `Operational\u002FDR-Plan*.html` — recovery procedures to reference (if exists)\n\n### Step 2: Ask Discovery Questions\n\nOnly ask what can't be inferred:\n\n1. **What constitutes an \"incident\" for this product?** (data breach, service outage, unauthorized access, integration failure, data corruption)\n2. **Who is the Incident Commander?** (default: PM, but confirm)\n3. **Vendor support model?** (SLA response times, escalation contacts, ticket system)\n4. **Legal\u002Fprivilege considerations?** (e.g., ProductB has legal privilege — incidents may require legal counsel)\n5. **Existing Coco Inc incident process?** (does the team already report through ServiceNow, Slack, etc.)\n\n### Step 3: Generate IRP Document\n\n**Output:** `Operational\u002FIRP-{ProductName}-{Date}.html`\n\nSelf-contained HTML with print-optimized CSS. No CDN dependencies — this document must work offline during an actual incident.\n\n**12 sections:**\n\n**1. Purpose & Scope**\n- Which product\u002Finstance this plan covers\n- What qualifies as an incident vs. a support request\n- Relationship to firm-wide incident process\n\n**2. Severity Classification**\n\nBuild product-specific severity matrix. See `references\u002Fseverity-matrix.md` for the framework.\n\nKey rule: **Data classification drives minimum severity.**\n- Purple Data incident = auto-SEV1\n- Red Data incident = minimum SEV2\n- Yellow\u002FGreen = severity based on impact\n\n| Severity | Definition | Response Time | Example |\n|----------|-----------|---------------|---------|\n| SEV1 — Critical | Data breach, complete service outage, legal\u002Fregulatory exposure | 15 min | Purple Data accessed by unauthorized user |\n| SEV2 — High | Significant functionality loss, data integrity issue, >50% users affected | 1 hour | Integration failure causing data sync halt |\n| SEV3 — Medium | Partial functionality loss, workaround available, \u003C50% users affected | 4 hours | Single module unavailable, manual process possible |\n| SEV4 — Low | Minor issue, cosmetic, single-user impact | Next business day | Report formatting error, UI glitch |\n\n**3. Detection & Reporting**\n- How incidents are typically detected (user report, monitoring, vendor notification)\n- Reporting channel (email, Slack, ServiceNow ticket)\n- What information to include when reporting\n\n**4. Escalation Matrix**\n- Per-severity: who to contact, in what order, with backup contacts\n- Pull real names and emails from stakeholder directory\n- Include vendor escalation path\n\n**5. Response Procedures**\n- Per-severity playbooks with triage, containment, investigation, resolution steps\n- See `references\u002Fescalation-patterns.md` for playbook structure\n\n**6. Communication Protocol**\n- Internal (team Slack\u002FTeams channel)\n- Stakeholder (email using `\u002Fpmstudio-comms incident` template)\n- Vendor (support ticket + phone for SEV1-2)\n- Leadership (when to escalate to SteerCo)\n- Per-severity: who communicates what, when, through which channel\n\n**7. Evidence Preservation**\n- What to capture: screenshots, logs, timestamps, affected records\n- Where to store: incident folder in SharePoint, not in the product itself\n- Chain of custody for legal\u002Fprivilege incidents\n\n**8. Resolution & Recovery**\n- Handoff to DR\u002FRecovery plan (if exists)\n- Verification steps before declaring resolved\n- Service restoration confirmation checklist\n\n**9. Post-Incident Review (PIR)**\n- PIR meeting within 48 hours of resolution\n- Template: timeline, impact, root cause, contributing factors, what went well, what to improve, action items\n- PIR document stored in `Meeting-Notes\u002FPIR-{Date}-{Summary}.md`\n\n**10. Roles & Responsibilities**\n- Incident Commander (owns coordination)\n- Communications Lead (owns stakeholder updates)\n- Technical Lead (owns diagnosis and fix)\n- Vendor Liaison (owns vendor communication)\n- Legal Counsel (for privilege\u002Fregulatory incidents)\n\n**11. Vendor Escalation**\n- Vendor support tiers and SLA response times\n- Escalation contacts (from project memory)\n- Ticket creation procedure\n- When to bypass normal support (SEV1 phone escalation)\n\n**12. Review & Maintenance**\n- Review cadence: semi-annually or after any SEV1-2 incident\n- Tabletop exercise schedule: annually\n- Contact list verification: quarterly\n- Version history\n\n### Step 4: Present for Review\n\nShow the complete plan structure with key content decisions highlighted:\n- Severity matrix with product-specific examples\n- Escalation matrix with real names\n- Any assumptions made\n\nAsk for approval before writing the file.\n\n## Critical Rules\n\n1. **Zero external dependencies.** The HTML must render fully offline. No CDN links. During an incident, internet may be unreliable.\n2. **Real contacts only.** Pull names\u002Femails from project files. Leave blanks with \"[TBD — add contact]\" markers rather than guessing.\n3. **Legal privilege awareness.** If the project involves legal privilege (like ProductB\u002FTax), include a section on when to involve legal counsel and how to protect privilege during incident response.\n4. **Severity ties to data.** Always tie severity classification to the product's data classification. Don't create a severity matrix that ignores data sensitivity.\n5. **Actionable, not aspirational.** Every procedure should be something the team can actually execute today with current tools and access. Don't include monitoring procedures if no monitoring exists yet.\n","# IRP — Incident Response Plan\n\n## Purpose\n\nGenerates an Incident Response Plan specific to the product\u002Fplatform. Not a generic IT incident template — this plan is scoped to the product, uses its real stakeholders as escalation contacts, and ties severity to its data classification.\n\n## Process\n\n### Step 1: Read Context\n\n**Read all that exist:**\n- `CLAUDE.local.md` — architecture, stakeholders, vendor contacts, data classification\n- `PRD\u002F*.html` or `PRD\u002F*.md` — security section, RBAC, NFRs, integrations\n- `Data\u002FStakeholder-Directory.*` — escalation contacts with roles and emails\n- `Operational\u002FDR-Plan*.html` — recovery procedures to reference (if exists)\n\n### Step 2: Ask Discovery Questions\n\nOnly ask what can't be inferred:\n\n1. **What constitutes an \"incident\" for this product?** (data breach, service outage, unauthorized access, integration failure, data corruption)\n2. **Who is the Incident Commander?** (default: PM, but confirm)\n3. **Vendor support model?** (SLA response times, escalation contacts, ticket system)\n4. **Legal\u002Fprivilege considerations?** (e.g., ProductB has legal privilege — incidents may require legal counsel)\n5. **Existing Coco Inc incident process?** (does the team already report through ServiceNow, Slack, etc.)\n\n### Step 3: Generate IRP Document\n\n**Output:** `Operational\u002FIRP-{ProductName}-{Date}.html`\n\nSelf-contained HTML with print-optimized CSS. No CDN dependencies — this document must work offline during an actual incident.\n\n**12 sections:**\n\n**1. Purpose & Scope**\n- Which product\u002Finstance this plan covers\n- What qualifies as an incident vs. a support request\n- Relationship to firm-wide incident process\n\n**2. Severity Classification**\n\nBuild product-specific severity matrix. See `references\u002Fseverity-matrix.md` for the framework.\n\nKey rule: **Data classification drives minimum severity.**\n- Purple Data incident = auto-SEV1\n- Red Data incident = minimum SEV2\n- Yellow\u002FGreen = severity based on impact\n\n| Severity | Definition | Response Time | Example |\n|----------|-----------|---------------|---------|\n| SEV1 — Critical | Data breach, complete service outage, legal\u002Fregulatory exposure | 15 min | Purple Data accessed by unauthorized user |\n| SEV2 — High | Significant functionality loss, data integrity issue, >50% users affected | 1 hour | Integration failure causing data sync halt |\n| SEV3 — Medium | Partial functionality loss, workaround available, \u003C50% users affected | 4 hours | Single module unavailable, manual process possible |\n| SEV4 — Low | Minor issue, cosmetic, single-user impact | Next business day | Report formatting error, UI glitch |\n\n**3. Detection & Reporting**\n- How incidents are typically detected (user report, monitoring, vendor notification)\n- Reporting channel (email, Slack, ServiceNow ticket)\n- What information to include when reporting\n\n**4. Escalation Matrix**\n- Per-severity: who to contact, in what order, with backup contacts\n- Pull real names and emails from stakeholder directory\n- Include vendor escalation path\n\n**5. Response Procedures**\n- Per-severity playbooks with triage, containment, investigation, resolution steps\n- See `references\u002Fescalation-patterns.md` for playbook structure\n\n**6. Communication Protocol**\n- Internal (team Slack\u002FTeams channel)\n- Stakeholder (email using `\u002Fpmstudio-comms incident` template)\n- Vendor (support ticket + phone for SEV1-2)\n- Leadership (when to escalate to SteerCo)\n- Per-severity: who communicates what, when, through which channel\n\n**7. Evidence Preservation**\n- What to capture: screenshots, logs, timestamps, affected records\n- Where to store: incident folder in SharePoint, not in the product itself\n- Chain of custody for legal\u002Fprivilege incidents\n\n**8. Resolution & Recovery**\n- Handoff to DR\u002FRecovery plan (if exists)\n- Verification steps before declaring resolved\n- Service restoration confirmation checklist\n\n**9. Post-Incident Review (PIR)**\n- PIR meeting within 48 hours of resolution\n- Template: timeline, impact, root cause, contributing factors, what went well, what to improve, action items\n- PIR document stored in `Meeting-Notes\u002FPIR-{Date}-{Summary}.md`\n\n**10. Roles & Responsibilities**\n- Incident Commander (owns coordination)\n- Communications Lead (owns stakeholder updates)\n- Technical Lead (owns diagnosis and fix)\n- Vendor Liaison (owns vendor communication)\n- Legal Counsel (for privilege\u002Fregulatory incidents)\n\n**11. Vendor Escalation**\n- Vendor support tiers and SLA response times\n- Escalation contacts (from project memory)\n- Ticket creation procedure\n- When to bypass normal support (SEV1 phone escalation)\n\n**12. Review & Maintenance**\n- Review cadence: semi-annually or after any SEV1-2 incident\n- Tabletop exercise schedule: annually\n- Contact list verification: quarterly\n- Version history\n\n### Step 4: Present for Review\n\nShow the complete plan structure with key content decisions highlighted:\n- Severity matrix with product-specific examples\n- Escalation matrix with real names\n- Any assumptions made\n\nAsk for approval before writing the file.\n\n## Critical Rules\n\n1. **Zero external dependencies.** The HTML must render fully offline. No CDN links. During an incident, internet may be unreliable.\n2. **Real contacts only.** Pull names\u002Femails from project files. Leave blanks with \"[TBD — add contact]\" markers rather than guessing.\n3. **Legal privilege awareness.** If the project involves legal privilege (like ProductB\u002FTax), include a section on when to involve legal counsel and how to protect privilege during incident response.\n4. **Severity ties to data.** Always tie severity classification to the product's data classification. Don't create a severity matrix that ignores data sensitivity.\n5. **Actionable, not aspirational.** Every procedure should be something the team can actually execute today with current tools and access. Don't include monitoring procedures if no monitoring exists yet.\n",{"name":5,"domain":31,"description":7},"main","cd89f013b617f7eea982a9bbc60e992974fda2aa","skills\u002Firp",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add coco-research\u002Fcoco --skill pmstudio-irp",{"tool":65,"command":66},"bunx","bunx skills add coco-research\u002Fcoco --skill pmstudio-irp",{"tool":68,"command":69},"pnpm","pnpm dlx skills add coco-research\u002Fcoco --skill pmstudio-irp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Firp\u002FSKILL.md",true,[73,79],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fescalation-patterns.md","REFERENCE","参考文档",3054,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Firp\u002Freferences\u002Fescalation-patterns.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fseverity-matrix.md",2344,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fskills\u002Firp\u002Freferences\u002Fseverity-matrix.md",[84,109,119,137,172,191],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":91,"publishedAt":44},"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",[90],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"super","trading super intelligence","intelligence","trading","validator","personas","local","composites","studio","team","across","world","first","gated","2026","lm studio","local-first",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":44},"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",[115],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[117,92,118,94,96,97,98,99,100,101,102,103,104,105,106,107,108],"strategy","strategy super intelligence",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":131,"publishedAt":44},"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",[125,126],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[132,92,133,134,135,94,96,97,98,99,136,100,101,102,103,104,105,106,107,108],"risk","risk compliance super intelligence","compliance","risk compliance","grc",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":156,"publishedAt":44},"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",[143,146,149,150,153],{"categoryNo":144,"categoryName":145,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":151,"categoryName":152,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000031","产品经理",{"categoryNo":154,"categoryName":155,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000032","设计师",[157,158,94,159,92,160,161,162,163,164,165,101,102,166,167,106,168,169,170,171],"design","product","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":44},"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":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},[181,92,182,94,183,184,171,185,97,186,187,188,117,101,102,189,134,190,106,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":44},"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":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[199,92,200,201,94,184,171,202,203,97,204,205,117,101,102,206,207,208,209,106],"healthcare","healthcare life sciences super intelligence","life","economics","discovery","policy","clinical","clinical trials","health","trials","genomics"]