本文へ移動
cccskills
無料GitHub で公開

learning-and-development

Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md3.9 KB
  • references/sources.md1.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Learning and development

Training is the most reliably wasted budget in an organization, because attendance is easy to measure and transfer to the job is not.

Start from the capability gap

Training is a solution. Establish the problem first: what should people be able to do that they cannot, and is the cause actually capability?

Frequently it is not. If someone knows how but does not, look for the real obstacle — no time, a process that makes the right thing harder, an incentive pointing elsewhere, or no feedback on whether they did it correctly. Training a motivation or system problem changes nothing and consumes the budget that would have fixed it.

Design for transfer

Most of what people can actually do is learned by doing it, with feedback, on real work. Formal instruction is a small part and it decays quickly without application.

So: teach close to the moment of use, give people real work immediately afterwards, and arrange feedback from someone competent. A course two months before the work is entertainment.

Measure transfer, not satisfaction. Whether attendees enjoyed it is uncorrelated with whether they now do the job differently. Ask their manager at ninety days what changed.

Career frameworks

A framework answers what is expected at each level and what growth looks like. It carries weight far beyond development — it drives compensation bands, promotion decisions, and whether people believe progression is fair. It should be built with people:compensation-and-leveling, not separately.

Make it observable. Levels described by scope, autonomy and impact can be assessed; levels described by seniority adjectives cannot, and collapse into tenure.

Provide a path that is not management. Forcing the best practitioners into management to progress is how organizations lose their best practitioners and gain mediocre managers.

Internal mobility

Internal moves are usually cheaper and lower-risk than external hiring, and they are the main reason capable people stay. The obstacle is almost always managers hoarding talent, which is rational for the manager and expensive for the company.

Fix the incentive rather than the policy: make developing and releasing people something managers are evaluated on. A mobility policy that costs a manager their best person and gives them nothing will be quietly resisted, and quiet resistance always wins.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Tooling

Delivery: TalentLMS, Docebo, WorkRamp, Absorb, and similar; smaller organizations often do better with a structured path built in the tools people already use than with a platform nobody visits.

Content libraries: LinkedIn Learning, Coursera, Pluralsight, Udemy Business, and similar. Licensed libraries buy breadth and almost never buy transfer — completion rates on self-serve content are low everywhere, and the ones that work are assigned against a named capability gap.

Skills and career frameworks: the HRIS's own, or a maintained document. The framework matters more than the software holding it.

Never

  • Deliver training for a problem that is not a capability problem.
  • Measure a program by satisfaction scores.
  • Write levels in adjectives rather than observable scope and impact.
  • Make management the only route to progression.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

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

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

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

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

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

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

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

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

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

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

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

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

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

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

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

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

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

cbrock84 のスキルをすべて見る

このスキルの問題を報告する