Security & Compliancelow risk
breakdown-feature-prd
Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.
github/awesome-copilot·skills/breakdown-feature-prd/SKILL.md
100/ 100品質分
匯入這個 Skill
選擇你的 coding agent，複製專案級或個人級安裝指令。
匯入目前專案.agents/skills/breakdown-feature-prd
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/breakdown-feature-prd -a codex -y匯入個人環境~/.agents/skills/breakdown-feature-prd
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/breakdown-feature-prd -a codex -g -y匯入目前專案.claude/skills/breakdown-feature-prd
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/breakdown-feature-prd -a claude-code -y匯入個人環境~/.claude/skills/breakdown-feature-prd
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/breakdown-feature-prd -a claude-code -g -y匯入目前專案.agents/skills/breakdown-feature-prd
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/breakdown-feature-prd -a github-copilot -y匯入個人環境~/.copilot/skills/breakdown-feature-prd
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/breakdown-feature-prd -a github-copilot -g -y匯入目前專案.agents/skills/breakdown-feature-prd
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/breakdown-feature-prd -a cursor -y匯入個人環境~/.cursor/skills/breakdown-feature-prd
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/breakdown-feature-prd -a cursor -g -y匯入目前專案.agents/skills/breakdown-feature-prd
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/breakdown-feature-prd -a gemini-cli -y匯入個人環境~/.gemini/skills/breakdown-feature-prd
npx skills add https://github.com/github/awesome-copilot/tree/0aaced533251f5b86c69dfbc5e55db74c4b4d1af/skills/breakdown-feature-prd -a gemini-cli -g -yNative Gemini CLI
gemini skills install https://github.com/github/awesome-copilot.git --scope workspace --path skills/breakdown-feature-prd⚠ 安裝指令使用開源 skills CLI。執行前請檢查來源、腳本與權限。
Skill 指令
在 GitHub 查看原始檔案 ↗# Feature PRD Prompt
## Goal
Act as an expert Product Manager for a large-scale SaaS platform. Your primary responsibility is to take a high-level feature or enabler from an Epic and create a detailed Product Requirements Document (PRD). This PRD will serve as the single source of truth for the engineering team and will be used to generate a comprehensive technical specification.
Review the user's request for a new feature and the parent Epic, and generate a thorough PRD. If you don't have enough information, ask clarifying questions to ensure all aspects of the feature are well-defined.
## Output Format
The output should be a complete PRD in Markdown format, saved to `/docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md`.
### PRD Structure
#### 1. Feature Name
- A clear, concise, and descriptive name for the feature.
#### 2. Epic
- Link to the parent Epic PRD and Architecture documents.
#### 3. Goal
- **Problem:** Describe the user problem or business need this feature addresses (3-5 sentences).
- **Solution:** Explain how this feature solves the problem.
- **Impact:** What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, etc.)?
#### 4. User Personas
- Describe the target user(s) for this feature.
#### 5. User Stories
- Write user stories in the format: "As a `<user persona>`, I want to `<perform an action>` so that I can `<achieve a benefit>`."
- Cover the primary paths and edge cases.
#### 6. Requirements
- **Functional Requirements:** A detailed, bulleted list of what the system must do. Be specific and unambiguous.
- **Non-Functional Requirements:** A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy).
#### 7. Acceptance Criteria
- For each user story or major requirement, provide a set of acceptance criteria.
- Use a clear format, such as a checklist or Given/When/Then. This will be used to validate that the feature is complete and correct.
#### 8. Out of Scope
- Clearly list what is _not_ included in this feature to avoid scope creep.
## Context Template
- **Epic:** [Link to the parent Epic documents]
- **Feature Idea:** [A high-level description of the feature request from the user]
- **Target Users:** [Optional: Any initial thoughts on who this is for]