reverse

To reverse engineer a legacy codebase, run `/reverse` in the project root to extract logic, data, and runtime specifications. This generates SDD specifications by analyzing APIs, database schemas, ORM models, and runtime configurations.

Code archaeology is the process of excavating undocumented software systems to generate comprehensive specifications. You need it when inheriting legacy systems lacking documentation, enabling faster onboarding and maintenance through extracted logic, data models, and runtime baselines.

Yes, you can extract data models by scanning database schemas, ORM models, and migrations. The analysis reverse engineers these data structures to generate comprehensive data model specifications as part of the system documentation.

Generating API definitions and module flows requires analyzing existing source code logic. The analysis extracts APIs, modules, and flows to produce logic specifications, with strict anti-hallucination rules ensuring all outputs include source attribution.

Yes, runtime analysis works by inspecting runtime configurations, logs, and infrastructure to establish a runtime baseline. This dimension examines deployment topology, dependencies, and environment setups to document the system's operational state.

The best way to document an undocumented inherited system is performing a full 3-dimension analysis covering logic, data, and runtime. This produces comprehensive SDD specifications including API definitions, data models, and runtime baselines for onboarding.