Individual skill
vibe-prd
Write or revise an MVP product requirements document with scope and observable acceptance criteria.
templates/.claude/skills/vibe-prd/SKILL.md
Source commit d26fb0d8a9cdac94cf99f004087620487e4da33d
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,227
- Repository last updated
- Oct 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-workflow Repository topic
- beginner-friendly Repository topic
- mvp-development Repository topic
- technical-design Repository topic
- vibe-coding Repository topic
- llm-tools Repository topic
- workflow-automation Repository topic
- claude-code Repository topic
- chatgpt Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,818 bytesSKILL.mdcore · 1,818 bytesreferences/cli-output.mddoc · 466 bytesreferences/question-bank.mddoc · 2,947 bytes
Read excerpt
# 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.