agentleFS
prosyo-aiprosyo-ai/gtm-skill/skills/mutual-action-plan/SKILL.md

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

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
  1. Distinctive:

    Use this once a buyer agrees the problem is worth solving.

    line 16
  2. Distinctive:

    Start from the date the buyer needs results, not your quarter end.

    line 27
  3. Distinctive:

    Every step has a named owner (buyer or seller side) and a date.

    line 33
  4. Distinctive:

    Update status, move dates honestly, and raise slips early.

    line 42
  5. Distinctive:

    MUST anchor dates on the buyer's goal.

    line 57
  6. Distinctive:

    MUST name an owner for every step.

    line 58
  7. Distinctive:

    NEVER invent deadlines or artificial urgency in the plan.

    line 59

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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."

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.