본문으로 건너뛰기
cccskills
무료GitHub에 공개

ma-playbook

M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(4)

  • SKILL.md4.3 KB
  • LICENSE1.0 KB
  • references/due-diligence-checklist.md4.8 KB
  • references/integration-playbook.md5.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Attribution: Sourced from alirezarezvani/claude-skills by Alireza Rezvani.

M&A Playbook

Frameworks for both sides of M&A: acquiring companies and being acquired.

Keywords

M&A, mergers and acquisitions, due diligence, acquisition, acqui-hire, integration, deal structure, valuation, LOI, term sheet, earnout

Quick Start

Acquiring: Start with strategic rationale → target screening → due diligence → valuation → negotiation → integration.

Being Acquired: Start with readiness assessment → data room prep → advisor selection → negotiation → transition.

When You're Acquiring

Strategic Rationale (answer before anything else)

  • Buy vs Build: Can you build this faster/cheaper? If yes, don't acquire.
  • Acqui-hire vs Product vs Market: What are you really buying? Talent? Technology? Customers?
  • Integration complexity: How hard is it to merge this into your company?

Due Diligence Checklist

DomainKey QuestionsRed Flags
FinancialRevenue quality, customer concentration, burn rate>30% revenue from 1 customer
TechnicalCode quality, tech debt, architecture fitMonolith with no tests
LegalIP ownership, pending litigation, contractsKey IP owned by individuals
PeopleKey person risk, culture fit, retention riskFounders have no lockup/earnout
MarketMarket position, competitive threatsDeclining market share
CustomersChurn rate, NPS, contract termsHigh churn, short contracts

Valuation Approaches

  • Revenue multiple: Industry-dependent (2-15x ARR for SaaS)
  • Comparable transactions: What similar companies sold for
  • DCF: For profitable companies only (most startups: use multiples)
  • Acqui-hire: $1-3M per engineer in hot markets

Integration Frameworks

See references/integration-playbook.md for the 100-day integration plan.

When You're Being Acquired

Readiness Signals

  • Inbound interest from strategic buyers
  • Market consolidation happening around you
  • Fundraising becomes harder than operating
  • Founder ready for a transition

Preparation (6-12 months before)

  1. Clean up financials (audited if possible)
  2. Document all IP and contracts
  3. Reduce customer concentration
  4. Lock up key employees
  5. Build the data room
  6. Engage an M&A advisor

Negotiation Points

TermWhat to WatchYour Leverage
ValuationEarnout traps (unreachable targets)Multiple competing offers
EarnoutMilestone definitions, measurement periodCash-heavy vs earnout-heavy split
LockupDuration, conditionsYour replaceability
Rep & warrantiesScope of liabilityEscrow vs indemnification cap
Employee retentionWho gets offers, at what termsKey person dependencies

Red Flags (Both Sides)

  • No clear strategic rationale beyond "it's a good deal"
  • Culture clash visible during due diligence and ignored
  • Key people not locked in before close
  • Integration plan doesn't exist or is "we'll figure it out"
  • Valuation based on projections, not actuals

Integration with C-Suite Roles

RoleContribution to M&A
CEOStrategic rationale, negotiation lead
CFOValuation, deal structure, financing
CTOTechnical due diligence, integration architecture
CHROPeople due diligence, retention planning
COOIntegration execution, process merge
CPOProduct roadmap impact, customer overlap

Resources

  • references/integration-playbook.md — 100-day post-acquisition integration plan
  • references/due-diligence-checklist.md — comprehensive DD checklist by domain

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use when long-lived agents, project memories, system prompts, or playbooks are repeatedly summarized, rewritten, or optimized and risk losing domain detail, provenance, or execution learnings.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mouadja02/skills102026년 10월 22일 업데이트

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mouadja02/skills102026년 10월 22일 업데이트

Adds educational comments to a code file so it becomes a learning resource, asking for the file (with a list of close matches) if none is given. Use when preparing code for learners, onboarding, or teaching.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mouadja02/skills102026년 10월 22일 업데이트

Write, debug, and optimize Adobe Illustrator automation scripts using ExtendScript (JavaScript/JSX). Use when creating or modifying scripts that manipulate documents, layers, paths, text frames, colors, symbols, artboards, or any Illustrator DOM objects. Covers the complete JavaScript object model, coordinate system, measurement units, export workflows, and scripting best practices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mouadja02/skills102026년 10월 22일 업데이트

Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mouadja02/skills102026년 10월 22일 업데이트

Check any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10 agentic risks - Generating a compliance report for security review or audit - Comparing agent framework security features against the standard - Any request like "is my agent OWASP compliant?", "check ASI compliance", or "agentic security audit"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mouadja02/skills102026년 10월 22일 업데이트

mouadja02의 스킬 모두 보기

이 스킬의 문제 신고