產品文件PRD漸進式產生技能
為什麼我們推薦這個技能
這項技能透過循序漸進的引導式對話，將零散的產品構想轉化為專業、可執行的PRD文件。它像一位經驗豐富的PM，透過精準提問和反覆確認，確保需求收集的全面性，特別適合ToB SaaS或Web應用等複雜產品的規劃，幫助團隊高效對齊，避免返工。
指令
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"
描述
prd-skill 不是讓你更快寫 PRD，而是幫你更想清楚產品。 🎯 一位會提問的產品導師 🎯 一套結構化的思考框架 🎯 一個強製品質標準的把關者 🎯 一個標準化文件的產生器 當你有一個想法，但還沒完全想清楚細節時，prd-skill 是你的最佳夥伴。
相關技能
查看全部
寫作曾國藩複盤skill
晨間複盤— 每天一次的結構化反思對話。讀取昨日日報，4 輪追問驅動認知複盤+ 今日優先提取。 觸發方式：/morning-review、/晨間複盤、/複盤、/review、“晨間複盤”“早上復盤”“morning review”“早上好”“來複盤”“開始復盤”“今天的複盤”“回顧一下昨天”“反思一下”“昨天的複盤”“回顧” 支持 qunings 快速模式：/ report, runs 4-question structured interview, extracts today's top 3 priorities. Saves output to Obsidian.
寫作學術論文AIGC降重與品質保真改寫專家v6.0
基於「源頭控制→過程糾偏→結果核查」三層遞進閉環，融合大循環鐵三角整體寫作觀、五源模型源頭控制、10種AI文本指紋診斷、三維度七亞類型細分診斷、13種句式變換手法與20個AI口頭禪消滅策略，在嚴守論文規範與保護原意的前提條件下，AIGC基礎針對投稿前論文全文或章節的AIGC風險診斷、偵測報告驅動改寫、目標期刊適配及投稿前終審。
寫作評審智能體提示詞教練
透過訪談式對話，一步步把老師"心裡有數但說不出來"的批改、評審標準萃取、顯性化，幫老師寫出一份完整、可直接部署到智能體平台（釦子/Coze、Dify、元器等）的作業批改智能體提示詞，附收指南、啟發式質性回饋、格式合規、元器等）的作業批改智能體提示詞，附收指南、啟發式質性回饋、格式合規、元器等）的作業批改智能體提示詞，附收指南、啟發式質性回饋、格式合規、元器等）的作業批改智能體提示字詞，附收指南、啟發式質性回饋、格式合規、元器等）的作業批改智能體提示詞，附收指南、啟發式質性回饋、格式合規、元器等）的作業批改智慧體提示字詞，附收指引小評式清單、多輪迭代表、多輪迭代、小評語、多輪迭代、小評定式，並附收成長小評。 產生的評價標準還能投給WORKBUDDY形成評審SKILL，呼叫該SKILL，讓WORKBUDDY自動幫你批改作業，尤其是「非良構」作業。
產品文件PRD漸進式產生技能
為什麼我們推薦這個技能
這項技能透過循序漸進的引導式對話，將零散的產品構想轉化為專業、可執行的PRD文件。它像一位經驗豐富的PM，透過精準提問和反覆確認，確保需求收集的全面性，特別適合ToB SaaS或Web應用等複雜產品的規劃，幫助團隊高效對齊，避免返工。
指令
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"
描述
prd-skill 不是讓你更快寫 PRD，而是幫你更想清楚產品。 🎯 一位會提問的產品導師 🎯 一套結構化的思考框架 🎯 一個強製品質標準的把關者 🎯 一個標準化文件的產生器 當你有一個想法，但還沒完全想清楚細節時，prd-skill 是你的最佳夥伴。
相關技能
查看全部寫作曾國藩複盤skill
晨間複盤— 每天一次的結構化反思對話。讀取昨日日報，4 輪追問驅動認知複盤+ 今日優先提取。 觸發方式：/morning-review、/晨間複盤、/複盤、/review、“晨間複盤”“早上復盤”“morning review”“早上好”“來複盤”“開始復盤”“今天的複盤”“回顧一下昨天”“反思一下”“昨天的複盤”“回顧” 支持 qunings 快速模式：/ report, runs 4-question structured interview, extracts today's top 3 priorities. Saves output to Obsidian.
寫作學術論文AIGC降重與品質保真改寫專家v6.0
基於「源頭控制→過程糾偏→結果核查」三層遞進閉環，融合大循環鐵三角整體寫作觀、五源模型源頭控制、10種AI文本指紋診斷、三維度七亞類型細分診斷、13種句式變換手法與20個AI口頭禪消滅策略，在嚴守論文規範與保護原意的前提條件下，AIGC基礎針對投稿前論文全文或章節的AIGC風險診斷、偵測報告驅動改寫、目標期刊適配及投稿前終審。
寫作評審智能體提示詞教練
透過訪談式對話，一步步把老師"心裡有數但說不出來"的批改、評審標準萃取、顯性化，幫老師寫出一份完整、可直接部署到智能體平台（釦子/Coze、Dify、元器等）的作業批改智能體提示詞，附收指南、啟發式質性回饋、格式合規、元器等）的作業批改智能體提示詞，附收指南、啟發式質性回饋、格式合規、元器等）的作業批改智能體提示詞，附收指南、啟發式質性回饋、格式合規、元器等）的作業批改智能體提示字詞，附收指南、啟發式質性回饋、格式合規、元器等）的作業批改智能體提示詞，附收指南、啟發式質性回饋、格式合規、元器等）的作業批改智慧體提示字詞，附收指引小評式清單、多輪迭代表、多輪迭代、小評語、多輪迭代、小評定式，並附收成長小評。 產生的評價標準還能投給WORKBUDDY形成評審SKILL，呼叫該SKILL，讓WORKBUDDY自動幫你批改作業，尤其是「非良構」作業。
發現下一個適合你的技能
繼續探索更多精選 AI 技能，用於研究、創作和日常工作。