Menu
按公司 PRD 模板与示例写法输出结构完整、工程可执行的需求文档
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user asks for a deep code review, adversarial review, multi-agent review, risk-ranked review, PR review, security-sensitive review, or implementation verification with concrete file and line evidence.
Use when the user asks to debug a failing test, runtime error, regression, flaky behavior, production-like failure, root-cause analysis, or loop-until-done repair workflow.
Use when the user asks for source-backed research, official-documentation lookup, technical comparison, dependency evaluation, repository investigation plus synthesis, or fan-out research with ranked conclusions.
Use when the user asks for a dynamic workflow, multi-agent workflow, task-specific harness, complex task orchestration, fan-out synthesis, adversarial verification, generate-and-filter exploration, tournament-style solution search, or loop-until-done execution in Codex.
Wireframe workflow for low-fidelity structure, hierarchy, and information layout exploration.
Animation workflow for motion-heavy artifacts, scene timing, and browser playback review.
| name | prd-spec-generation |
| description | 按公司 PRD 模板与示例写法输出结构完整、工程可执行的需求文档 |
| version | v0.1 |
| template_version | 1.1 |
| owner | xiaoz |
| cn_title | PRD需求文档写作 |
| en_alias | prd-spec-generation |
| skill_family | prd |
| primary_artifact | PRD document |
01-discovery-research。04-roadmap-prioritization。05-meeting-review-synthesis。references/prd-template-sanitized.md：PRD 一级章节和核心表格硬模板references/prd-writing-patterns-sanitized.md：PRD 写法模式、P0-P4 优先级、页面逻辑和多模块联动写法references/prd-edge-cases-sanitized.md：AI 需求的边界处理、数据优先级、无信息回复原则references/source-coverage.md：本 skill 可使用的脱敏来源覆盖说明| Category | Typical tool types | Enable when | Avoid when | Expected evidence |
|---|---|---|---|---|
| Local docs/files | shell / file read / pdf text extraction | 用户给了 PRD 模板、历史需求文档、会议记录、PDF | 没有本地材料时不要虚构“历史规范” | 来源文件名 + 提取要点 |
| Structured docs | markdown / table / template writing | 需要输出标准 PRD、功能表、边界表、埋点表 | 不需要正式需求文档时避免过度模板化 | 完整 PRD 章节与表格 |
| Data analysis | spreadsheet / metric parsing | 需求涉及指标、埋点、实验结果、优先级量化 | 没有数据时不要编造 KPI | 指标来源、口径说明 |
| Web research | official docs / product pages / current facts | 用户明确要求补最新竞品/政策/标准能力 | 仅需按本地模板整理内部需求时 | 外部来源链接与时间说明 |
| No-browse reasoning | direct synthesis only | 本地材料已足够、只做内部需求整理 | 一旦要写“行业通行做法/竞品现在如何”就不能只靠记忆 | 基于本地材料的结构化重写 |
需求文档基础模版.pdf 作为硬模板。请把下面材料整理成正式 PRD：目标是“字字助手-报告编辑器智能审核”，材料包括一个旧版聊天助手需求文档、一个页面逻辑草稿、几条销售反馈和研发限制说明。请严格按 PRD 模板输出，必须保留“1需求背景、2用户场景、3功能需求（3.1功能清单 / 3.2功能详情）、4非功能需求、5埋点需求、6设计图”这六个一级章节；同时借鉴历史文档中的 P0-P4 优先级、页面逻辑、数据来源优先级、边界问题写法。