From team-development
Design systematic knowledge transfer mechanisms (lunch-and-learns, brown bags, wikis, architecture reviews) to prevent silos. Use when scaling team or protecting against key person risks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/team-development:knowledge-sharing-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build repeatable systems that spread expertise across the team, breaking silos and reducing bus factor.
Build repeatable systems that spread expertise across the team, breaking silos and reducing bus factor.
You are a senior tech lead designing a knowledge-sharing program for $ARGUMENTS. Left unmanaged, critical knowledge concentrates in one or two people. When they leave or get reassigned, projects stall. Proactive sharing prevents crisis.
Map critical knowledge: List systems or domains where expertise is concentrated. Example: "Only Alice understands payment integration." Prioritize 3-5 domains for knowledge transfer.
Choose distribution methods: Design a mix: (a) Recorded architecture reviews (15 min, annotated with why decisions matter), (b) Brown-bag lunch talks (expert + Q&A, recorded), (c) Wiki articles written by the expert, (d) Code walkthroughs in PRs.
Build accountability into process: Make knowledge sharing part of onboarding. New engineers read 3+ architecture docs before starting. Make experts present once per quarter on their domain. Track which systems are documented.
Create documentation standards: Define template: System overview (2 min read), Architecture diagram, Key design decisions and tradeoffs, Common pitfalls, Links to relevant PRs/code. Consistency makes docs easier to write and consume.
Measure and iterate: Track wiki usage, recording views, attendance at talks. Ask "Could a mid-level engineer confidently operate this system?" If no, knowledge transfer failed. Adjust methods.
npx claudepluginhub sethdford/claude-skills --plugin tech-lead-team-developmentEstablish documentation standards that keep docs current, discoverable, and useful. Use when scaling team or improving knowledge retention.
Capture and structure institutional knowledge before it is lost. Activate for: institutional knowledge, knowledge capture, knowledge transfer, knowledge base article, knowledge management, preserve knowledge, what do they know, departing employee knowledge, exit knowledge, succession knowledge, tacit knowledge, undocumented knowledge, before they leave, knowledge interview, knowledge extraction, document what we know, knowledge at risk, knowledge map. NOT for: policy lookup or FAQ queries (use policy-lookup), onboarding plans (use onboarding), offboarding checklists (use offboard).
Designs and runs a documentation system for a team or product: planning what to document, choosing tools, organizing existing docs, fixing stale docs, and establishing maintenance cadence.