English | 한국어 | 中文 | 日本語 | Español
Interview-driven PRD generator for vibe coders — from one sentence to 4 design documents.
Turn a single idea into a complete product plan. Answer 5–6 structured questions and get four design documents ready to hand off to any AI coding tool.
Quick Start • Why show-me-the-prd • How it works • Features • Commands • Requirements
/plugin marketplace add https://github.com/fivetaku/gptaku_plugins.git
/plugin install show-me-the-prd
The plugin loads on session start — restart once after installing.
/show-me-the-prd I want to build a photo organization app
Or just say it naturally:
Make me a PRD for a task manager
- No planning experience required — Every question comes with plain-language explanations and tradeoffs, not jargon
- AI leads, you decide — AI researches options in real time and presents them as choices; you never have to Google anything
- Research-backed, not guesswork — Live web searches power the feature list, stack comparison, and complexity ratings
- Four documents, not one — PRD, data model, phase plan, and AI project spec are generated together as a coherent set
- Production-oriented — Each phase targets a real deployment with real auth and a real database, not a local mock
- Existing plans welcome — Drop in an existing spec; the plugin identifies gaps and fills them in
One-sentence idea
|
v
[ Interview ] ←── live web research runs between each question
|
Turn 1: clarify the idea (1–3 questions)
Turn 2: pick core features + MVP scope
Turn 3: confirm data model
Turn 4: confirm phase breakdown
Turn 5: choose tech stack + auth method
|
v
[ 4 Documents ]
|
+── PRD/01_PRD.md What you're building and who it's for
+── PRD/02_DATA_MODEL.md Core data structure (conceptual ERD)
+── PRD/03_PHASES.md Phase plan with start prompts
+── PRD/04_PROJECT_SPEC.md AI rules + "never do this" list
+── PRD/README.md Navigation guide
Every option in the interview includes a plain-language description, pros, cons, and a complexity rating (Simple / Moderate / Complex). If you are unsure, pick the one marked (recommended).
No developer vocabulary required. Instead of "choose your auth strategy," it asks "how should users log in?" with concrete options like "social login (Google/Kakao)" and "email + password."
Between each interview turn, the plugin runs live searches to find relevant features, common pitfalls, and current best-practice stacks. What you see in the options is grounded in actual results, not hardcoded suggestions.
Each feature in the feature-selection step is labeled:
| Label | Meaning |
|---|---|
| Simple | Works out of the box with most frameworks |
| Moderate | Requires an external service; some cost likely |
| Complex | Recommended to skip in the first version |
| Document | Contents | When to use |
|---|---|---|
01_PRD.md |
Product goals, user stories, feature list | Share at project start |
02_DATA_MODEL.md |
Core entities and relationships | Share when designing the database |
03_PHASES.md |
Phase-by-phase plan with start prompts | Reference for build order |
04_PROJECT_SPEC.md |
AI behavior rules + "never do this" list | Share with AI on every session |
If you already have a spec or notes, share them before running the command. The plugin reads them, identifies what is missing against the four-document standard, and runs only the questions needed to fill the gaps.
| Command | Description |
|---|---|
/show-me-the-prd [idea] |
Start an interview with your idea inline |
/show-me-the-prd |
Start with an interactive opening question |
The plugin also activates when you say:
- "Make me a PRD"
- "Create a planning document"
- "Show me the PRD"
- "Plan this app for me"
- "Plan [idea] for me"
- Claude Code CLI
Installing these alongside show-me-the-prd improves research quality:
| Plugin | What it adds |
|---|---|
docs-guide |
Official documentation lookups during tech stack research |
insane-research |
Deeper market and trend analysis |
The plugin works without them — it falls back to WebSearch automatically.
MIT
One sentence in. Four documents out.