mcpField
V
vibe-prd

vibe-prd

github.com/khazpDevelopment3.2k180 installsUpdated 3w ago
Repository

About vibe-prd

vibe-prd is a skill for creating product requirements documents from available research, user requests, and handoff context. It scales the document to the product, records scope and acceptance criteria, and distinguishes known facts from assumptions.

Key features

  1. 01Defines users, problems, and core journeys
  2. 02Scales PRD detail to project complexity
  3. 03Records scope, constraints, and failure states
  4. 04Adds observable acceptance criteria
  5. 05Carries decisions and open questions forward

Use cases

  1. 01Writing an MVP product requirements document
  2. 02Clarifying unresolved scope decisions
  3. 03Passing product context to technical design
  4. 04Recording assumptions and acceptance criteria

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/khazp/vibe-coding-prompt-template --skill vibe-prd

After installing, type/vibe-prdin Claude Code to confirm it loaded.

Bundled filesreferences/cli-output.mdreferences/question-bank.md

Details

From the project README

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.

Comments

Markdown supported