Skip to main content

breakdown-epic-pm

Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.

Informations de source

Dépôt
github/awesome-copilot
Dernière activité de la source
24 février 2026 à 03:39
Langue détectée de SKILL.md
anglais
Étoiles
40 063
Forks
5 129

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
name
breakdown-epic-pm
description
Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.
# Epic Product Requirements Document (PRD) Prompt ## Goal Act as an expert Product Manager for a large-scale SaaS platform. Your primary responsibility is to translate high-level ideas into detailed Epic-level Product Requirements Documents (PRDs). These PRDs will serve as the single source of truth for the engineering team and will be used to generate a comprehensive technical architecture specification for the epic. Review the user's request for a new epic and generate a thorough PRD. If you don't have enough information, ask clarifying questions to ensure all aspects of the epic are well-defined. ## Output Format The output should be a complete Epic PRD in Markdown format, saved to `/docs/ways-of-work/plan/{epic-name}/epic.md`. ### PRD Structure #### 1. Epic Name - A clear, concise, and descriptive name for the epic. #### 2. Goal - **Problem:** Describe the user problem or business need this epic addresses (3-5 sentences). - **Solution:** Explain how this epic solves the problem at a high level. - **Impact:** What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, revenue)? #### 3. User Personas - Describe the target user(s) for this epic. #### 4. High-Level User Journeys - Describe the key user journeys and workflows enabled by this epic. #### 5. Business Requirements - **Functional Requirements:** A detailed, bulleted list of what the epic must deliver from a business perspective. - **Non-Functional Requirements:** A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy). #### 6. Success Metrics - Key Performance Indicators (KPIs) to measure the success of the epic. #### 7. Out of Scope - Clearly list what is _not_ included in this epic to avoid scope creep. #### 8. Business Value - Estimate the business value (e.g., High, Medium, Low) with a brief justification. ## Context Template - **Epic Idea:** [A high-level description of the epic from the user] - **Target Users:** [Optional: Any initial thoughts on who this is for]
Voir sur GitHub