Guides the drafting of clear product requirements and acceptance criteria.
Install
mkdir -p .claude/skills/prd-tai-ch0802 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17546" && unzip -o skill.zip -d .claude/skills/prd-tai-ch0802 && rm skill.zipInstalls to .claude/skills/prd-tai-ch0802
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
撰寫本專案的 PRD (產品需求文件)，位置為 /docs/specs/{type}/{ID-PREFIX}_{desc}/PRD_spec.md。當使用者提到「PRD、產品需求、需求文件、寫規格、新功能規劃、acceptance criteria」時觸發。分級 SDD 之 T2（完整流程）的 Phase 1，產出物提供給 sa skill 銜接；T1 輕量案件不需獨立 PRD。Key capabilities
- →Define product background and goals
- →Write user stories and functional requirements
- →Outline UI/UX flows
- →Define acceptance criteria using Given-When-Then
How it works
It guides the user through drafting a PRD, covering sections like background, goals, user stories, functional and non-functional requirements, UI/UX flows, and analytics. It emphasizes clear language and Given-When-Then acceptance criteria.
Inputs & outputs
When to use prd
- →Drafting a new feature spec
- →Defining acceptance criteria for a bug fix
- →Creating product documentation
About this skill
Product Requirement Document (PRD) Skill
本技能旨在協助撰寫結構完整、邏輯清晰的產品需求文件 (PRD)。PRD 是產品的核心藍圖，它告訴我們「為什麼要建構這個產品」以及「它應該具備什麼功能」。
適用層級：本 skill 屬於分級 SDD 的 T2（完整流程）Phase 1。 T1 輕量案件直接用
sddskill 的單檔SPEC.md即可，不需獨立 PRD； 分級判準見.agent/skills/sdd/SKILL.md（單一事實來源）。
為何需要 PRD？
- 對齊目標: 確保開發者、設計師和利害關係人對產品有共同的理解。
- 減少歧義: 透過清晰的文字與圖表，將模糊的想法轉化為具體的需求。
- 作為測試基準: PRD 中的驗收標準 (Acceptance Criteria) 是 QA 測試的依據。
PRD 核心組成
一份完整的 PRD 通常包含以下章節：
- 背景與目標 (Background & Goals): 為什麼要做？解決什麼問題？成功指標是什麼？
- 使用者故事 (User Stories): 誰是使用者？他們想要做什麼？為了達到什麼目的？
- 功能需求 (Functional Requirements): 具體的系統行為描述。
- 非功能需求 (Non-Functional Requirements): 性能、安全性、可靠性等限制。
- UI/UX 流程 (User Interaction): 頁面流程圖、Wireframe 或 Mockup 連結。
- 數據埋點 (Analytics): 需要追蹤哪些使用者行為數據。
- 未包含範圍 (Out of Scope): 明確定義什麼 不做，以避免範圍蔓延 (Scope Creep)。
如何使用此 Skill
當 User 提出一個模糊的想法 (e.g., "我想做一個讓使用者可以分享書籤的功能")，請依循以下步驟：
- Initial Interview: 詢問 User 關鍵問題 (Who, Why, What)。
- Drafting: 使用
template_comprehensive.md(完整版) 或template_simple.md(簡易版) 起草 PRD。 - Review: 請 User 審閱草稿，確認是否符合預期。
- Finalize: 定稿後，這份 PRD 將成為後續 SA (系統分析) 和 SDD (開發規格) 的輸入。
技巧與最佳實踐
- 使用清晰的語言: 避免 "可能"、"應該" 等模糊詞彙，使用 "必須" (Shall/Must)、"可以" (Can) 等明確用語。
- 圖文並茂: 盡量使用流程圖 (Mermaid) 來輔助文字說明。
- 保持更新: PRD 是活的文件 (Living Document)，若需求變更，務必更新 PRD。
本專案 PRD 慣例（呼應 sdd skill）
- 檔案位置：
/docs/specs/{type}/{ID-PREFIX}_{desc}/PRD_spec.mdtype：feature/fix/refactor/choreID_PREFIX：ISSUE-{n}（一般功能／bug，對應 GitHub Issue）／PR-{n}（外部貢獻無 Issue）／BASE-{n}（歷史補規格）
- Functional Requirements：建議使用 EARS syntax（Event-driven / Unwanted / State / Optional / Complex）。
- Acceptance Criteria：必須使用 Given-When-Then 三段式，每條 AC 都要可驗證。
- Out of Scope：明確列出「這次不做」的項目，避免 scope creep；後續若補做，另立 PRD 版本。
- Living Document：Frozen 後變更須 bump 版本（v1.0 → v1.1），在 Revision History 記原因。
Chrome Extension 專案的 PRD 重點
- 使用者介面類型：明確標註是 sidepanel / popup / content script / new tab override / context menu。
- 權限申請：列出新功能要 manifest.json 加哪些
permissions/host_permissions，並說明最小化策略。 - 跨裝置同步：若涉及
chrome.storage.sync，要評估 quota（每項 8KB，總計 100KB）。 - 多語系影響：若新增 UI 文案，要在 PRD 提醒「同步觸發 update-multilingual-docs」。
When not to use it
- →When the task is a lightweight case that doesn't require a separate PRD
- →When the user wants to ignore scope definition
- →When the document is not intended to be a living document
Limitations
- →Requires explicit definition of out-of-scope items
- →Acceptance criteria must be verifiable
- →PRD is a living document and requires updates
How it compares
This skill structures product requirements into a formal PRD, ensuring alignment among stakeholders and providing a clear basis for subsequent technical analysis, unlike informal feature descriptions.
Compared to similar skills
prd side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| prd (this skill) | 0 | 1mo | No flags | Intermediate |
| internal-comms | 8 | 3mo | No flags | Beginner |
| startup-business-analyst-business-case | 6 | 3mo | No flags | Beginner |
| getting-started-guide | 1 | 7mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Tai-ch0802
View all by Tai-ch0802 →You might also like
internal-comms
anthropics
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
startup-business-analyst-business-case
sickn33
Generate comprehensive investor-ready business case document with market, solution, financials, and strategy
getting-started-guide
Microck
当用户开始新小说项目时激活 - 通过温和的提示和解释引导他们完成七步方法论（constitution → specify → clarify → plan → tasks → write → analyze）
content-creation-flow
OutSystems
Step-by-step content creation workflow for documentation and training materials. Includes MCP validation, discovery, content design, Jira planning, and draft generation with priority-based execution. Use when starting the content creation flow, creating documentation or training materials, or when t
project-proposals
SofiaDT
When the user wants to write a project proposal, business case, project charter, or project brief to get something approved. Use when the user says "I need to write a proposal," "business case," "project charter," "getting this approved," "I need to make the case for this project," or "project brief
write-a-prd
twentyonedot
Create a PRD through user interview, codebase exploration, and module design. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.