prd-generator

Generate Product Requirements Documents from existing codebases via static analysis.

Updated Mar 30, 2026

Search Tags:#static analysis #code analysis #specification #brownfield development #PRD generation

Ready to run

npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill prd-generator-emeaappgbb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-generator
Source: https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield/tree/main/.github/skills/prd-generator
Command: npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill prd-generator-emeaappgbb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the creation of Product Requirements Documents (PRD) from existing codebases, eliminating the manual process and reducing errors in brownfield development workflows.

Core Features & Use Cases

Codebase Analysis: Reverse-engineers product vision, user personas, and feature list from existing code.
PRD Generation: Outputs a spec2cloud-compatible PRD with all necessary information for downstream development tasks.
Human Approval: Generated PRD requires human review and approval before proceeding.

Quick Start

Run the prd-generator skill on your codebase to generate a PRD and prepare it for FRD generation.

Frequently Asked Questions about prd-generator

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

FAQPage Schema

How do I generate a PRD from an existing codebase?▼

To generate a PRD from an existing codebase, this Skill uses static analysis and documentation extraction to reverse-engineer product vision, user personas, and feature lists, outputting a spec2cloud-compatible document for downstream development.

Can I use static analysis to reverse-engineer specifications for brownfield development?▼

Yes, static analysis is used to parse existing code and extract documentation, making it applicable for brownfield development where existing code requires specification for modernization or new feature implementation.

What is the best way to automate Product Requirements Document creation for legacy code?▼

Automating Product Requirements Document creation for legacy code involves parsing the codebase to reverse-engineer features and personas, which eliminates manual processes and reduces errors in modernization workflows.

Does the generated PRD require human approval before proceeding to downstream development?▼

Yes, the generated PRD requires human review and approval before proceeding, ensuring the reverse-engineered product vision and feature list are accurate for guiding downstream development tasks.

How do I prepare generated specifications for FRD generation?▼

You prepare generated specifications for FRD generation by running the Skill on your codebase to produce a spec2cloud-compatible PRD, which contains all necessary information for downstream development tasks.

What limitations exist when using code analysis for PRD generation?▼

A key limitation is that static analysis cannot capture undocumented business logic perfectly, making human review and approval mandatory before using the generated PRD to guide downstream development.