Code → PRD
Skill Verified ActiveReverse-engineer any codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, state management, API integrations, and user interactions to produce business-readable documentation detailed enough for engineers or AI agents to fully reconstruct every page and endpoint. Works with frontend frameworks (React, Vue, Angular, Svelte, Next.js, Nuxt), backend frameworks (NestJS, Django, Express, FastAPI), and fullstack applications. Trigger when users mention: generate PRD, reverse-engineer requirements, code to documentation, extract product specs from code, document page logic, analyze page fields and interactions, create a functional inventory, write requirements from an existing codebase, document API endpoints, or analyze backend routes.
To automatically generate complete Product Requirements Documents from any codebase, saving significant manual documentation effort and ensuring all technical details are captured for reconstruction.
Features
- Analyzes frontend, backend, and fullstack applications.
- Supports numerous frameworks (React, Vue, Next.js, NestJS, Django, FastAPI, etc.).
- Generates structured PRD output with per-page details, API inventory, and enums.
- Includes analysis and scaffolding scripts for a complete workflow.
Use Cases
- Generating documentation for legacy codebases.
- Creating initial PRDs for new projects based on early code structure.
- Understanding complex application architectures for onboarding or maintenance.
- Extracting API specifications from existing backend services.
Non-Goals
- Generating code from PRDs.
- Performing static code analysis for bugs or performance issues.
- Providing UI design mockups or wireframes.
Workflow
- Phase 1: Project Global Scan (Identify Structure, Build Route/Page Inventory, Map Global Context)
- Phase 2: Page-by-Page Deep Analysis (Analyze Overview, Layout, Fields, Interactions, APIs, Relationships)
- Phase 3: Generate Documentation (Create PRD directory with README, page stubs, appendix files)
Practices
- Code-to-documentation
- Product requirement generation
- Technical documentation
Prerequisites
- Python 3.x installed
- Read access to the target codebase
Installation
First, add the marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install code-to-prd@claude-code-skillsQuality Score
VerifiedTrust Signals
Similar Extensions
Pathfinder
100Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.
Ui Ux Pro Max
100UI/UX design intelligence with searchable style, palette, typography, and chart databases. Use when designing UI components, choosing colors/fonts, reviewing code for UX issues, building landing pages, or implementing responsive layouts.
Google Docs
100Interact with Google Docs - create documents, search by title, read content, and edit text. Use when user asks to: create a Google Doc, find a document, read doc content, add text to a doc, or replace text in a document. Lightweight alternative to full Google Workspace MCP server with standalone OAuth authentication.
Sweep Flag Namespace
99Bulk-extract every candidate flag from a binary namespace, build an extraction inventory with occurrence counts and call-type tags, cross- reference against a documented set, and track completeness across probe campaigns until the undocumented remainder reaches zero. Covers namespace prefix harvesting, gate-vs-telemetry disambiguation at the call-site level, completeness metrics, DEFAULT-TRUE population reporting, and a final completion confirmation scan. Use upstream of probe-feature-flag- state when you need a complete catalog rather than a sample, or when a prior wave-based campaign needs a verifiable end condition.
Metal
100Extract the conceptual essence of a repository as skills, agents, and teams — the project's roles, procedures, and coordination patterns expressed as agentskills.io-standard definitions. Reads an arbitrary codebase and produces generalized definitions that capture WHAT the project does and WHO operates it, without replicating HOW it does it. Use when onboarding to a new codebase and wanting to understand its conceptual architecture, when bootstrapping an agentic system from an existing project, when studying a project's organizational DNA for cross-pollination, or when creating a skill/agent/team library inspired by a reference implementation.
Lean Ctx
100Context Runtime for AI Agents — 59 MCP tools, 10 read modes, 95+ shell patterns, tree-sitter AST for 18 languages. Compresses LLM context by up to 99%. Use when reading files, running shell commands, searching code, or exploring directories. Auto-installs if not present.