knowledge-sharing

Diagnose engineering knowledge silos and implement cross-team documentation and onboarding mechanisms.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imsus/cto --skill knowledge-sharing-imsus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-sharing
Source: https://github.com/imsus/cto/tree/main/.agents/skills/knowledge-sharing
Command: npx skills add https://github.com/imsus/cto --skill knowledge-sharing-imsus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps engineering managers break down knowledge silos by replacing tribal knowledge with lightweight cross-team flow, durable documentation, and structured onboarding.

Core Features & Use Cases

  • Root-cause silo diagnosis: Identifies whether the bottleneck is horizontal information flow, documentation practices, onboarding, or cross-team “us vs. them” incentives.
  • Engineering Guilds framework: Establishes cross-team domain groups with the strategic alignment, recognition, and member freedom needed to produce real outputs.
  • Minimum-viable documentation via ADRs: Implements a just-enough documentation culture that preserves decision rationale and key protocols using Architecture Decision Records.
  • Structured onboarding model: Reduces ramp time through buddy-led pair programming plus domain deep dives and cross-team introductions.
  • Cross-team request decision framework: Guides faster, clearer handling of incoming requests (no attention, delayed attention, or prioritization) to prevent hidden cost of ambiguity.

Quick Start

Ask: "I need help reducing knowledge silos across our engineering teams—what should we change first, and what exact mechanism should we implement this month?"

Frequently Asked Questions about knowledge-sharing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down engineering knowledge silos across multiple teams?

Improve cross-team collaboration by establishing a request decision framework that clarifies handling for no attention, delayed attention, or prioritization cases, preventing the hidden costs of ambiguity and reducing stalled requests.

What is the best way to reduce new hire ramp time during engineering onboarding?

Implement a structured onboarding model featuring buddy-led pair programming, domain deep dives, and cross-team introductions to accelerate knowledge transfer and reduce ramp time for new engineering hires.

How do I create a documentation culture that engineers actually follow?

Adopt minimum-viable documentation using Architecture Decision Records to capture decision rationale and key protocols, establishing a just-enough documentation culture that engineers will actually maintain without bureaucracy.

How do engineering guilds improve cross-team collaboration?

Engineering guilds improve cross-team collaboration by establishing cross-functional domain groups with strategic alignment, member freedom, and recognition, enabling teams to produce real shared outputs and break down silos.

How do I fix cross-team collaboration when requests stall or get delayed?

Fix stalled cross-team requests by applying a structured decision framework that guides faster, clearer handling of incoming requests based on attention and prioritization, eliminating the hidden cost of ambiguity.