# Leadership Os

> Use when the user is navigating people/leadership situations as a PM — managing up to executives, managing down to a team, cross-functional conflict, 1:1s, performance reviews, post-mortems, incident response, roadmap negotiation, or stakeholder communication. Trigger when the question is about *how to handle a person or situation*, not about code or product mechanics.

- Skill: `shwetank/leadership-os` (Agent Skill)
- Install (CLI): `npx skillmds@latest add shwetank/leadership-os`
- Raw SKILL.md: https://api.skillmd.com/api/skills/shwetank/leadership-os/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: shwetank (https://skillmd.com/u/shwetank)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/shwetank/leadership-os

---


# Leadership Operating System (Leadership-OS)

Technical competence gets you the meeting; leadership maturity keeps you in the room. Use these frameworks when the user is navigating the human complexity of building AI products.

## Foundational Philosophy

1. **People leave managers, not companies.** The job is to make the team's lives easier, not harder.
2. **Clarity is kindness.** Ambiguity breeds anxiety; owe team and stakeholders crisp communication.
3. **Title grants authority, behavior grants influence.** Trust comes from consistency, not demands.

## Managing Down: The Team Shield & Accelerator

### Mode: The Heat Shield
**Trigger:** Executive "swoop and poop," sudden pivots, external panic.
**Objective:** Protect team focus and psychological safety.
**Process:**
1. Triage: genuine strategic pivot, or executive's momentary anxiety?
2. "Yes, And" deflection: "Yes, we can look at that. And to do it well, we'll need to pause [Project X]. Which is the priority?"
3. Absorb the shock: never pass raw panic to the team. Translate into a calm, actionable directive.

### Mode: The Career Architect
**Trigger:** 1:1s, performance reviews, stagnation.
**Objective:** Connect daily work to long-term career growth.
**Process:**
1. Identify the gap: "You're great at execution. To get to Senior, you need strategic influence. Let's find a project that forces it."
2. Create the stretch: delegate something that scares them slightly but is reachable with support.
3. Narrative building: help them write the impact story for their next promo packet.

### Mode: The Mirror
**Trigger:** Post-mortems, repeated mistakes, interpersonal friction.
**Objective:** Deliver radical candor without breaking trust.
**Process:**
1. Separate intent from impact: "I know you were trying to help, but it shut down the junior engineer. Here's how it landed."
2. Ask, don't tell: "What was your thought process there?" reveals root cause faster than a lecture.
3. Follow up two weeks later. Feedback without follow-up is just criticism.

## Managing Up: The Strategic Translator

### Mode: The Calibrator
**Trigger:** Roadmap reviews, asking for resources, delivering bad news.
**Objective:** Align ground truth with executive expectations.
**Process:**
1. No-Surprise Rule: bad news travels up faster than good news. A 5-min heads-up prevents a 30-min disaster meeting.
2. Speak in trade-offs: never present a problem without two options and a recommendation.
3. Translate tech to biz: "context window too small" → "can't process large documents, blocks Enterprise tier launch."

### Mode: The Resource Negotiator
**Trigger:** New project initiation, re-prioritization.
**Objective:** Secure capital (headcount, budget, time).
**Process:**
1. Why before what: lead with business outcome, not the ask.
2. Pilot programs: if a full yes isn't possible, ask for a "pilot yes" — one engineer for two weeks to prove the concept.

## Managing Across: The Diplomat & Unblocker

### Mode: The Diplomat
**Trigger:** Competing roadmaps, dependency deadlock, turf wars.
**Objective:** Turn friction into momentum.
**Process:**
1. Find the shared "why": align on the joint outcome (e.g., Q4 revenue).
2. Make them the hero: "If your team delivers X, my feature shines. How can I clear the path?"
3. Pre-mortem: before a cross-team launch, ask "imagine this failed — why?" Solve those before they happen.

### Mode: The Credit Splitter
**Trigger:** Project wins, successful launches.
**Objective:** Distribute recognition to build long-term political capital.
**Process:**
1. Public praise, private critique. Always.
2. Specific attribution: "Sarah cracked the eval metric problem" beats "the team did great" 10x.

## High-Stakes Situations

### Mode: The Triage Lead
**Trigger:** Production outages, critical bugs, security incidents.
**Objective:** Restore order without creating chaos.
**Process:**
1. Stabilize: stop the bleeding (rollback, kill switch).
2. Delegate roles: Comms lead, Tech lead, Investigator.
3. Communicate: clear, blameless update to stakeholders every 30–60 min.

### Mode: The Mediator
**Trigger:** Interpersonal conflict, toxic behavior, clashing styles.
**Objective:** Resolve conflict while preserving the relationship (or managing the exit).
**Process:**
1. Listen separately on neutral ground.
2. Focus on behavior, not character: "When you interrupt in meetings…" not "You're arrogant."
3. Define the new normal: concrete behavioral changes with weekly check-ins.

## Self-Measurement

Effectiveness indicators:
- **Retention:** do high performers stay and grow?
- **Autonomy:** can the team function when the user is out?
- **Psychological safety:** does the team admit mistakes and ask "dumb" questions?
- **Succession:** is there someone who could step into the user's role in 12–18 months?