What problem does it solve? Starting a reverse engineering analysis on an unfamiliar legacy codebase is slow and error-prone: you must manually discover the folder structure, languages, frameworks, dependencies, and entry points before any real documentation work can begin. This Skill automates that initial reconnaissance phase. ## Core Features & Use Cases - Project Surface Mapping: Lists the full directory tree (excluding noise like node_modules and build outputs), counts files by language, and identifies frameworks and package managers from config files like package.json, requirements.txt, and pom.xml. - Entry Point & Infrastructure Detection: Finds application entry 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 reverse-engineered specs should be organized, with evidence-backed rationale. - Use Case: When onboarding to an undocumented legacy system, run this Skill first to generate inventory.md, dependencies.md, and a structured surface.json that downstream analysis agents consume. ## Quick Start Ask the agent to run the reversa-scout reconnaissance on this repository to generate the initial project inventory and surface.json context file.
