MCP HubMCP Hub
SKILL·2D8B4D

traction-eos

wondelai
Mis à jour 20 days ago
6 vues
2,065
213
2,065
Voir sur GitHub
Designdesigndata

À propos

Cette compétence de Claude met en œuvre le cadre Entrepreneurial Operating System (EOS) pour aider les entreprises en croissance à aligner leur vision avec l'exécution et à résoudre les problèmes organisationnels récurrents. Elle fournit des outils structurés pour la fixation d'objectifs, la tenue de réunions et la responsabilisation, couvrant les six composantes de l'EOS : Vision, Personnes, Données, Problèmes, Processus et Traction. Utilisez-la lorsque les développeurs doivent remédier au chaos organisationnel, établir des rythmes de réunions ou mettre en œuvre des cadres systématiques de résolution de problèmes.

Installation rapide

Claude Code

Recommandé
Principal
npx skills add wondelai/skills -a claude-code
Commande PluginAlternatif
/plugin add https://github.com/wondelai/skills
Git CloneAlternatif
git clone https://github.com/wondelai/skills.git ~/.claude/skills/traction-eos

Copiez et collez cette commande dans Claude Code pour installer cette compétence

Documentation

Entrepreneurial Operating System (EOS)

A complete system for running a business with six key components. Designed for entrepreneurial companies ($2M-$50M revenue, 10-250 employees) that want to align vision and execution.

Core Principle

Most businesses suffer from the same core issues: people, vision, traction. Great vision without traction is hallucination; traction without vision is aimless. EOS connects the two through a practical weekly operating rhythm that strengthens the Six Key Components of any organization.

Scoring

Goal: 10/10. Score the business by how many of the six Quick Diagnostic rows pass (each component is either in place or not), mapped to the bands below. Bands: 9-10 = all six diagnostic rows pass and rocks consistently hit 80%+ completion; 7-8 = five rows pass, one component weak; 5-6 = three to four rows pass; 3-4 = one to two rows pass; <=2 = no operating rhythm in place. Always state the current score, the failing diagnostic rows, and the next action for each.

The Six Key Components

Vision → People → Data → Issues → Process → Traction

1. Vision Component

Question: Does everyone in the organization know where you're going and how you plan to get there?

Tool: Vision/Traction Organizer (V/TO) — answers eight questions on two pages:

QuestionWhat It DefinesExample
Core Values3-7 non-negotiable beliefs"Own it", "Do the right thing", "Grow or die"
Core FocusPurpose/cause/passion + niche"Simplify small business" + "Cloud accounting"
10-Year TargetBig, hairy, audacious goal"$100M revenue" or "10,000 customers"
Marketing StrategyTarget market, 3 uniques, proven process, guaranteeWho you serve, why you're different
3-Year PictureWhat the company looks like in 3 yearsRevenue, profit, headcount, key metrics
1-Year PlanRevenue, profit, measurables, goalsSpecific targets for this year
Quarterly Rocks3-7 priorities for this quarterMost important things in 90 days
Issues ListAll unresolved obstaclesProblems, ideas, opportunities

Process: Leadership completes the V/TO together (2-day off-site), shares it with the entire organization, reviews quarterly, updates annually.

Key insight: If the leadership team can't agree on the V/TO, you have a bigger problem — alignment comes first.

See references/vto.md when filling in the V/TO — the eight-question template and the off-site exercise sequence.

2. People Component

Question: Do you have the right people in the right seats?

Tool: Accountability Chart — not an org chart; it defines the structure and who owns what.

Visionary ←→ Integrator
              ├── Sales/Marketing
              ├── Operations
              └── Finance
  • Visionary: Big ideas, culture, key relationships, creative problem solving
  • Integrator: Runs the business day-to-day, manages the team, executes the vision
  • Rule: One person per seat — shared accountability is no accountability

Tool: People Analyzer — evaluate every person on two dimensions:

  1. Right Person (core values fit): Rate +, +/-, or - on each core value. Must be "+" on all; one "+/-" is a conversation; any "-" means wrong person.
  2. Right Seat (GWC): Gets it (understands the role), Wants it (genuinely), Capacity (mental, physical, emotional). Must be "yes" on all three.

People decisions:

  • Right person, right seat → keep and invest in
  • Right person, wrong seat → move to the right seat
  • Wrong person, right seat → coach or exit (hardest call)
  • Wrong person, wrong seat → exit immediately

See references/people.md when building the accountability chart or running People Analyzer — templates plus GWC scoring guidance.

3. Data Component

Question: Are you managing based on objective data, or subjective opinions?

Tool: Scorecard — a weekly report card of 5-15 numbers that tell you how the business is doing. Weekly data spots problems 2-4 weeks earlier than monthly and replaces gut-feel management with accountability.

Scorecard rules:

  • Activity-based metrics (leading indicators), not results (lagging)
  • Weekly numbers — monthly is too slow to react
  • Every number has an owner and a goal
  • Red/green: on track or off track

