Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-02-24 04:15:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add comprehensive prompts for Epic and Feature planning, implementation, and testing (#148)

Browse Source 
- Introduced a detailed Epic Architecture Specification prompt to guide technical architecture creation based on PRDs.
- Created an Epic Product Requirements Document (PRD) prompt for translating high-level ideas into detailed PRDs.
- Developed a Feature Implementation Plan prompt for crafting implementation plans following the Epoch monorepo structure.
- Added a Feature PRD prompt for generating detailed PRDs for new features based on parent Epics.
- Implemented a GitHub Issue Planning and Automation prompt for generating project plans with a structured hierarchy and automated tracking.
- Established a Test Planning and Quality Assurance prompt for creating comprehensive test strategies and quality validation plans.
This commit is contained in:
Craig Bekker
2025-08-04 02:32:29 +02:00
committed by GitHub
parent 0a59e67fa4
commit 57e32ef029
7 changed files with 1193 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
prompts/breakdown-epic-pm.prompt.md Normal file
View File

@@ -0,0 +1,58 @@
---
mode: 'agent'
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]