reverse-engineering

To generate V-Model artifacts from a legacy codebase, you provide codebase references, existing documentation, and specific source sections. The Skill derives plan-context, ADRs, arc42 snapshots, and backlog seeds with mandatory traceability to the proven evidence.

Reverse engineering a codebase for V-Model traceability is the process of deriving missing project artifacts like ADRs and arc42 snapshots from existing source code. It identifies and documents traceable evidence to reconstruct a complete V-Model context for brownfield projects.

Yes, you can use reverse engineering to create arc42 snapshots and backlog seeds for brownfield projects. The Skill automates the generation of these artifacts from existing code paths and documentation, ensuring they are traceable to the original source sections.

You need proof-based input sources to derive ADRs and plan-context from a codebase. Required inputs include specific code paths, existing documentation, and source sections that serve as traceable evidence for generating the V-Model artifacts.

You should not use codebase reverse engineering when proof-based input sources like code paths, docs, and source sections are unavailable. The Skill requires concrete evidence to enforce traceability rules and cannot generate V-Model artifacts from unsupported assumptions.

The best way to document traceable evidence in a legacy repository is by deriving a complete V-Model artefact context. This process outputs artifacts with mandatory frontmatter discipline and traceability rules, linking ADRs and backlog seeds directly to source code.