apex-takeover

Taking ownership of an inherited codebase requires structured reconnaissance to map architecture, dependencies, and security risks. This Skill coordinates a phased takeover workflow, producing a final report with a system map, technical debt inventory, and rollout roadmap.

Auditing infrastructure and CI pipelines for a legacy project involves running deep reconnaissance across infrastructure, CI/CD, and observability layers. This Skill orchestrates that discovery phase to identify risks, map deployment workflows, and generate a comprehensive takeover report.

Performing a security audit on an existing codebase requires mapping security posture and vulnerabilities before modifications. This Skill executes structured reconnaissance across security layers to assess risk, identify technical debt, and define quick wins for stabilization.

Yes, this structured reconnaissance workflow applies to inherited systems across backend services and infrastructure. It coordinates mapping across code, infrastructure, CI pipelines, security, and observability to reconcile ownership comprehensively.

A phased codebase takeover process produces a final synthesis report containing a system map, risk assessment, technical debt inventory, quick wins, and a rollout roadmap. These deliverables reduce ambiguity and guide stabilization after the reconnaissance phase.