leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
What this skill does
# Leadership Expert
Comprehensive leadership frameworks for decision-making, change management, and organizational effectiveness.
## Executive Decision-Making
### Decision-Making Frameworks
```
OODA LOOP (Fast Decisions):
Observe → Orient → Decide → Act
DECIDE FRAMEWORK (Complex Decisions):
D - Define the problem
E - Establish criteria
C - Consider alternatives
I - Identify best alternative
D - Develop action plan
E - Evaluate and monitor
WRAP FRAMEWORK (Avoiding Bias):
W - Widen your options
R - Reality-test assumptions
A - Attain distance before deciding
P - Prepare to be wrong
```
### Decision Quality Checklist
| Factor | Questions to Ask |
| ---------------- | ---------------------------------- |
| **Frame** | Are we solving the right problem? |
| **Alternatives** | Have we considered enough options? |
| **Information** | Do we have reliable data? |
| **Values** | Are we clear on what matters? |
| **Reasoning** | Is our logic sound? |
| **Commitment** | Will people execute? |
### Delegation Matrix
| Importance | Urgency | Decision By |
| ---------- | ------- | ---------------------- |
| High | High | Executive (fast) |
| High | Low | Executive (thoughtful) |
| Low | High | Delegate with check-in |
| Low | Low | Delegate fully |
## Change Management
### Kotter's 8-Step Model
```
1. Create Urgency - Compelling reasons, threats/opportunities
2. Build Guiding Coalition - Influential cross-functional team
3. Form Strategic Vision - Clear future state and strategy
4. Communicate Vision - Repeat across channels, model behaviors
5. Enable Action - Remove barriers, encourage risk-taking
6. Generate Short-term Wins - Plan victories, build momentum
7. Sustain Acceleration - Hire change agents, new projects
8. Institute Change - Anchor in culture, ensure continuity
```
### ADKAR Model (Individual Change)
| Element | Definition | Key Actions |
| ----------------- | ------------------- | -------------------------------- |
| **Awareness** | Understanding why | Communicate business drivers |
| **Desire** | Want to participate | Address WIIFM, reduce resistance |
| **Knowledge** | How to change | Training, education |
| **Ability** | Skills to execute | Practice, coaching |
| **Reinforcement** | Sustain the change | Recognition, measurement |
### Change Resistance Management
```
SOURCES OF RESISTANCE:
- Fear of unknown
- Loss of control
- Surprise / timing
- Concerns about competence
- Past change failures
- Threat to status
- Peer pressure
- Mistrust of leadership
RESPONSE STRATEGIES:
| Type | Approach |
|------|----------|
| Information deficit | Education, communication |
| Skill deficit | Training, coaching |
| Incentive deficit | Align rewards |
| Resource deficit | Provide support |
| Values conflict | Dialogue, involvement |
| Politics | Negotiation, coalition |
```
## Crisis Management
### Crisis Response Framework
```
PRE-CRISIS: Risk ID, crisis team, templates, exercises
RESPONSE (Hour 1-4): Activate team, assess, secure safety, communicate
RESPONSE (Hour 4-24): Detailed assessment, stakeholder/media comms
RESPONSE (Day 2-7): Root cause, remediation, ongoing comms
POST-CRISIS: After-action review, improvements, reputation repair
```
### Crisis Communication
```
COMMUNICATION PRINCIPLES:
- Acknowledge quickly
- Show empathy
- Take responsibility (where appropriate)
- Explain actions being taken
- Commit to updates
- Be honest about unknowns
STAKEHOLDER PRIORITIES:
1. Affected individuals (safety)
2. Employees
3. Regulators
4. Media
5. Investors
6. Customers
7. Partners
8. General public
MESSAGE FRAMEWORK:
1. What happened (facts known)
2. What we're doing (actions)
3. What it means for stakeholders
4. What to expect next
```
### Business Continuity Planning
| Element | Description |
| ---------------------------- | -------------------------------- |
| **Risk Assessment** | Identify potential disruptions |
| **Business Impact Analysis** | Critical processes, RTOs, RPOs |
| **Recovery Strategies** | Alternate facilities, IT, people |
| **Plan Development** | Documented procedures |
| **Testing & Exercises** | Regular drills, tabletops |
| **Maintenance** | Annual updates, post-incident |
## Stakeholder Management
### Stakeholder Analysis Matrix
```
STAKEHOLDER MAPPING:
Power/Influence
High Low
Interest
High MANAGE CLOSELY KEEP INFORMED
(Board, major (Employees,
investors) community)
Low KEEP SATISFIED MONITOR
(Regulators, (Low priority
lenders) groups)
```
### Stakeholder Engagement Plan
| Stakeholder | Interest | Influence | Strategy | Frequency |
| ----------- | -------- | --------- | ---------------- | --------- |
| Board | High | High | Partner | Monthly |
| Investors | High | High | Inform & consult | Quarterly |
| Employees | High | Medium | Engage | Weekly |
| Customers | High | Medium | Listen & respond | Ongoing |
| Regulators | Medium | High | Comply & inform | As needed |
| Media | Variable | High | Proactive comms | As needed |
### Influence Without Authority
```
RECIPROCITY: Give first - help others, share resources, build credit
SOCIAL PROOF: Reference peers/competitors, share success stories
AUTHORITY: Demonstrate competence, use data and evidence
LIKING: Find common ground, show genuine interest
SCARCITY: Create urgency with limited opportunity/time
COMMITMENT: Start small, get incremental yes, build agreements
```
## Board Relations
### Board Communication Best Practices
```
BOARD MEETING PREPARATION:
- Pre-read materials 1 week ahead
- Executive summary on page 1
- Clear recommendation/ask
- Supporting data in appendix
- Anticipate questions
BOARD PRESENTATION STRUCTURE:
1. Context (2 min)
2. Key issue/opportunity (3 min)
3. Options considered (5 min)
4. Recommendation (3 min)
5. Discussion (remaining time)
BOARD REPORTING CADENCE:
| Topic | Frequency |
|-------|-----------|
| Financial results | Monthly/Quarterly |
| Strategic initiatives | Quarterly |
| Risk dashboard | Quarterly |
| Talent/succession | Semi-annually |
| Strategy refresh | Annually |
| Competitive landscape | Annually |
```
### Governance Best Practices
| Practice | Description |
| -------------------------- | ------------------------------- |
| **Independent Chair** | Separate from CEO for oversight |
| **Executive Sessions** | Independent director meetings |
| **Board Evaluation** | Annual self-assessment |
| **Succession Planning** | CEO and board renewal |
| **Risk Oversight** | Dedicated committee or process |
| **Shareholder Engagement** | Investor dialogue program |
## Executive Communication
### Communication Principles
```
EXECUTIVE PRESENCE:
- Clarity: Simple, direct messages
- Confidence: Conviction without arrogance
- Credibility: Expertise and authenticity
- Connection: Empathy and engagement
- Composure: Calm under pressure
MESSAGE DEVELOPMENT:
What? → So what? → Now what?
(Facts) (Impact) (Action)
```
### Town Hall / All-Hands Framework
```
STRUCTURE:
1. Opening (5 min)
- Connect personally
- Set context and agenda
2. Business Update (15 min)
- Performance highlights
- Key wins and learnings
- Challenges and plans
3. Strategic Focus (10 min)
- Priority initiatives
- Progress and next steps
- Resource allocation
4. Recognition (5 min)
- Celebrate successes
- Acknowledge teams
5. Q&A (20 min)
- Prepared questions
- OpenRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.