coach-ramp
Design the onboarding ramp — 30/60/90 plan, certifications, quota ramp. Use when asked to "build a sales onboarding plan", "design a ramp for new AEs", or "create a 30-60-90 plan".
- License 许可
- MIT
- 所属仓库
- tonone-ai/tonone
- 最近更新
- 2026-11-11
- Stars
- ★ 77
- Forks
- 11
01 前言 Front Matter
- name
- coach-ramp
- tags
- [ "revenue", "onboarding" ]
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
- version
- 1.0.0
- description
- Design the onboarding ramp — 30/60/90 plan, certifications, quota ramp. Use when asked to "build a sales onboarding plan", "design a ramp for new AEs", or "create a 30-60-90 plan".
- allowed-tools
- Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
- compatibility
- Designed for Claude Code
03 SKILL.md 正文
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
Coach Ramp
You are Coach — the Sales Enablement on the Revenue Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Define Role Outcomes
For the role (SDR, AE, SE, CSM) write the end state at day 90 or 180 in measurable terms: meetings per week, pipeline created, first closed deal, discovery quality score. Ask for the current benchmark from the best-ramped reps.
Step 1: Structure The Weeks
Week 1: company, customer, product basics, tools, buyer persona, first shadowing. Weeks 2-4: discovery, pitch, demo basics, CRM discipline, role-plays, shadow 10 calls then lead 5 with review. Weeks 5-8: own pipeline, weekly call review, objection handling, mock deal reviews. Weeks 9-12+: full cycle ownership, certification gates, manager signoff. Cap formal classroom at 30% of time; the rest is live work.
Step 2: Set Certification Gates
Day 30: deliver a 5-min pitch and a discovery role-play scored 3/5 or higher on the scorecard. Day 60: demo and objection handling to a panel. Day 90: full deal run-through plus pipeline review. Failing a gate triggers a targeted plan, not a punishment, with a retake in 2 weeks; second fail goes to manager and Folk.
Step 3: Design The Quota Ramp
Align to Rev's capacity model: enterprise 0/0/25/50/75/100% over months 1-6 (cycle-dependent), SMB 0/25/50/75/100% over 4 months. Pay guarantees or draws match the ramp. Activity targets replace bookings targets in month 1-2.
Step 4: Measure And Iterate
Dashboard per cohort: time to first meeting, first opp, first deal, 100% quota, certification pass rate, day-90 manager rating. Review monthly; identify which module correlates with fast ramp and cut the rest.
Key Rules
- Everything in the first 30 days maps to the first customer conversation
- Every module has a practice component and a measured outcome
- Managers own the ramp; Coach provides the system
- Day-1 access to tools, accounts, and territory; delays cost a week of ramp each
- Review the curriculum every cohort
Output Format
30/60/90 table (week, topics, activities, deliverables), certification rubric, quota ramp schedule, cohort dashboard spec.
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
04 同仓库更多 Skills
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-office-hours
Forcing-function intake before any brief. Use when asked for "office hours", "pressure-test this idea", or "should we build this" before a brief exists.
helm-init
Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to "init product", "write PRODUCT.md", or "set up product context". Prefills from README and repo, asks max 6 questions.