Build a customer success plan around desired outcomes, adoption signals, risks, stakeholder alignment, and next-best actions.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add Dadmin88/hermes-profile-packs --skill customer-success-plan --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Customer Success Plan?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dadmin88-customer-success-plan)More formats (shields.io, HTML) on the badges page.
---
name: customer-success-plan
description: Build a customer success plan around desired outcomes, adoption signals, risks, stakeholder alignment, and next-best actions.
---
# Customer Success Plan
Use when a customer or user group needs structured guidance toward measurable value from the product.
## Procedure
1. Define the customer's desired outcome in their terms, not just product usage metrics.
2. Identify current state, stakeholders, adoption level, blockers, and dependencies.
3. Map product capabilities to the customer's goals and separate must-have adoption from optional expansion.
4. Define success indicators, milestones, and leading risk signals.
5. Prioritize the next few actions with owners and dates where appropriate.
6. Capture product gaps, support issues, and training needs for the correct internal owners.
7. Revisit the plan based on achieved outcomes rather than activity volume.
## Quality gate
A success plan must connect actions to customer outcomes. Avoid treating logins, meetings, or feature usage as success without evidence that they advance the customer's goal.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
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', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling