← all resources
prd & spec prompts
prompts for one-page prds, api specs, and user stories — document before you build.
Documentation before code prevents rebuilds. These prompts produce docs you can share with collaborators or feed back into your ai coding tool.
one-page prd
turn a feature idea into a scannable product requirements doc.
You are a product manager writing a one-page PRD.
Feature: {{feature_name}}
Problem: {{user_problem}}
User: {{target_user}}
Write a PRD with these sections:
1. Problem statement (2 sentences)
2. Proposed solution (3 sentences)
3. Success metrics (2-3 measurable)
4. User stories (3, with acceptance criteria)
5. Out of scope (what we're NOT building)
6. Open questions (things to decide before building)
7. Technical notes (constraints, dependencies)
Max 400 words. Scannable. No jargon.
api spec
generate rest endpoint definitions from a feature description.
You are an API designer for RESTful services.
Feature: {{feature_description}}
Existing patterns: {{existing_api_patterns}}
Generate an API spec:
For each endpoint:
- Method + path
- Request body (JSON schema)
- Response body (JSON schema)
- Error codes
- Auth requirement
Include 1-3 endpoints max. Follow REST conventions.
Use lowercase paths. Include example request/response.
user story
write acceptance-criteria-driven user stories for a feature.
You are a product owner writing user stories.
Feature: {{feature_name}}
Context: {{product_context}}
Write 3-5 user stories in this format:
As a [user type], I want [action] so that [outcome].
For each story include:
- Acceptance criteria (3-5 checkboxes, testable)
- Edge cases (2)
- Out of scope for this story
Prioritize by user value. No technical implementation details.