AI Agent Hub
Back to skills
Idea to Dev Prompt Generator icon

Idea to Dev Prompt Generator

Development Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @user_af28adda/idea-to-dev-prompt according to https://skillhub.cn/install/skillhub.md.

About this skill

From Vague Ideas to Implementable Prompts

When an engineer or product owner has only a rough idea, without screenshots or complete requirements, asking a model to write a development prompt often produces generic output: missing user roles, page boundaries, data entities, permissions, and acceptance criteria. This skill focuses on turning a vague concept into an implementable scope instead of immediately producing final code or documentation.

How the Skill Works

It starts with multi-turn clarification, asking at most 3 questions per turn and prioritizing the core user, problem to solve, and main user action. It then maps the workflow into entry points, actions, system responses, branches, and failure paths. From there, it decomposes the product into navigation, pages, modules, forms, tables, search, and permissions. Labels such as user-confirmed, reasonable-assumption, recommended, to-confirm, and out-of-scope help avoid presenting assumptions as requirements.

Scope and Caveats

It is suitable for MVP-level development prompts, lightweight product specifications, and page/data inventories. It is not a substitute for architecture design, security compliance review, or a full PRD. If the tech stack is unconfirmed, it may recommend defaults such as React + TypeScript or Next.js + PostgreSQL, but these should still be treated as assumptions.

Use Cases

  • Receive a one-sentence product request and confirm users, main flow, and MVP page boundaries before writing a dev prompt.
  • Prepare an internal admin system by clarifying roles, permissions, entities, forms, and status transitions.
  • Convert a client business goal into pages, actions, exception paths, and acceptance criteria for frontend and backend estimation.

Best For

  • Indie developers: have a rough product idea and need to clarify MVP scope into an implementable prompt.
  • Frontend / full-stack engineers: need to break verbal requirements into pages, forms, permissions, and state transitions.
  • Product managers: need to organize user flows, core objects, and recommendations when a full PRD is missing.
  • Startup founders: need to confirm user roles, platform stack, and acceptance criteria before assigning engineering work.