A workflow that examines an existing frontend, backend, or full-stack codebase and turns it into a business-readable Product Requirements Document, or PRD. A PRD describes what a product must do, including pages, data, APIs, and user interactions.

Use it to document routes, components, models, state, integrations, endpoints, interactions, and mock data across web, server, .NET, Android, and iOS projects.

It makes an unfamiliar system easier to understand and gives engineers or coding agents enough detail to recreate its behavior.

code-to-prd — Skill by wei6bin

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/wei6bin/skills/code-to-prd

Any agent

npx skills add wei6bin/skills --skill code-to-prd

Clone the repo

git clone --depth 1 https://github.com/wei6bin/skills

Made for: Claude Code, Codex.

Per session 194 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,508 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00194	$0.05508
Opus 5	$0.00097	$0.02754
Sonnet 5	$0.00039	$0.01102
Haiku 4.5	$0.00019	$0.00551

Measured 2d ago against content hash acb231cfbb3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-to-prd scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/codebase_analyzer.py, scripts/prd_scaffolder.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

code-to-prd/skills/code-to-prd/SKILL.md · 549 lines

How it starts

The opening of the file, as written. The whole thing — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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
.NET / ASP.NET support: Web API/MVC controllers, WCF services, ASP.NET Web Forms (.aspx)
Native mobile support: Android (Java/Kotlin — activities, fragments, Retrofit), iOS (Swift/Objective-C — view controllers, storyboards, URLSession/AFNetworking)
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 — including C# [EnumMember], Java/Kotlin enums, Swift enum/Objective-C NS_ENUM
Model extraction: Parses Django models, NestJS entities, Pydantic schemas, .NET POCOs/EF entities, Android POJOs/Room entities, iOS Codable structs/NSObject models
Automation scripts: codebase_analyzer.py for scanning, prd_scaffolder.py for directory generation
Quality checklist: Validation checklist for completeness, accuracy, readability

Usage

# Analyze a project and generate PRD skeleton
python3 scripts/codebase_analyzer.py /path/to/project -o analysis.json
python3 scripts/prd_scaffolder.py analysis.json -o prd/ -n "My App"

# Or use the slash command
/code-to-prd /path/to/project

Examples

Frontend (React)

/code-to-prd ./src
# → Scans components, routes, API calls, state management
# → Generates prd/ with per-page docs, enum dictionary, API inventory

Read the full file on GitHub · 549 lines

Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 549 lines · 194 tokens per session scan A acb231cfbb3f

Subscribe to this mod's changes

code-to-prd is a skill published in the GitHub repository wei6bin/skills (2 stars, last pushed 10d ago), licensed MIT. It adds 194 tokens to every session and 5,508 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens