generar-prd

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

PRD Generator (Light)

PRD Generator(轻量化版)

Goal

目标

Generate a first-draft PRD that is intentionally fast and light — a starting point to review and refine, not a finished requirements process. This skill does not replace deep product discovery; it exists to unblock the next phase (design, architecture) with a working draft.
The primary outcome is a file written to disk:
PRD.md
at the project root, unless the user specifies another path.
生成一份刻意追求快速、轻量化的PRD初稿——作为审阅和完善的起点,而非完整的需求流程产物。本Skill无法替代深度产品探索;它的作用是通过一份可用初稿,为下一阶段(设计、架构)扫清障碍。
核心产出是写入磁盘的文件:项目根目录下的
PRD.md
,除非用户指定其他路径。

Required Input

必填输入

Before writing, the user must have provided (or be asked for, in a single concise question if missing):
  • The product idea, in a sentence or two.
  • Who it's for (target user).
  • The core problem it solves.
If any of these three is missing or too vague to write a meaningful PRD, ask once, concisely, before generating. Do not invent the product idea itself — secondary details (success criteria, edge cases) may be filled as best-effort suggestions the user is expected to revise.
生成前,用户必须已提供(若缺失则以简洁的单个问题询问)以下信息:
  • 产品想法(一两句话描述)
  • 目标用户
  • 解决的核心问题
若上述三项中有任何一项缺失或过于模糊,无法生成有意义的PRD,则在生成前简洁询问一次。不得自行编造产品想法——次要细节(成功标准、边缘案例)可作为尽力而为的建议补充,供用户后续修订。

Workflow

工作流程

  1. Confirm the three required inputs (idea, target user, problem). Ask once if missing.
  2. Generate
    PRD.md
    using the template in
    assets/prd-template.md
    , filling every section. Leave no placeholder unresolved — if information is missing, write a best-effort draft and flag it inline with
    <!-- REVISAR: ... -->
    .
  3. Write the file to disk. Do not just paste the PRD into chat.
  4. Close with a short reminder: this is a fast draft (minutes) — the real work is the review that follows (ambiguities, success criteria, scope, edge cases) before using it as input for design or architecture.
  1. 确认三项必填输入(想法、目标用户、问题)。若有缺失则询问一次。
  2. 使用
    assets/prd-template.md
    中的模板生成
    PRD.md
    ,填充所有章节。不得留下未处理的占位符——若信息缺失,则撰写尽力而为的草稿,并使用
    <!-- REVISAR: ... -->
    在文中标记。
  3. 将文件写入磁盘。不得仅将PRD粘贴至聊天窗口。
  4. 最后附上简短提醒:这是一份快速生成的草稿(仅需数分钟)——在将其用作设计或架构的输入前,后续的审阅工作(明确模糊点、完善成功标准、界定范围、梳理边缘案例)才是关键。

PRD.md Sections

PRD.md章节

See
assets/prd-template.md
for the full template. Sections, in order:
  • Problema
  • Usuario objetivo
  • Objetivo / resultado esperado
  • Alcance (qué sí incluye esta versión)
  • No alcance (qué explícitamente no incluye esta versión)
  • Criterios de éxito
  • Casos borde a contemplar
  • Supuestos y riesgos abiertos
完整模板请查看
assets/prd-template.md
。章节顺序如下:
  • 问题
  • 目标用户
  • 目标/预期结果
  • 范围(当前版本包含内容)
  • 排除范围(当前版本明确不包含内容)
  • 成功标准
  • 需考虑的边缘案例
  • 假设与未解决风险

Quality Gate

质量检查

Before returning, silently check:
  • No section is empty — a thin bullet beats a missing section.
  • "No alcance" contains at least one explicit exclusion, not just "todo lo no mencionado".
  • Success criteria are verifiable, not vague adjectives ("rápido", "intuitivo") without a measurable anchor.
  • Any assumption the model made stands out with
    <!-- REVISAR: ... -->
    so the human catches it during review.
返回前需静默检查:
  • 所有章节均不得为空——即使是简短的项目符号也比缺失章节要好。
  • “排除范围”需包含至少一项明确的排除内容,不得仅写“所有未提及内容”(todo lo no mencionado)。
  • 成功标准需可验证,不得是无衡量依据的模糊形容词(如“快速(rápido)”、“直观(intuitivo)”)。
  • 模型做出的任何假设需用
    <!-- REVISAR: ... -->
    标记,以便用户在审阅时注意到。