Point it at a legacy module and it writes the as-is specification — purpose, screens by role, the fields users fill, the tables and real reference data, reconstructed relationships and PII. Then author specs for brand-new features grounded in the same system.
Every module gets a spec.md — purpose, screens, fields, tables, the actual reference codes, and PII — assembled from the graph, not guessed.
code-Spec runs both ways: reverse for legacy (KB → spec) and forward for new development (spec → build → back into the KB).
Book a walkthrough with our team — bring your hardest legacy app and we'll map it live.
Code