up-recovering-specs-from-code

Recovers the specifications of an existing system from its code and running behavior: actors from authorization, a use case map from server, front-end and hosted-service entry points grouped by user goal, an entity model from the schema in the project's own words, and use case specifications at the depth the owner chooses (a short baseline for every use case, or full ones where change is coming), written at business level with implementation detail kept out by check. Keeps an evidence ledger and a list of suspect behavior instead of correcting anything, prepares the two-role baseline review (what the system does versus what it was meant to do) and the first change log, and pins current behavior with tests before the first change. Use when the user wants to reverse-engineer, document, baseline or onboard a legacy or brownfield codebase into use cases, bring an existing project under spec-driven development, or extract the business rules from existing code, even from a single class or service.