Strategic Alignment
Cascade strategy from boardroom to IC, detect and fix misalignment.
$skillfish add ~skills/strategic-alignment What This Skill Can Do
Concrete capabilities you get when you install this skill.
Design OKR systems that cascade from company to team to individual
Diagnose misalignment between strategy, priorities, and execution
Facilitate cross-functional alignment sessions and resolve priority conflicts
Build strategy communication frameworks for all-hands and team meetings
Track strategic progress against annual and quarterly goals
Design planning cycles (annual, quarterly) with clear input/output expectations
Real Conversations
See how the Strategic Alignment skill responds to actual requests. These are representative examples of what your AI agent will produce.
We set Q1 OKRs in January — company-level stuff like 'reach $2.5M ARR' and 'improve NRR to 115%'. It's mid-February and when I look at what ICs are actually working on, half of it has nothing to do with our OKRs. How do I fix this without micromanaging?
The OKR-to-IC gap is almost always a design problem, not a motivation problem. Here's how to diagnose and fix it.
Root Cause Audit (run this first):
Ask 5 random ICs: "What are you working on this week, and which company OKR does it connect to?"
If they can't answer, you have one of three problems:
- Cascade failure — OKRs weren't translated to team-level and then IC-level key results
- Backlog contamination — old priorities are still in the queue and nobody pruned them
- Missing context — ICs know the OKR but don't understand the connection to their daily work
The Cascade Architecture:
Company OKR: Reach $2.5M ARR
→ Sales KR: 12 new logos in Q1
→ AE task: 3 demos/week minimum
→ Product KR: Ship 2 top-requested features (linked to win/loss data)
→ Eng task: Feature X in sprint 3, Feature Y in sprint 5
→ CS KR: NRR to 115%
→ CSM task: QBR for all accounts >$10K by March 15
Fix without micromanaging:
- Weekly 15-min OKR pulse in team standups: "What did you ship this week toward [KR]?" — makes the link visible without policing
- Prune the backlog — anything not connected to a Q1 OKR gets labeled "Q2 candidate" and removed from active sprints
- One-pager per OKR — explain WHY the OKR matters and what "done" looks like for each IC role
How are your team leads currently tracking progress — do you have any OKR tooling?
Get Started
How to install and use this skill in your preferred environment.
Skills are designed for AI coding agents (Claude Code, Cursor, Windsurf) and IDE-based workflows where the agent can read files, run scripts, and act on your codebase. Web-based AI can use the knowledge and frameworks, but won't have tool access.
Models & Context
Which AI models and context windows work best with this skill.
Recommended Models
Larger models produce more detailed, production-ready outputs.
Context Window
This skill's SKILL.md is typically 3–10 KB — fits in any modern context window.
All current frontier models (Claude, GPT, Gemini) support 100K+ context. Use the full window for complex multi-service work.
Pro tips for best results
Be specific
Include numbers — users, budget, RPS — so the skill can size the architecture.
Share constraints
Compliance needs, team size, and existing stack all improve the output.
Iterate
Start with a high-level design, then ask follow-ups for IaC, cost analysis, or security review.
Combine skills
Pair with companion skills below for end-to-end coverage.
Ready to try Strategic Alignment?
Install the skill and start getting expert-level guidance in your workflow — any agent, any IDE.
$skillfish add ~skills/strategic-alignment