force-field-analysis

force-field-analysis is a skill for Claude Code, Codex from fzfclee/consulting-skills. It costs 50 tokens per session (729 once invoked), scanned A, original, Apache-2.0.

A method for examining the forces that support or resist a desired change. It considers the people involved, their incentives, limits, and the strength of each force.

In plain words
What is it for?
Use it to diagnose organizational change, stakeholder support, adoption problems, and action plans for shifting behavior or decisions.
Why use it?
It shows why adoption or stakeholder support is stuck and whether reducing resistance would work better than adding pressure.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to diagnose organizational change, stakeholder support, adoption problems, and action plans for shifting behavior or decisions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fzfclee/consulting-skills/force-field-analysis
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add fzfclee/consulting-skills --skill force-field-analysis
Clone the repo
git clone --depth 1 https://github.com/fzfclee/consulting-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for force-field-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/fzfclee/consulting-skills/force-field-analysis/github.svg)](https://agentmods.dev/skills/fzfclee/consulting-skills/force-field-analysis)
Your own site
<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/force-field-analysis"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/force-field-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for force-field-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/force-field-analysis"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/force-field-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 729 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00729
Opus 5 $0.00025 $0.00365
Sonnet 5 $0.00010 $0.00146
Haiku 4.5 $0.00005 $0.00073

Measured 9d ago against content hash dc76409c4096, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

force-field-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/force-field-analysis/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Force Field Analysis

Use this skill to run Force Field Analysis as a practical consulting method, not as a generic framework explanation.

Method Notes

  • List driving and restraining forces separately.
  • Reducing a restraining force is often better than adding pressure.

Required Inputs

Collect or infer these inputs before execution:

  • desired change
  • supporting forces
  • resisting forces
  • stakeholders
  • constraints

If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.

When Not To Use

Do not use when the target change and relevant actors are unclear. Avoid generic pros-and-cons lists: each driving or restraining force needs evidence, relative strength, and a practical response.

Adjacent Methods

  • change-impact-analysis: assess affected groups, readiness, and adoption support.
  • stakeholder-power-map: diagnose named sponsors, blockers, incentives, and vetoes.

Step-by-Step Execution

Step Required input How to execute Output
Define change Desired change, current state, target state. State the behavior or decision that must shift. Change statement.
List driving forces Sponsors, incentives, pressures, benefits. Identify forces pushing toward the change. Driving-force list.
List restraining forces Concerns, incentives, risks, capacity, politics. Identify forces resisting the change. Restraining-force list.
Score forces Force lists and evidence. Rate strength, addressability, owner, and evidence quality. Force field map.
Choose levers Force field map. Decide which restraining forces to reduce and which driving forces to strengthen. Change lever plan.

Output Template

### 1. Change Objective
Desired change:
Current state:
Decision owner:
Time horizon:

### 2. Forces
| Force | Driver / restraint | Strength | Evidence | Controllability |
|---|---|---|---|---|
|  |  |  |  |  |

### 3. Net Diagnosis
Dominant drivers:
Dominant restraints:
Fragile assumptions:

### 4. Intervention Plan
| Force to change | Move | Owner | Timing | Signal / side effect |
|---|---|---|---|---|
|  |  |  |  |  |

### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:

Read the full file on GitHub · 87 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 87 lines · 50 tokens per session scan A dc76409c4096

Subscribe to this mod's changes

force-field-analysis is a skill published in the GitHub repository fzfclee/consulting-skills (4 stars, last pushed 21d ago), licensed Apache-2.0. It adds 50 tokens to every session and 729 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

ppt-keynote

An operating-model redesign for a scaling logistics firm — the diagnosis, the target model, and the transition roadmap. Built as a decision-grade consulting deck for client sponsor, ops leaders.

nexu-io/open-design · 40 tokens

doblin-ten-types

Maps and designs innovation strategy using Doblin's Ten Types of Innovation across Configuration (Profit Model, Network, Structure, Process), Offering (Product Performance, Product System), and Experience (Service, Channel, Brand, Customer Engagement). Use when auditing current innovation profile, identifying…

fatihguner/foreman · 92 tokens

grow-model

Facilitates coaching conversations and structured decision-making using Whitmore's GROW model: Goal (clarify objectives), Reality (assess current state honestly), Options (generate alternatives), and Will (commit to action). Use when coaching team members, making strategic decisions as a founder, breaking through…

fatihguner/foreman · 89 tokens

hackman-enabling-conditions

Diagnoses and designs team effectiveness using Hackman's six enabling conditions: a real team, compelling direction, right people, sound structure, supportive context, and expert coaching. Shifts focus from blaming team members to establishing the structural and environmental conditions that make high performance…

fatihguner/foreman · 99 tokens

myers-briggs-type-indicator

Maps team cognitive diversity using the MBTI four-dichotomy personality framework: Extraversion/Introversion, Sensing/Intuition, Thinking/Feeling, Judging/Perceiving. Use when diagnosing co-founder communication friction, designing cognitively diverse teams, adapting communication style for different audiences…

fatihguner/foreman · 81 tokens

negotiation-mindset-and-self

Builds the internal foundation required before entering any negotiation: identity as a negotiator, strategic self-awareness, emotional self-management, assumption auditing, and deliberate style selection. Provides practical self-assessment checklists and pre-negotiation protocols. Use when preparing mentally for a…

fatihguner/foreman · 101 tokens