From pm-sales
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-sales:account-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produces a structured account plan — the document that separates account managers who grow accounts from those who just service them.
Produces a structured account plan — the document that separates account managers who grow accounts from those who just service them.
Account Manager: [Name] | Period: [Date range]
| Metric | Current | Target (EOY) |
|---|---|---|
| ARR / Revenue | £[amount] | £[target] |
| NPS / Health score | [Score] | [Target] |
| Products in use | [List] | [Expansion targets] |
| Renewal date | [Date] | — |
| Risk level | Low / Medium / High | — |
| Name | Title | Influence | Relationship | Notes |
|---|---|---|---|---|
| [Name] | [Role] | Decision maker / Influencer / User | Strong / Neutral / Weak | [Insight] |
Relationship gaps: [Who we do not have access to that we should] Executive sponsor: [Do we have one? If not — who could become one?]
[2-3 specific reasons this account renews. If the list is short, that is the risk signal.]
| Opportunity | Product | Est. Value | Timeline | Next Action |
|---|---|---|---|---|
| [Opportunity] | [Product] | £[value] | [Q/Year] | [Specific action] |
Whitespace: What products do we have that this account does not use, and why?
| Risk | Likelihood | Impact | Mitigation | Owner |
|---|---|---|---|---|
| [Risk] | H/M/L | H/M/L | [Action] | [Name] |
| Action | Why | Owner | Due |
|---|---|---|---|
| [Specific action] | [Why it matters] | [Name] | [Date] |
Next QBR / EBR: [Date — if no EBR cadence, flag as a risk]
At end of [period]:
npx claudepluginhub mileadev/pm-claude-skills --plugin pm-salesGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
2plugins reuse this skill
First indexed Jul 8, 2026