onboarding-program-builder
Skill14 starsChanged 8 months agoMITView on GitHub
Build role-based ramp plans that help new hires become productive faster through job-critical practice, evidence checkpoints, and manager coaching. Use when the user asks for onboarding plans, 30-60-90 views, competency-based ramp plans, manager check-ins, or diagnostic onboarding checkpoints for sales or customer-facing teams. Route formal pass/fail readiness standards, certification decisions, and assessor calibration to certification-program-builder.
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- account-brief-builderSkill
- battlecard-builderSkill
- call-insights-to-objectionsSkill
- call-review-coachSkill
- case-study-extractorSkill
- certification-program-builderSkill
- content-gap-analysisSkill
- content-governance-systemSkill
- deal-inspection-coachSkill
- discovery-and-demo-structureSkill
- discovery-rubric-auditorSkill
- enablement-house-styleSkill
- enablement-impact-storySkill
- enablement-metrics-and-instrumentationSkill
- enablement-program-designSkill
- enablement-routerSkill
- executive-briefing-builderSkill
- field-feedback-synthesizerSkill
- forecast-risk-briefSkill
- manager-coaching-cadenceSkill
- mutual-action-plan-builderSkill
- objection-library-builderSkill
- onboarding-to-value-playbookSkill
- one-pager-and-slide-outlineSkill
- partner-enablement-packageSkill
- pipeline-stage-definition-and-exit-criteriaSkill
- product-launch-enablementSkill
- proposal-rfp-orchestratorSkill
- qbr-ebr-builderSkill
- quarterly-enablement-plannerSkill
- release-notes-to-seller-updatesSkill
- renewal-and-expansion-enablementSkill
- revenue-enablement-contextSkill
- roleplay-scenario-builderSkill
- talk-track-builderSkill
- value-prop-and-positioningSkill
- win-loss-synthesisSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Ask only for the inputs that change the plan:
- Distinctive: line 31
Keep role standards, ramp targets, and capacity unknown until verified.
- Distinctive: line 35
Read references/onboarding-framework.md for phase gates, evidence checkpoints, and the certification boundary.
- Distinctive: line 39
Start from the job, not the catalog.
- Distinctive: line 48
Use feedback and retries before increasing difficulty or independence.
- Very specific: line 54
If a certification exists, show where onboarding gathers evidence for it.
- Very specific: line 55
Leave the standard and the decision to certification-program-builder.
- Very specific: line 72
Do not write customer first-value milestones.
≈ “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 program builder
Help new hires learn, practise, and demonstrate the work their role requires, with support matched to their starting proficiency.
Onboarding teaches the job and collects diagnostic evidence. A pass/fail gate is certification-program-builder. A customer time-to-value journey is onboarding-to-value-playbook.
Performance checkpoint. "Before independent discovery, observe a live call: the rep clarifies the buyer's problem and its impact, then agrees a useful next step. If no live opportunity is available, continue practice and leave the checkpoint pending."
Calendar. "Days 1-30: complete product training. Days 31-60: shadow. Days 61-90: carry a full pipeline."
Each phase should give the hire a useful work task and the manager a clear way to judge what support is needed.
Inputs
Reuse supplied context first. If a missing company fact would change the result, check the relevant sections of .enablement/context.md when available. Preserve source dates and approval limits.
Ask only for the inputs that change the plan:
- Role, segment, and experience mix: new hire, internal transfer, experienced external
- Job-critical tasks, expected outcomes, and costly failure risks
- Target time to supervised and independent work
- Starting-proficiency evidence, if any exists
- Learner, facilitator, SME, and manager capacity
- Whether a formal certification exists that onboarding should prepare for, not score
Keep role standards, ramp targets, and capacity unknown until verified. Missing baseline is unknown ability, not low ability.
Supporting material
Read references/onboarding-framework.md for phase gates, evidence checkpoints, and the certification boundary. Skip it if the user already has competencies and only wants a focused checkpoint revision.
Procedure
- Start from the job, not the catalog. Critical tasks, outcomes, failure risks. Done when each competency is a thing someone does at work.
- Take a short starting baseline. Knowledge check, work sample, roleplay, or observed task. Use it to compress or add support by profile.
- Gate phases on evidence, not dates. Foundation, supervised application, independent execution. Add a 30-60-90 view only when asked or useful. Dates do not prove progression.
- Map each competency to practice, live-work evidence, and a manager check. Done when this week's proof is observable without a quiz score.
- Space learning, practice, application, and review across realistic work opportunities. Use feedback and retries before increasing difficulty or independence. Where live work is unavailable, use a representative simulation and state which evidence still needs to come from live work.
- Build a capacity ledger first.
Learners, facilitators, SMEs, managers, systems, timezones. Return
fits,reduce,sequence, orblockedbefore assigning work that overflows. - Give managers checks they can actually run. Lightweight, scheduled inside available coaching time.
- Name ramp-risk triggers and the evidence that returns someone to the path.
- If a certification exists, show where onboarding gathers evidence for it.
Leave the standard and the decision to
certification-program-builder.
LMS completion is not proof of readiness. Style, confidence, and familiarity are not competence.
What to return
For a new ramp, include the items below. For one phase or learner profile, revise that part and its dependencies:
- Outcome-gated ramp, with 30-60-90 only when requested or useful
- Adjustments for the learner profiles actually in scope
- Job-task, competency, practice, and evidence map
- Manager checkpoints tied to practice, application opportunities, and required evidence
- Diagnostic tracker that does not pass or fail
- Ramp-risk triggers and the return-to-path evidence
- Certification handoff when a formal gate is in scope
- Capacity ledger and
fits/reduce/sequence/blocked
Do not write customer first-value milestones. That is onboarding-to-value-playbook.
Quality bar
- Each phase includes observable work and a realistic opportunity for manager feedback.
- 30-60-90 is a calendar view, not a readiness gate.
- Experience variants change practice and support, not slogans.
- Manager checks fit real coaching time.
- Diagnostic evidence stays separate from any certification decision.
- The plan prepares the hire for job tasks and identifies any separate certification requirements.
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.

