Open Prompts
Submit a prompt
Coding

Deep Research to Implementation Plan

Give it a raw feature idea along with product context, target users, technical stack, and constraints, and get back more than a task list. It clarifies the problem statement, surfaces assumptions and open research questions, scopes an MVP with explicit out-of-scope items, then works through user stories, technical design, data model needs, implementation phases, and risks before ending with a validation plan.

Prompt
You are a product-minded senior engineer.

Turn this feature idea into a researched implementation plan.

Feature idea:
{{feature_idea}}

Product context:
{{product_context}}

Users:
{{users}}

Technical stack:
{{stack}}

Constraints:
{{constraints}}

Create:
1. Clarified problem statement.
2. Assumptions.
3. Research questions.
4. MVP scope.
5. Out-of-scope items.
6. User stories.
7. Technical design.
8. Data model or API needs.
9. Implementation phases.
10. Risks and mitigations.
11. Validation plan.

Rules:
- Separate product decisions from technical decisions.
- Keep the MVP small.
- Mark open questions.
Download .md

Variables

Related prompts

Coding

Database schema design assistant

Describe a feature in plain language along with your database engine, expected scale, and existing tables to get a second opinion before writing migrations that are painful to undo. Returns proposed tables, keys, and indexes with the reasoning behind each normalization or denormalization decision, flags which constraints belong at the database level instead of application code, and stress-tests the design against one likely future change.

Coding

Architecture Tradeoff Advisor

Describe a system you're about to build along with its scale, team, timeline, and current plan, and get tradeoffs surfaced instead of textbook best practices. - Ranks the top 3 risks specific to your approach - Identifies what would break first at 10x scale - Proposes the simplest version you could ship first - Best used before writing code — for schema design, API contracts, or system boundaries

Coding

Framework and Database Migration Assistant

Plans a framework, database, or API migration from your current setup to a target one, honoring the compatibility window, downtime limit, and behavior you say must be preserved. - Takes old/new stack, current and target setup, and hard constraints as input - Outputs an ordered migration checklist, tackling the riskiest changes first - Generates code transformations for common patterns and lists breaking changes - Includes a rollback plan and validation tests to confirm the migration worked