code-to-prd

alirezarezvani/claude-skills · .gemini/skills/cmd-code-to-prd/SKILL.md

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

Software EngineeringNo license★ 25441⑂ 3598commit 19392f7

What this skill does

/code-to-prd

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

Usage

/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

Scan — Run codebase_analyzer.py to detect framework, routes, APIs, enums, and project structure
Scaffold — Run prd_scaffolder.py to create prd/ directory with README.md, per-page stubs, and appendix files
Analyze — Walk through each page following the Phase 2 workflow: fields, interactions, API dependencies, page relationships
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:

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

Display a summary of findings: framework, page count, API count, enum count.

Step 2: Scaffold

Generate the PRD directory skeleton:

python3 {skill_path}/scripts/prd_scaffolder.py .code-to-prd-analysis.json -o prd/

Step 3: Fill

For each page in the inventory, follow the SKILL.md Phase 2 workflow:

Read the page's component files
Document fields, interactions, API dependencies, page relationships
Fill in the corresponding prd/pages/ stub

Work in batches of 3-5 pages for large projects (>15 pages). Ask the user to confirm after each batch.

Step 4: Finalize

Complete the appendix files:

prd/appendix/enum-dictionary.md — all enums and status codes found
prd/appendix/api-inventory.md — consolidated API reference
prd/appendix/page-relationships.md — navigation and data coupling map

Clean up the temporary analysis file:

rm .code-to-prd-analysis.json

Output

A prd/ directory containing:

README.md — system overview, module map, page inventory
pages/*.md — one file per page with fields, interactions, APIs
appendix/*.md — enum dictionary, API inventory, page relationships

Skill Reference

product-team/code-to-prd/skills/code-to-prd/SKILL.md
product-team/code-to-prd/skills/code-to-prd/scripts/codebase_analyzer.py
product-team/code-to-prd/skills/code-to-prd/scripts/prd_scaffolder.py
product-team/code-to-prd/skills/code-to-prd/references/prd-quality-checklist.md

Installation

Copy a source-pinned command for your client. You run it yourself.

Destination: .claude/skills/cmd-code-to-prd · pinned to the source commit

# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/cmd-code-to-prd" ".claude/skills/"
rm -rf .skillboard-tmp

Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.

New here? Step-by-step setup – from installing the agent to using the skill

Operating systemAgentI already use Claude Code

1
Install Git
Install Git with your package manager (Debian/Ubuntu shown; use dnf/pacman on others). Official download.
```
sudo apt update && sudo apt install -y git
```
2
Install Claude Code
Requires Node.js 18+. Install the CLI globally: Official docs. (command-line tool)
```
npm install -g @anthropic-ai/claude-code
```

Get the skill, pinned to its exact version

Open a terminal and run these steps (they clone the source, check out the exact commit, and copy the skill into place):

# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/cmd-code-to-prd" ".claude/skills/"
rm -rf .skillboard-tmp

Destination: .claude/skills/cmd-code-to-prd

4
Use it in Claude Code
Open Claude Code in your project. It reads skills from the folder above, so code-to-prd is now available. Always review the source before using it – static checks cannot prove runtime safety.

Security & Audits

Scanner static-checks@0.1.0 · commit 19392f7a0826. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.

No static rules matched. This is not a safety guarantee.

code-to-prd

alirezarezvani/claude-skills · .gemini/skills/cmd-code-to-prd/SKILL.md

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

Software EngineeringNo license★ 25441⑂ 3598commit 19392f7

Install skillView source on GitHub

What this skill does

/code-to-prd

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

Usage

/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

Scan — Run codebase_analyzer.py to detect framework, routes, APIs, enums, and project structure
Scaffold — Run prd_scaffolder.py to create prd/ directory with README.md, per-page stubs, and appendix files
Analyze — Walk through each page following the Phase 2 workflow: fields, interactions, API dependencies, page relationships
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:

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

Display a summary of findings: framework, page count, API count, enum count.

Step 2: Scaffold

Generate the PRD directory skeleton:

python3 {skill_path}/scripts/prd_scaffolder.py .code-to-prd-analysis.json -o prd/

Step 3: Fill

For each page in the inventory, follow the SKILL.md Phase 2 workflow:

Read the page's component files
Document fields, interactions, API dependencies, page relationships
Fill in the corresponding prd/pages/ stub

Work in batches of 3-5 pages for large projects (>15 pages). Ask the user to confirm after each batch.

Step 4: Finalize

Complete the appendix files:

prd/appendix/enum-dictionary.md — all enums and status codes found
prd/appendix/api-inventory.md — consolidated API reference
prd/appendix/page-relationships.md — navigation and data coupling map

Clean up the temporary analysis file:

rm .code-to-prd-analysis.json

Output

A prd/ directory containing:

README.md — system overview, module map, page inventory
pages/*.md — one file per page with fields, interactions, APIs
appendix/*.md — enum dictionary, API inventory, page relationships

Skill Reference

product-team/code-to-prd/skills/code-to-prd/SKILL.md
product-team/code-to-prd/skills/code-to-prd/scripts/codebase_analyzer.py
product-team/code-to-prd/skills/code-to-prd/scripts/prd_scaffolder.py
product-team/code-to-prd/skills/code-to-prd/references/prd-quality-checklist.md

Installation

Copy a source-pinned command for your client. You run it yourself.

Destination: .claude/skills/cmd-code-to-prd · pinned to the source commit

# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/cmd-code-to-prd" ".claude/skills/"
rm -rf .skillboard-tmp

Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.

New here? Step-by-step setup – from installing the agent to using the skill

Operating systemAgentI already use Claude Code

1
Install Git
Install Git with your package manager (Debian/Ubuntu shown; use dnf/pacman on others). Official download.
```
sudo apt update && sudo apt install -y git
```
2
Install Claude Code
Requires Node.js 18+. Install the CLI globally: Official docs. (command-line tool)
```
npm install -g @anthropic-ai/claude-code
```

Get the skill, pinned to its exact version

Open a terminal and run these steps (they clone the source, check out the exact commit, and copy the skill into place):

# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/cmd-code-to-prd" ".claude/skills/"
rm -rf .skillboard-tmp

Destination: .claude/skills/cmd-code-to-prd

4
Use it in Claude Code
Open Claude Code in your project. It reads skills from the folder above, so code-to-prd is now available. Always review the source before using it – static checks cannot prove runtime safety.

Security & Audits

Scanner static-checks@0.1.0 · commit 19392f7a0826. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.

No static rules matched. This is not a safety guarantee.

code-to-prd

What this skill does

/code-to-prd

Usage

What It Does

Steps

Step 1: Analyze

Step 2: Scaffold

Step 3: Fill

Step 4: Finalize

Output

Skill Reference

Installation

Install Git

Install Claude Code

Get the skill, pinned to its exact version

Use it in Claude Code

Security & Audits

code-to-prd

What this skill does

/code-to-prd

Usage

What It Does

Steps

Step 1: Analyze

Step 2: Scaffold

Step 3: Fill

Step 4: Finalize

Output

Skill Reference

Installation

Install Git

Install Claude Code

Get the skill, pinned to its exact version

Use it in Claude Code

Security & Audits