Example:

MetricOwnerGoalW1W2W3W4
RevenueSales Lead$50K/wk
New LeadsMarketing100/wk
Cash BalanceFinance>$200K

Metric selection: If you had to go on vacation for 4 weeks, what 5-15 numbers would tell you how the business is doing?

See references/data.md when building the scorecard — templates plus how to pick leading-indicator metrics.

4. Issues Component

Question: Are you identifying, discussing, and solving issues quickly?

Tool: Issues Solving Track (IDS)Identify → Discuss → Solve:

  1. Identify: Ask "Why?" until you reach the root cause (not the symptom); state the issue in one sentence
  2. Discuss: Everyone gets input (not equal time); stop tangents; one issue at a time, time-boxed 5-15 minutes
  3. Solve: Make the decision, assign action items (who + what + when), move on

Three types of issues:

TypeExamplesAction
ProblemsCustomer churn, team conflict, outageIDS → solve
IdeasNew feature, process change, opportunityIDS → decide (yes/no/later)
ObstaclesBlocked rock, resource constraintIDS → remove or escalate

Issues list rules: Anyone can add issues; prioritize most important first; unsolved issues carry forward — not everything gets solved each meeting.

Common IDS failures: discussing symptoms instead of root cause, rehashing the same issue weekly, ending without clear action items.

See references/issues.md when facilitating IDS — a Five Whys worked example and tangent-control tactics.

5. Process Component

Question: Have you documented and consistently followed your core processes?

Tool: Core Process Documentation — the 20/80 rule: document 20% of your processes to get 80% consistency.

Core processes to identify: HR (hiring, onboarding, reviews), sales (lead → close), operations (delivery, fulfillment), customer service (support → resolution), finance (invoicing, collections).

Documentation format: Name the process, list 5-20 major steps with just enough detail (not a 50-page manual), make it visual where possible.

Example: Sales Process "The Closer"

  1. Qualify lead (BANT: Budget, Authority, Need, Timeline)
  2. Discovery call (30 min, question guide)
  3. Demo (customized to their pain points)
  4. Proposal (within 24 hours)
  5. Follow up (3 touches in 7 days)
  6. Close or disqualify

Followed By All (FBA): Document it, train on it, measure compliance, update quarterly.

See references/process.md when documenting a core process — full templates and a worked HR/sales/ops example.

6. Traction Component

Question: Are you executing on your vision every day?

Rocks (Quarterly Priorities)

The 3-7 most important things to accomplish in the next 90 days. Ninety days is long enough to achieve something meaningful, short enough to maintain urgency.

Rock-setting process:

  1. Review the V/TO (vision, 3-year, 1-year)
  2. Brainstorm what must get done this quarter to stay on track
  3. Narrow to 3-7 company rocks, one owner each
  4. Each leadership member also sets 3-7 individual rocks
  5. Share with the organization and track weekly

SMART rocks: Specific ("Launch new pricing page", not "improve pricing"), Measurable (clear completion criteria), Achievable in 90 days, Realistic given resources, Time-bound (due end of quarter).

Rock scoring: Done = checked off (no partial credit); not done = carried forward or dropped. Target 80%+ completion. Beware rocks that are just "business as usual" — they don't move the needle.

See references/rocks.md when setting quarterly rocks — the binary done-test, the nine-row mistakes table, and a mid-quarter check-in.

Level 10 Meeting (Weekly Leadership Meeting)

The most important meeting in EOS. Every week, same day, same time, same agenda — 90 minutes, never longer.

TimeSectionPurpose
5 minSegueGood news, personal and professional
5 minScorecardReview weekly numbers
5 minRock ReviewOn track / off track per rock
5 minHeadlinesCustomer/employee quick updates
5 minTo-Do ListLast week's to-dos: done or not done
60 minIDSIdentify, Discuss, Solve issues
5 minConcludeRecap to-dos, rate meeting 1-10

Rules:

  • Starts and ends on time — protecting the rhythm is what makes it work
  • No phones/laptops (except the agenda) — IDS needs full attention
  • IDS gets 60 of 90 minutes — solving issues is the point, updates are not
  • Rate the meeting 1-10 at the end (hence "Level 10"); below 8 means discuss what to improve
  • To-dos are 7-day action items with an owner; done = 100% complete; target 90%+ completion

See references/level-10.md when running or fixing a Level 10 — facilitation script and how to interpret the meeting rating.

EOS Implementation Timeline

Typical rollout: 2 years to full implementation.

PhaseTimelineFocus
Focus DayDay 1 (8 hours)Accountability chart, rocks, scorecard, Level 10
Vision Building Day 1Month 1V/TO: core values, core focus, 10-year target
Vision Building Day 2Month 2V/TO: marketing strategy, 3-year, 1-year, rocks
Quarterly SessionsEvery 90 daysReview rocks, set new rocks, IDS major issues
Annual PlanningYearlyFull V/TO review, 1-year plan, Q1 rocks

