New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

MVP Product Requirements Writer

by KhazP in KhazP/vibe-coding-prompt-template

Writes or revises an MVP product requirements document, sized to the product, with observable acceptance criteria and no repeated questions.

MITAuto-check passedProduct & Project Management

Install MVP Product Requirements Writer

skills CLI
$ npx skills add KhazP/vibe-coding-prompt-template --skill vibe-prd -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install KhazP/vibe-coding-prompt-template vibe-prd --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/vibe-prd .claude/skills/vibe-prd && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vibe-prd
GitHub stars
3.1k
Token cost
~455 tokens
SKILL.md length
219 words
Files
3 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Writes or revises an MVP product requirements document, sized to the product, with observable acceptance criteria and no repeated questions.

  • Writing a first-draft PRD for a new MVP feature
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Revising an existing PRD after requirements change
  • Clarifying scope and acceptance criteria before implementation starts

What it does

The skill draws on existing research, the user's request and a handoff context to define the product outcome, rather than running a fresh interview whose answers are already known. It asks only about unresolved requirements that affect scope or acceptance, makes any reversible assumption explicit, and keeps going once the brief is sufficient rather than demanding a fixed set of answers.

A PRD covers the target user and problem, the core journey, MVP scope, what is out of scope, meaningful failure states, constraints and observable acceptance criteria, adding sections like accounts, payments or analytics only when the product actually needs them. Length matches the product: a short document for a small project, more clarification for a complex one. The output goes to a configured path or a default MVP PRD path and ends with a handoff context covering the app, user level, platform and open questions; a guided interview can pull optional prompts from a bundled question bank.

When your agent uses it

  • Writing a first-draft PRD for a new MVP feature
  • Revising an existing PRD after requirements change
  • Clarifying scope and acceptance criteria before implementation starts

Example prompts

  • “Write the MVP PRD for our waitlist feature from the notes in docs/research.md.”
  • “Revise the PRD now that we are dropping payments from the MVP scope.”
  • “Run a guided interview to fill the gaps in the onboarding PRD.”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Glob, Grep, AskUserQuestion

What it can do on your machine

Read from SKILL.md and the folder at commit d26fb0d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Glob
    • Grep
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

MVP Product Requirements Writer loads about 455 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 27 tokens; SKILL.md has 219 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~27
When it runs · the whole SKILL.md, loaded when a task matches
~455
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from KhazP/vibe-coding-prompt-template at commit d26fb0d, republished under its MIT licence (© KhazP). 219 words, ~455 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-prd/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
vibe-prd
description
Write or revise an MVP product requirements document with scope and observable acceptance criteria.
allowed-tools
Read, Write, Glob, Grep, AskUserQuestion

Product requirements

Use existing research, the user's request, and Handoff Context to define the product outcome. Do not repeat an interview whose answers are already known. Ask only for unresolved requirements that affect scope or acceptance; make reversible assumptions explicit and continue when the brief is sufficient.

Write a PRD proportional to the product. Cover the target user and problem, the core journey, MVP scope, out-of-scope work, meaningful failure states, constraints, and observable acceptance criteria. Include AI, accounts, payments, analytics, compliance, or automation only when the product needs them.

For a small project, a short document is enough. For a complex one, clarify dependencies and consequential decisions before they block implementation. Avoid fixed feature counts, mandatory personas, or market research that does not change the product decision. Distinguish agreed facts from assumptions.

Use the manifest's configured PRD path or docs/PRD-[AppName]-MVP.md. End with Handoff Context carrying app, known user level, platform, budget, timeline, mode, constraints, decisions, source files, and open questions. Do not present planned acceptance checks as executed evidence. If the user requested the whole workflow, continue into the technical design within that scope.

For a guided interview with unresolved requirements, consult the relevant optional question prompts.

When producing a document for vibeworkflow, include the exact CLI output metadata. This is a parser contract, not an optional prose template.

© KhazP, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/vibe-prd of KhazP/vibe-coding-prompt-template.

  • SKILL.md
  • references/cli-output.md
  • references/question-bank.md

Open the folder on GitHubat commit d26fb0d

Compare with similar skills

MVP Product Requirements Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

MVP Product Requirements Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
MVP Product Requirements Writer this skillKhazP/vibe-coding-prompt-template3.1k—~455Automated safety check: PassMIT
Ouroboros PM InterviewQ00/ouroboros6.2k—~5.7kAutomated safety check: PassMIT
Qiaomu AI PRDjoeseesun/qiaomu-ai-prd211—~1.6kAutomated safety check: PassMIT
User Alignment and Agent-Ready PRDstryproduck/produck-skills511—~5.3kAutomated safety check: PassApache-2.0
Code to PRDalirezarezvani/claude-skills28k1 repos~4.9kAutomated safety check: PassMIT
Requirements From HTML Mocksimbue-ai/bouncer399—~410Automated safety check: PassAGPL-3.0

