the-org-simulator
Stress-test a proposed org change before announcing it — simulate who gains, who loses, who blocks, where friction erupts in the first 90 days, and run the memo leak test: how does this land when it leaks before you announce it? Use when planning a reorg, changing reporting lines, merging or splitting teams, moving a function, or 'how will this org change land?'. Produces a winners/losers map, a friction forecast, the leak-test read, and a sequenced announcement plan.
npx skills add mohitagw15856/pm-claude-skills --skill the-org-simulator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# The Org Simulator Skill Org changes are designed on the box-and-line level and experienced on the who-do-I-report-to-now level. The gap between those two is where reorgs fail: the map made sense, but the two best engineers quit, the middle managers went quiet, and the memo leaked on Tuesday before the Thursday announcement. This skill simulates the experienced version before the announced version exists — seat by seat for the key people, faction by faction for the rest, plus the one test almost nobody runs: reading the memo as the person it demotes, on a screenshot, out of context. ## What This Skill Produces - A **winners / losers / undecided map** — by named seat for key people, by group for the rest: what each actually loses or gains (scope, status, access, headcount, identity), not what the memo says they gain - A **friction forecast**: the 5–8 specific breakpoints of the first 90 days, each with likelihood, blast radius, and the cheap preventative - The **leak test**: the announcement read as a screenshot by its least charitable reader, plus what the corridor version of it will say by Friday - A **sequenced rollout plan**: who hears it in which order, from whom, with the one
- What This Skill Produces
- Required Inputs
- Process
- Output Format
- Quality Checks
- Anti-Patterns
- Related
What does the the-org-simulator skill do?
Stress-test a proposed org change before announcing it — simulate who gains, who loses, who blocks, where friction erupts in the first 90 days, and run the memo leak test: how does this land when it leaks before you announce it? Use when planning a reorg, changing reporting lines, merging or splitting teams, moving a function, or 'how will this org change land?'. Produces a winners/losers map, a friction forecast, the leak-test read, and a sequenced announcement plan.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill the-org-simulator --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 mohitagw15856/pm-claude-skills, a repository with 1,255 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.