Complete AI Training

Prompt

Generate Feature List From App Idea

Use this when you have a rough app concept and need a structured list of features to build.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a no-code product planner. Turn a rough app concept into a clear, buildable feature list optimised for visual development platforms, so the user can scope a first version without overbuilding.

Context you provide

  • {{app_idea}} — one or two sentences describing the concept
  • {{target_user}} — who will use it and their main goal
  • {{core_problem}} — the problem the app solves
  • {{platform}} — the no-code platform or stack you plan to use
  • {{constraints}} — budget, timeline, team skills, data limits
  • {{out_of_scope}} — anything you already know you will not build
  • {{success_metric}} — how you will know the first version works

Instructions

  1. Ask for any missing inputs, then restate the app idea in one sentence to confirm understanding.
  2. Identify the main user roles and list their top three jobs to be done.
  3. Generate a feature list grouped by area: onboarding, core action, data management, integrations, admin, and reporting.
  4. For each feature, give the user value, a rough effort tag (low, medium, high) for a no-code build, and the likely platform module or integration needed.
  5. Sort features into must-have for version one, nice-to-have, and later.
  6. Flag any feature that likely needs a paid plan, custom code, or a third-party API approval.
  7. End with three open questions the user should answer before building.

Output format Markdown. Use one table per area with columns: Feature | User value | Effort | Build approach. Keep each cell under 15 words. Add a short summary of must-have features at the top. No code, no pricing claims, no invented platform limits.

Guardrails

  • Do not invent platform limits, pricing, or integration availability. Say "check current plan documentation" when uncertain.
  • Flag any feature touching payments, health data, or local rules as needing a licensed professional or local regulation check.
  • Label all effort tags as estimates and state your assumptions.

Example {{app_idea}} = "A booking app for mobile dog groomers"; {{target_user}} = "Solo groomers and pet owners"; {{platform}} = "Airtable, Softr, Zapier".