Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Strategic Alignment

  • 518 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

strategic-alignment is a Claude Code skill that compresses quarterly strategy into a one-page cascade, runs OKR workshops, and detects execution drift for developers who lead product priorities without a dedicated strate

About

Strategic Alignment is an agent skill playbook for developers who wear the founder and PM hat and need discipline borrowed from scaled teams without hiring a strategy office. It teaches how to compress strategy onto one page so it is clear enough to cascade, then run structured workshops where leaders translate company OKRs into department contributions and surface gaps before anyone writes code. The one-page filter forces a six-word vision, three owned priorities, an honest list of what you are not doing, and a small metric set—because without explicit deprioritization every squad invents its own roadmap. Follow-on sections in the skill address drift detection and maintaining alignment over time, which matters when you ship fast and context slips between async updates. Use it when you are planning a quarter, reconciling conflicting initiatives, or feeling “everyone is busy but nothing strategic moves.” It is methodology and templates, not an integration; pair it with your existing issue tracker and OKR tooling.

  • One-page strategy filter template with 6-word vision, owned TOP 3 priorities, and explicit NOT-doing list
  • Three-step cascade workshop: company OKR walkthrough, department draft OKRs, cross-check for gaps and conflicts
  • Techniques for cascading strategy and detecting drift at scale beyond a single planning doc
  • Emphasis that deprioritization is as important as stated priorities for real alignment
  • Success metrics block ties strategy to measurable outcomes per quarter

Strategic Alignment by the numbers

  • 518 all-time installs (skills.sh)
  • +2 installs in the week ending Jun 18, 2026 (Skillselion tracking)
  • Ranked #744 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill strategic-alignment

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs518
repo stars23.5k
Security audit3 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills

How do you cascade quarterly strategy into OKRs?

Compress quarterly strategy into a one-page cascade, run OKR workshops, and detect execution drift when you lead product priorities without a full strategy team.

Who is it for?

Engineering leads and product-minded developers who own quarterly priorities and need OKR alignment without a strategy department.

Skip if: Skip strategic-alignment when you need low-level implementation tasks like API design or unit test generation.

When should I use this skill?

A developer discusses quarterly strategy, OKR workshops, priority cascades, or detecting execution drift across teams.

What you get

One-page strategy document, OKR set with owners, and drift detection checklist for quarterly alignment.

  • one-page strategy document
  • OKR workshop output
  • drift detection checklist

Files

SKILL.mdMarkdownGitHub ↗

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

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 communicate
  • < 3 agree: 🔴 Strategy isn't clear enough to cascade. Fix this before fixing cascade.

Format test: The strategy should be statable in one sentence. If leadership needs a paragraph, teams won't internalize it.

  • ❌ "We focus on product-led growth while maintaining enterprise relationships and expanding our international presence and investing in platform capabilities"
  • ✅ "Win the mid-market healthcare segment in DACH before Series B"

Step 2: Cascade Mapping

Map the flow from company strategy → each level of the organization.

Company level:  OKR-1, OKR-2, OKR-3
    ↓
Dept level:     Sales OKRs, Eng OKRs, Product OKRs, CS OKRs
    ↓
Team level:     Team A OKRs, Team B OKRs...
    ↓
Individual:     Personal goals / rocks

For each goal at every level, ask:

  • Which company-level goal does this support?
  • If this goal is 100% achieved, how much does it move the company goal?
  • Is the connection direct or theoretical?

Step 3: Alignment Detection

Three failure patterns:

Orphan goals: Team or individual goals that don't connect to any company goal.

  • Symptom: "We've been working on this for a quarter and nobody above us seems to care"
  • Root cause: Goals set bottom-up or from last quarter's priorities without reconciling to current company OKRs
  • Fix: Connect or cut. Every goal needs a parent.

Conflicting goals: Two teams' goals, when both succeed, create a worse outcome.

  • Classic example: Sales commits to volume contracts (revenue), CS is measured on satisfaction scores. Sales closes bad-fit customers; CS scores tank.
  • Fix: Cross-functional OKR review before quarter begins. Shared metrics where teams interact.

Coverage gaps: Company has 3 OKRs. 5 teams support OKR-1, 2 support OKR-2, 0 support OKR-3.

  • Symptom: Company OKR-3 consistently misses; nobody owns it
  • Fix: Explicit ownership assignment. If no team owns a company OKR, it won't happen.

See scripts/alignment_checker.py for automated detection against your JSON-formatted OKRs.

Step 4: Silo Identification

Silos exist when teams optimize for local metrics at the expense of company metrics.

Silo signals:

  • A department consistently hits their goals while the company misses
  • Teams don't know what other teams are working on
  • "That's not our problem" is a common phrase
  • Escalations only flow up; coordination never flows sideways
  • Data isn't shared between teams that depend on each other

