code-Spec: Reverse-Engineering the Specification Nobody Kept

The missing document

Every legacy module was built to a specification that no longer exists. Rebuilding or extending it means rediscovering what it does — usually by reading code and guessing intent. code-Spec removes the guessing.

Assembled from the graph

Point code-Spec at a module and it assembles the as-is spec from real facts: its purpose, its screens by role, the fields users fill, the tables it touches with their actual reference data, the reconstructed relationships, and any PII involved.

The contract for change

That spec is the document a rewrite must match and the brief a new developer needs. It's not someone's interpretation — it's the module's real behavior, extracted and written down.

Both directions

code-Spec runs forward too: author a specification for a new feature, grounded against the existing system so it reuses what's already there. Reverse for what exists, forward for what's next — the same engine, closing the loop between understanding and building.