Agent skill

strategic-alignment

Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different directions, OKRs don't connect, departments optimize locally at company expense, or when user mentions alignment, strategy cascade, silo, conflicting OKRs, or strategy communication.

Alireza Rezvani23,369★ · +428/wk · 1 repos on radarProfile →
claude-codecodexcursorships scriptsMIT
Install
npx skills add alirezarezvani/claude-skills --skill strategic-alignment --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 9 KB
Bundled scripts: yes
Version: 1.0.0
Declared author: Alireza Rezvani
Path: c-level-advisor/skills/strategic-alignment/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 23,791 · +422 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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, alignment checker, strategy articulation, cross-functional, goal cascade, misalignment, alignment score ## Quick Start ```bash python scripts/alignment_checker.py # Check OKR alignment: orphans, conflicts, coverage gaps ``` ## Core Framework 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. ### Step 1: Strategy Articulation Test Before checking cascade, check the source. Ask five people from five different teams: **"What is the company's most important strategic priority right now?"** **Scoring:** - All five give the same answer: ✅ Articulation is clear - 3–4 give similar answers: 🟡 Loose alignment — clarify and comm

What's inside
Steps it walks through
  1. Keywords
  2. Quick Start
  3. Core Framework
  4. Step 1: Strategy Articulation Test
  5. Step 2: Cascade Mapping
  6. Step 3: Alignment Detection
  7. Step 4: Silo Identification
  8. Step 5: Communication Gap Analysis
  9. Step 6: Realignment Protocol
  10. Alignment Score
  11. Key Questions for Alignment
  12. Red Flags
  13. Integration with Other C-Suite Roles
  14. Detailed References
Ships with 2 files
  • references/alignment-playbook.md
  • scripts/alignment_checker.py
Commands it runs
python scripts/alignment_checker.py    # Check OKR alignment: orphans, conflicts, coverage gaps
More from claude-skills
All skills →
About this skill
What does the strategic-alignment skill do?

Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different directions, OKRs don't connect, departments optimize locally at company expense, or when user mentions alignment, strategy cascade, silo, conflicting OKRs, or strategy communication.

How do I install it?

Run `npx skills add alirezarezvani/claude-skills --skill strategic-alignment --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going