vuluu2k/breakdown-epic-pm
skills/breakdown-epic-pm/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add vuluu2k/skills breakdown-epic-pmInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 12:04 AM93.7s3 files scanned
SKILL.md
- 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]
Related Skills
vuluu2k/vue
development
VerifiedTrustedCommunity
Vue 3 Composition API — <script setup>, reactivity (shallowRef/ref), props without destructure, computed, watch, provide/inject, and composables. Use when the project uses modern Vue 3 Composition API style.
1SKILL.mdUpdated May 8, 2026
vuluu2k/vue-options
development
VerifiedTrustedCommunity
Vue 3 Options API — data, props, computed, methods, watch, emits, provide/inject, lifecycle hooks, and mixins. Use when the project uses Options API style (Vue 2 legacy or explicit Vue 3 Options API preference).
1SKILL.mdUpdated May 8, 2026
vuluu2k/vue-antdv-tailwind
tools
VerifiedTrustedCommunity
Best practices for mixing Ant Design Vue components with Tailwind CSS utility classes. Use this skill to keep styling consistent without custom CSS files.
1SKILL.mdUpdated May 8, 2026
vuluu2k/pinia
development
VerifiedTrustedCommunity
Pinia state management for Vue 3 using Composition API (Setup Stores) — TypeScript-first, storeToRefs for reactivity, focused stores, and API calls in composables. Use when the project uses Vue 3 Composition API / <script setup>.
1SKILL.mdUpdated May 8, 2026