reverse-engineering

Reverse-engineering a brownfield codebase involves walking the V-Model backward from Coding up to Business Analysis. This Skill analyzes your codebase to generate structured documentation, proving every step from existing code.

The V-Model backward walk is a code analysis technique that traces existing code back up to Business Analysis. It generates proven artifacts like plan-context, ADRs, arc42 snapshots, and BA drafts from the existing codebase.

Yes, you can generate a stable project context and backlog seed from an existing codebase. The Skill creates a BACKLOG.md file serving as a single source of truth for status, phase, and claims.

Yes, this reverse-engineering approach is specifically designed for brownfield projects. It analyzes existing codebase structure and content to produce structured documentation and wayfinder layers for token-efficient context.

Codebase reverse engineering generates V-Model artifacts including plan-context, ADRs, arc42 snapshots, FEATURE inventories, backlog seeds, and BA drafts. These provide a stable, shared project context for team validation.

Wayfinder layers are produced as the primary output of reverse engineering to offer token-efficient project context. They enable subsequent V-Model phases to navigate the codebase without consuming excessive tokens.