Package a hard-won way of working so the whole team — and their agents — inherit it for free.
The team friction One person figures out a genuinely good workflow — the prompt that nails the migration, the agent setup that produces clean tests, the local tooling that just works. It stays theirs. Everyone else re-discovers it slowly or never, and the team’s collective capability lags its best member by months. With agents, this gap widens fast: skill in how to drive them is the new differentiator, and it’s the least shared.
The pattern The team treats reusable skill as a shared artifact: capture it where others (and their agents) pick it up automatically — committed into the product repository, or as a plugin published on the marketplace. A teammate gets the capability by using the repo, not by attending a brownbag they forgot. Codify the workflow once; the team inherits it.
Why it works with AI Agent know-how is unusually packageable — much of it is prompts, configs, and scripts, which are already shareable as code. So the team can distribute capability mechanically instead of hoping it spreads by osmosis. Shared tooling raises everyone’s floor to the best person’s level.
Watch-outs A shared skill needs an owner and upkeep, or it rots into a trap that teaches the old way. Share the reusable ones; not every personal trick deserves the packaging overhead.
Related Reshape roles — drop the silos · Agent-written shared docs · Current-architecture workshop