Similar skills

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub stars~5.7k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Qiaomu AI PRD

    joeseesun/qiaomu-ai-prd

    Turns a one-line product idea into an AI-implementable PRD with 11 chapters, a speed-read card, constraint layers and acceptance criteria, written Chinese-first.

    211 GitHub stars~1.6k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed

  • User Alignment and Agent-Ready PRDs

    tryproduck/produck-skills

    Turns a vague feature request into a written spec with scope, phases, acceptance criteria and do-not-do limits that a coding agent can follow without guessing.

    511 GitHub stars~5.3k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Product & Project ManagementAuto-check passed

  • Requirements From HTML Mocks

    imbue-ai/bouncer

    Turns an HTML mock iteration session into a requirements document that describes only user-facing behavior.

    399 GitHub stars~410 tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Creating Issues

    opsmill/infrahub

    Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue.

    534 GitHub stars~1.2k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from KhazP/vibe-coding-prompt-template

All 11 skills in this repo

  • Vibe Research

    KhazP/vibe-coding-prompt-template

    Researches an app idea or settles product and technical uncertainties before a design is fixed, and saves the findings with a handoff for the next stage.

    3.1k GitHub stars~473 tokensUpdated 5 days ago
    Auto-check passed

  • MVP Technical Design

    KhazP/vibe-coding-prompt-template

    Writes an MVP technical design from agreed requirements, covering architecture, data ownership, integration contracts, deployment and tradeoffs, then hands off to the next stage.

    3.1k GitHub stars~512 tokensUpdated 5 days ago
    Auto-check passed

  • Vibe Debug

    KhazP/vibe-coding-prompt-template

    A short debugging procedure for an existing project: reproduce the failure, test one hypothesis at a time, make the smallest fix, add a regression check and re-verify.

    3.1k GitHub stars~403 tokensUpdated 5 days ago
    Auto-check: notes

  • Vibe Workflow Router

    KhazP/vibe-coding-prompt-template

    Picks the next useful step for an app project, whether planning a new product, changing an existing app, fixing a bug or writing a handoff, loading only the context needed.

    3.1k GitHub stars~544 tokensUpdated 5 days ago
    Auto-check: notes

  • Vibe Agents Instructions

    KhazP/vibe-coding-prompt-template

    Writes project agent instructions and tool setup from decided requirements and the existing repo, keeping only stable, non-obvious guidance in always-loaded files.

    3.1k GitHub stars~421 tokensUpdated 5 days ago
    Auto-check: notes

  • Build a New-Project Slice

    KhazP/vibe-coding-prompt-template

    Builds one working slice of a new project from the brief, runs the affected checks and the user journey, and reports what was and was not verified.

    3.1k GitHub stars~353 tokensUpdated 5 days ago
    Auto-check: notes

Categories

Questions about MVP Product Requirements Writer

What does MVP Product Requirements Writer do?

Writes or revises an MVP product requirements document, sized to the product, with observable acceptance criteria and no repeated questions. The skill draws on existing research, the user's request and a handoff context to define the product outcome, rather than running a fresh interview whose answers are already known. It asks only about unresolved requirements that affect scope or acceptance, makes any reversible assumption explicit, and keeps going once the brief is sufficient rather than demanding a fixed set of answers.

When should I use MVP Product Requirements Writer?

MVP Product Requirements Writer fits situations like: writing a first-draft PRD for a new MVP feature; revising an existing PRD after requirements change; clarifying scope and acceptance criteria before implementation starts.

How do I install MVP Product Requirements Writer in Claude Code?

Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-prd -a claude-code`. Or copy the skill folder (.agents/skills/vibe-prd in KhazP/vibe-coding-prompt-template) into .claude/skills/vibe-prd in your project. Claude Code loads it when a task matches its description.

How do I install MVP Product Requirements Writer in Codex?

Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-prd -a codex`. Or copy the skill folder (.agents/skills/vibe-prd in KhazP/vibe-coding-prompt-template) into .agents/skills/vibe-prd in your project. Codex loads it when a task matches its description.

Can I use MVP Product Requirements Writer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-prd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-prd, .gemini/skills/vibe-prd, .github/skills/vibe-prd and .opencode/skills/vibe-prd in your project.

What does MVP Product Requirements Writer need to run?

SKILL.md names no scripts, command-line tools or credentials: MVP Product Requirements Writer is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Glob, Grep, AskUserQuestion.

Does MVP Product Requirements Writer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is MVP Product Requirements Writer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does MVP Product Requirements Writer use?

MVP Product Requirements Writer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does MVP Product Requirements Writer use?

About 455 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 854 tokens, read only when the agent opens those files.

What are the alternatives to MVP Product Requirements Writer?

Skills that share tags, products or a category with MVP Product Requirements Writer: Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), Qiaomu AI PRD (joeseesun/qiaomu-ai-prd, 211 stars), User Alignment and Agent-Ready PRDs (tryproduck/produck-skills, 511 stars) and Code to PRD (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains MVP Product Requirements Writer?

KhazP (a GitHub user) maintains it in KhazP/vibe-coding-prompt-template, which has 3,130 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 4, 2026.

Source: KhazP/vibe-coding-prompt-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.