What problem does it solve? Starting a reverse engineering analysis on an unfamiliar legacy codebase is slow and error-prone without an initial inventory. This Skill automates the reconnaissance phase by scanning the project surface and producing structured artifacts that downstream agents and humans can consume. ## Core Features & Use Cases - Project Surface Mapping: Lists the full directory tree (excluding noise like node_modules and .git), counts files by language, and identifies frameworks, package managers, and dependency versions from manifest files. - Entry Point & Infrastructure Detection: Locates application entry files, config files, CI/CD pipelines, Dockerfiles, database schema hints, and test coverage estimates. - Spec Organization Suggestion: Applies ordered heuristics (endpoint, module, use-case, hybrid, feature) to recommend how specs should be organized, with evidence-backed signals. - Use Case: When beginning a reverse engineering engagement on a legacy monorepo, run this Skill first to generate inventory.md, dependencies.md, and a machine-readable surface.json that later analysis agents use as shared context. ## Quick Start Scan this legacy project and generate the initial inventory, dependency report, and surface.json context file in the reversa output folders.