[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73DMF1SZGFKQZTYS808Z5S7":3,"skill-same:01M73DMF1SZGFKQZTYS808Z5S7":67},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M73DMF1SZGFKQZTYS808Z5S7","consulting-report-writing",null,"Guides Communications Lead through writing McKinsey\u002FBCG-style consulting reports. Covers issue tree structure, MECE principle application, slide\u002Fpage design logic, and recommendation framing with impact-feasibility assessment. Sets the quality floor for all client-facing deliverables.","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-consult\u002F.hermes\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-consult\ndescription: >\n  Guides Communications Lead through writing McKinsey\u002FBCG-style consulting\n  reports. Covers issue tree structure, MECE principle application, slide\u002Fpage\n  design logic, and recommendation framing with impact-feasibility assessment.\n  Sets the quality floor for all client-facing deliverables.\ncapability: consulting-report-writing\nversion: 1.0.1\nlast_reviewed: 2026-10-08\nstatus: active\nowner: communications-lead\nprerequisites: narrative-framework\nrelates_to:\n  - skill: narrative-framework\n    type: composes_with\n  - skill: executive-presentation\n    type: composes_with\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\nUse in Phase 3 whenever a formal consulting deliverable (strategy report, assessment, recommendation memo) is being produced. The narrative-framework skill should be completed before this skill is invoked.\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\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-consult.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- narrative-framework\n- executive-presentation\n- insight-synthesis\n","## Context\n\nUse in Phase 3 whenever a formal consulting deliverable (strategy report, assessment, recommendation memo) is being produced. The narrative-framework skill should be completed before this skill is invoked.\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\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-consult.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- narrative-framework\n- executive-presentation\n- insight-synthesis\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"capability":5,"relates_to":36,"description":42,"last_reviewed":43,"prerequisites":39,"catalog-parity":44},"communications-lead","co-consult","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",[37,40],{"type":38,"skill":39},"composes_with","narrative-framework",{"type":38,"skill":41},"executive-presentation","Guides Communications Lead through writing McKinsey\u002FBCG-style consulting reports. Covers issue tree structure, MECE principle application, slide\u002Fpage design logic, and recommendation framing with impact-feasibility assessment. Sets the quality floor for all client-facing deliverables.\n",1791417600000,"skip","main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fco-consult\u002F.hermes\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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill consulting-report-writing",{"tool":59,"command":60},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill consulting-report-writing",{"tool":62,"command":63},"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-consult\u002F.hermes\u002Fskills\u002Fconsulting-report-writing\u002FSKILL.md",true,[],[68,76,81,86,91,96],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":75},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":77,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":75},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":82,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":75},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":87,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":75},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":92,"name":70,"nameZh":6,"description":71,"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":75},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":97,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":75},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]