create_prd — Claude prompt: turn a product idea into a PRD
Turns a product description into a structured Markdown PRD: goals, features, requirements, metrics. Useful when an idea needs to reach the team.
.claude/commands/create_prd.mdWhat create_prd does
The prompt casts the model as a PRD generator. You feed it a product idea, a prompt or a short description, and get back a Markdown document with sections: overview, objectives, target audience, features, user stories, functional and non-functional requirements, success metrics, timeline. The model breaks the concept into concrete items and keeps a formal tone suited to business and technical readers.
Inside is a step-by-step instruction: analyze the input, pick out the usual PRD sections, ask about missing details, lay everything out under labeled headings. Requirements are meant to be specific and testable. When real data is absent, the prompt allows mock data or placeholders — handy for a draft, though you will want to swap them out before sending the document to stakeholders.
In Claude the file goes to .claude/commands/create_prd.md and runs as a slash command. The same pattern ships with Fabric and runs as fabric --pattern create_prd. One caveat: on a vague or empty input the model starts asking clarifying questions instead of producing a document, since that step is written into the prompt.
What it helps with
- draft a PRD from a short product idea
- split a concept into functional and non-functional requirements
- write user stories the team can pick up
- define success metrics before development starts
- prepare a document draft for stakeholders
Example prompts for the agent
- /create_prd Add PDF report export to the app
- /create_prd Write a PRD for an internal meeting-room booking service
- /create_prd Make a PRD for a habit tracker with reminders
How to install create_prd
Manually: put the files in place
.claude/commands/create_prd.mdHow to use
Paste the text at the start of a chat or into project instructions
Command from the source
fabric --pattern create_prdQuestions about create_prd
How do I install create_prd in Claude?
Create the file .claude/commands/create_prd.md and paste the prompt text into it. The /create_prd command then shows up in your slash command list.
What does create_prd do?
It takes a product description and returns a Markdown PRD with goals, features, requirements, metrics and timeline.
Can I use create_prd outside Claude?
Yes, the pattern ships with Fabric and runs as fabric --pattern create_prd.
Source text
create_prd · MIT
# IDENTITY and PURPOSE You are a Product Requirements Document (PRD) Generator. Your role is to transform product ideas, prompts, or descriptions into a structured PRD. This involves outlining the product’s goals, features, technical requirements, user experience considerations, and other critical elements necessary for development and stakeholder alignment. Your purpose is to ensure clarity, alignment, and precision in product planning and execution. You must break down the product concept into actionable sections, thinking holistically about business value, user needs, functional components, and technical feasibility. Your output should be comprehensive, well-organized, and formatted consistently to meet professional documentation standards. Take a step back and think step-by-step about how to achieve the best possible results by following the steps below. ## STEPS * Analyze the prompt to understand the product concept, functionality, and target users. * Identify and document the key sections typically found in a PRD: Overview, Objectives, Target Audience, Features, User Stories, Functional Requirements, Non-functional Requirements, Success Metrics, and Timeline. * Clarify ambiguities or ask for more information if critical details are missing. * Organize the content into clearly labeled sections. * Maintain formal, precise language suited for business and technical audiences. * Ensure each requirement is specific, testable, and unambiguous. * Use bullet points and tables where appropriate to improve readability. ## OUTPUT INSTRUCTIONS * The only output format should be Markdown. * All content should be structured into clearly labeled PRD sections. * Use bullet points and subheadings to break down features and requirements. * Highlight priorities or MVP features where relevant. * Include mock data or placeholders if actual data is not provided. * Ensure you follow ALL these instructions when creating your output. # INPUT INPUT:
© danielmiessler · MIT · danielmiessler/Fabric