Self-implementation (read the book, follow the tools — free, slower) vs. EOS Implementer (certified facilitator — faster, expensive).

See references/implementation.md when planning the rollout — phase-by-phase sequencing and the self-vs-Implementer decision. For examples of how real companies sequenced it, see references/case-studies.md.

Organizational Checkup

Rate the company 1-5 on each statement:

ComponentStatementScore (1-5)
VisionLeadership team agrees on where we're going and how to get there
PeopleWe have the right people in the right seats
DataWe manage from a weekly scorecard of 5-15 numbers
IssuesWe solve issues quickly and permanently
ProcessCore processes are documented and followed by all
TractionWe set and achieve 90-day priorities (rocks)

Scoring: 25-30 strong (fine-tune) | 20-24 good (close gaps) | 15-19 average (significant work) | below 15 weak (consider an EOS Implementer).

Common Mistakes

MistakeWhy It FailsFix
Skipping Level 10sWeekly rhythm lost, issues pile upProtect the meeting, never cancel
No scorecardManaging by gut, constant surprisesChoose 5-15 weekly numbers
Wrong people keptDrags the entire team downPeople Analyzer, make the tough calls
V/TO not sharedTeam doesn't know the visionShare with the entire company

For rock-specific mistakes (too many, too vague, business-as-usual, mid-quarter changes), see references/rocks.md — full nine-row table with fixes.

Quick Diagnostic

QuestionIf NoAction
Does leadership agree on vision?MisalignmentComplete the V/TO together
Right people in right seats?Performance issuesPeople Analyzer on all seats
Managing from data weekly?Reactive managementBuild a weekly scorecard
Issues solved permanently?Same problems repeatIDS in Level 10s
Core processes documented?InconsistencyDocument the top 5 processes
90-day priorities set and tracked?No tractionSet quarterly rocks

Further Reading

For the complete system:

About the Author

Gino Wickman is the creator of EOS and founder of EOS Worldwide, a community of certified Implementers. Traction has sold over 2 million copies, and EOS is used by more than 250,000 companies worldwide. His work focuses on the practical tools entrepreneurial leadership teams need to get real traction.

Dépôt GitHub

wondelai/skills
Chemin: plugins/wondelai-skills/skills/traction-eos
0
agent-skillsai-skillsbusinessclaude-codeclaude-code-marketplaceclaude-code-plugin
FAQ

Questions fréquentes

Qu’est-ce que le Skill traction-eos ?

traction-eos est un Skill Claude créé par wondelai. Un Skill regroupe des instructions et des ressources que Claude charge à la demande pour effectuer des tâches liées à traction-eos sans consigne supplémentaire.

Comment installer traction-eos ?

Utilisez les commandes d’installation de cette page : ajoutez traction-eos à Claude Code comme plugin ou clonez son dépôt dans votre dossier skills, puis redémarrez Claude pour charger le Skill.

À quelle catégorie appartient traction-eos ?

traction-eos appartient à la catégorie Design.

traction-eos est-il gratuit ?

Oui. traction-eos est référencé sur AIMCP et son installation est gratuite.

Compétences associées

executing-plans
Design

Utilisez la compétence executing-plans lorsque vous disposez d'un plan de mise en œuvre complet à exécuter par lots contrôlés avec des points de contrôle de revue. Elle charge et examine le plan de manière critique, puis exécute les tâches par petits lots (3 tâches par défaut) tout en rapportant la progression entre chaque lot pour une revue par l'architecte. Cela garantit une mise en œuvre systématique avec des points de contrôle de qualité intégrés.

Voir la compétence
requesting-code-review
Design

Cette compétence délègue un sous-agent réviseur de code pour analyser les modifications apportées au code par rapport aux exigences avant de poursuivre. Elle doit être utilisée après avoir terminé des tâches, implémenté des fonctionnalités majeures, ou avant une fusion vers la branche principale. La revue aide à détecter précocement les problèmes en comparant l'implémentation actuelle avec le plan initial.

Voir la compétence
connect-mcp-server
Design

Cette compétence fournit un guide complet permettant aux développeurs de connecter des serveurs MCP à Claude Code via les transports HTTP, stdio ou SSE. Elle couvre l'installation, la configuration, l'authentification et la sécurité pour intégrer des services externes tels que GitHub, Notion et des API personnalisées. Utilisez-la lors de la configuration d'intégrations MCP, de la configuration d'outils externes ou du travail avec le Protocole de Contexte de Modèle de Claude.

Voir la compétence
web-cli-teleport
Design

Cette compétence aide les développeurs à choisir entre les interfaces Web et CLI de Claude Code en fonction de l'analyse des tâches, puis permet une téléportation transparente des sessions entre ces environnements. Elle optimise le flux de travail en gérant l'état et le contexte de la session lors du passage entre le web, la CLI ou le mobile. Utilisez-la pour des projets complexes nécessitant différents outils à diverses étapes.

Voir la compétence