產品文件PRD漸進式產生技能
Featured by
nene@YouMind.AI
Why we love this skill
這項技能透過循序漸進的引導式對話，將零散的產品構想轉化為專業、可執行的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"
description
prd-skill 不是讓你更快寫 PRD，而是幫你更想清楚產品。 🎯 一位會提問的產品導師 🎯 一套結構化的思考框架 🎯 一個強製品質標準的把關者 🎯 一個標準化文件的產生器 當你有一個想法，但還沒完全想清楚細節時，prd-skill 是你的最佳夥伴。
Related Skills
View all
課程大綱包裝師
將老師提供的學術課程大綱，改造為具有行銷吸引力的課程詳情頁文案，包含主標題、Slogan、亮點、課綱等完整模組，忠實於原始內容，不誇大、不偏離。
課程變現策劃師
您是否擁有專業知識和獨特經驗，卻苦於不知如何轉化為有價值的課程產品？ 「課程變現策劃師」能為您提供一站式解決方案，助您從零開始，系統策劃一門能成功變現的爆款課程。本技能將引導您深入挖掘自身優勢，精準定位市場需求，並結合您的實際情況，量身訂做課程開發策略。 透過與AI的對話式共創，您將逐步完成課程的定位、內容體系建構、教學設計以及商業變現規劃。我們不僅幫助您整理知識架構、設計引人入勝的教學環節，還會為您提煉核心賣點，建構「引流—信任—利潤—高端」的產品矩陣，並規劃切實可行的變現路徑。無論是培訓師、知識部落客或企業內訓師，本技能都能成為您的得力助手，將您的專業累積轉化為實實在在的市場價值。 最終，您將獲得一份完整的課程開發規劃案，涵蓋從使用者畫像、課程大綱到教學方法、PPT框架建議，再到變現策略的全部細節。這份詳細的規劃案將為您後續的課程製作和推廣提供清晰指引，確保您的知識產品不僅內容紮實，更具市場競爭力和商業成功潛力。
AI科學研究繪圖顧問
專為學術研究者打造的AI圖表生成顧問。輸入你的研究主題或論文段落，它會自動解析核心變數和邏輯關係，從7+1種學術圖表類型（內容框架圖、技術路線圖、研究思路圖、理論框架圖、分析框架圖、研究結論圖、紮根理論模型圖）中精準匹配，再從10種結構佈局（線性流程、閉環循環、中心輻射、矩陣矩陣模型圖）中精準匹配，再從10種結構佈局（線性流程、閉環循環、中心輻射、矩陣矩陣、矩陣式等標準尺寸，內建"道vs術"和"借vs造"雙重糾偏－再也不會分不清技術路線圖和研究思路圖。
產品文件PRD漸進式產生技能
Featured by
nene@YouMind.AI
Why we love this skill
這項技能透過循序漸進的引導式對話，將零散的產品構想轉化為專業、可執行的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"
description
prd-skill 不是讓你更快寫 PRD，而是幫你更想清楚產品。 🎯 一位會提問的產品導師 🎯 一套結構化的思考框架 🎯 一個強製品質標準的把關者 🎯 一個標準化文件的產生器 當你有一個想法，但還沒完全想清楚細節時，prd-skill 是你的最佳夥伴。
Related Skills
View all課程大綱包裝師
將老師提供的學術課程大綱，改造為具有行銷吸引力的課程詳情頁文案，包含主標題、Slogan、亮點、課綱等完整模組，忠實於原始內容，不誇大、不偏離。
課程變現策劃師
您是否擁有專業知識和獨特經驗，卻苦於不知如何轉化為有價值的課程產品？ 「課程變現策劃師」能為您提供一站式解決方案，助您從零開始，系統策劃一門能成功變現的爆款課程。本技能將引導您深入挖掘自身優勢，精準定位市場需求，並結合您的實際情況，量身訂做課程開發策略。 透過與AI的對話式共創，您將逐步完成課程的定位、內容體系建構、教學設計以及商業變現規劃。我們不僅幫助您整理知識架構、設計引人入勝的教學環節，還會為您提煉核心賣點，建構「引流—信任—利潤—高端」的產品矩陣，並規劃切實可行的變現路徑。無論是培訓師、知識部落客或企業內訓師，本技能都能成為您的得力助手，將您的專業累積轉化為實實在在的市場價值。 最終，您將獲得一份完整的課程開發規劃案，涵蓋從使用者畫像、課程大綱到教學方法、PPT框架建議，再到變現策略的全部細節。這份詳細的規劃案將為您後續的課程製作和推廣提供清晰指引，確保您的知識產品不僅內容紮實，更具市場競爭力和商業成功潛力。
AI科學研究繪圖顧問
專為學術研究者打造的AI圖表生成顧問。輸入你的研究主題或論文段落，它會自動解析核心變數和邏輯關係，從7+1種學術圖表類型（內容框架圖、技術路線圖、研究思路圖、理論框架圖、分析框架圖、研究結論圖、紮根理論模型圖）中精準匹配，再從10種結構佈局（線性流程、閉環循環、中心輻射、矩陣矩陣模型圖）中精準匹配，再從10種結構佈局（線性流程、閉環循環、中心輻射、矩陣矩陣、矩陣式等標準尺寸，內建"道vs術"和"借vs造"雙重糾偏－再也不會分不清技術路線圖和研究思路圖。
Find your next favorite skill
Explore more curated AI skills for research, creation, and everyday work.