retro_requirements

# Reverse Requirements Engineering > **CodeOps Skills Version**: 3.19.0 Analyze an existing codebase — any language, any framework — and produce a structured **reconstruction brief** that can be fed to the make_requirements skill to generate formal requirement documents capable of rebuilding the entire application from scratch. > **Resolve output paths layout-aware — ONCE, here.** Everything this skill writes lives in > **the resolved `_retro/` dir**: > > - **Flat layout** (no marker): `requirements/_retro/` > - **Nested layout** (marker present): `codeops/features/<f>/requirements/_retro/` — ask which > feature the reconstruction targets (create it lazily); never guess. > > Detection per **[../../_shared/layout-convention.md](../../_shared/layout-convention.md)**. > Every mention of the `_retro/` dir in this skill and its reference docs (`phases.md`, > `triage-gate.md`) means THIS resolved path — including `_progress.md`, the triage register, > and the reconstruction brief. `--continue` reads `_progress.md` from the same resolved > location. This skill is the **inverse** of the make_requirements skill and **upstream** of the full forward pipeline: ``` Existing Codebase → retro_requirements (THIS skill — reverse-engineer the code) → <resolved _retro dir>/09-reconstruction-brief.md → the make_requirements skill (enrich, validate, formalize into RDs) → the make_plan skill (implementation pipeline → rebuild) ``` ## Core Principle:...