/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.pyto detect framework, routes, APIs, enums, and project structure - Scaffold — Run
prd_scaffolder.pyto createprd/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:
Display a summary of findings: framework, page count, API count, enum count.
Step 2: Scaffold¶
Generate the PRD directory skeleton:
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:
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/SKILL.mdproduct-team/code-to-prd/scripts/codebase_analyzer.pyproduct-team/code-to-prd/scripts/prd_scaffolder.pyproduct-team/code-to-prd/references/prd-quality-checklist.md