Feature Spec Template (Problem → Solution → Success)
Write feature specs that engineers and designers can actually build from.
Prompt
Write a feature spec for {FEATURE}.
Input:
- Feature: {FEATURE}
- Problem it solves: {PROBLEM}
- Target users: {USERS}
Rules:
- Start with problem and user impact
- Include user stories with acceptance criteria
- Note technical constraints and dependencies
- Define success metrics
- List open questions
Output format:
OVERVIEW
- Problem statement
- Impact (why now, why us)
SOLUTION
- High-level approach
- Key user stories (As a [user], I want to [action] so that [outcome])
- Acceptance criteria per story
TECHNICAL CONSIDERATIONS
- Constraints
- Dependencies
- Edge cases
SUCCESS METRICS
- How we measure success
- Target outcomes
OPEN QUESTIONS
- Decisions still needed
Feature: {FEATURE}
Problem: {PROBLEM}
Users: {USERS}Variations
• Add mockups or wireframe descriptions.
• Include technical design details for engineering.
• Make it lean (one-pager for simple features).
• Add competitive analysis section.
Works well with
• GPT
• Claude
• Gemini
Appears in collections
Related prompts
Product Requirements Generator (Spec → Build)
Turn product ideas into clear specifications that engineering can build without constant clarification meetings.
7-Day Study Plan (Realistic, Not Delusional)
Build a study plan that assumes you're human and get tired.
Landing Page Copy Audit (Fix Confusing Text)
Improve website copy so users understand it in 5 seconds instead of leaving.
Meeting Agenda (Clear Outcomes, Not Generic Lists)
Create agendas that make meetings actually productive.
Content Strategy Planner (Audience-First, Goal-Driven)
Design content strategies that attract, engage, and convert target audiences.
Risk Assessment Matrix (Identify, Prioritize, Mitigate)
Systematically identify and prioritize risks to make better decisions about where to invest in mitigation.