onboarding-plan
Skill2 starsChanged 3 months agoMITView on GitHub
Use when the user says "onboarding plan", "just closed a new customer", "kickoff is next week", "first 90 days", "time to first value", "is this customer really live", or names an account that signed recently. Produces a shared plan with a readiness call, success criteria that carry a baseline, dated milestones with owners on both sides, and a watchlist. Not for the sales handover itself (use handoff) or the long-run account plan (use account-plan).
4 other projects use a version of this.
Adopted by
Most recently taken up by
- genspark-ai/genofficetheir own version, first seen Oct 25, 2026
- fworks-tech/agenthoodtheir own version, first seen Sep 28, 2026
- oswarld/notion-skillstheir own version, first seen Sep 23, 2026
- ficilcom/otame4-work-skillstheir own version, first seen Aug 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- genspark-ai/genoffice★ 12ksame name
- oswarld/notion-skills★ 11same name
- ficilcom/otame4-work-skills★ 3same name
- fworks-tech/agenthood★ 3same 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 repository54 other files it gives its agents.
- account-contextSkill
- account-planSkill
- account-reviewSkill
- adoption-planSkill
- advocacy-askSkill
- book-reviewSkill
- book-triageSkill
- business-reviewSkill
- call-prepSkill
- call-recapSkill
- champion-lossSkill
- churn-postmortemSkill
- coachingSkill
- commitmentsSkill
- coverage-modelSkill
- csm-hiringSkill
- csm-rampSkill
- csql-motionSkill
- cs-scorecardSkill
- cs-startSkill
- customer-updateSkill
- day-planSkill
- email-criticSkill
- escalationSkill
- exec-conversationSkill
- expansion-caseSkill
- expansion-scanSkill
- handoffSkill
- hard-conversationSkill
- health-scoreSkill
- internal-askSkill
- invoice-chaseSkill
- mutual-action-planSkill
- nrr-narrativeSkill
- offboardingSkill
- one-pagerSkill
- playbook-builderSkill
- portfolio-reviewSkill
- price-increaseSkill
- renewal-forecastSkill
- renewal-negotiationSkill
- renewal-riskSkill
- renewal-runwaySkill
- sales-handoffSkill
- save-planSkill
- stakeholder-mapSkill
- status-updateSkill
- survey-follow-upSkill
- team-rollupSkill
- usage-emailSkill
- value-ledgerSkill
- voice-of-customerSkill
- what-do-i-oweSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 13
If the user gave the account, what was sold, and who bought it, go straight to "Do this".
- Distinctive: line 26
Audit the handover for what is missing: Check six items: business objective, deal context, stakeholders including sceptics, open risks, …
- Distinctive: line 31
Confirm the criteria in writing the same day: No written yes means no agreement.
- Distinctive: line 35
Use this skeleton. Keep it shareable with the customer, minus the watchlist.
- Distinctive: line 66
Unwritten promises become scope disputes in month three: Write each one down now, even the roadmap hints.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Onboarding Plan
A plan the customer can point to later: what value means for them, who owns each step, and what would tell you in week three that the year is going badly.
Start here
If the user gave the account, what was sold, and who bought it, go straight to "Do this".
Otherwise ask for these in ONE message, then proceed with whatever comes back:
- What was sold, the signature date, and the contract value
- Who signed, who will use it, and the problem the customer said they were solving
- What sales promised that may not be in the contract
Handover notes, the contract scope or a stakeholder list are a bonus. If an "Account context" block exists in the conversation, use it for segment and value metric.
Do this
- Define value per customer before kickoff. One sentence in their words, with a baseline, a target, a date and a named person on their side who owns the number. If they cannot state a baseline, making the baseline the first criterion is the plan.
- Audit the handover for what is missing. Check six items: business objective, deal context, stakeholders including sceptics, open risks, every promise made in the sale, and the customer's own responsibilities. Each gap becomes a line in the plan.
- Validate, do not re-interrogate. Draft the opener as "here is what we understand from your talks with sales, what would you change". Ask only operational questions: who approves change, the real integrations, whether the champion has changed.
- Separate first value from full value. First value is the first result they care about, not finished configuration. Date five milestones: kickoff (a common default is within 14 days of signature), technical live, training, first go-live, and an ROI review tied to the original goals. Book the first cadence call within 30 days (a common default, set your own).
- Name customer owners with hours per week. "The exec will handle it" is not an owner. Add the one early win achievable in week one or two.
- Write the watchlist for weeks 1 to 4, using the signals in Rules, and warn the customer about the post-go-live dip.
- Confirm the criteria in writing the same day. No written yes means no agreement.
Output
Use this skeleton. Keep it shareable with the customer, minus the watchlist.
ONBOARDING PLAN: [Account] | [value] | signed [date] | kickoff by [date]
Call: READY TO KICK OFF / FIX THESE FIRST
Biggest risk: [one line]
Value in their words: [one sentence]
Success criteria
| Measure | Baseline | Target | By | Owner (theirs) | Tag |
Milestones
| Milestone | Date | Their owner | Our owner | Depends on |
Customer commitments: [name, hours per week, what]
Sold but not in scope: [promise, who made it, how to resolve]
Watchlist, weeks 1 to 4: [signal, threshold, action]
What I could not check
- [gap, marked (assumed, confirm) inline]A filled example is in examples/sample.md. Match its length and tone.
Rules
- Done means the customer can walk you through a result. Go-live is a vendor event, adoption is a customer state, and the renewal is judged on the second.
- A target without a baseline cannot be falsified. At renewal nobody can prove it moved, so the argument for renewing is opinion.
- Diagnose a refusal to commit. Cannot articulate means no baseline exists (build one). Lacks authority is a sponsor problem (get 20 minutes with the budget holder). Hedging means a sponsor who will not say what good looks like will not defend the spend.
- Fallback ladder when no outcome metric exists: a leading metric with a baseline, then a named workflow live in production by a date, then a named person who will say it worked. Never close a plan with none.
- Unwritten promises become scope disputes in month three. Write each one down now, even the roadmap hints.
- Sceptics belong on the stakeholder list. They are the people most often left out and most often the ones who kill the renewal.
- Plan the security and IT review. Planned, it runs days. Found after kickoff, it is unbounded.
- Perceived momentum outranks green metrics. A customer who feels nothing is moving carries that feeling into renewal. Early warning signs: kickoff slips, sponsor skips it, shrinking attendance, environment provisioned and never used, blockers that age.
Related (only if installed)
handoff if the sales transfer is the problem. account-plan when the first 90 days end. stakeholder-map for the sceptics.
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.

