create-brownfield-prd

A brownfield PRD documents an existing system's current state by analyzing the codebase to extract features, identify gaps, and prioritize modernization opportunities. This approach produces a formal requirements document from reverse-engineered architectural analysis, enabling evidence-based planning for legacy systems lacking initial specifications.

Confidence scoring quantifies the reliability of extracted features and modernization recommendations based on codebase analysis depth. High scores indicate features validated across multiple code patterns; low scores flag areas needing stakeholder validation before committing resources to modernization roadmap decisions.

Yes. A brownfield PRD identifies core features worth preserving, legacy components candidates for replacement, dependencies between systems, and gaps in functionality. The modernization roadmap prioritizes these findings with confidence scoring, enabling phased migration strategies that balance risk and business value.

Brownfield PRD generation requires prior codebase analysis and architectural documentation as input. The Skill depends on project analysis and architecture review outputs to extract feature inventories, dependency maps, and gap assessments needed to produce the PRD with confidence metrics.

After generating the PRD, use confidence scores to prioritize validation with stakeholders and product owners. Output includes modernization roadmap, feature categorization, and risk assessments that feed into architectural redesign, technical debt prioritization, or migration planning workflows.

A brownfield PRD reverse-engineers requirements from existing code rather than collecting them upfront, making it suited for legacy systems where documentation is missing or outdated. This evidence-based approach reduces assumptions, captures actual system behavior, and provides confidence metrics for validation planning.