정보
이 스킬은 성장 중인 기업이 비전과 실행을 일치시키고 반복되는 조직 문제를 해결할 수 있도록 기업 운영 체계(EOS) 프레임워크를 구현합니다. 목표 설정, 회의 운영, 책임 관리에 대한 체계적인 도구를 제공하며, EOS의 여섯 가지 구성 요소인 비전, 인재, 데이터, 문제점, 프로세스, 실행력을 다룹니다. 분기별 계획 수립, 레벨 10 회의 진행, 운영상의 혼란 해결을 위한 체계적인 프레임워크가 필요할 때 사용하세요.
빠른 설치
Claude Code
추천npx skills add wondelai/skills -a claude-code/plugin add https://github.com/wondelai/skillsgit clone https://github.com/wondelai/skills.git ~/.claude/skills/traction-eosClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
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:
| Question | What It Defines | Example |
|---|---|---|
| Core Values | 3-7 non-negotiable beliefs | "Own it", "Do the right thing", "Grow or die" |
| Core Focus | Purpose/cause/passion + niche | "Simplify small business" + "Cloud accounting" |
| 10-Year Target | Big, hairy, audacious goal | "$100M revenue" or "10,000 customers" |
| Marketing Strategy | Target market, 3 uniques, proven process, guarantee | Who you serve, why you're different |
| 3-Year Picture | What the company looks like in 3 years | Revenue, profit, headcount, key metrics |
| 1-Year Plan | Revenue, profit, measurables, goals | Specific targets for this year |
| Quarterly Rocks | 3-7 priorities for this quarter | Most important things in 90 days |
| Issues List | All unresolved obstacles | Problems, 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:
- Right Person (core values fit): Rate +, +/-, or - on each core value. Must be "+" on all; one "+/-" is a conversation; any "-" means wrong person.
- 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:
| Metric | Owner | Goal | W1 | W2 | W3 | W4 |
|---|---|---|---|---|---|---|
| Revenue | Sales Lead | $50K/wk | ✓ | ✓ | ✗ | ✓ |
| New Leads | Marketing | 100/wk | ✓ | ✗ | ✓ | ✓ |
| Cash Balance | Finance | >$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:
- Identify: Ask "Why?" until you reach the root cause (not the symptom); state the issue in one sentence
- Discuss: Everyone gets input (not equal time); stop tangents; one issue at a time, time-boxed 5-15 minutes
- Solve: Make the decision, assign action items (who + what + when), move on
Three types of issues:
| Type | Examples | Action |
|---|---|---|
| Problems | Customer churn, team conflict, outage | IDS → solve |
| Ideas | New feature, process change, opportunity | IDS → decide (yes/no/later) |
| Obstacles | Blocked rock, resource constraint | IDS → 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"
- Qualify lead (BANT: Budget, Authority, Need, Timeline)
- Discovery call (30 min, question guide)
- Demo (customized to their pain points)
- Proposal (within 24 hours)
- Follow up (3 touches in 7 days)
- 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:
- Review the V/TO (vision, 3-year, 1-year)
- Brainstorm what must get done this quarter to stay on track
- Narrow to 3-7 company rocks, one owner each
- Each leadership member also sets 3-7 individual rocks
- 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.
| Time | Section | Purpose |
|---|---|---|
| 5 min | Segue | Good news, personal and professional |
| 5 min | Scorecard | Review weekly numbers |
| 5 min | Rock Review | On track / off track per rock |
| 5 min | Headlines | Customer/employee quick updates |
| 5 min | To-Do List | Last week's to-dos: done or not done |
| 60 min | IDS | Identify, Discuss, Solve issues |
| 5 min | Conclude | Recap 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.
| Phase | Timeline | Focus |
|---|---|---|
| Focus Day | Day 1 (8 hours) | Accountability chart, rocks, scorecard, Level 10 |
| Vision Building Day 1 | Month 1 | V/TO: core values, core focus, 10-year target |
| Vision Building Day 2 | Month 2 | V/TO: marketing strategy, 3-year, 1-year, rocks |
| Quarterly Sessions | Every 90 days | Review rocks, set new rocks, IDS major issues |
| Annual Planning | Yearly | Full 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:
| Component | Statement | Score (1-5) |
|---|---|---|
| Vision | Leadership team agrees on where we're going and how to get there | |
| People | We have the right people in the right seats | |
| Data | We manage from a weekly scorecard of 5-15 numbers | |
| Issues | We solve issues quickly and permanently | |
| Process | Core processes are documented and followed by all | |
| Traction | We 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
| Mistake | Why It Fails | Fix |
|---|---|---|
| Skipping Level 10s | Weekly rhythm lost, issues pile up | Protect the meeting, never cancel |
| No scorecard | Managing by gut, constant surprises | Choose 5-15 weekly numbers |
| Wrong people kept | Drags the entire team down | People Analyzer, make the tough calls |
| V/TO not shared | Team doesn't know the vision | Share 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
| Question | If No | Action |
|---|---|---|
| Does leadership agree on vision? | Misalignment | Complete the V/TO together |
| Right people in right seats? | Performance issues | People Analyzer on all seats |
| Managing from data weekly? | Reactive management | Build a weekly scorecard |
| Issues solved permanently? | Same problems repeat | IDS in Level 10s |
| Core processes documented? | Inconsistency | Document the top 5 processes |
| 90-day priorities set and tracked? | No traction | Set quarterly rocks |
Further Reading
For the complete system:
- "Traction: Get a Grip on Your Business" by Gino Wickman
- "Get a Grip" by Gino Wickman & Mike Paton (EOS as a business fable)
- "Rocket Fuel" by Gino Wickman & Mark C. Winters (Visionary + Integrator relationship)
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.
GitHub 저장소
자주 묻는 질문
traction-eos Skill이란 무엇인가요?
traction-eos은(는) wondelai이(가) 만든 Claude Skill입니다. Skill은 Claude가 필요할 때 불러오는 지침과 리소스를 묶어 추가 프롬프트 없이 traction-eos 관련 작업을 수행할 수 있게 합니다.
traction-eos은(는) 어떻게 설치하나요?
이 페이지의 설치 명령을 사용하세요. traction-eos을(를) Claude Code 플러그인으로 추가하거나 저장소를 skills 디렉터리에 복제한 다음 Claude를 다시 시작해 Skill을 불러옵니다.
traction-eos은(는) 어떤 카테고리에 속하나요?
traction-eos은(는) 디자인 카테고리에 속합니다.
traction-eos은(는) 무료로 사용할 수 있나요?
네. traction-eos은(는) AIMCP에 등록되어 있으며 무료로 설치할 수 있습니다.
연관 스킬
executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
