create-brownfield-prd

Analyze a legacy codebase and generate a structured brownfield PRD.

1|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill create-brownfield-prd-acidicsoil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-brownfield-prd
Source: https://github.com/AcidicSoil/lms-llmsTxt/tree/main/.claude/skills/create-brownfield-prd
Command: npx skills add https://github.com/AcidicSoil/lms-llmsTxt --skill create-brownfield-prd-acidicsoil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of Brownfield PRDs by analyzing an existing codebase, extracting features and gaps, scoring confidence, and delivering a structured PRD to guide modernization.

Core Features & Use Cases

  • Step 1: Codebase Analysis to identify project structure, tech stack, and data models.
  • Step 2: Feature Extraction to map code components to user-facing capabilities and categorize them (Core/Secondary/Legacy).
  • Step 3: User Flow Reconstruction to outline end-to-end journeys from routes and UI components.
  • Step 4: PRD Generation to compile a comprehensive brownfield PRD document (docs/brownfield-prd.md) with sections and confidence scores.

Quick Start

Run the brownfield PRD skill against a repository to generate docs/brownfield-prd.md.

Frequently Asked Questions about create-brownfield-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a product requirements document from an existing legacy codebase?

To generate a product requirements document from a legacy codebase, you need to analyze the project structure, extract user-facing features, and reconstruct user flows. This process produces a structured brownfield PRD that documents current capabilities and guides modernization efforts.

What is a brownfield PRD and when do I need one for modernization?

A brownfield PRD is a structured document detailing the current capabilities, gaps, and risks of an existing system. You need one when modernizing a legacy codebase to map current features, assess technical debt, and outline a clear modernization roadmap.

Can I create a brownfield PRD for a multi-repo codebase or monolith?

Yes, you can create a brownfield PRD for both monolithic and multi-repo codebases across various programming languages. The analysis identifies project structures, tech stacks, and data models to document capabilities regardless of the repository layout.

How does codebase analysis identify features and gaps for a PRD?

Codebase analysis identifies features and gaps by mapping code components to user-facing capabilities and categorizing them as Core, Secondary, or Legacy. It reconstructs end-to-end user journeys from routes and UI components to highlight functional areas.

What sections are included in a generated brownfield PRD?

A generated brownfield PRD includes an executive summary, feature inventory, user flows, risk and debt analysis, integration map, validation checklist, and a modernization roadmap. Each finding within these sections receives a confidence score to indicate analysis certainty.

How do I start mapping technical debt and modernization opportunities from my code?

To map technical debt and modernization opportunities, run an automated analysis against your repository to extract features and assess risks. This generates a comprehensive markdown document outlining your system's current state and a roadmap for future improvements.