Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Plan Post Merger Integration

ASecurity

Turn synergies into an owner/date/cost-to-achieve register and a 100-day plan, and price integration cost back into the valuation — so the deal isn't underwritten on flawless integration. Reach for this before signing, not after close.

7 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agents

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill plan-post-merger-integration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Plan Post Merger Integration?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Plan Post Merger Integration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-plan-post-merger-integration/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-plan-post-merger-integration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: plan-post-merger-integration
description: "Turn synergies into an owner/date/cost-to-achieve register and a 100-day plan, and price integration cost back into the valuation — so the deal isn't underwritten on flawless integration. Reach for this before signing, not after close."
---

# Skill: Plan post-merger integration

Integration risk is priced pre-signing or paid post-close (§3 #6).

## Step 1 — Build the synergy register
List every synergy with a named **owner**, a **realization date**, and a **one-time cost to achieve** (§3 #3). Separate cost synergies (higher confidence) from revenue synergies (lower confidence, phased later). An un-owned synergy is a wish — drop it or assign it.

## Step 2 — Estimate dis-synergies and integration cost
Estimate the one-time integration cost, expected dis-synergies (customer/employee attrition, disruption), and the timeline. This number feeds back to the valuation (§3 #6).

## Step 3 — Design the operating model
Decide the integration depth (full absorb / partner / standalone) per function, and the Day-1 readiness list (systems, comms, authority, customer continuity).

## Step 4 — Underwrite retention
Build the retention plan for key people identified in diligence (§3 #7) — the economics, the timing, the risk if they leave. Route package terms to counsel.

## Step 5 — Sequence the 100 days
Sequence the first 100 days across operating model, systems, people, and customers, with owners and dates and the synergy milestones that fall inside the window.

## Output
A synergy register (owner/date/cost-to-achieve), an integration-cost + dis-synergy estimate fed back to valuation, an operating-model decision, a retention plan, and a 100-day plan. See [`../../templates/integration-plan.md`](../../templates/integration-plan.md).

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →