Sign inGet started
Skills / Leadership

Extreme Ownership

Discipline equals freedom.

Extreme Ownership is a combat-proven leadership framework that places total accountability on the leader for everything that happens on their team. Developed by Navy SEAL commanders Jocko Willink and Leif Babin from their experience leading Task Unit Bruiser in the 2006 Battle of Ramadi, it provides a repeatable operating system for accountability, decision-making under pressure, and building autonomous teams. Where other leadership frameworks offer principles, Extreme Ownership delivers a field-tested execution protocol.

By Jocko Willink & Leif Babin · Free
Specimen 01 · Live diagnosisExtreme Ownership
Input

“My engineering team has missed sprint deadlines three releases in a row. The engineers say the product team keeps changing requirements mid-sprint.…”

Diagnosis
Let's cut to it.
Full transcript ↓
Calibrated referenceagent-skills.ai
The gap

Own everything in your domain — no excuses, no blame, no exceptions

Extreme Ownership is built around a single axiom — leaders own everything in their domain — and structured into three layers. The foundational ownership mindset demands that leaders take total accountability for failures without externalizing blame, subordinate ego to mission, and personally believe in the objective before asking their team to execute. The operational core is four Laws of Combat: Cover and Move (teams and departments must support each other, never compete), Simple (plans and orders must be clear enough for the lowest-ranking member to execute), Prioritize and Execute (a five-step decision loop for leaders overwhelmed by simultaneous problems), and Decentralized Command (every leader at every level must understand Commander's Intent well enough to make autonomous decisions). A strategic layer adds deliberate planning through briefs and back-briefs, leading both up and down the chain of command, decisiveness under uncertainty (a 70% solution now beats a 100% solution too late), and the counter-intuitive Discipline Equals Freedom principle — that rigid personal and operational standards create the freedom to act without firefighting.

The problem

Most leaders facing team performance problems spend their energy diagnosing what other people did wrong — the engineer who missed the deadline, the manager who miscommunicated, the executive who shifted direction. This blame cycle produces no improvement, erodes accountability culture, and leaves the leader feeling powerless. Extreme Ownership names this as the fundamental failure: the leader is the one variable they actually control, and until they own that, nothing changes.

The solution

Stop waiting for your team to get better and start owning the conditions that make improvement possible — because on any team, in any organization, the only lever that reliably changes outcomes is the leader taking complete, unconditional accountability for everything in their domain.

You bring
  • A specific leadership failure, team performance problem, or decision you're wrestling with
  • Willingness to examine your own contributions before identifying external causes
  • A completed project, event, or decision to debrief in a structured After Action Review
  • Context on your team's structure, size, current performance, and chain of command
You get
  • An Ownership Diagnostic identifying exactly what you could have done differently — with no blame assigned to external parties
  • A ranked Priority Stack from the Prioritize and Execute loop, with your single #1 action clearly identified and ready to brief
  • A Commander's Intent statement your team can execute against autonomously, without constant escalation
  • A structured After Action Review with every failure attributed to a specific leadership gap — not a personality — and three concrete behavior changes going forward
In action

Watch the methodology work.

Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.

Fig.01The same situation, two ways
Specimens A · B
Specimen AVague
Unaided

“Your team has missed three consecutive sprint deadlines. In the last retrospective, the engineering lead blamed unclear requirements. The product manager blamed slow execution. You spent 45 minutes mediating the argument, left with no decisions made and no accountability assigned, and the same dynamics are set up to repeat next sprint.”

×Vague — nothing concrete to act on.
Specimen BCalibrated
With Extreme Ownership

“You've run an Ownership Diagnostic and identified two specific gaps in your own leadership that created the conditions for failure. You've built a Commander's Intent both teams can operate against without escalating to you. Your Priority Stack gave you one clear #1 to brief this week. Your After Action Review assigned each failure to a specific leadership gap — not a personality — and produced three concrete behavior changes for the next sprint that both teams helped define.”

Specific, grounded, and ends with one clear next step.
Fig.02A real session, unedited
In-app · assistant
Extreme OwnershipClaude
Extreme Ownership
Let's cut to it. Tell me the leadership challenge you're dealing with — and I want to hear it framed as a problem you own, not a problem someone else is creating for you. What's going wrong on your team?
My engineering team has missed sprint deadlines three releases in a row. The engineers say the product team keeps changing requirements mid-sprint. The product team says engineering is just slow. I've been stuck mediating and we keep having the same argument every two weeks.
Before we talk about the engineers or the product team — let's run the Ownership Diagnostic. You're the leader. Everything in your domain is your responsibility. Set aside what the engineers should have done differently and what the product team should have done differently. What could YOU have done differently to prevent this situation? I need your answer, not theirs.
Honestly... I've been letting the product team change requirements mid-sprint without pushing back. And I've never clearly defined what 'done' means at sprint start — I assumed both sides understood it. I've been hoping they'd figure it out.
Good. That's the ownership mindset — and you just identified two root causes that are entirely within your control. Now you're facing multiple problems at once: unclear requirements, slipping deadlines, broken trust between teams. That's the overwhelm state. Law of Combat #3: Prioritize and Execute. Step back from the emotion of this situation. What is the single highest-priority problem — the one that, if resolved, makes everything else easier to address?
Requirements clarity. If requirements are locked at sprint start, engineering knows exactly what they're building and the product team can't keep shifting the target.
That's your #1. Brief your team on that single priority this week — not the full list, just this one. Now let's build the Commander's Intent: a clear, simple rule both teams can operate against without escalating to you every time something changes. It needs to be simple enough that the newest engineer and the newest PM both understand it and can act on it without asking. Draft it in one sentence.
How about: 'Requirements are locked at sprint planning — any change after that requires explicit approval and an agreed timeline adjustment'?
That's it. Simple, clear, and it gives your engineering lead the authority to push back on mid-sprint changes without escalating to you every time. That's Decentralized Command working — you've moved a recurring decision down to the level where it belongs. Now let's run a quick After Action Review on your last failed sprint to extract the full lessons before you brief the team.
Reply to Extreme Ownership
What the skill is doing
01Ownership Diagnostic
02Prioritize and Execute Loop
03Decentralized Command Design
Fig.03The same skill, in the channel you already use
WhatsApp · live
9:41
EOExtreme Ownershiptyping…
Messages are end-to-end encrypted. No one outside of this chat can read them.
Today
My engineering team has missed sprint deadlines three releases in a row. The engineers say the product team keeps changing requirements mid-sprint. Th…9:14✓✓
Tell me the leadership challenge you're dealing with — and I want to hear it framed as a problem you own, not a problem someone el…9:14
What's going wrong on your team?9:15
Message

The same skill, where the work happens.

No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.

Reads the situation, names the pattern, returns one concrete next move.
Delivered in seconds, inside a conversation that already exists.
Specimen · WhatsApp Business API · live
Capabilities

What it does, specifically.

Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.

CapabilityC-01

Ownership Diagnostic

A structured analysis of any leadership failure that begins with one question: what could the leader have done differently? The diagnostic systematically maps all contributing factors — communication gaps, unclear priorities, insufficient planning, failure to lead up the chain — back to leadership decisions, eliminating external blame as an explanatory category. The output is a specific list of actions the leader would take differently, grounded in the situations they actually controlled.

Based on Willink's foundational principle that 'on any team, in any organization, all responsibility for success and failure rests with the leader' — the diagnostic enforces the ownership mindset by structurally preventing externalization of blame.
CapabilityC-02

Prioritize and Execute Loop

A five-step decision protocol for leaders overwhelmed by simultaneous problems. The skill walks users through: stepping back from the emotional pull of the situation, identifying the single highest-priority problem, briefing the team on that one priority only, executing a solution, then cycling to the next priority. This prevents both paralysis and scattered execution — the two failure modes when multiple threats compete for a leader's attention at once.

Directly encodes Law of Combat #3 as taught in Extreme Ownership: 'Relax, look around, make a call' — derived from combat situations in Ramadi where multiple simultaneous threats forced SEAL commanders to make rapid, sequential priority decisions rather than attempting to address everything at once.
CapabilityC-03

Decentralized Command Design

A structured exercise for drafting Commander's Intent — a mission statement clear enough that any team member can make the right call independently without escalation. The skill helps leaders write a one-to-two sentence mission objective, map leadership layers to the 6–10 direct reports guideline, and define exactly which decisions each leadership level can make autonomously. The output reduces the leader as a bottleneck while keeping the team aligned.

Based on Law of Combat #4: every subordinate leader must understand not just the immediate task but the broader 'why' — the Commander's Intent — well enough to adapt and execute when communication breaks down or the situation changes unexpectedly.
CapabilityC-04

After Action Review (AAR)

A structured debrief protocol applied to any completed project, decision, or event. The five-stage format covers: What was the mission? What actually happened? What went right and why? What went wrong and why? What would we do differently? The skill enforces Extreme Ownership discipline throughout — ensuring 'what went wrong' answers are owned by the team as leadership failures, not attributed to external circumstances or other people's behavior.

The AAR is the primary continuous improvement tool in Echelon Front's consulting methodology, used with Fortune 500 companies, military units, and sports franchises to operationalize the Discipline Equals Freedom principle into specific, repeatable behavior changes.
CapabilityC-05

Dichotomy Calibration

A calibration exercise drawn from Willink and Babin's 2018 follow-up book that identifies when a leader has overcorrected into a damaging extreme. Leaders who push ownership too hard become micromanagers; those who push decentralized command too far abdicate responsibility. The skill maps a specific leadership situation against the relevant dichotomy and helps the leader identify which extreme they're closer to, then recalibrate toward the productive center.

Based on The Dichotomy of Leadership's core thesis that every strength taken too far becomes a liability — confident but not cocky, attentive to detail but not micromanaging, driven but not reckless, close to the team but not too familiar.
Tested

Graded before it shipped.

Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.

What it produces
OutputD-01

Ownership Diagnostic Report

A structured breakdown of a specific leadership failure showing every contributing factor mapped back to leadership decisions — with zero external blame assigned and a clear list of specific actions the leader would take differently. Designed to be shared with a coach or mentor, or retained as a personal development record.

OutputD-02

Priority Stack

A ranked list of the simultaneous problems a leader is facing, with the single #1 priority identified and a brief execution statement — the direct output of the Prioritize and Execute loop that the leader can brief to their team immediately before addressing the next item on the list.

OutputD-03

Commander's Intent Statement

A one-to-two sentence mission statement defining the objective, the desired end state, and the 'why' — specific enough that any team member who loses communication with leadership can make the right call independently. Includes a delegation map showing which decisions each leadership level owns.

OutputD-04

After Action Review

A structured five-section document covering mission, execution, wins, failures, and lessons learned — with every failure attributed to a specific leadership action or gap rather than external causes. Suitable for team distribution, project retrospective systems, or individual leadership development archives.

The source

Grounded in the original work.

Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.

Source authorA-01

Jocko Willink & Leif Babin

Jocko Willink is a retired Navy SEAL officer who commanded Task Unit Bruiser — the most decorated special operations unit of the Iraq War — during the 2006 Battle of Ramadi. He co-founded Echelon Front, a leadership consulting firm with Fortune 500, military, and professional sports clients. He is the co-author of Extreme Ownership, which has sold over 5 million copies and reached #1 on the New York Times bestseller list, and hosts the Jocko Podcast, which has surpassed 400 episodes and ranks among the most-listened leadership shows in the world.

Status · Inspired by Jocko Willink & Leif Babin’s work — not yet claimed. Are you Jocko Willink & Leif Babin?
Primary sourceS-01

Extreme Ownership: How U.S. Navy SEALs Lead and Win

by Jocko Willink & Leif Babin

Former Commander, SEAL Task Unit Bruiser; Co-founder of Echelon Front; NYT #1 bestselling author (5M+ copies sold); host of the Jocko Podcast (400+ episodes)

Read the original ↗
Citationechelonfront.com
Get started

Put it to work.

agent-skills runs as MCP — connect it once and Extreme Ownership works in Claude, ChatGPT, Cursor, or any MCP-compatible client. Sign in to see your config and accept the terms.