# Traction EOS

> Entrepreneurial Operating System for running a business — an AI agent skill based on *Traction* by Gino Wickman.

Published 2026-02-19 · Updated 2026-08-17 · Team & Operations · Free and MIT-licensed
Canonical: https://skills.wondel.ai/skills/traction-eos/
Source: https://github.com/wondelai/skills/tree/main/traction-eos

**Install:** `npx skills add wondelai/skills/traction-eos --global`

## What is the Traction EOS skill?

Traction EOS is the Entrepreneurial Operating System from Gino Wickman’s Traction, rebuilt as a free skill your AI agent runs. It writes the Vision/Traction Organizer, sets three to seven quarterly Rocks with a single owner each, designs a weekly scorecard of leading numbers, and structures a Level 10 meeting that ends in decisions.

## Key concepts from Traction your agent applies

- **Vision/Traction Organizer (V/TO)** — Align your entire organization with a shared vision, 10-year target, 3-year picture, and 1-year plan.
- **Rocks (90-Day Priorities)** — Set 3-7 quarterly priorities for the company and each leader — the most important things to accomplish.
- **The Accountability Chart** — Define clear seats with roles and responsibilities — Right People in the Right Seats.
- **Scorecard & Measurables** — Track 5-15 weekly metrics that give you a pulse on the business without waiting for financials.
- **Level 10 Meetings** — Run weekly 90-minute meetings with a strict agenda: scorecard review, rock review, IDS (Identify, Discuss, Solve).

## When to use Traction EOS — and when not to

Reach for it when:

- The leadership meeting is ninety minutes of status updates, and the same three issues resurface every month.
- Quarterly priorities exist on a slide, but nobody can say who owns each one or what done means.
- Two people each assume the other owns hiring, and the org chart does not settle it.
- You only find out how the month went when the accountant closes the books three weeks later.

Reach for something else when:

- You don’t yet know what you are executing toward — Good Strategy Bad Strategy supplies the diagnosis first.
- The bottleneck is how you personally spend your hours — High Output Management is about managerial leverage.
- Handoffs between teams eat more calendar time than the actual work — Team Topologies reshapes those boundaries.
- You are three people still hunting for product-market fit — Lean Startup fits that stage far better.

## About Gino Wickman

Creator of EOS, founder of EOS Worldwide. Gino Wickman is an entrepreneur, author, and creator of the Entrepreneurial Operating System (EOS). He has helped thousands of leadership teams implement EOS through his company EOS Worldwide.
The book: https://openlibrary.org/books/OL25351393M/Traction

## Example prompts

- Create a V/TO (Vision/Traction Organizer) for my startup using traction-eos skill _(Strategic planning)_
- Set quarterly Rocks for my leadership team using traction-eos skill _(Goal setting)_
- Design a weekly Scorecard with the right measurables using traction-eos skill _(Metrics)_
- Build a Level 10 Meeting agenda template for our team using traction-eos skill _(Meeting design)_

## Frequently asked questions

### How do I install the Traction EOS skill?

Run `npx skills add wondelai/skills/traction-eos --global`. It takes about 30 seconds and needs no account. The Traction EOS skill then works in Claude, Claude Code, Claude Cowork, Codex, Cursor, OpenClaw and Hermes Agent — anything that reads the open agentskills.io format — and your agent loads it on its own when a task calls for it. It is free and MIT-licensed, and the source is at https://github.com/wondelai/skills.

### Which book is the Traction EOS skill based on?

It packages *Traction* by Gino Wickman — creator of EOS, founder of EOS Worldwide. The skill distils the book's method into instructions your agent follows while it works, covering vision/traction organizer (v/to), rocks (90-day priorities) and the accountability chart. It sits in the Team & Operations part of the library.

### What actually happens in a Level 10 Meeting?

Same day, same time, ninety minutes, same agenda every week: a short segue, the scorecard, the Rock review, headlines about customers and staff, the to-do list from last week — then roughly sixty minutes of IDS, Identify, Discuss, Solve. Everything before IDS is a scan for what is off track. The meeting closes with everyone rating it out of ten, which is where the name comes from and how the format keeps itself honest.

### How is this different from the High Output Management skill?

EOS is a system you install; Grove teaches a craft you practise. EOS is deliberately prescriptive and company-wide — fixed artifacts, fixed cadence, one right way to run the week — and it was written for owner-led small and mid-sized businesses. High Output Management gives an individual manager judgement: where their hours have leverage, how deep to monitor delegated work, what a 1:1 is for. Many teams run both, at different altitudes.

### Do I still need the book?

The skill will generate every artifact — V/TO, accountability chart, scorecard, Rocks, meeting agenda — so you can start without it. The book’s contribution is the reasoning behind the numbers: why ninety days, why no more than seven Rocks, why five to fifteen measurables, and what happens socially when you tell a long-serving executive their seat is being redefined. That last part is most of the difficulty in practice.

### Where does EOS fall short?

It is rigid on purpose, and the rigidity is the whole benefit — which means it does nothing at all unless the leadership team actually holds the cadence for a couple of quarters. It is also an operating system, not a strategy: the V/TO will cascade a mediocre direction with total fidelity. And an agent can draft your Rocks, but it cannot run the room in a quarterly session where people disagree.

## Related

- All Team & Operations skills: https://skills.wondel.ai/skills/team/
- Drive Motivation: https://skills.wondel.ai/skills/drive-motivation/
- High Output Management: https://skills.wondel.ai/skills/high-output-management/
- Team Topologies: https://skills.wondel.ai/skills/team-topologies/