strategic-alignment
Cascades strategy from boardroom to individual contributor and detects misalignment
Install / Use
npx skills add borghei/Claude-Skills --skill strategic-alignmentInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of strategic-alignment
strategic-alignment scores 89/100 on our quality scale, 1714th of 4,702 Development & Engineering skills we index (top 37%).
Its SKILL.md is 20 KB long, well organised into 34 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.
It has 817 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so strategic-alignment is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
strategic-alignment compared with similar skills
All 4 of these similar skills score higher than strategic-alignment; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| strategic-alignment (this skill)by borghei | 89 | 817 | 57d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.7k | today | MCP Server |
Frequently asked questions
- How do I install strategic-alignment?
- Run
npx skills add borghei/Claude-Skills --skill strategic-alignment. The install tabs above show the steps for each supported agent. - Which AI agents does strategic-alignment work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is strategic-alignment safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is strategic-alignment still maintained?
- The repository was last updated about 2 months ago, so strategic-alignment is actively maintained.
Skill content
View source on GitHubname: strategic-alignment description: > Cascades strategy from boardroom to individual contributor and detects misalignment. Use when teams pull in different directions, OKRs don't connect, departments optimize locally at company expense, or strategy doesn't translate to execution. license: MIT + Commons Clause metadata: version: 2.0.0 author: borghei category: c-level domain: strategic-alignment updated: 2026-03-09 frameworks: - articulation-test - cascade-mapping - orphan-detection - conflict-detection - silo-diagnosis - communication-gap - realignment-protocol - alignment-scoring triggers: - strategic alignment - strategy cascade - OKR alignment - orphan OKRs - conflicting goals - silos - communication gap - department alignment - alignment checker - strategy articulation - cross-functional alignment - goal cascade - misalignment - alignment score - teams pulling in different directions - departments not aligned - OKRs don't connect - local optimization - strategy communication
Strategic Alignment Engine
Strategy fails at the cascade, not the boardroom. This skill detects misalignment before it becomes dysfunction and builds systems that keep strategy connected from CEO to individual contributor.
Keywords
strategic alignment, strategy cascade, OKR alignment, orphan OKRs, conflicting goals, silos, communication gap, department alignment, strategy articulation, cross-functional alignment, goal cascade, misalignment, alignment score, local optimization, strategy communication, cascade mapping
The Alignment Problem
The further a goal gets from the strategy that created it, the less likely it reflects the original intent.
This is the organizational telephone game. It happens at every stage. The question is how bad it is and how to fix it.
CEO says: "We need to win the mid-market healthcare segment"
VP hears: "Healthcare is the priority"
Director translates: "Build healthcare features"
Team executes: "Add HIPAA compliance checkbox to the roadmap"
IC works on: "HIPAA feature that nobody asked for and doesn't close deals"
Result: Effort spent, strategy not advanced.
Clarify First
Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- [ ] Which deliverable is needed (full diagnostic, cascade map, silo diagnosis, communication-gap analysis, or workshop agenda) — each uses a different step of the framework
- [ ] The current strategy stated in one sentence — alignment is tested against the source; if the strategy itself is vague, fix that before cascading
- [ ] The actual goals/OKRs at company, team, and individual levels — orphan, conflict, and coverage-gap detection needs the real cascade, not a hypothetical one
- [ ] Company size and structure — the 5-person test and hierarchical cascade assumptions need adapting for large or matrixed orgs
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Step 1: Strategy Articulation Test
Before checking cascade, check the source.
The 5-Person Test
Ask five people from five different teams:
"What is the company's most important strategic priority right now?"
| Result | Score | Diagnosis | |--------|-------|-----------| | All 5 give the same answer | 10/10 | Clear articulation. Check cascade. | | 4 give similar answers | 7-8/10 | Close. Clarify the outlier. | | 3 agree | 5-6/10 | Loose alignment. Re-communicate. | | 2 agree | 2-4/10 | Strategy is unclear. Fix before cascade. | | No agreement | 0-1/10 | No shared strategy exists. Start here. |
Strategy Format Test
The strategy must be statable in one sentence.
| Format | Score | |--------|-------| | One clear sentence | Good | | Two sentences | Acceptable | | A paragraph | Too complex to cascade | | A document | Too complex to internalize |
Examples:
| Bad | Why | Good | |-----|-----|------| | "Focus on growth while maintaining enterprise relationships and expanding internationally and investing in platform" | Four priorities = no priority | "Win the mid-market healthcare segment in DACH before Series B" | | "Be the best at what we do" | Not falsifiable | "Reach $5M ARR by Q4 with 110%+ NRR" | | "Customer-first approach to innovation" | Sounds nice, means nothing | "Ship the workflow automation feature that our top 10 prospects asked for" |
Step 2: Cascade Mapping
Map the flow from company strategy through every organizational level.
Cascade Visualization
Company Level: Strategy Statement
|
Company OKR-1 Company OKR-2 Company OKR-3
| | |
Dept Level: Sales OKRs Eng OKRs Product OKRs
| | |
Team Level: Team A OKRs Team B OKRs Team C OKRs
| | |
Individual: Personal goals Personal goals Personal goals
Cascade Validation Questions
For each goal at every level:
| Question | Purpose | |----------|---------| | Which company goal does this support? | Tests upward connection | | If achieved 100%, how much does it move the parent goal? | Tests impact significance | | Is the connection direct or theoretical? | Tests proximity of impact | | Who else is working on the same parent goal? | Tests coverage and overlap |
Step 3: Alignment Failure Detection
Three failure patterns to detect:
Pattern 1: Orphan Goals
Goals that don't connect to any company-level objective.
| Symptom | Root Cause | Fix | |---------|-----------|-----| | "We've been working on this all quarter and nobody cares" | Goals set bottom-up without reconciliation | Connect or cut. Every goal needs a parent. | | Team proud of achievement, leadership unaware | Misaligned definition of success | Explicit cascade mapping before quarter starts | | Individual goals from last quarter carried forward | Inertia, not intention | Fresh cascade each quarter |
Pattern 2: Conflicting Goals
Two teams' goals, when both succeed, create a worse outcome.
| Example | Conflict | Fix | |---------|----------|-----| | Sales: maximize new logos / CS: maximize NPS | Sales closes bad-fit customers, CS suffers | Shared goal: qualified new logos that retain | | Product: ship fast / Security: no vulnerabilities | Speed vs. quality tension | Shared SLA: ship within X days with Y security checks | | Marketing: maximize leads / Sales: close enterprise | Marketing optimizes for volume, sales needs quality | Shared metric: qualified pipeline $, not lead count |
Pattern 3: Coverage Gaps
Company has 3 OKRs. 5 teams support OKR-1, 2 teams support OKR-2, 0 teams support OKR-3.
| Detection | Impact | Fix | |-----------|--------|-----| | Company OKR consistently misses while others hit | Nobody actually owns the failing OKR | Explicit team assignment to every company OKR | | Resource allocation does not match priority | Top priority underfunded | Align resources to stated priorities | | Strategy says X is important but no team's goals reflect it | Strategy is aspirational, not operational | Translate strategy to owned team goals |
Step 4: Silo Diagnosis
Silos exist when teams optimize for local metrics at the expense of company metrics.
Silo Detection Matrix
| Signal | Score (1-5) | Weight | |--------|-------------|--------| | Department hits goals while company misses | 5 = always | 25% | | Teams don't know other teams' priorities | 5 = never | 20% | | "That's not our problem" is common | 5 = daily | 20% | | Cross-functional escalations only flow up | 5 = always | 15% | | Data not shared between dependent teams | 5 = never shared | 10% | | Cross-functional projects take 3x expected time | 5 = always | 10% |
Score 30+: Severe silos. Immediate intervention required. Score 20-29: Moderate silos. Address in next quarter. Score 10-19: Minor friction. Monitor and address specific hot spots. Score < 10: Healthy cross-functional operation.
Silo Root Causes and Fixes
| Root Cause | Fix | Owner | |-----------|-----|-------| | Incentive misalignment | Create shared goals where teams interact | CEO + COO | | No shared goals | Add 1 cross-functional OKR per interacting team pair | COO | | No shared language | Cross-functional show-and-tell monthly | Culture Architect | | Geography/timezone | Intentional async overlap + quarterly in-person | COO + CHRO | | Org design | Consider restructuring to reduce handoffs | CEO + CHRO |
Step 5: Communication Gap Analysis
What the CEO says is not what teams hear. The gap grows with company size.
Message Decay Model
CEO communicates strategy
|
v [10-20% loss]
VP interprets through their lens
|
v [10-20% loss]
Manager translates for team
|
v [10-20% loss]
IC receives modified version
|
v [10-20% loss]
IC interprets further based on daily work
Total signal loss: 40-80% from CEO to IC
Communication Gap Sources
| Source | Detection | Fix | |--------|-----------|-----| | Ambiguity | Different teams interpret differently | Make strategy specific enough to be wrong | | Frequency | Said once, expected to stick | Repeat strategy 7x through different channels | | Medium mismatch | Written doc for visual thinkers | Use multiple formats (written, visual, verbal) | | Trust deficit | Team doesn't believe strategy is real | Show resource allocation that proves it | | Filtering | Managers edit the message | Skip-level communication + all-hands |
Step 6: Realignment Protocol
How to fix misalignment without creating fear.
Realignment Decision Tree
START: Misalignment detected
|
v
[Is the problem at the strategy level or the cascade level?]
|
+-- STRATEGY (Step 1 failed)
| --> CEO rewrites strategy as one sentence
| --> Re-communicate through all channels
| --> Re-run 5-person test after 2 weeks
|
+-- CASCADE (Step 2-3 failures)
| |
| v
| [Which failure pattern?]
| |
| +-- Orphan goals --> Connect or cut workshop
| +-- Conflicting goals --> Cross-functional OKR review
| +-- Coverage gaps --> Assign explicit ownership
|
+-- SILOS (Step 4)
| --> Fix incentives first
| --> Add shared metrics
| --> Consider org design change
|
+-- COMMUNICATION (Step 5)
--> Increase frequency (weekly, not quarterly)
--> Add skip-level communication
--> Show resource proof (money follows words)
Realignment Workshop (Half-day)
Agenda:
1. CEO restates strategy (15 min)
2. Each dept maps their goals to strategy (45 min)
3. Identify orphans, conflicts, gaps together (30 min)
4. Fix orphans: connect or cut (30 min)
5. Fix conflicts: shared metrics or priority resolution (30 min)
6. Fix gaps: assign ownership (15 min)
7. Communication plan (15 min)
Alignment Score
Quick health check. Score each area 0-10.
| Area | Question | Score | |------|----------|-------| | Strategy clarity | Can 5 people from different teams state strategy consistently? | /10 | | Cascade completeness | Do all team goals connect to company goals? | /10 | | Conflict detection | Have cross-team OKR conflicts been reviewed and resolved? | /10 | | Coverage | Does each company OKR have explicit team ownership? | /10 | | Communication | Do teams' behaviors reflect the strategy? | /10 |
Score Interpretation
| Total (/50) | Status | Action | |-------------|--------|--------| | 45-50 | Excellent | Maintain the system. Quarterly check is sufficient. | | 35-44 | Good | Address specific weak areas in next OKR cycle. | | 20-34 | Misalignment costing you | Immediate attention. Workshop within 2 weeks. | | < 20 | Strate
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.7k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
