mutual-action-plan
Skill13 starsChanged 23 days agoMITView on GitHub
Use this skill when a B2B deal needs a shared plan to get from evaluation to signature and go-live: \"build a mutual action plan\", \"close plan for this deal\", \"what are the steps to sign\", \"deal keeps slipping\". Works backwards from the buyer's go-live date, lists every step on both sides (evaluation, security, legal, procurement, approvals, onboarding) with owners and dates, flags the critical path, and writes the email that introduces the plan to the champion as a tool to help them, not to pressure them.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- CSPulse/customer-success-skillstheir own version, first seen Nov 8, 2026
- jacobtop-tcg/sales-engineering-skillstheir own version, first seen Nov 8, 2026
- zime-ai/zime-gtm-skillstheir own version, first seen Nov 1, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- zime-ai/zime-gtm-skills★ 19same name
- CSPulse/customer-success-skills★ 2same name
- jacobtop-tcg/sales-engineering-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository77 other files it gives its agents.
- AGENTS.mdAGENTS.md
- abm-account-planSkill
- account-research-briefSkill
- account-tieringSkill
- aeo-answer-optimizerSkill
- breakup-emailSkill
- buyer-persona-builderSkill
- buying-committee-mapperSkill
- buying-signal-scoringSkill
- call-coaching-scorecardSkill
- campaign-performance-analyzerSkill
- case-study-writerSkill
- churn-win-backSkill
- closed-lost-reactivationSkill
- cold-call-scriptSkill
- cold-email-sequenceSkill
- cold-email-writerSkill
- comparison-page-writerSkill
- competitive-battlecardSkill
- competitor-teardownSkill
- crm-hygiene-auditSkill
- customer-interview-guideSkill
- deal-qualificationSkill
- deliverability-auditSkill
- discovery-call-prepSkill
- domain-warmup-planSkill
- email-authentication-setupSkill
- email-copy-reviewSkill
- event-follow-upSkill
- expansion-opportunity-finderSkill
- first-line-personalizationSkill
- follow-up-email-writerSkill
- funding-signal-outreachSkill
- gtm-global-rulesSkill
- hiring-signal-outreachSkill
- icp-builderSkill
- job-change-playsSkill
- lead-list-builderSkill
- lead-magnet-builderSkill
- lead-scoring-modelSkill
- linkedin-comment-strategySkill
- linkedin-connection-noteSkill
- linkedin-message-sequenceSkill
- linkedin-post-writerSkill
- linkedin-profile-optimizerSkill
- list-cleaningSkill
- lookalike-account-finderSkill
- meeting-booking-replySkill
- messaging-matrixSkill
- multichannel-cadenceSkill
- negotiation-playbookSkill
- no-show-recoverySkill
- objection-handlerSkill
- outbound-ab-testSkill
- outbound-mathSkill
- outreach-compliance-checkSkill
- pipeline-reviewSkill
- post-engagement-outreachSkill
- proposal-follow-upSkill
- prospect-research-briefSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Use this once a buyer agrees the problem is worth solving.
- Distinctive: line 27
Start from the date the buyer needs results, not your quarter end.
- Distinctive: line 33
Every step has a named owner (buyer or seller side) and a date.
- Distinctive: line 42
Update status, move dates honestly, and raise slips early.
- Distinctive: line 57
MUST anchor dates on the buyer's goal.
- Distinctive: line 58
MUST name an owner for every step.
- Distinctive: line 59
NEVER invent deadlines or artificial urgency in the plan.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Use this once a buyer agrees the problem is worth solving. A shared plan turns "we'll get back to you" into dated steps both sides own, and shows early whether the close date is real.
Inputs
- The buyer's target date for value (go-live, a launch, a quarter start) and why it matters.
- What is known about their decision and paper process.
- Stakeholders on both sides.
The play
1. Anchor on their date
Start from the date the buyer needs results, not your quarter end. "To have reps using it by 1 March, onboarding starts 1 February, so signature by 25 January."
2. List every step, both sides
Evaluation, stakeholder meetings, technical review, security questionnaire, legal review, procurement and vendor setup, budget approval, signature, kickoff, onboarding milestones. Most slipped deals slip on steps nobody listed. Read references/map-template.md for the template and typical durations.
3. Assign owners and dates
Every step has a named owner (buyer or seller side) and a date. Steps without a buyer-side owner are wishes.
4. Mark the critical path
The longest chain of dependent steps, usually security plus legal plus procurement. Start them in parallel and early.
5. Introduce it as help
Send the plan to the champion as a tool for their internal process: "Here's a draft of what usually needs to happen; what did I miss?" Let them edit it. A plan the buyer has changed is a plan they own.
6. Review it every week
Update status, move dates honestly, and raise slips early.
Champion email
Hi Priya, to hit reps live by 1 March, I sketched the steps that usually need to happen on both sides (attached). Some I've guessed, especially security and procurement at Lumen. Could you fix what's wrong and add anything I missed? Happy to walk through it on Thursday's call.
What good looks like
- The buyer edits the plan, adds steps and owns dates.
- Security, legal and procurement start before the final presentation, not after.
- The plan continues past signature into the first value milestone, which keeps the conversation about outcomes.
- The common mistake is a seller-only checklist sent as an ultimatum the week before quarter end.
Rules
- MUST anchor dates on the buyer's goal.
- MUST name an owner for every step.
- NEVER invent deadlines or artificial urgency in the plan.
Example prompts
- "Build a mutual action plan for our $60k deal with Lumen; they want reps live by 1 March."
- "This deal keeps slipping. Turn my notes into a close plan with the critical path."
- "Write the email that introduces the plan to our champion."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

