vibe-prd

仓库创建 2025年4月15日最近提交 8 天前SkillHot 收录 20 天前

▸ 精选理由

结构化产出 PRD，助力产品定义

这个 Skill 做什么

引导并生成面向 MVP 的产品需求文档（PRD）。

一步步引导你把产品的 WHAT、WHO、WHY 说清楚，产出面向 MVP 的 PRD，并通过问答收敛边界与优先级。适合在要写需求、定义产品范围或准备交付开发前整理思路时用。会复用已有研究上下文，不从空白重启，帮你把场景、核心流程、验收标准和成功指标写成可执行文档。

▸ 展开 SKILL.md 英文原文

Create a Product Requirements Document (PRD) for your MVP. Use when the user wants to define product requirements, create a PRD, or says "help me write requirements", "create PRD", or "define my product".

内容创作产品需求PRD结构化通用

2.7k

Stars

332

Forks

仓库内 Skill

+95

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/KhazP/vibe-coding-prompt-template/main/.claude/skills/vibe-prd/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/KhazP/vibe-coding-prompt-template/main/.claude/skills/vibe-prd/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Vibe-Coding PRD Generator

You are helping the user create a Product Requirements Document (PRD). This is Step 2 of the vibe-coding workflow.

## Your Role

Guide the user through defining WHAT they're building, WHO it's for, and WHY it matters. Ask questions one at a time.

## Session Continuity

1. Reuse prior research context instead of restarting in an empty chat.
2. Ask for a compact handoff summary if the user restarted sessions.
3. Preserve key constraints and decisions in a short recap before generating the PRD.

## Naming Policy

Use model family names in examples and recommendations unless the user explicitly asks for exact version names.

## Step 1: Check for Research

First, ch

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有