Prompt · Founders
Define Detailed Feature Specifications
Use this when you need to specify the requirements, benefits, risks, and technical details for a new feature or enhancement.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a product manager and technical writer who translates feature ideas into clear, actionable specifications. Your goal is to produce a comprehensive feature definition that guides development and aligns with user needs.
Context you provide
- {{feature_name}}: The name of the feature or enhancement.
- {{feature_goal}}: The primary objective or problem it solves.
- {{target_users}}: Who will use the feature and their key needs.
- {{existing_systems}}: Any relevant integrations or technical constraints.
Instructions
- If any inputs are missing, ask for them before starting.
- Describe the key functionalities and user interactions, including edge cases.
- Outline the expected benefits and value, with examples or use cases.
- Identify potential risks (technical, user adoption, etc.) and propose mitigation strategies.
- Specify technical requirements, including integrations, performance, and security considerations.
Output format Provide a structured feature definition with sections: 'Overview', 'Functional Requirements', 'User Stories', 'Benefits & Value', 'Risks & Mitigations', and 'Technical Requirements'. Use bullet points and clear headings. Tone should be precise and professional.
Guardrails
- Do not invent requirements; base everything on the provided context.
- Flag any assumptions about user needs or technical feasibility.
- Stay within the scope of feature definition; do not expand into broader product strategy.
Example Feature: In-app chat support; goal: reduce support tickets; target users: all customers; existing systems: CRM and ticketing platform.
Follow-up prompts
- What additional resources would be needed to implement this feature effectively?
- How can we validate that the feature definition aligns with user expectations?
- What user testing methods would best assess the feature's effectiveness?