prd-generator

Original：🇺🇸 English

Translated

Generate comprehensive Product Requirements Documents (PRD) from idea validation files. Use when users ask to "create a PRD", "generate product requirements", "write a PRD", or want to turn validated ideas into actionable product specs. Works with idea.md and validate.md files from the idea-validator skill.

3installs

Sourceluongnv89/skills

Added on2026-02-08

NPX Install

npx skill4agent add luongnv89/skills prd-generator

SKILL.md Content

View Translation Comparison →

PRD Generator

Generate comprehensive Product Requirements Documents from validated idea files.

Input

Preferred: project folder path in

$ARGUMENTS

containing:

```
idea.md
```
- Product concept and technical context (required)
```
validate.md
```
- Evaluation and recommendations (required)

If path is not provided (auto-pick mode):

Reuse the most recent project folder path from this chat/session (typically from idea-validator output).
If unavailable, use env var
```
IDEAS_ROOT
```
when present.
Else check shared marker file
```
~/.config/ideas-root.txt
```
.
Backward compatibility fallback:
```
~/.openclaw/ideas-root.txt
```
.
If still unavailable, auto-discover the newest folder containing both
```
idea.md
```
+
```
validate.md
```
under:
- ```
/home/luongnv/workspace/ideas
```
  (default)
- ```
/home/luongnv/workspace/idea-2-prd
```
  (legacy fallback)
If multiple candidates are plausible, ask user to choose.

Workflow

Phase 1: Validate Input

Resolve
```
PROJECT_DIR
```
(from
```
$ARGUMENTS
```
or auto-pick mode above)
Check
```
PROJECT_DIR/idea.md
```
exists
Check
```
PROJECT_DIR/validate.md
```
exists

If

PROJECT_DIR/prd.md

exists, create backup:

prd.backup.YYYYMMDD_HHMMSS.md

Phase 2: Extract Context

From

idea.md

:

Product name/concept
Target audience
Goals & objectives
Technical context (stack, constraints)

From

validate.md

:

Verdict and ratings
Strengths/weaknesses
Competitors
Enhanced version suggestions
Implementation roadmap

Phase 3: Clarify Requirements

Ask user (if not clear from input files):

Official product name?
Business model? (SaaS, marketplace, freemium)
Target MVP timeframe?
Team size/composition?
Compliance requirements? (GDPR, HIPAA, SOC2)

Phase 4: Generate PRD

Create

prd.md

with these sections:

Product Overview - Vision, users, objectives, success metrics
User Personas - 2-3 detailed personas from target audience
Feature Requirements - Matrix with MoSCoW prioritization, user stories, acceptance criteria
User Flows - Primary flows with mermaid diagrams
Non-Functional Requirements - Performance, security, compatibility, accessibility
Technical Specifications - Architecture diagram, frontend/backend/infrastructure specs
Analytics & Monitoring - Key metrics, events, dashboards, alerts
Release Planning - MVP and version roadmap with checklists
Open Questions & Risks - Questions, assumptions, risk mitigation
Appendix - Competitive analysis, glossary, revision history

See references/prd-template.md for full template structure.

Phase 5: Output

Write
```
prd.md
```
to project folder
Summarize sections created
Highlight areas needing user review
Suggest next steps

Phase 6: README Maintenance (ideas repo)

After writing

prd.md

, if the project folder is inside an

ideas

repo, update the repo README ideas table:

Preferred:
```
cd
```
to the repo root and run
```
python3 scripts/update_readme_ideas_index.py
```
(if it exists)
Fallback: update
```
README.md
```
manually (ensure PRD status becomes ✅ for that idea)

Modification Mode

If user wants to modify existing PRD:

Create timestamped backup
Ask what to modify (features, priorities, timeline, specs, personas)
Apply changes preserving structure
Update revision history

Guidelines

Thorough: Cover all sections comprehensively
Realistic: Base on validate.md feasibility ratings
Specific: Include concrete metrics and criteria
Actionable: Every section guides implementation
Visual: Include mermaid diagrams for architecture and flows