What problem does it solve? Engineering teams often carry hidden knowledge gaps: critical modules understood by only one person (bus factor of 1), undocumented architectural decisions, and onboarding that consists of just reading READMEs. This Skill measures shared team understanding, exposes concentrated knowledge risk, and produces a concrete first-week onboarding plan for new engineers. ## Core Features & Use Cases - Structured Audit Interviews: Five targeted questions asked privately to each team member to reveal divergent mental models of architecture, invariants, and risky code. - Risk Heatmap Generation: Produces a module-by-module table of criticality, bus factor, last refactor date, and owner, flagging any high-criticality module with bus factor 1 as a P0 action. - First-Week Onboarding Playbook: Generates a day-by-day operational guide (ADRs to read, pairing sessions, on-call shadowing, first low-risk change) so new hires ship a reviewed change by end of week one. - Use Case: A new developer starts Monday and the billing module is understood only by one senior engineer. Run the audit to map shared architecture understanding, identify the bus-factor risk, and produce a pairing-based onboarding plan that transfers knowledge. ## Quick Start Ask the AI to run a context audit on your team to identify knowledge gaps and create a first-week onboarding plan for a new engineer.
