retro_requirementslisted

Reverse-engineer an existing codebase into structured requirements. Use for "retro_requirements", "reverse requirements", "reconstruct requirements from code", "requirements archaeology", or "reverse-engineer this codebase". Trigger when the user wants to reconstruct requirements from an existing, undocumented, or legacy codebase — for documentation, migration, or a from-scratch rebuild — e.g. "document what this app does", "extract requirements from this code", "reverse-engineer this service into a spec". Analyzes any language/framework through a 9-phase archaeology pipeline and produces a reconstruction brief that feeds the make_requirements skill. Extracts WHAT the system does (not HOW), classifies every behavior by confidence (✅/⚠️/🔴), and enforces a hard Bug-or-Feature Triage Gate so bugs are never silently documented as features. Supports --scope <path> to analyze one module/package and --continue to resume an interrupted session.
blendsdk/claude-codeops · ★ 4 · AI & Automation · score 75

Install: claude install-skill blendsdk/claude-codeops

# Reverse Requirements Engineering > **CodeOps Skills Version**: 3.20.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: