code-to-prd

Reverse-engineer codebases to generate structured Product Requirements Documents.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Patasse97/claude-skills --skill code-to-prd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-to-prd
Source: https://github.com/Patasse97/claude-skills/tree/main/product-team/code-to-prd
Command: npx skills add https://github.com/Patasse97/claude-skills --skill code-to-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Reverse engineers frontend, backend, or fullstack codebases to automatically generate a complete Product Requirements Document (PRD), saving product teams time and reducing manual effort.

Core Features & Use Cases

  • Analyze routes, components, models, and APIs to produce a structured PRD.
  • Produce per-page inventories, API inventories, enum dictionaries, and page relationships.
  • Scaffold a ready-to-fill PRD directory for collaborative product planning and engineering work.

Quick Start

Run the tool against a codebase directory to generate a PRD scaffold and documentation.

Frequently Asked Questions about code-to-prd

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, you can reverse-engineer your frontend, backend, or fullstack project by analyzing routes, components, models, and APIs to automatically produce a structured Product Requirements Document.

What is reverse-engineering a codebase for product documentation?▼

Reverse-engineering a codebase for product documentation involves extracting routes, components, models, and API interactions from existing source code to compose a comprehensive, production-ready PRD without manual effort.

Can I use this PRD generator for fullstack projects?▼

Yes, you can use this PRD generator for fullstack projects, as well as standalone frontend or backend codebases, to extract APIs and page relationships into a structured documentation scaffold.

How to document API inventories and page relationships from source code?▼

To document API inventories and page relationships from source code, run a reverse-engineering analysis that extracts models and interactions, scaffolding a ready-to-fill PRD directory with per-page inventories and enum dictionaries.

What's the best way to scaffold a PRD directory for collaborative product planning?▼

The best way to scaffold a PRD directory for collaborative product planning is to automatically generate a structured output from your codebase, including per-page inventories, API inventories, and enum dictionaries for engineering teams.

Why do I need to reverse-engineer code into a PRD?▼

You need to reverse-engineer code into a PRD to save product teams time and reduce manual effort when documenting existing frontend, backend, or fullstack applications for future development and planning.