adlc-product-init

Reverse-engineering product decisions from an existing codebase involves generating Product Decision Records (PDRs) that infer implicit choices from code and documentation, assigning confidence levels, and writing non-destructive drafts for validation.

Product Decision Records (PDRs) are structured documents that clarify implicit product choices. You need them for brownfield projects to extract inferred decisions from existing artifacts, ensuring team alignment through evidence-based documentation.

You can generate PDR drafts non-destructively by analyzing existing documentation and code, then writing the inferred product decisions to a designated drafts directory within your repository root for safe review.

Yes, you can infer product decisions from code and docs for projects lacking clear specifications. The process extracts implicit decisions from artifacts, assigns confidence levels to the findings, and creates drafts for team clarification.

To validate inferred product decisions extracted from a legacy codebase, the generated PDR drafts are prepared for an auto-hand-off clarification phase, allowing your team to review evidence-based findings and confirm alignment.