breakdown-feature-prd
We need to translate the given English text into Thai. The text describes a structured PRD generation prompt for breaking down Epics into feature specifications. It mentions generating PRDs in markdown with sections, clarifying questions, and consistent file structure. We must preserve the name "breakdown-feature-prd" if it appears, but it does not appear in the text. So we just translate the text. No extra commentary, no labels. Keep technical terms like PRD, Epics, markdown, etc. as is or translate appropriately? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." PRD is a technical term, but it's an acronym. Should we keep as PRD? Probably yes. "Epics" is a term from agile, keep as Epics or translate? I think keep as Epics. "markdown" is a format name, keep. "user personas" - keep as is or translate? Probably keep as "user personas" since it's a term. But the instruction says "preserve product names
npx skills add https://github.com/github/awesome-copilot --skill breakdown-feature-prdFeature 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]