principal-code-analyst

What problem does it solve?

This Skill helps you understand whether a subsystem is structurally healthy or costly to change by connecting code-level details to architecture, risk, ownership, reliability, performance, and maintenance burden.

Core Features & Use Cases

• Principal-level assessment: Explains what is wrong, what it costs, and what to fix first for a subsystem or codebase area.
• Architecture and risk mapping: Produces an as-is architecture view, a risk register with evidence, tradeoffs, and a small-step remediation sequence.
• Decision support: Useful for technical due diligence, fragile code areas, expensive subsystems, or prioritizing limited engineering effort.
• Validation planning: Recommends observable signals to confirm each remediation step worked.

Quick Start

Ask for a principal-level analysis of the subsystem you are worried about, including the decision it should inform, the top risks, and the first small fixes to make.