mirror of https://github.com/TechNomadCode/AI-Product-Development-Toolkit.git synced 2026-10-20 08:39:44 +02:00

Files

T

History

TechNomadCodeandClaude Opus 5.5 30b9b8cf55 Give each planning step one name and make the guides easier to follow

- Rename prompt-templates/ to planning-prompts/ with numbered step
  folders, so GitHub lists them in workflow order. Folder, prompt file
  and skill now share one name per step (2-prd/prd.md is /prd).
- Merge the full and ultra-lean MVP plan prompts into 5-mvp-plan/, as
  the /mvp-plan skill already did.
- Rename the /mvp skill to /mvp-scope; the installer removes an earlier
  mvp install and tells the owner about the new name.
- Rename agent-configs/claude-code-desktop/ to agent-configs/claude-code/,
  since the rules apply to the terminal too.
- Rewrite each prompt guide in one short layout with previous and next
  links, drop outdated model and temperature advice, and fix the copied
  "final PRD draft" lines and the claimed v0.dev section.
- Point to GitHub's Copy raw content button for copying a prompt.
- Move the AI App Starter details from the root README into the starter
  guide, add the skills to the top table, and align the test plan
  wording with what the prompt produces.
- Add issue forms, a Discussions link and a short contributing guide.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-12 14:57:27 +02:00

prd.md

Give each planning step one name and make the guides easier to follow

2026-10-12 14:57:27 +02:00

README.md

Give each planning step one name and make the guides easier to follow

2026-10-12 14:57:27 +02:00

README.md

PRD prompt

Step 2 of the planning prompts. The AI interviews you about your idea, then drafts a product requirements document (PRD).

Prompt: prd.md

What you get

A draft PRD with an overview, goals, target users, user stories, functional and non-functional requirements, design considerations, success metrics, and open questions.

What to bring

Your notes (required): ideas, goals, features, problems, anything you have, however rough. They go between --- BRAINDUMP START --- and --- BRAINDUMP END ---. Did user research? Paste its PRD Research Input section here.
Product type and constraints (optional): fill in the two bracketed lines under TONE & CONSTRAINTS, such as "a web app" or "3-month timeline", or delete them.

How to use it

Open prd.md and copy it with the copy button at the top right of the file (Copy raw content).
In a text editor, replace the placeholders with your material.
Paste it into a new AI chat and answer its questions. It asks a few at a time, states its assumptions, and checks with you before it moves on.
When it offers to write the PRD, say yes. Review the draft and save it as a Markdown file: the next steps ask for it.

In Claude Code or Codex? The /prd skill runs this same prompt and fills it in from your message or files.

Good to know

Rough notes are fine. The interview fills the gaps, and the more you share up front, the fewer questions it asks.
Use a model that keeps a long conversation in view: the PRD is built from everything you said.
The PRD is a draft. Check every requirement, especially any you don't remember agreeing to.

Next step

UX and user flow: turn this PRD into screens and user flows. Or skip to the MVP scope if the app has only a few screens.

← Previous: User research · All planning prompts