[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73F2KXFRPV0MHRT84RAMWM4":3,"skill-same:01M73F2KXFRPV0MHRT84RAMWM4":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M73F2KXFRPV0MHRT84RAMWM4","consulting-report-writing",null,"Guides any agent producing a client-facing deliverable through writing McKinsey\u002FBCG-style consulting reports. Covers issue tree structure, MECE principle application, page design logic, and recommendation framing with impact-feasibility assessment. Sets the quality floor for all client-facing deliverables in co-hr — not exclusive to any single agent.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-hr\u002Fskills\u002Fconsulting-report-writing\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\ncatalog-parity: skip  # variant-maintained fork — excluded from the root Variant-Exclusive catalog (W5 disposition)\nname: consulting-report-writing\nscope: co-hr\ndescription: >\n  Guides any agent producing a client-facing deliverable through writing\n  McKinsey\u002FBCG-style consulting reports. Covers issue tree structure, MECE\n  principle application, page design logic, and recommendation framing with\n  impact-feasibility assessment. Sets the quality floor for all client-facing\n  deliverables in co-hr — not exclusive to any single agent.\ncapability: hr-consulting-report-writing\nversion: 1.0.1\nlast_reviewed: 2026-10-08\nstatus: active\nowner: pm\nprerequisites: none\nmetadata:\n  type: process\n  triggers:\n    - consulting report\n    - strategy report\n    - recommendation memo\n    - report writing\n    - issue tree\n    - consulting deliverable\n---\n\n## Context\n\nShared quality-floor skill. Use whenever any co-hr agent produces a formal client-facing consulting deliverable (compliance review, HR system design proposal, workforce statistics report, restructuring plan, etc.). It has no single natural owner among the 11 specialists, so `pm` holds it and any agent may invoke it directly when writing a deliverable.\n\n## When to Use\n\n- When producing any formal client-facing consulting deliverable\n- When structuring a strategy report, assessment, or recommendation memo\n- When recommendations need to be prioritized and sequenced for a client\n- When the engagement reaches the deliverable production stage in Phase 3\n\n## Execution Steps\n\n1. **Apply Issue Tree Structure**:\n   - Start from the central question (the client's decision)\n   - Decompose into MECE sub-questions (Mutually Exclusive, Collectively Exhaustive)\n   - Each section of the report answers one branch of the issue tree\n\n2. **Section Architecture** (standard consulting report structure):\n   - Executive Summary (1-2 pages): findings, conclusions, recommendations — written last, placed first\n   - Situation \u002F Context (1-2 pages): what is true today\n   - Complication \u002F Problem (1-2 pages): why the status quo is not acceptable\n   - Resolution \u002F Recommendations (3-5 pages): what should be done, in what order\n   - Implementation Roadmap (1-2 pages): phased actions with owners and timelines\n   - Appendix: supporting data, methodology, detailed analysis\n\n3. **MECE Check**: Review each section. Ask: Do the sections overlap? Do they together cover the full scope?\n\n4. **Recommendation Framing**: Each recommendation must have:\n   - What (specific action)\n   - Why (evidence-backed rationale)\n   - How (implementation approach)\n   - Who (owner)\n   - When (timeline)\n   - Impact-Feasibility Matrix: plot each recommendation on a 2x2 (Impact × Feasibility) to prioritize\n\n5. **Language Standards**:\n   - Active voice, present tense for recommendations\n   - Quantify every claim where possible (\"20% cost reduction\" not \"significant cost reduction\")\n   - One idea per paragraph, topic sentence first\n   - No jargon without definition\n   - Legal\u002Fregulatory proper nouns of the active jurisdiction stay in backticks per co-hr's English-prose language policy\n\n6. **Visual Communication**: Every data point should have a chart or table. Every complex argument should have a visual framework.\n\n7. **Quality Checks**:\n   - MECE compliance across all sections\n   - So-What statement present per section\n   - Evidence backing every claim\n   - Executive summary matches body conclusions\n\n## Output Format\n\n- **Full consulting report** in the section structure above\n- **Recommendation Prioritization Matrix** (Impact × Feasibility)\n- **Executive Summary** (standalone, max 2 pages)\n\n> **Save Output To**: See Output Destination Mapping in `docs\u002Fco-hr.context.md` for destination folder and naming convention. Create the folder if it does not exist. Do not hard-code output paths.\n\n## Related Skills\n\n- (none yet in co-hr — add once a downstream skill exists)\n","## Context\n\nShared quality-floor skill. Use whenever any co-hr agent produces a formal client-facing consulting deliverable (compliance review, HR system design proposal, workforce statistics report, restructuring plan, etc.). It has no single natural owner among the 11 specialists, so `pm` holds it and any agent may invoke it directly when writing a deliverable.\n\n## When to Use\n\n- When producing any formal client-facing consulting deliverable\n- When structuring a strategy report, assessment, or recommendation memo\n- When recommendations need to be prioritized and sequenced for a client\n- When the engagement reaches the deliverable production stage in Phase 3\n\n## Execution Steps\n\n1. **Apply Issue Tree Structure**:\n   - Start from the central question (the client's decision)\n   - Decompose into MECE sub-questions (Mutually Exclusive, Collectively Exhaustive)\n   - Each section of the report answers one branch of the issue tree\n\n2. **Section Architecture** (standard consulting report structure):\n   - Executive Summary (1-2 pages): findings, conclusions, recommendations — written last, placed first\n   - Situation \u002F Context (1-2 pages): what is true today\n   - Complication \u002F Problem (1-2 pages): why the status quo is not acceptable\n   - Resolution \u002F Recommendations (3-5 pages): what should be done, in what order\n   - Implementation Roadmap (1-2 pages): phased actions with owners and timelines\n   - Appendix: supporting data, methodology, detailed analysis\n\n3. **MECE Check**: Review each section. Ask: Do the sections overlap? Do they together cover the full scope?\n\n4. **Recommendation Framing**: Each recommendation must have:\n   - What (specific action)\n   - Why (evidence-backed rationale)\n   - How (implementation approach)\n   - Who (owner)\n   - When (timeline)\n   - Impact-Feasibility Matrix: plot each recommendation on a 2x2 (Impact × Feasibility) to prioritize\n\n5. **Language Standards**:\n   - Active voice, present tense for recommendations\n   - Quantify every claim where possible (\"20% cost reduction\" not \"significant cost reduction\")\n   - One idea per paragraph, topic sentence first\n   - No jargon without definition\n   - Legal\u002Fregulatory proper nouns of the active jurisdiction stay in backticks per co-hr's English-prose language policy\n\n6. **Visual Communication**: Every data point should have a chart or table. Every complex argument should have a visual framework.\n\n7. **Quality Checks**:\n   - MECE compliance across all sections\n   - So-What statement present per section\n   - Evidence backing every claim\n   - Executive summary matches body conclusions\n\n## Output Format\n\n- **Full consulting report** in the section structure above\n- **Recommendation Prioritization Matrix** (Impact × Feasibility)\n- **Executive Summary** (standalone, max 2 pages)\n\n> **Save Output To**: See Output Destination Mapping in `docs\u002Fco-hr.context.md` for destination folder and naming convention. Create the folder if it does not exist. Do not hard-code output paths.\n\n## Related Skills\n\n- (none yet in co-hr — add once a downstream skill exists)\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"capability":36,"description":37,"last_reviewed":38,"prerequisites":39,"catalog-parity":40},"pm","co-hr","active","1.0.1",{"type":28,"triggers":29},"process",[30,31,32,33,34,35],"consulting report","strategy report","recommendation memo","report writing","issue tree","consulting deliverable","hr-consulting-report-writing","Guides any agent producing a client-facing deliverable through writing McKinsey\u002FBCG-style consulting reports. Covers issue tree structure, MECE principle application, page design logic, and recommendation framing with impact-feasibility assessment. Sets the quality floor for all client-facing deliverables in co-hr — not exclusive to any single agent.\n",1791417600000,"none","skip","main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fco-hr\u002Fskills\u002Fconsulting-report-writing",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill consulting-report-writing",{"tool":55,"command":56},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill consulting-report-writing",{"tool":58,"command":59},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill consulting-report-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-hr\u002Fskills\u002Fconsulting-report-writing\u002FSKILL.md",true,[],[64,70,76,82,89,96],{"skillNo":65,"name":66,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M73HG1JK5J3A3AMG6WNH8V6E","discovery","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftests\u002Fprocedures-fixtures\u002Ftemplates\u002Fco-fixt\u002Fskills\u002Fdiscovery\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M73HG0VZMCNH9YJX8ERV6R7C","x","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftests\u002Fprocedures-fixtures\u002Ftemplates\u002Fco-bad\u002Fskills\u002Fx\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M73HFZR1J6DMW5BRXG1ND6ET","root-skill","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftests\u002Fprocedures-fixtures\u002Fskills\u002Froot-skill\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M73HFSYWV2FPF895DK295NCV","update-bun-packages","Scans, updates, and upgrades Bun dependencies and packages across the AI workspace (L0) or standalone project (L2\u002FL3) while ensuring lockfile consistency, package.json version bumps, and security compliance. Use when: updating bun dependencies, upgrading packages to @latest, checking outdated packages in workspace or templates.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002Fskills\u002Fupdate-bun-packages\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M73HFPZ7G1AHF80CDEJ94SZ9","ui-ux-design-intelligence","Provides comprehensive UI\u002FUX design capabilities including design system creation, component design, visual hierarchy, and user-centered design principles. Use when: building design systems, creating visual designs, designing UI components, or establishing design specifications.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002Fskills\u002Fui-ux-design-intelligence\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M73HFMBER8AQEX2HF02JE2G4","translate","Translation helper for README and documentation files with diff preview and guidance","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002Fskills\u002Ftranslate\u002FSKILL.md",[],[]]