Command

/code-to-prd

Reverse-engineer a frontend codebase into a PRD. Usage: /code-to-prd [path]

shell

$ npx -y skills add alirezarezvani/claude-skills --agent claude-code

Ships with claude-skills. Installing the plugin gets this command.

How it fires

How this command gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/code-to-prd

Context preview

What this command does when you run it.

Reverse-engineer a frontend codebase into a PRD. Usage: /code-to-prd [path]

Stats

Stars23,060

Forks3,139

LanguagePython

LicenseMIT

Ships with claude-skills

Command definition

code-to-prd.md

---
name: code-to-prd
description: "Reverse-engineer a frontend codebase into a PRD. Usage: /code-to-prd [path]"
argument-hint: "[path]"
---

# /code-to-prd

Reverse-engineer a frontend codebase into a complete Product Requirements Document.

## Usage

```bash
/code-to-prd                    # Analyze current project
/code-to-prd ./src              # Analyze specific directory
/code-to-prd /path/to/project   # Analyze external project
```

## What It Does

1. **Scan** — Run `codebase_analyzer.py` to detect framework, routes, APIs, enums, and project structure
2. **Scaffold** — Run `prd_scaffolder.py` to create `prd/` directory with README.md, per-page stubs, and appendix files
3. **Analyze** — Walk through each page following the Phase 2 workflow: fields, interactions, API dependencies, page relationships
4. **Generate** — Produce the final PRD with all pages, enum dictionary, API inventory, and page relationship map

## Steps

### Step 1: Analyze

Determine the project path (default: current directory). Run the frontend analyzer:

```bash
python3 {skill_path}/scripts/codebase_analyzer.py {project_path} -o .code-to-prd-analysis.json
```