create-prd

Generate a structured Product Requirements Document using an 8-section template.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/moonzff/Codex_up --skill create-prd-moonzff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-prd
Source: https://github.com/moonzff/Codex_up/tree/main/skills/global-installed/create-prd
Command: npx skills add https://github.com/moonzff/Codex_up --skill create-prd-moonzff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a Product Requirements Document from scratch is time-consuming and often produces inconsistent, incomplete specs that fail to align stakeholders. This Skill turns a product idea, feature request, or attached context into a complete PRD following a proven 8-section structure. ## Core Features & Use Cases - 8-Section PRD Template: Covers Summary, Contacts, Background, Objective (with SMART OKRs), Market Segments, Value Propositions, Solution (UX, features, assumptions), and Release planning. - Context-Aware Drafting: Reads user-provided files, repository context, and referenced research, and can use web search for current market information with cited sources. - Accessible Output: Produces a clear markdown document written in plain language, with assumptions explicitly flagged for validation. - Use Case: A product manager needs a feature spec for a new onboarding flow. Provide the feature idea and any research notes, and receive a complete PRD ready to share with engineering and leadership. ## Quick Start Ask the assistant to create a PRD for your product or feature idea, optionally attaching research notes or context files.

Frequently Asked Questions about create-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a product requirements document with AI?▼

Provide your product or feature idea along with any research notes or files, and the Skill drafts a complete PRD using an 8-section template. It covers problem, objectives, market segments, value propositions, solution, and release planning in plain language.

What sections should a PRD template include?▼

This template includes Summary, Contacts, Background, Objective with SMART key results, Market Segments, Value Propositions, Solution (UX, key features, technology, assumptions), and Release planning with relative timeframes.

Can the PRD include current market research?▼

Yes. When external or current-market information is needed, the Skill uses web research tooling and cites sources. It incorporates market insights into the Background, Market Segments, and Value Proposition sections.

Does the PRD get saved as a file automatically?▼

No. The PRD is presented as formatted markdown in the response by default. It is saved as a PRD-[product-name].md file only when you ask or when the project workflow already establishes a documentation path.

When should I not use a full PRD template?▼

A full 8-section PRD is excessive for small bug fixes, minor tweaks, or early exploratory ideas. For those cases, a lightweight one-pager or ticket description is more appropriate than a formal requirements document.