Silo root causes: 1. Incentive misalignment: Teams rewarded for local metrics don't optimize for company metrics 2. No shared goals: When teams share a goal, they coordinate. When they don't, they drift. 3. No shared language: Engineering doesn't understand sales metrics; sales doesn't understand technical debt 4. Geography or time zones: Silos accelerate when teams don't interact organically

Silo measurement:

  • How often do teams request something from each other vs. proceed independently?
  • How much time does it take to resolve a cross-functional issue?
  • Can a team member describe the current priorities of an adjacent team?

Step 5: Communication Gap Analysis

What the CEO says ≠ what teams hear. The gap grows with company size.

The message decay model:

  • CEO communicates strategy at all-hands → managers filter through their lens → teams receive modified version → individuals interpret further

Gap sources:

  • Ambiguity: Strategy stated at too high a level ("grow the business") lets each team fill in their own interpretation
  • Frequency: One all-hands per quarter isn't enough repetition to change behavior
  • Medium mismatch: Long written strategy doc for teams that respond to visual communication
  • Trust deficit: Teams don't believe the strategy is real ("we've heard this before")

Gap detection:

  • Run the Step 1 articulation test across all levels
  • Compare what leadership thinks they communicated vs. what teams say they heard
  • Survey: "What changed about how you work since the last strategy update?"

Step 6: Realignment Protocol

How to fix misalignment without calling it a "realignment" (which creates fear).

Step 6a: Don't start with what's wrong Starting with "here's our misalignment" creates defensiveness. Start with "here's where we're heading and I want to make sure we're connected."

Step 6b: Re-cascade in a workshop, not a memo Alignment workshops are more effective than documents. Get company-level OKR owners and department leads in a room. Map connections. Find gaps together.

Step 6c: Fix incentives before fixing goals If department heads are rewarded for local metrics that conflict with company goals, no amount of goal-setting fixes the problem. The incentive structure must change first.

Step 6d: Install a quarterly alignment check After fixing, prevent recurrence. See references/alignment-playbook.md for quarterly cadence.

---

Alignment Score

A quick health check. Score each area 0–10:

AreaQuestionScore
Strategy clarityCan 5 people from different teams state the strategy consistently?/10
Cascade completenessDo all team goals connect to company goals?/10
Conflict detectionHave cross-team OKR conflicts been reviewed and resolved?/10
CoverageDoes each company OKR have explicit team ownership?/10
CommunicationDo teams' behaviors reflect the strategy (not just their stated understanding)?/10

Total: __ / 50

ScoreStatus
45–50Excellent. Maintain the system.
35–44Good. Address specific weak areas.
20–34Misalignment is costing you. Immediate attention required.
< 20Strategic drift. Treat as crisis.

---

Key Questions for Alignment

  • "Ask your newest team member: what is the most important thing the company is trying to achieve right now?"
  • "Which company OKR does your team's top priority support? Can you trace the connection?"
  • "When Team A and Team B both hit their goals, does the company always win? Are there scenarios where they don't?"
  • "What changed in how your team works since the last strategy update?"
  • "Name a decision made last week that was influenced by the company strategy."

Red Flags

  • Teams consistently hit goals while company misses targets
  • Cross-functional projects take 3x longer than expected (coordination failure)
  • Strategy updated quarterly but team priorities don't change
  • "That's a leadership problem, not our problem" attitude at the team level
  • New initiatives announced without connecting them to existing OKRs
  • Department heads optimize for headcount or budget rather than company outcomes

Integration with Other C-Suite Roles

When...Work with...To...
New strategy is setCEO + COOCascade into quarterly rocks before announcing
OKR cycle startsCOORun cross-team conflict check before finalizing
Team consistently misses goalsCHRODiagnose: capability gap or alignment gap?
Silo identifiedCOODesign shared metrics or cross-functional OKRs
Post-M&ACEO + Culture ArchitectDetect strategy conflicts between merged entities

Detailed References

  • scripts/alignment_checker.py — Automated OKR alignment analysis (orphans, conflicts, coverage)
  • references/alignment-playbook.md — Cascade techniques, quarterly alignment check, common patterns

Related skills

FAQ

What is the one-page strategy filter?

strategic-alignment's one-page strategy filter compresses vision, top three quarterly priorities with owners, and a not-doing list onto a single page. If strategy cannot fit one page, the playbook treats it as too unclear to cascade.

How does strategic-alignment detect drift?

strategic-alignment provides drift detection techniques that compare active work against cascaded OKRs and quarterly priorities, surfacing misalignment before teams commit further engineering effort.

Is Strategic Alignment safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.