code-to-prd

Reverse-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. Use 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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete commands and complete templates and a clear 3-phase workflow. The main weaknesses are modest verbosity from redundant sections and a missing explicit validation checkpoint in the generation workflow.

Suggestions

Consolidate overlapping sections (Features, Supported Stacks, Page Type Strategies) into a single stack/matrix to reduce redundancy and trim token cost.

Add an explicit validation checkpoint in Phase 3 (e.g., run the prd-quality-checklist before finalizing) with a fix→re-validate feedback loop.

Move the large inlined README and per-page templates into a reference file, keeping only a concise inline example plus a clearly signaled link in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete templates and tables, but the ~485-line body includes redundant sections (Features, Supported Stacks, and Page Type Strategies overlap, and the Role/Dual Audience section restates the frontmatter), so it is mostly efficient but could be tightened per the 3 anchor.	3 / 5
Actionability	Provides copy-paste-ready executable commands (python3 scripts/codebase_analyzer.py ...) plus full README and per-page Markdown templates with concrete field tables, matching the fully-executable 5 anchor.	5 / 5
Workflow Clarity	A clear 3-phase sequence (Global Scan → Page-by-Page → Generate) with concrete steps, but the batch generation workflow lacks an explicit in-flow validation checkpoint (the quality checklist is only referenced, not embedded as a validate→fix→retry step), capping it just below 5.	4 / 5
Progressive Disclosure	Good structure with one-level-deep, clearly signaled references (references/prd-quality-checklist.md, references/framework-patterns.md) and a References table, though the large inlined body still holds content that could be moved to references, placing it just below the 5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states the skill's purpose and provides an extensive list of natural trigger phrases. The only minor gap is some breadth-induced overlap risk with generic documentation skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Analyzes routes, components, state management, API integrations, and user interactions" and "produce business-readable documentation" — with comprehensive coverage of analysis targets and output, matching the 5 anchor.	5 / 5
Completeness	Explicitly answers both what (reverse-engineer any codebase into a complete PRD) and when (Use when users mention: ...), with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Includes a rich "Use when users mention:" clause with natural phrases like "generate PRD", "reverse-engineer requirements", "code to documentation", "extract product specs from code", matching comprehensive synonym coverage of the 5 anchor.	5 / 5
Distinctiveness Conflict Risk	Clear niche (code-to-PRD reverse engineering) with distinct triggers and minimal conflict risk, but broad "any codebase" framing creates minor overlap with general documentation skills, placing it just below the 5 anchor.	4 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: product-team/code-to-prd/skills/code-to-prd/SKILL.md
Commit: 19392f7

Reviewed: ~2 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.