Breakdown Epic PM
SkillTurns a new epic idea into a PRD: problem and goals, personas, user journeys, functional and non-functional requirements, success metrics and out-of-scope items, asking questions when information is missing, saved as Markdown. From GitHub's awesome-copilot collection.
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]
Ressources associées
prd
SkillWrites product requirement docs for software and AI features: first asks about the problem, success metrics and constraints, then outputs an executive summary, user stories, technical specs and risk analysis with measurable requirements. From GitHub's awesome-copilot community library.
github/awesome-copilot40.1k
write-spec
SkillTurns a feature idea or problem statement into a structured spec or PRD with goals and non-goals, user stories, success metrics and acceptance criteria, and can split large requests into phases. From Anthropic's official product-management plugin.
anthropics/knowledge-work-plugins29.9k
CCPM
SkillSpec-driven project management for software: guides brainstorming into a PRD, breaks it into epics and dependent tasks synced as GitHub Issues, answers standup, next-step and blocker questions, and can dispatch several agents to code in parallel. Needs Git, an authenticated gh CLI and a GitHub repo.
automazeio/ccpm8.4k
Grill Me
SkillBefore you build, the agent grills you on your plan or design, offering a recommended answer each round, until every decision branch is resolved. It calls the grilling skill from the same repo, so install both.
mattpocock/skills294kSpec Kit
CLIGitHub's official spec-driven development toolkit: the specify CLI sets up spec, plan and task workflows for Copilot, Claude Code, Codex and other agents so the spec comes before the code, plus bug-fix and idea-evaluation flows. Needs Python 3.11+ and uv.
github/spec-kit142k
office-hours (gstack)
SkillYC office hours skill from gstack: startup mode tests real demand, the narrowest wedge and future fit with six probing questions; builder mode brainstorms side projects, hackathons and open source. Ends with a design doc. Maintained by Garry Tan.
garrytan/gstack137k