What problem does it solve?
Provides a structured, data-driven assessment to determine whether a codebase should be continued, refactored, rebuilt, forked, extracted from, or abandoned, removing guesswork and sunk-cost bias from project decisions.
Core Features & Use Cases
- Two audit tracks (A/B): Track A for owned projects (refactor vs rebuild) and Track B for external projects (use, fork, extract, or discard).
- Quick automated scan: Project identity, code size, largest files, dependency summary, directory structure, and git activity metrics for a rapid verdict.
- Deep multi‑dimension audit: Optional in‑depth analysis across technical choices, divergence from documented goals, dead code rate, dependency health, test quality, and complexity trends, producing a dated plan or asset extraction list.
- Output plans and asset extractions: Produces actionable plans saved to a standard path and a precise list of files/functions to keep, extract, or remove.
- Use case: Before investing engineering time on a third‑party library or deciding whether to refactor an internal engine, run a quick scan followed by a deep audit to produce a concrete plan.
Quick Start
Ask the skill to run a quick scan and produce a recommendation and a dated plan for the repository, specifying Track A for an owned project or Track B for an external project.
