跳到主内容
智客 ZICQ

技能库 智客分类:文档办公 prd

Prd

生成高质量 软件系统和AI动力特性的产品要求文件(PRD). 包括内容提要、用户故事、技术规格和风险分析.

24665 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

生成高质量 软件系统和AI动力特性的产品要求文件(PRD). 包括内容提要、用户故事、技术规格和风险分析.

何时用

当 :

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Product Requirements Document (PRD)、Overview、When to Use、Operational Workflow、Phase 1: Discovery (The Interview)、Phase 2: Analysis & Scoping。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

Product Requirements Document (PRD)OverviewWhen to UseOperational WorkflowPhase 1: Discovery (The Interview)Phase 2: Analysis & ScopingPhase 3: Technical DraftingPRD Quality StandardsRequirements QualityVague (BAD)Concrete (GOOD)Strict PRD Schema

· 许可:MIT

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
prd
description
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
许可
MIT
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「prd」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-0583aa812a2cc254-%E7%BA%B8.html
请存为 .cursor/skills/prd/SKILL.md 或 .claude/skills/prd/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/github/awesome-copilot' --list

npx skills add 'https://github.com/github/awesome-copilot' --skill 'prd'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: prd description: 'Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.' license: MIT

Product Requirements Document (PRD)

Overview

Design comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined.

When to Use

Use this skill when:

  • Starting a new product or feature development cycle
  • Translating a vague idea into a concrete technical specification
  • Defining requirements for AI-powered features
  • Stakeholders need a unified "source of truth" for project scope
  • User asks to "write a PRD", "document requirements", or "plan a feature"

Operational Workflow

Phase 1: Discovery (The Interview)

Before writing a single line of the PRD, you MUST interrogate the user to fill knowledge gaps. Do not assume context.

Ask about:

  • The Core Problem: Why are we building this now?
  • Success Metrics: How do we know it worked?
  • Constraints: Budget, tech stack, or deadline?

Phase 2: Analysis & Scoping

Synthesize the user's input. Identify dependencies and hidden complexities.

  • Map out the User Flow.
  • Define Non-Goals to protect the timeline.

Phase 3: Technical Drafting

Generate the document using the Strict PRD Schema below.


PRD Quality Standards

Requirements Quality

Use concrete, measurable criteria. Avoid "fast", "easy", or "intuitive".

# Vague (BAD)
- The search should be fast and return relevant results.
- The UI must look modern and be easy to use.

# Concrete (GOOD)
+ The search must return results within 200ms for a 10k record dataset.
+ The search algorithm must achieve >= 85% Precision@10 in benchmark evals.
+ The UI must follow the 'Vercel/Next.js' design system and achieve 100% Lighthouse Accessibility score.

Strict PRD Schema

You MUST follow this exact structure for the output:

1. Executive Summary

  • Problem Statement: 1-2 sentences on the pain point.
  • Proposed Solution: 1-2 sentences on the fix.
  • Success Criteria: 3-5 measurable KPIs.

2. User Experience & Functionality

  • User Personas: Who is this for?
  • User Stories: As a [user], I want to [action] so that [benefit].
  • Acceptance Criteria: Bulleted list of "Done" definitions for each story.
  • Non-Goals: What are we NOT building?

3. AI System Requirements (If Applicable)

  • Tool Requirements: What tools and APIs are needed?
  • Evaluation Strategy: How to measure output quality and accuracy.

4. Technical Specifications

  • Architecture Overview: Data flow and component interaction.
  • Integration Points: APIs, DBs, and Auth.
  • Security & Privacy: Data handling and compliance.

5. Risks & Roadmap

  • Phased Rollout: MVP -> v1.1 -> v2.0.
  • Technical Risks: Latency, cost, or dependency failures.

Implementation Guidelines

DO (Always)

  • Define Testing: For AI systems, specify how to test and validate output quality.
  • Iterate: Present a draft and ask for feedback on specific sections.

DON'T (Avoid)

  • Skip Discovery: Never write a PRD without asking at least 2 clarifying questions first.
  • Hallucinate Constraints: If the user didn't specify a tech stack, ask or label it as TBD.

Example: Intelligent Search System

1. Executive Summary

Problem: Users struggle to find specific documentation snippets in massive repositories. Solution: An intelligent search system that provides direct answers with source citations. Success:

  • Reduce search time by 50%.
  • Citation accuracy >= 95%.

2. User Stories

  • Story: As a developer, I want to ask natural language questions so I don't have to guess keywords.
  • AC:
    • Supports multi-turn clarification.
    • Returns code blocks with "Copy" button.

3. AI System Architecture

  • Tools Required: codesearch, grep, webfetch.

4. Evaluation

  • Benchmark: Test with 50 common developer questions.
  • Pass Rate: 90% must match expected citations.

相关技能

文档办公

Ontology

为结构化的代理内存和可堆肥技能所打入的知识图. 在创建/征服实体(Person, project, Task, Evention, Document)时使用,链接相关对象,强制约束,规划多步动作作为图变,或技能需要共享状态时使用. 触发到"记住","我知道什么","链接X到Y",…

文档办公

Nano Pdf

使用纳米-pdf CLI编辑带有自然语言指令的PDF.

文档办公

Word / DOCX

创建,检查,并编辑有可靠样式的Microsoft Word文档和DOCX文件,编号,跟踪更改,表格,章节,并进行相容性检查. 当 (1) 任务涉及 Word 或 ".docx " 时使用; (2) 文件包括跟踪的更改,评论,字段,表格,模板,或页面布局限制; (3) 文档必须在不…

文档办公

Api Gateway

通过 Maton 网关调用第三方 API, 它为用户已经连接的应用程序注入证书 。 当用户命名一个连接的应用程序和其中的具体行动时使用此技能——读取一个邮箱,查询一个CMM,归档一个问题,更新一个电子表格,通过一个连接的搜索或刮取提供者运行一个查询. 每一次通话都到用户连接的应用…