design-organizational-structure

design-organizational-structure is a skill for Claude Code from jeffreytse/grimoire-core. It costs 27 tokens per session (1,087 once invoked), scanned A, original, MIT.

A guide for designing an organisation’s reporting lines, team structure, and division of responsibilities around its strategy.

In plain words
What is it for?
Use it to create, review, or restructure departments, reporting relationships, decision rights, and team responsibilities.
Why use it?
It helps prevent unclear authority, duplicated work, and slow decisions caused by a structure that does not match how the organisation needs to operate.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 156 skills shipped together

Good fit Use it to create, review, or restructure departments, reporting relationships, decision rights, and team responsibilities.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/design-organizational-structure
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 jeffreytse/grimoire-core --skill design-organizational-structure
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 156 skills.

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 design-organizational-structure

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-organizational-structure/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/design-organizational-structure)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-organizational-structure"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-organizational-structure/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 design-organizational-structure

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-organizational-structure"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-organizational-structure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,087 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.00027 $0.01087
Opus 5.5 $0.00011 $0.00435
Sonnet 5.5 $0.00005 $0.00217
Haiku 4.5 $0.00003 $0.00109

Measured 1mo ago against content hash 49cb8cc6eac8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-organizational-structure 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 1mo 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/business/leadership/skills/design-organizational-structure/SKILL.md · 63 lines

How it starts

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

Design Organizational Structure

Design an organizational structure that aligns authority, accountability, and coordination mechanisms with strategic priorities.

Why This Is Best Practice

Adopted by: McKinsey & Company, Bain, Deloitte, and enterprises undergoing growth-stage or strategic restructuring Impact: Galbraith research shows misaligned org structures cause 30–50% productivity loss through coordination overhead. McKinsey data shows organizations that realign structure to strategy see 20–30% faster execution on strategic initiatives. Mintzberg demonstrated that structure misaligned to context causes systematic dysfunction regardless of individual talent. Why best: Structure is not neutral — it determines information flow, decision speed, collaboration patterns, and what behaviors get rewarded. Deliberate structure design produces outcomes; default structure produces the org chart equivalent of technical debt.

Sources: Mintzberg "The Structuring of Organizations" (1979); Galbraith "Designing Organizations" (3rd ed., 2014); McKinsey "Organizational Design for Innovation" (2020)

Steps

  1. Start with strategy, not structure — identify the organization's primary source of competitive advantage: product innovation, operational efficiency, customer intimacy, or geographic expansion. Structure must enable the strategy; not the reverse.

  2. Audit the current state — map the current org chart, decision rights (RACI or DACI), and coordination mechanisms. Identify structural pain points: decision bottlenecks, duplication of effort, chronic cross-team friction, unclear accountability.

  3. Select the primary structural dimension — choose one primary axis: (a) functional (by discipline: engineering, sales, finance), (b) product/BU (by product line or business unit), (c) geographic (by region), or (d) matrix (dual reporting on two axes). The primary dimension reflects the most critical coordination requirement.

  4. Design for key cross-cutting needs — identify the 2–3 coordination challenges that the primary structure creates. Design secondary mechanisms: shared services, communities of practice, cross-functional teams, integration roles, or overlay processes.

Read the full file on GitHub · 63 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. 1mo ago First seen · 63 lines · 27 tokens per session scan A 49cb8cc6eac8

Subscribe to this mod's changes

design-organizational-structure is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 1,087 once invoked, about $0.0001 per session on Opus 5.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-09-03.