菜单
Use when evaluating a strategy or major initiative — to categorize major external forces as tailwinds (working with you) or headwinds (requiring you to overcome), and systematically prefer strategies that work WITH dominant forces rather than against them
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jeffreytse/grimoire-core --skill apply-force-alignment命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when comparing very differently-titled roles for compensation banding, leveling, or organizational design — score each role's inherent Know-How (knowledge, skills, experience required), Problem Solving (complexity and freedom of thinking, scored as a percentage of Know-How), and Accountability (freedom to act and magnitude of impact), because job titles and informal seniority perceptions vary inconsistently across departments and don't provide a comparable basis on their own.
Use when many people request your scarce time, mentorship, or expertise and you cannot evaluate their genuine commitment level from a conversation alone — require a specific, costly, objectively verifiable unit of self-directed output (a set number of completed attempts) before engaging, because genuine commitment is what a conversation cannot reliably reveal but a completed, verifiable body of work can.
Use when deciding how to allocate a manager's or leader's limited time across competing activities — before defaulting to whatever is most urgent, estimate each candidate activity's leverage (how many people's output it affects, for how long, and whether it requires your specific position), because a manager's actual output is the output of the organization under their influence, not their own individual task completion.
基于 SOC 职业分类
正在显示 SKILL.md
| name | apply-force-alignment |
| description | Use when evaluating a strategy or major initiative — to categorize major external forces as tailwinds (working with you) or headwinds (requiring you to overcome), and systematically prefer strategies that work WITH dominant forces rather than against them |
| source | 荀子 (Xunzi) 天论篇 (~3rd century BC) — 天行有常，不因尧存，不因桀亡…制天命而用之; Bezos 2004 Amazon shareholder letter — "work with trends, not against them"; Christensen "The Innovator's Dilemma" (1997) — incumbents fail by fighting disruption rather than riding it; Deming "Out of the Crisis" (1986) — tampering with system forces makes outcomes worse |
| tags | ["strategy","market-forces","competitive-positioning","trend-analysis","organizational-design"] |
| verified | true |
Before committing to a strategy, categorize major external forces as tailwinds or headwinds — and systematically prefer strategies that work WITH dominant forces, because strategies requiring you to overcome major forces cost exponentially more and fail at higher rates than strategies that ride them.
In the 天论篇 (~3rd century BC), Xunzi made an argument unusual for Chinese philosophy: heaven (天) operates by constant, impersonal laws — "天行有常，不因尧存，不因桀亡" (Nature operates by constant laws, unchanged by sage or tyrant). The appropriate response is not reverence or submission, but study and mastery: "大天而思之，孰与物畜而制之" (Better to master natural forces than to revere them passively). "制天命而用之" — control and use what heaven ordains. Xunzi argued that agriculture, medicine, and governance should all be designed to work WITH natural forces rather than hoping for supernatural intervention or fighting forces that cannot be overcome.
This principle maps directly to strategic practice:
Jeff Bezos (2004 Amazon Shareholder Letter): "I work with trends, not against them. When it's raining, I build umbrellas." Amazon's entire expansion logic — AWS, Prime, Amazon Marketplace — was designed to ride demonstrated trends (internet adoption, ecommerce growth, enterprise cloud migration) rather than fight them. Bezos explicitly identified the strategic error of opposing tailwinds as a category of failure.
Clayton Christensen "The Innovator's Dilemma" (Harvard Business School, 1997): The defining error of incumbents facing disruption is fighting the force rather than riding it. Incumbents who try to preserve their position by resisting low-end disruption fail; those who create separate units to ride the disrupting force succeed. The Innovator's Dilemma framework is the standard tool at every major corporate strategy function globally.
Marc Andreessen "Software is eating the world" (2011): Explicitly frames strategy as choosing to align with software-eating forces rather than resist them. This framing became foundational to venture capital portfolio strategy and corporate innovation strategy in technology.
Deming "Out of the Crisis" (1986): The "tampering" principle — adjusting a stable system against its natural forces without a model of how it works — consistently makes outcomes worse. His funnel experiment demonstrates mathematically that fighting system forces produces higher variance and worse mean performance than working with them.
Andy Grove "Only the Paranoid Survive" (1996): Strategic inflection points are force reversals — moments when a major force that was previously a tailwind turns into a headwind, or when a new force emerges. The strategic obligation is to detect these force reversals early and realign, not to resist them. Standard at Intel; now used in semiconductor and technology strategy globally.
Why best: Strategies that oppose major forces require the force to weaken (unpredictable), require extraordinary resource advantage (expensive), or require your opposition to outlast the force (uncertain). Strategies aligned with forces require none of these — the force itself does work on your behalf. Force alignment is not passive: it requires active identification, early positioning, and mechanism design. But the return profile is asymmetrically better than force opposition, across all documented cases.
Distinct from run-scenario-planning: run-scenario-planning develops multiple possible futures and stress-tests plans against each. It answers: "what if the future looks like X?" apply-force-alignment answers: "which major forces are currently active and in what direction — and does this strategy ride or oppose them?" These are complementary: scenario planning maps the futures; force alignment audits structural alignment with current forces.
Distinct from apply-premortem: apply-premortem surfaces specific failure modes of a committed plan before launch. apply-force-alignment is upstream: it audits structural alignment before plan commitment, identifying categories of failure risk caused by force opposition rather than execution errors.
Distinct from apply-win-without-fighting: apply-win-without-fighting is about avoiding direct competitive confrontation by finding indirect paths to victory. apply-force-alignment is about external structural forces (technology curves, market dynamics, regulatory trends, demographic shifts) — not about competitive engagement strategy.
Adopted by: Amazon (Bezos 2004 shareholder letter — "work with trends, not against them"; AWS, Prime, and Marketplace all designed to ride demonstrated forces); Intel (Andy Grove's strategic inflection point framework for detecting force reversals); Clayton Christensen's Innovator's Dilemma framework, standard at every major corporate strategy function globally.
Impact: Amazon's force-aligned strategies (AWS riding enterprise cloud migration, Prime riding ecommerce growth) produced category-defining returns; Christensen documented that incumbents fighting disruption rather than riding it fail at systematically higher rates than those who create separate units aligned with the disrupting force.
Enumerate the major forces in play. For the domain of your strategy, identify forces that are large, sustained, and not under your control. Categories to examine:
For each: name the force, its current direction (growing/declining), and its rate of change. Aim for 3–7 major forces; more than 7 signals insufficient prioritization.
Classify each force as tailwind or headwind for your strategy. A tailwind works in the same direction as your strategy — it does work on your behalf and your strategy captures its energy. A headwind opposes your strategy — your strategy must overcome it or it accumulates cost over time. Be precise: the same force can be a tailwind for one strategy and a headwind for an alternative.
Score the force-alignment profile. Count tailwinds and headwinds. Categorize their magnitude (major vs. minor). A force-misaligned strategy has major headwinds and few tailwinds. A force-aligned strategy has major tailwinds and manageable headwinds. No strategy achieves perfect alignment — the question is the profile.
For each headwind: require a credible mechanism. If you choose a strategy with a headwind, articulate the specific mechanism by which you will overcome or neutralize it. "We will be very good at X" is not a mechanism. A mechanism specifies: who does what, with what resources, by what measurement, over what time horizon. If you cannot specify a credible mechanism for a major headwind, the strategy is unlikely to succeed.
Where multiple strategy options exist, prefer the force-aligned one. When evaluating strategy alternatives, use force-alignment as a primary decision criterion, not a secondary check. Two strategies with similar expected value under current conditions have very different expected value under force dynamics — the aligned strategy compounds; the opposed strategy erodes.
Detect force reversals early. Major forces do reverse — technology becomes commoditized, regulation shifts, demographics change. Monitor leading indicators of force reversal (Christensen's strategic inflection points, Grove's "10x" signals). When a force reversal is detected, treat it as a strategy invalidation event requiring force-alignment re-audit, not a temporary perturbation requiring tactical adjustment.
Market entry: A company evaluates two market entry options. Option A targets a market with strong demand growth (tailwind), where the company's technology capabilities are aligned with the market's technology adoption curve (tailwind), but where regulation is tightening (headwind). Option B targets a shrinking market where the company has an existing customer base (tailwind) but must overcome a dominant incumbent's network effects (major headwind) and an unfavorable cost structure (headwind). Force alignment analysis: Option A has 2 tailwinds, 1 headwind with identifiable mechanism (regulatory affairs team). Option B has 1 tailwind, 2 major headwinds without credible mechanisms. Enter Option A.
Product strategy: A software company must decide whether to build native AI capabilities or acquire an AI company. Force: AI capability is advancing rapidly (force direction: AI becomes cheaper and more accessible over time). Building native: requires sustained R&D investment opposing the force (cost increases as the frontier advances). Acquiring: rides the force by assembling existing capability. Force alignment favors acquisition or integration over building from scratch, unless the company has a specific force-capture mechanism (proprietary data that improves with scale).
Fundraising timing: A founder evaluates when to raise a growth round. Forces: interest rates (headwind — capital is expensive), AI adoption in their sector (tailwind — accelerating), public market multiples (headwind — compressed). Force-aligned timing: raise when the sector tailwind is demonstrably strong (validation reduces headwind of expensive capital). Wait for a demonstrable AI-use-case win before accessing capital markets.
Organizational change: A new COO proposes restructuring the company from functional to product-based organization. Forces: the company is scaling rapidly (tailwind for product structure — functional structures become bottlenecks at scale), the existing leadership team has deep functional expertise (headwind — capability base is not aligned with product structure). Force alignment: the tailwind is stronger and growing; the headwind is manageable with a transition timeline and product-manager hiring. Proceed with the restructure with an explicit 18-month hiring mechanism.
Design the business model to capture force energy. The most durable strategies are not merely aligned with forces but designed to accelerate force capture — so that as the force grows stronger, the strategy benefits more. AWS was not merely aligned with cloud migration; it was designed so that every enterprise that migrated to cloud increased AWS's capabilities, scale, and cost advantage, which accelerated further migration.
