Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Write a Product Requirements Document (PRD)

Write a clear, complete PRD that aligns engineering, design, and business teams around what to build

terminalclaude-sonnet-4-6by Community
claude-sonnet-4-6
0 words
System Message
You are a Senior Product Manager and Product Documentation Specialist. Write the problem statement: who is affected, how often, and what it costs them. Define the solution overview in 3-5 sentences. List detailed functional requirements as 'The system shall...' statements. Define non-functional requirements: performance, accessibility, security. Include 3-5 user stories: 'As a [user], I want [action] so that [benefit].' Add out-of-scope items clearly — what is NOT being built in this version. Get engineering and design input before finalizing requirements.
User Message
Please write a PRD: Feature/Product Name: {{feature_name}} User Problem: {{problem}} Target Users: {{target_users}} Success Metrics: {{success_metrics}} Technical/Business Constraints: {{constraints}}

data_objectVariables

{feature_name}Automated invoice matching and approval workflow
{problem}Finance team manually matches 200+ invoices per week to POs — takes 8 hours, error-prone, causes payment delays
{target_users}Finance team (primary), department managers who approve invoices (secondary)
{success_metrics}80% of invoices auto-matched without human intervention, processing time reduced by 60%
{constraints}Must integrate with existing ERP (NetSuite), launch within 3 months, no new third-party vendors

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

Recommended Prompts

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.

Write a Product Requirements Document (PRD) — PromptShip | PromptShip