What problem does it solve? Teams rarely have an accurate, code-grounded answer to "what does this software actually do" — the README describes aspirations, and no one has read every handler. This Skill produces a maintainer-grade functional description derived from the code itself, including hidden features and places where documentation and code disagree. ## Core Features & Use Cases - Feature and entry-point inventory: Enumerates CLI commands, routes, UI screens, hooks, and config keys from registration tables, then describes the 10-20 features that carry the product with evidence citations. - Workflow and data mapping: Reconstructs 3-6 end-to-end user workflows, inventories data stores and their lifecycles, and maps external integrations with their failure behavior. - Hidden functionality and doc-vs-code gaps: Finds feature flags, dormant commands, stubs, and every place the README or help text promises something the code does not do. - Use Case: During a handover or due diligence, run the scan against a repository with a Sokrates _sokrates analysis to get a validated functionality-scan.json report and an interactive explorer page describing what the software does. ## Quick Start Ask the AI to run the functionality scan on this repository and report what the software does, its main features, and where the documentation disagrees with the code.