context-audit

What problem does it solve? Engineering teams often hold critical system knowledge in the heads of a few senior members, creating bus factor risks and slow onboarding for new developers. This Skill measures shared understanding across the team, exposes concentrated knowledge, and produces a concrete first-week onboarding roadmap. ## Core Features & Use Cases - Private Audit Interviews: Runs five structured questions with each team member to detect divergent understanding 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 P0 actions for high-criticality modules with a bus factor of 1. - Onboarding Runbook: Creates a day-by-day first-week plan combining reading, pairing, on-call shadowing, and a reviewed low-risk change. - Use Case: A new developer starts Monday and the billing module is understood by only one person. Use this Skill to audit the team, identify the bus factor risk, and generate a pairing plan so the newcomer ships a reviewed change by Friday. ## Quick Start Audit my team's shared understanding of the codebase and create a first-week onboarding plan for our new engineer.