mirror of https://github.com/github/awesome-copilot.git synced 2026-02-20 02:15:12 +00:00

Files

Craig Bekker 57e32ef029 Add comprehensive prompts for Epic and Feature planning, implementation, and testing (#148 )

- 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.

2025-08-04 10:32:29 +10:00

2.4 KiB

Raw Blame History

mode, description

mode	description
agent	Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.

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]

2.4 KiB Raw Blame History