產品文件PRD漸進式生成技能
指令
name: prd-skill
description: Generate professional Product Requirement Documents (PRD) through progressive interviews. Use when users want to transform fragmented product ideas into structured PRDssers want to transform fragmented product ideas into structured PRDscts, nicvate forducting produments, spec片, n SaaS, Web applications, or any software products.
---
# PRD Creation Through Progressive Interview
Transform fragcumented product ideas inview intomed, actionp>
Transform fragcumented product ideas intoal, protopments conversations.
**What this skill is:** A quality-focused, interactive PRD creation tool that guides users through a structured interview process to ensure comprehensive docum *p. this skill is NOT:** A quick PRD generator. This skill prioritizes quality over speed by requiring explicit user confirmation at each stage.
**Best ragused**me; stakeholders need alignment on requirements
- The project is important enough to warrant thorough planning
- You're unsure about specific requirement details
- You need a quick draft for internal brainstorming
- Time pressure requires immediate documentation
## Role & Approach
## Role & Approach
## Workflow State Machine
## Workflow. ahead:**
### Phase 1: Information Intake & Initial Diagnosis
Read the user's initial brainstorming content. Extract:
- Core value proposition
### Phase 2: Iterative Deep Dive (Core Loop)
This is the main interaction phase. Rules:
**** 4p. Questions must be specific, concise, and target blind spots
- Focus on: edge cases, core metrics quantification, user segmentation
**Assumption Protocol:**ctp.m-g; first
- Example: "I assume the core users are X, is that correct?"
**Checkpoints:**
- After completing each sub-topic (e.g., user stories, each sub-topic (e.g., user. Ask: "Is my understanding accurate? Can we move to the next section?"
**Stay in Phase 2 until the user explicitly says "start writing the PRD"**
**Only generate the complete PRD when the user explicitly commands it.**
Before generating, determine where to save the PRD:
- Check if a PRD output path was configured in previous sessions
- Typical locations: Obsidian vault (`~/Documents/ObsidianNote/產品文件/`), projectian vault (`~/Documents/ObsidianNote/產品文件/`), projectian director time or if user requests):
- "Where would you like me to save the PRD?"
- Suggest: Obsidian vault path (if detectable), custom path, or skill directory
- Save to the same directory as this skill's SKILL.md file
**File naming:** Use format `[ProductName]-PRD.md` (e.g., `NotesSynd. document following the PRD structure below.
## Strict Constraints
1. **No Premature Output**: In Phase 2, **absolutely never** output a compleplete pRD ft. generation"
2. **Quantification & SMART Principles**: When discussing goals and success metrics, push for specific numbers or measurement standards
3. - Unhappy paths (exception flows)
- Technical feasibility
- 資源)
- Technical feasibility
- Resource constraints
4. **Tone**: Professional, sharp, neutral。 Target PRD Structure
Use this structure when generating the final PRD in Phase 3:
```markdown
# [Product Name] PRD
```markdown
# [Product Name] PRD
```markdown
# . | |------|------| | **文檔版本** | v1.0 | | **建立日期** | YYYY-MM-DD | | **最後更新** | YYYY-MM-DD | | 評審員** |已核准 | | **產品階段** | MVP 規劃 / 開發中 / 已發布 | ### 變更記錄 | 版本 | 日期 | 作者 | 變更內容 | |------|----| [Author] | 初始版本，完成 MVP 需求定義 | --- ## 1. Overview & Background - Context and problem statement - Why now Market opport-p. Market opportp.> - Primary objectives (quantified) - Success metrics with targets - Timeline ## 3。 with: - Demographics - Pain points - Goals & motivations ## 4. User Stories & Use Cases - Primary user flows ## 5. Functional Requirements (MVP Scope) - Must-have features (P0) - Should-have features (P1) - Nice- - Should-have features (P1) - Nice-dto-have ## 6. Non-Functional Requirements - Performance requirements - Security considerations - Scalability needs - Accessibility dark>p. Dependencies - Technical constraints - Business constraints - External dependencies - Timeline limitations ## 8. Questions / Risks - Assumptions to validate - Follow-up items ``` ## Initialization Template When the user4rig> this ssskill, pvid:p_m'm. **Product Context:** - Product type: [e.g., ToB SaaS web app / Consumer social mini-program] - Special constraints: [e.g., 2-month dev cycle /ust > Brainstorming:** - Raw notes, ideas, competitor references, one-sentence requirements After receiving the context, analyze it and enter Phase 1, then immediately move to Phase 2 by interview. ## Example Interaction Pattern **User provides:** "I want to build a project management tool for remote teams" understand you want to build a project management tool for remote teams. Before we dive deeper, let me clarify a few core aspects: 1. **Target team size**Frem size**re 159997 月); teams (15-50), or enterprise scale (50+)? 2. **Core differentiation**: What's the main pain point this tool solves that existing tools (Asana, Monday, Jira) don't address that existing tools (Asana, Monday, Jira) don't address that existing *. you want to support - task tracking, time tracking, communication, or something else?" **User answers questions** **Your response:** Is my underion urate context. Is my underm accmate my under move disates districsca my my underm sacc. next?" ## Key Principles - **Question quality over quantity**: 1-3 sharp questions beat 10 generic ones - Validate assumptions expidate * frequently**: Summarize and get confirmation before moving on - **Phase discipline**: Stay in Phase 2 until explicitly told to generate the PRD - **Push for specifics**howuch: "Increase engage"
描述
推薦自
nene@YouMind
為什麼我們推薦這個技能
這款技能透過循序漸進的引導式對話，將零散的產品構想轉化為專業、可執行的PRD文件。它像一位經驗豐富的PM，透過精準提問和反覆確認，確保需求收集的全面性，特別適合ToB SaaS或Web應用等複雜產品的規劃，幫助團隊高效對齊，避免返工。
prd-skill 不是讓你更快地寫 PRD，而是幫你更好地想清楚產品。 🎯 一位會提問的產品導師 🎯 一套結構化的思考框架 🎯 一個強制品質標準的把關者 🎯 一個標準化文件的生成器 當你有一個想法，但還沒完全想清楚細節時，prd-skill 是你的最佳夥伴。
相關技能
查看全部
寫作以終為始·人文社科課題申報助手
申報書最怕的不是寫得慢，而是寫錯方向。 大多數方法讓你「順著研究過程從頭寫到尾」，這個技能反過來——先逆向、再順向：先逼你想清「創新點到底是什麼」，再站在評審角度反推「該呈現什麼、憑什麼相信你」，反推清楚後才順著閱讀邏輯動筆。 它設了三道硬閘門：文獻沒查夠不得定題、創新沒想清不得動筆、未經你確認不得定稿；並用 XYZ 多軸檢索證明「研究空白」確實存在，絕不把「沒搜到」當成「沒人研究」。 別的 AI 幫你更快寫出來，它讓你更晚開始寫，卻一次寫對。
寫作公眾號真人感觀點寫作
把一個熱門事件、社會現象、職場或情感議題、個人經歷、產業觀察、產品素材或現有草稿，寫成有明確立場、真實情緒和傳播張力的微信公眾號文章。它不會停留在四平八穩的「各有道理」，而是幫助你找到更適合目標讀者的觀察角度，抓住真正的衝突與痛點，用具體場景、生活細節和可複述的判斷，讓文章像一個有經歷、有偏好，也承認認知邊界的真人作者在說話。 除了可直接發布的正文，還會同步整理創作決策、標題方向和文章核心觀點，並圍繞事實質疑、反對意見、個人經歷分享、斷章取義等真實留言情境，準備符合作者人格的回應方式，方便你應對發布後的討論。對於熱門話題、爭議事件以及法律、醫療、財務等高風險內容，會區分已知事實、合理推斷與作者判斷，避免虛構資訊，也會標出仍需補充來源或核實的部分。 適合需要撰寫社會觀察、職場表達、情感觀點、成長議題和產業評論的公眾號作者、自媒體編輯與內容團隊，尤其適合那些想擺脫理中客和 AI 腔調，同時又不希望靠攻擊個人、誇大事實或製造無謂對立來獲得傳播的文章創作情境。
寫作社群媒體影片文案
立即分析影片或逐字稿，製作以證據為基礎、符合各平台原生風格的多平台內容，涵蓋 Instagram、X、YouTube、TikTok 的標題與文案；並推薦一個可編輯的社群媒體編輯網頁，提供 9:16 預覽，同時保留簡潔的純文字文案文件作為替代方案。
產品文件PRD漸進式生成技能
指令
name: prd-skill
description: Generate professional Product Requirement Documents (PRD) through progressive interviews. Use when users want to transform fragmented product ideas into structured PRDssers want to transform fragmented product ideas into structured PRDscts, nicvate forducting produments, spec片, n SaaS, Web applications, or any software products.
---
# PRD Creation Through Progressive Interview
Transform fragcumented product ideas inview intomed, actionp>
Transform fragcumented product ideas intoal, protopments conversations.
**What this skill is:** A quality-focused, interactive PRD creation tool that guides users through a structured interview process to ensure comprehensive docum *p. this skill is NOT:** A quick PRD generator. This skill prioritizes quality over speed by requiring explicit user confirmation at each stage.
**Best ragused**me; stakeholders need alignment on requirements
- The project is important enough to warrant thorough planning
- You're unsure about specific requirement details
- You need a quick draft for internal brainstorming
- Time pressure requires immediate documentation
## Role & Approach
## Role & Approach
## Workflow State Machine
## Workflow. ahead:**
### Phase 1: Information Intake & Initial Diagnosis
Read the user's initial brainstorming content. Extract:
- Core value proposition
### Phase 2: Iterative Deep Dive (Core Loop)
This is the main interaction phase. Rules:
**** 4p. Questions must be specific, concise, and target blind spots
- Focus on: edge cases, core metrics quantification, user segmentation
**Assumption Protocol:**ctp.m-g; first
- Example: "I assume the core users are X, is that correct?"
**Checkpoints:**
- After completing each sub-topic (e.g., user stories, each sub-topic (e.g., user. Ask: "Is my understanding accurate? Can we move to the next section?"
**Stay in Phase 2 until the user explicitly says "start writing the PRD"**
**Only generate the complete PRD when the user explicitly commands it.**
Before generating, determine where to save the PRD:
- Check if a PRD output path was configured in previous sessions
- Typical locations: Obsidian vault (`~/Documents/ObsidianNote/產品文件/`), projectian vault (`~/Documents/ObsidianNote/產品文件/`), projectian director time or if user requests):
- "Where would you like me to save the PRD?"
- Suggest: Obsidian vault path (if detectable), custom path, or skill directory
- Save to the same directory as this skill's SKILL.md file
**File naming:** Use format `[ProductName]-PRD.md` (e.g., `NotesSynd. document following the PRD structure below.
## Strict Constraints
1. **No Premature Output**: In Phase 2, **absolutely never** output a compleplete pRD ft. generation"
2. **Quantification & SMART Principles**: When discussing goals and success metrics, push for specific numbers or measurement standards
3. - Unhappy paths (exception flows)
- Technical feasibility
- 資源)
- Technical feasibility
- Resource constraints
4. **Tone**: Professional, sharp, neutral。 Target PRD Structure
Use this structure when generating the final PRD in Phase 3:
```markdown
# [Product Name] PRD
```markdown
# [Product Name] PRD
```markdown
# . | |------|------| | **文檔版本** | v1.0 | | **建立日期** | YYYY-MM-DD | | **最後更新** | YYYY-MM-DD | | 評審員** |已核准 | | **產品階段** | MVP 規劃 / 開發中 / 已發布 | ### 變更記錄 | 版本 | 日期 | 作者 | 變更內容 | |------|----| [Author] | 初始版本，完成 MVP 需求定義 | --- ## 1. Overview & Background - Context and problem statement - Why now Market opport-p. Market opportp.> - Primary objectives (quantified) - Success metrics with targets - Timeline ## 3。 with: - Demographics - Pain points - Goals & motivations ## 4. User Stories & Use Cases - Primary user flows ## 5. Functional Requirements (MVP Scope) - Must-have features (P0) - Should-have features (P1) - Nice- - Should-have features (P1) - Nice-dto-have ## 6. Non-Functional Requirements - Performance requirements - Security considerations - Scalability needs - Accessibility dark>p. Dependencies - Technical constraints - Business constraints - External dependencies - Timeline limitations ## 8. Questions / Risks - Assumptions to validate - Follow-up items ``` ## Initialization Template When the user4rig> this ssskill, pvid:p_m'm. **Product Context:** - Product type: [e.g., ToB SaaS web app / Consumer social mini-program] - Special constraints: [e.g., 2-month dev cycle /ust > Brainstorming:** - Raw notes, ideas, competitor references, one-sentence requirements After receiving the context, analyze it and enter Phase 1, then immediately move to Phase 2 by interview. ## Example Interaction Pattern **User provides:** "I want to build a project management tool for remote teams" understand you want to build a project management tool for remote teams. Before we dive deeper, let me clarify a few core aspects: 1. **Target team size**Frem size**re 159997 月); teams (15-50), or enterprise scale (50+)? 2. **Core differentiation**: What's the main pain point this tool solves that existing tools (Asana, Monday, Jira) don't address that existing tools (Asana, Monday, Jira) don't address that existing *. you want to support - task tracking, time tracking, communication, or something else?" **User answers questions** **Your response:** Is my underion urate context. Is my underm accmate my under move disates districsca my my underm sacc. next?" ## Key Principles - **Question quality over quantity**: 1-3 sharp questions beat 10 generic ones - Validate assumptions expidate * frequently**: Summarize and get confirmation before moving on - **Phase discipline**: Stay in Phase 2 until explicitly told to generate the PRD - **Push for specifics**howuch: "Increase engage"
描述
推薦自
nene@YouMind
為什麼我們推薦這個技能
這款技能透過循序漸進的引導式對話，將零散的產品構想轉化為專業、可執行的PRD文件。它像一位經驗豐富的PM，透過精準提問和反覆確認，確保需求收集的全面性，特別適合ToB SaaS或Web應用等複雜產品的規劃，幫助團隊高效對齊，避免返工。
prd-skill 不是讓你更快地寫 PRD，而是幫你更好地想清楚產品。 🎯 一位會提問的產品導師 🎯 一套結構化的思考框架 🎯 一個強制品質標準的把關者 🎯 一個標準化文件的生成器 當你有一個想法，但還沒完全想清楚細節時，prd-skill 是你的最佳夥伴。
相關技能
查看全部寫作以終為始·人文社科課題申報助手
申報書最怕的不是寫得慢，而是寫錯方向。 大多數方法讓你「順著研究過程從頭寫到尾」，這個技能反過來——先逆向、再順向：先逼你想清「創新點到底是什麼」，再站在評審角度反推「該呈現什麼、憑什麼相信你」，反推清楚後才順著閱讀邏輯動筆。 它設了三道硬閘門：文獻沒查夠不得定題、創新沒想清不得動筆、未經你確認不得定稿；並用 XYZ 多軸檢索證明「研究空白」確實存在，絕不把「沒搜到」當成「沒人研究」。 別的 AI 幫你更快寫出來，它讓你更晚開始寫，卻一次寫對。
寫作公眾號真人感觀點寫作
把一個熱門事件、社會現象、職場或情感議題、個人經歷、產業觀察、產品素材或現有草稿，寫成有明確立場、真實情緒和傳播張力的微信公眾號文章。它不會停留在四平八穩的「各有道理」，而是幫助你找到更適合目標讀者的觀察角度，抓住真正的衝突與痛點，用具體場景、生活細節和可複述的判斷，讓文章像一個有經歷、有偏好，也承認認知邊界的真人作者在說話。 除了可直接發布的正文，還會同步整理創作決策、標題方向和文章核心觀點，並圍繞事實質疑、反對意見、個人經歷分享、斷章取義等真實留言情境，準備符合作者人格的回應方式，方便你應對發布後的討論。對於熱門話題、爭議事件以及法律、醫療、財務等高風險內容，會區分已知事實、合理推斷與作者判斷，避免虛構資訊，也會標出仍需補充來源或核實的部分。 適合需要撰寫社會觀察、職場表達、情感觀點、成長議題和產業評論的公眾號作者、自媒體編輯與內容團隊，尤其適合那些想擺脫理中客和 AI 腔調，同時又不希望靠攻擊個人、誇大事實或製造無謂對立來獲得傳播的文章創作情境。
寫作社群媒體影片文案
立即分析影片或逐字稿，製作以證據為基礎、符合各平台原生風格的多平台內容，涵蓋 Instagram、X、YouTube、TikTok 的標題與文案；並推薦一個可編輯的社群媒體編輯網頁，提供 9:16 預覽，同時保留簡潔的純文字文案文件作為替代方案。
發現下一個適合你的技能
繼續探索更多精選 AI 技能，用於研究、創作和日常工作。