traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "Entrepreneurial Operating System", or "business operating system". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.
What this skill does
# 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.** EOS provides a simple, complete operating system that strengthens the Six Key Components of any organization.
**The foundation:** Great vision without traction is hallucination. Traction without vision is aimless. EOS connects the two through a practical, weekly operating rhythm.
## Scoring
**Goal: 10/10.** When evaluating or implementing business processes, rate 0-10 based on EOS component strength. A 10/10 means all six components are strong, meetings are productive, and quarterly rocks are consistently achieved; lower scores indicate gaps. Always provide current score and improvements to reach 10/10.
## The Six Key Components
```
Vision → People → Data → Issues → Process → Traction
```
Every business is built on these six components. EOS strengthens all six.
### 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)**
The 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 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 | The most important things to accomplish in 90 days |
| **Issues List** | All unresolved obstacles | Problems, ideas, opportunities to discuss |
**Process:**
1. Leadership team completes V/TO together (2-day off-site)
2. Share with entire organization
3. Review quarterly
4. Update annually
**Key insight:** If leadership team can't agree on V/TO, you have a bigger problem. Alignment comes first.
See: [references/vto.md](references/vto.md) for V/TO templates and exercises.
### 2. People Component
**Question:** Do you have the right people in the right seats?
**Tool: Accountability Chart**
Not an org chart—an accountability chart. Defines the structure and who owns what.
**Structure:**
```
Visionary ←→ Integrator
├── Sales/Marketing
├── Operations
└── Finance
```
**Two key roles:**
- **Visionary:** Big ideas, culture, key relationships, creative problem solving
- **Integrator:** Runs business day-to-day, manages team, executes vision, resolves conflicts
**Rule:** One person per seat. No shared accountability.
**Tool: People Analyzer**
Evaluate every person on two dimensions:
**1. Right Person (core values fit)**
| Core Value | + (most of the time) | +/- (sometimes) | - (rarely) |
|-----------|---------------------|-----------------|------------|
| Own it | + | | |
| Do the right thing | | +/- | |
| Grow or die | + | | |
**Standard:** Must be "+" on all core values. One "+/-" is a conversation. Any "-" is wrong person.
**2. Right Seat (GWC)**
- **G**et it: Understands the role
- **W**ant it: Genuinely wants the role
- **C**apacity: Has the mental, physical, emotional capacity
**Must be "yes" on all three.** If missing any one, wrong seat.
**The formula:** Right People + Right Seats = A-players
**People decisions:**
- Right person, right seat → Keep and invest in
- Right person, wrong seat → Move to right seat
- Wrong person, right seat → Coaching/exit (hardest call)
- Wrong person, wrong seat → Exit immediately
See: [references/people.md](references/people.md) for accountability chart and people analyzer templates.
### 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.
**Scorecard rules:**
- Activity-based metrics (leading indicators), not results (lagging)
- Weekly numbers (monthly is too slow)
- Every number has an owner
- Every number has a goal
- Red/green: on track or off track
**Example Scorecard:**
| Metric | Owner | Goal | W1 | W2 | W3 | W4 |
|--------|-------|------|----|----|----|----|
| Revenue | Sales Lead | $50K/wk | ✓ | ✓ | ✗ | ✓ |
| New Leads | Marketing | 100/wk | ✓ | ✗ | ✓ | ✓ |
| Demos Completed | Sales | 20/wk | ✗ | ✓ | ✓ | ✓ |
| Customer NPS | Support | >50 | ✓ | ✓ | ✓ | ✓ |
| Cash Balance | Finance | >$200K | ✓ | ✓ | ✓ | ✓ |
**Benefits:**
- Spot problems 2-4 weeks earlier
- Reduce "gut feeling" management
- Create accountability without micromanagement
- Everyone knows the score
**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](references/data.md) for scorecard templates and metric selection.
### 4. Issues Component
**Question:** Are you identifying, discussing, and solving issues quickly?
**Tool: Issues Solving Track (IDS)**
**I**dentify → **D**iscuss → **S**olve
**Step 1: Identify**
- What's the real issue? (Not the symptom)
- Ask "Why?" until you reach root cause
- State the issue in one sentence
**Step 2: Discuss**
- Everyone gets input (not equal time)
- Tangents are stopped
- Focus on the ONE issue
- Time-boxed (usually 5-15 minutes)
**Step 3: Solve**
- Decision is made
- Action items are assigned (who + what + when)
- Move to next issue
**Three types of issues:**
| Type | Examples | Action |
|------|----------|--------|
| **Problems** | Customer churn, team conflict, system outage | IDS → solve |
| **Ideas** | New feature, process change, market opportunity | IDS → decide (yes/no/later) |
| **Obstacles** | Blocking a rock, resource constraint, dependency | IDS → remove or escalate |
**Issues list rules:**
- Everyone can add issues
- Prioritize: most important first
- Not all issues get solved every meeting
- Unsolved issues carry forward
**Common IDS mistakes:**
- Discussing symptoms, not root cause
- Rehashing same issue every week
- No clear action items
- Too much discussion, not enough solving
See: [references/issues.md](references/issues.md) for IDS facilitation guides.
### 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.
**Identify core processes:**
- HR process (hiring, onboarding, reviews)
- Sales process (lead → close)
- Operations process (delivery, fulfillment)
- Customer service process (support → resolution)
- Finance process (invoicing, collections)
**Documentation format:**
1. Name the process
2. List 5-20 major steps
3. Add just enough detail (not a 50-page manual)
4. Make it visual where possible
**Example: Sales Process "The Closer"**
1. Qualify lead (BANT: Budget, Authority, Need, Timeline)
2. Discovery call (30 min, use question guide)
3. Demo (customize to their pain points)
4. Proposal (send 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](references/process.md) for process documentation templates.
### 6. Traction Component
**Question:** Are you executing on your vision every day?
**Two tools: Rocks and Level 10 Meetings**
#### Rocks (Quarterly Priorities)
**Definition:** The 3-7 most important things to accomplish inRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.