本文へ移動
cccskills

「org-design」の検索結果

5 件 ・ 関連度順

概要と使いどころ

Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Help users design high-performing product and engineering organizations by choosing the right reporting models, team sizes, and cross-functional partnerships. It focuses on reducing friction and maximizing ownership through structural clarity.

日本語の概要は準備中です。原文の説明を表示しています。

RefoundAI/lenny-skills1,3892026年7月17日 更新

AI leadership advisor on AI strategy, governance, risk, investment, and org design. Use when defining an AI strategy, building an AI governance program, scoring AI maturity, or drafting an AI risk register.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

Use when designing organizational structure (team topologies, Conway's Law alignment), mapping stakeholders by power-interest for change initiatives, defining team interface contracts (APIs, SLAs, decision rights, handoffs), assessing capability maturity (DORA, CMMC, agile maturity models), planning org restructures (functional to product teams, platform teams, shared services), or when user mentions "org design", "team structure", "stakeholder map", "team interfaces", "capability maturity", "Conway's Law", or "RACI".

日本語の概要は準備中です。原文の説明を表示しています。

nicepkg/ai-workflow2852026年1月20日 更新

Use when shaping team structure — functional vs squad, span-of-control, reorg cost, Conway-aware boundaries. Triggers on 'should we reorg', 'how do we split this team'.

日本語の概要は準備中です。原文の説明を表示しています。

event4u-app/agent-config112026年10月13日 更新