Skills: Everyone's job, no one's responsibility
Skills are the knowledge that defines how your team works: architecture decisions, coding conventions, and other practices packaged into Markdown documents.
Skills are becoming increasingly important in the age of AI. The difference between generic AI slop and useful output is often the quality of the team's shared skills.
The challenge is that skills fall into the same category as documentation. Everyone wants them, but nobody is excited or obligated maintain them. This creates an ownership problem. Teams rely on skills every day, but the work of capturing and maintaining them is easy to postpone. Eventually knowledge ends up scattered across pull requests, Slack messages, and a handful of experienced engineers.
Documentation teams have tackled this problem in a few different ways:
- Documentation is treated as part of the Definition of Done. Work isn't complete until the knowledge is captured.
- Documentation owners review changes just like code reviewers review pull requests.
- Teams measure and reward knowledge sharing, making it visible work rather than invisible effort.
Skills need similar treatment. Shared ownership sounds good in theory, but in practice the teams that succeed find ways to make maintaining skills part of everyday work rather than an occasional clean-up exercise.
Shared skills are an investment that keeps paying back.
Interested in how we manage team knowledge? Get in touch.