Agent skill · product strategy · alirezarezvani
code-to-prd
Use when asked to write a PRD or product spec from an existing codebase (reverse-engineer requirements, document pages, fields, routes and endpoints). Maps the code with codebase_analyzer.py and scaffolds the PRD with prd_scaffolder.py.
Why this skill is useful
Adds automation scripts for analyzing codebases and generating comprehensive PRDs that aren't available in public documentation.
What it needs
Requires python3 installed locally. About 11k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
Name Code → PRD Description Reverse-engineer any frontend, backend, or fullstack codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, models, APIs, and user interactions to produce business-readable documentation detailed enough for engineers or AI agents to fully reconstruct every page and endpoint. Code → PRD: Reverse-Engineer Any Codebase into Product Requirements Features 3-phase workflow: global scan → page-by-page analysis → structured document generation Frontend support: React, Vue, Angular, Svelte, Next.js (App + Pages Router), Nuxt, SvelteKit, Remix Backend support: NestJS, Express, Django, Django REST Framework, FastAPI, Flask Fullstack support: Combined frontend + backend analysis with unified PRD output Mock detection: Automatically distinguishes real API integrations from mock/fixture data Enum extraction: Exhaustively lists all status codes, type mappings, and constants Model extraction: Parses Django models, NestJS entities, Pydantic schemas Automation scripts: codebaseanalyzer.py for scanning, prdscaffolder.py for directory generation Quality checklist: Validation checklist for completeness, accuracy, readability Usage Examples Frontend (React) Backend (Django) Fullstack (Next.js) --- Role You are a senior product analyst and technical architect. Your job is to read a frontend codebase, understand every page's business purpose, and produce a complete PRD in product-manager-friendly language. Dual Audience 1. Product managers / business stakeholders — need to understand what the system does, not how 2. Engineers / AI agents — need enough detail to fully reconstruct every page's fields, interactions, and relationships Your document must describe functionality in non-technical language while omitting zero business details. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/code-to-prd--a622d8