
ownership-coach
Use when a team is deflecting blame to external factors or a leader is micromanaging—shifts from permission-seeking to intent-stating using Willink's Extreme Ownership and Marquet's Leader-Leader model.
- Installs
- 39
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/joellewis/skill-library --skill ownership-coach- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ownership-coach automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Overview
Ownership coaching is the practice of developing total accountability in leaders and teams. This skill shifts the paradigm from "Leader-Follower" (giving orders) to "Leader-Leader" (giving intent), ensuring that every individual owns their world, understands the "why," and maintains a non-negotiable standard of performance.
Guiding Principles
Principle 1: Extreme Ownership (Source: Willink, Extreme Ownership)
There are no bad teams, only bad leaders. The leader must own everything in their world. If a subordinate fails, the leader must take the blame and find a path to victory. Excuses are the death of ownership.
Principle 2: Leader-Leader Model (Source: Marquet, Turn the Ship Around!)
Move from "Leader-Follower" (giving orders) to "Leader-Leader" (giving intent). Ownership is built when subordinates provide "I intend to..." statements rather than asking for permission.
Principle 3: Standard of Performance (Source: Walsh, The Score Takes Care of Itself)
Ownership starts with a non-negotiable standard for every role. If the process and the standard are followed with absolute rigor, the "score" (the result) will take care of itself.
Principle 4: Hell Yeah or No (Source: Sivers, Hell Yeah or No)
Ownership requires radical prioritization. If an opportunity doesn't elicit an enthusiastic "Hell yeah!", the answer is "No." This protects the time and focus needed to own the few things that truly matter.
Principle 5: Protect the Maker's Schedule (Source: Graham, "Maker's Schedule, Manager's Schedule")
A leader owns the environment of their team. For "Makers" (engineers, writers), this means protecting large, uninterrupted blocks of time. Meetings are "exceptions" that can kill a maker's ownership of a project.
When to Use This Skill
- When a team is "blaming" external factors for failure.
- When a leader is micromanaging and needs to "release control."
- When a project is stalled due to a lack of clear accountability.
- When an individual is overwhelmed and needs to reclaim ownership of their schedule.
When NOT to Use This Skill
- In high-velocity "Wartime" situations where immediate, centralized command is required for survival (unless the goal is to transition to peacetime). (Source: Horowitz, Ch. 7)
- For trivial tasks where the overhead of "intent-based" leadership exceeds the benefit.
Core Process
Step 1: Conduct an Accusation Audit (The Mirror)
Identify where you (the leader) have failed to provide clarity, resources, or support. (Source: Willink, Ch. 1)
- The Question: "What am I doing (or not doing) that is preventing my team from owning this?"
- The Ownership Statement: Publicly take the blame for the team's current failure to reset the culture.
Step 2: Transition to "I Intend To..."
Shift the communication pattern from permission-seeking to intent-stating. (Source: Marquet, Ch. 15)
- Coach the Subordinate: When asked "What should I do?", respond with "What do you intend to do?"
- Verify Competence and Clarity: Only approve the "intent" if the subordinate proves they have the technical competence and the strategic clarity to succeed.
Step 3: Define the Standard of Performance
Document the specific behaviors and quality levels required for every role. (Source: Walsh, Ch. 1)
- Focus on Process: Reward adherence to the standard, not just the "lucky" result.
- The "Non-Negotiables": State clearly which standards are absolute and which have room for experimentation.
Step 4: Decentralized Command (Intent-Based Control)
Empower subordinates to make decisions within their scope. (Source: Willink, Ch. 8)
- Give the Goal (Commander's Intent): Explain the "Why" and the "End State."
- Define Boundaries: What is the specific "Left and Right limit" for their decision-making?
- Release Control: Step back and let them execute.
Step 5: Audit for "Hell Yeah" Focus
Review current commitments and remove the "clutter." (Source: Sivers, "Hell Yeah or No")
- List Commitments: Every project, meeting, and recurring task.
- The Filter: If it's not a "Hell yeah!", mark it for delegation, deferral, or deletion.
Frameworks & Models
The Leader-Leader Hierarchy (Source: Marquet, Turn the Ship Around!)
- Level 1: Tell me what to do. (Follower)
- Level 2: I think... (Follower)
- Level 3: I recommend... (Follower)
- Level 4: I intend to... (Leader)
- Level 5: I've done... (Leader)
Peacetime vs. Wartime CEO (Source: Horowitz, Hard Thing About Hard Things)
- Peacetime: Focuses on culture, long-term vision, and "how we do things."
- Wartime: Focuses on survival, immediate execution, and "what must be done now." Ownership in wartime means absolute adherence to the survival plan.
Cross-Skill Invocations
- REQUIRED SUB-SKILL:
feedback-coach— To deliver the "Extreme Ownership" message without destroying morale. - RECOMMENDED SUB-SKILL:
difficult-conversations— For holding the line on the "Standard of Performance." - RECOMMENDED SUB-SKILL:
operational-excellence— To build the "Mechanisms" that sustain ownership.
Common Mistakes
- The Blame Game: Blaming the team, the market, or the competition instead of owning the failure. (Source: Willink, Ch. 1)
- Micromanagement: Holding on to control because you don't trust the team's competence. (Source: Marquet, Ch. 10)
- Ambiguous Intent: Giving a goal without the "Why," leading to misaligned execution. (Source: Willink, Ch. 3)
- Meeting Bloat: Ignoring the "Maker's Schedule" and killing team ownership via interruptions. (Source: Graham, "Maker's Schedule")
Diagnostic Checklist
- Have I (the leader) taken personal ownership of the current failure?
- Is my team providing "I intend to..." statements instead of asking for permission?
- Is there a clear "Standard of Performance" for every role involved?
- Have we defined the "Commander's Intent" (the Why and the End State)?
- Are we saying "No" to everything that isn't a "Hell yeah!"?
Sources
- Willink, Extreme Ownership, Ch. 1, 3, 8 — Ownership, Belief, Decentralized Command.
- Marquet, Turn the Ship Around!, Ch. 1-3, 10, 15 — Leader-Leader, Control, Intent.
- Walsh, The Score Takes Care of Itself, Ch. 1, 3 — Standard of Performance, Accountability.
- Horowitz, The Hard Thing About Hard Things, Ch. 5, 7 — People/Product/Profit, Peacetime/Wartime.
- Sivers, Hell Yeah or No — Radical prioritization.
- Paul Graham, "Maker's Schedule, Manager's Schedule" — Time ownership.
FAQ
What does the ownership-coach skill do?
Use when a team is deflecting blame to external factors or a leader is micromanaging—shifts from permission-seeking to intent-stating using Willink's Extreme Ownership and Marquet's Leader-Leader model.
How do I install ownership-coach?
Run npx skills add https://github.com/joellewis/skill-library --skill ownership-coach in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ownership-coach/ (personal) or .claude/skills/ownership-coach/ (project).
Which AI agents can use ownership-coach?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ownership-coach safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ownership-coach?
It is published by joellewis in joellewis/skill-library. It has 39 recorded installs.
More from joellewis/skill-library
fiction-architect
joellewis/skill-library
Designs plot structure and story arcs using McKee's value turns, Campbell's monomyth, and Sanderson's Promise/Progress/Payoff model to ensure causal integrity and emotional resonance. Use when constructing narratives, outlining novels, or diagnosing why a story feels broken.
dialogue-craft
joellewis/skill-library
Writes and refines dialogue that serves plot and reveals character through subtext, intention, and behavioral exchange — applying McKee's subtext principle and Sorkin's intention-and-obstacle model. Use when dialogue feels flat, expository, or 'on the nose.'
world-building-logic
joellewis/skill-library
Engineers internally consistent fictional worlds using Brand's Pace Layers for social structure and Sanderson's Laws of Magic for system constraints. Use when building settings, designing magic or tech systems, or auditing a world for logical contradictions.
problem-framing
joellewis/skill-library
Use when beginning analytical or strategic tasks, facing undefined problems, or facing analysis paralysis—requires explicit problem definition before proceeding.
character-vulnerability
joellewis/skill-library
Use when a character feels flat, too competent, or unrelatable—identifies the Sacred Flaw (Storr's Theory of Control) and dials the Three Sliders (Sanderson) to create earned vulnerability.
one-pager
joellewis/skill-library
Use when compressing a complex strategy or analysis into a strictly one-page narrative—enforces Pyramid SCQ structure and Orwell word-budget discipline.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.