[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F98GF62F6C69X5CPMRZ7T2":3,"skill-same:01M7F98GF62F6C69X5CPMRZ7T2":63},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7F98GF62F6C69X5CPMRZ7T2","managing-value-creation-plans",null,"Structures 100-day and long-term value creation plans with initiative tracking and KPI targets. Use when building value creation plans, tracking improvement initiatives, or managing post-acquisition integration.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fmanaging-value-creation-plans\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: managing-value-creation-plans\nlanguage: en\ndescription: Structures 100-day and long-term value creation plans with initiative tracking and KPI targets. Use when building value creation plans, tracking improvement initiatives, or managing post-acquisition integration.\ntags:\n  - management\n  - private-equity\nmetadata:\n  author: casemark\n  practice_areas:\n    - Private Equity\n    - Venture Capital\n    - Growth Equity\n  document_types:\n    - Management Report\n  skill_modes:\n    - Management\n    - Coordination\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Ffinance\u002Fmanaging-value-creation-plans\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Managing Value Creation Plans\n\n## When To Use\n\n- Building a 100-day plan immediately following acquisition close or new platform investment\n- Structuring a multi-year value creation roadmap across revenue growth, margin expansion, and strategic repositioning levers\n- Tracking initiative progress for quarterly board or investment committee reporting\n- Aligning management teams on prioritized improvement initiatives with measurable KPI targets\n- Preparing for exit by documenting realized value creation across holding period\n\n## Inputs To Gather\n\n- **Deal thesis and investment memo** — the original underwriting assumptions, projected returns, and identified value levers\n- **Baseline financials** — trailing twelve-month (TTM) revenue, EBITDA, margins, and capital structure at acquisition\n- **Management team roster** — key operators, their roles, and capacity for initiative ownership\n- **Existing operational data** — sales pipeline, customer concentration, vendor contracts, headcount, and technology stack\n- **Comparable benchmarks** — portfolio company or industry KPIs for revenue growth rate, gross margin, SG&A as % of revenue, working capital days, and customer retention\n- **Integration or transition items** — any carve-out TSAs, IT migrations, or leadership changes in flight\n\n## Workflow\n\n1. **Map value levers to deal thesis** — Categorize each underwritten assumption into a lever: revenue growth (organic\u002Finorganic), cost optimization, working capital improvement, pricing\u002Fmix, or multiple expansion. Assign a preliminary EBITDA impact estimate to each lever.\n\n2. **Design the 100-day plan** — For the first 100 days post-close, define 8–15 discrete initiatives. Each initiative needs:\n   - An accountable owner (single person, not a committee)\n   - A concrete deliverable and completion date\n   - A binary success criterion or quantified KPI target\n   - Dependencies on other initiatives or external factors\n   - Priority tier: \"must-win\" (thesis-critical), \"quick-win\" (low effort, visible impact), or \"foundational\" (enables future initiatives)\n\n3. **Build the long-term roadmap** — Extend beyond 100 days into Year 1, Year 2, and hold-period horizons. Sequence initiatives by dependency order and resource availability. Group into workstreams (e.g., commercial excellence, operational efficiency, talent\u002Forg, M&A\u002Fbolt-on, technology\u002Fdata).\n\n4. **Set KPI targets and tracking cadence** — For each workstream, define 2–4 KPIs with baseline, target, and stretch values. Establish reporting frequency:\n   - Weekly: operational metrics owned by management (pipeline, production, cash)\n   - Monthly: financial and initiative-level progress review with deal team\n   - Quarterly: board-level scorecard with initiative RAG status and EBITDA bridge updates\n\n5. **Build the EBITDA bridge** — Create a waterfall from entry EBITDA to projected exit EBITDA, attributing value to each initiative or lever. Update this bridge quarterly with actual vs. plan variance.\n\n6. **Assign governance structure** — Define the operating rhythm: who runs the value creation meeting, frequency, escalation path for stalled initiatives, and criteria for killing or replacing underperforming initiatives.\n\n7. **Document and version** — Maintain a living tracker (typically a spreadsheet or project management tool export) that captures status changes, revised timelines, and scope adjustments with date stamps.\n\n## Output\n\nThe deliverable is a structured value creation plan document containing:\n\n- **Executive summary** — investment thesis recap, total targeted EBITDA impact, and plan horizon\n- **100-day initiative table** — columns: initiative name, owner, lever category, priority tier, target KPI, baseline value, target value, due date, status (RAG), and notes\n- **Long-term roadmap** — workstream-by-workstream initiative sequencing with quarterly milestones through projected exit\n- **EBITDA bridge** — waterfall chart or table from entry to target exit EBITDA with per-initiative attribution\n- **KPI scorecard template** — ready-to-populate tracker with defined metrics, data sources, and reporting owners\n- **Governance calendar** — meeting cadence, attendees, and standing agenda items\n\n## Quality Checks\n\n- Every initiative traces back to a specific deal thesis lever — no orphan projects\n- Each initiative has exactly one accountable owner, not shared ownership\n- KPI targets are grounded in baseline data, not aspirational round numbers [VERIFY baseline data sources and measurement methodology]\n- The sum of individual initiative EBITDA impacts reconciles to the total bridge target (watch for double-counting across levers)\n- 100-day milestones are genuinely achievable within the timeframe given integration realities — pressure-test with management\n- [VERIFY] Tax, regulatory, or union\u002Flabor constraints that may delay specific initiatives in the target jurisdiction\n- RAG status definitions are explicit and consistent (e.g., Red = >2 weeks behind schedule or >20% below KPI run-rate)\n- The plan distinguishes between controllable operational improvements and market\u002Fmacro-dependent assumptions\n","# Managing Value Creation Plans\n\n## When To Use\n\n- Building a 100-day plan immediately following acquisition close or new platform investment\n- Structuring a multi-year value creation roadmap across revenue growth, margin expansion, and strategic repositioning levers\n- Tracking initiative progress for quarterly board or investment committee reporting\n- Aligning management teams on prioritized improvement initiatives with measurable KPI targets\n- Preparing for exit by documenting realized value creation across holding period\n\n## Inputs To Gather\n\n- **Deal thesis and investment memo** — the original underwriting assumptions, projected returns, and identified value levers\n- **Baseline financials** — trailing twelve-month (TTM) revenue, EBITDA, margins, and capital structure at acquisition\n- **Management team roster** — key operators, their roles, and capacity for initiative ownership\n- **Existing operational data** — sales pipeline, customer concentration, vendor contracts, headcount, and technology stack\n- **Comparable benchmarks** — portfolio company or industry KPIs for revenue growth rate, gross margin, SG&A as % of revenue, working capital days, and customer retention\n- **Integration or transition items** — any carve-out TSAs, IT migrations, or leadership changes in flight\n\n## Workflow\n\n1. **Map value levers to deal thesis** — Categorize each underwritten assumption into a lever: revenue growth (organic\u002Finorganic), cost optimization, working capital improvement, pricing\u002Fmix, or multiple expansion. Assign a preliminary EBITDA impact estimate to each lever.\n\n2. **Design the 100-day plan** — For the first 100 days post-close, define 8–15 discrete initiatives. Each initiative needs:\n   - An accountable owner (single person, not a committee)\n   - A concrete deliverable and completion date\n   - A binary success criterion or quantified KPI target\n   - Dependencies on other initiatives or external factors\n   - Priority tier: \"must-win\" (thesis-critical), \"quick-win\" (low effort, visible impact), or \"foundational\" (enables future initiatives)\n\n3. **Build the long-term roadmap** — Extend beyond 100 days into Year 1, Year 2, and hold-period horizons. Sequence initiatives by dependency order and resource availability. Group into workstreams (e.g., commercial excellence, operational efficiency, talent\u002Forg, M&A\u002Fbolt-on, technology\u002Fdata).\n\n4. **Set KPI targets and tracking cadence** — For each workstream, define 2–4 KPIs with baseline, target, and stretch values. Establish reporting frequency:\n   - Weekly: operational metrics owned by management (pipeline, production, cash)\n   - Monthly: financial and initiative-level progress review with deal team\n   - Quarterly: board-level scorecard with initiative RAG status and EBITDA bridge updates\n\n5. **Build the EBITDA bridge** — Create a waterfall from entry EBITDA to projected exit EBITDA, attributing value to each initiative or lever. Update this bridge quarterly with actual vs. plan variance.\n\n6. **Assign governance structure** — Define the operating rhythm: who runs the value creation meeting, frequency, escalation path for stalled initiatives, and criteria for killing or replacing underperforming initiatives.\n\n7. **Document and version** — Maintain a living tracker (typically a spreadsheet or project management tool export) that captures status changes, revised timelines, and scope adjustments with date stamps.\n\n## Output\n\nThe deliverable is a structured value creation plan document containing:\n\n- **Executive summary** — investment thesis recap, total targeted EBITDA impact, and plan horizon\n- **100-day initiative table** — columns: initiative name, owner, lever category, priority tier, target KPI, baseline value, target value, due date, status (RAG), and notes\n- **Long-term roadmap** — workstream-by-workstream initiative sequencing with quarterly milestones through projected exit\n- **EBITDA bridge** — waterfall chart or table from entry to target exit EBITDA with per-initiative attribution\n- **KPI scorecard template** — ready-to-populate tracker with defined metrics, data sources, and reporting owners\n- **Governance calendar** — meeting cadence, attendees, and standing agenda items\n\n## Quality Checks\n\n- Every initiative traces back to a specific deal thesis lever — no orphan projects\n- Each initiative has exactly one accountable owner, not shared ownership\n- KPI targets are grounded in baseline data, not aspirational round numbers [VERIFY baseline data sources and measurement methodology]\n- The sum of individual initiative EBITDA impacts reconciles to the total bridge target (watch for double-counting across levers)\n- 100-day milestones are genuinely achievable within the timeframe given integration realities — pressure-test with management\n- [VERIFY] Tax, regulatory, or union\u002Flabor constraints that may delay specific initiatives in the target jurisdiction\n- RAG status definitions are explicit and consistent (e.g., Red = >2 weeks behind schedule or >20% below KPI run-rate)\n- The plan distinguishes between controllable operational improvements and market\u002Fmacro-dependent assumptions\n",{"name":5,"tags":24,"source":27,"license":15,"language":28,"metadata":29,"description":7,"imported_at":40,"source_path":41,"source_repository":42},[25,26],"management","private-equity","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":30,"skill_modes":31,"document_types":34,"practice_areas":36},"casemark",[32,33],"Management","Coordination",[35],"Management Report",[37,38,39],"Private Equity","Venture Capital","Growth Equity","2026-09-20","skills\u002Ffinance\u002Fmanaging-value-creation-plans\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fmanaging-value-creation-plans","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-value-creation-plans",{"tool":55,"command":56},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-value-creation-plans",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-value-creation-plans","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fmanaging-value-creation-plans\u002FSKILL.md",true,[],[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]