prd-epic

Creates and audits type-aware Epic PRDs for platform, engine, and domain layers.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/siegenthalerroger/.llmctl-marketplace --skill prd-epic-siegenthalerroger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-epic
Source: https://github.com/siegenthalerroger/.llmctl-marketplace/tree/main/plugins/llmctl-product-0.2.1/skills/prd-epic
Command: npx skills add https://github.com/siegenthalerroger/.llmctl-marketplace --skill prd-epic-siegenthalerroger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing Epic-level PRDs often produces bloated, inconsistent documents that mix platform, engine, and domain concerns, making them unreliable as a source of truth for engineering teams. ## Core Features & Use Cases - Type-Aware Authoring: Classifies each epic as Platform, Engine, or Domain before drafting, enforcing the correct personas and Section 4 structure (journeys vs. Domain Integration Contract). - Structured PRD Generation: Produces a complete Epic PRD in Markdown saved to docs/product/{epic-name}/epic.md with capped requirement counts (≤15 functional, ≤8 non-functional). - Severity-Graded Review: Audits existing epics against a checklist covering classification, journeys, requirements, metrics, scope, and consistency, returning findings labeled Critical, High, Medium, Low, or Act Now. - Use Case: A product manager planning a scheduling SaaS asks for an epic PRD; the skill first confirms splitting it into a platform epic, a solver engine epic, and a school domain epic, then drafts each with the correct structure. ## Quick Start Ask the assistant to create an Epic PRD for your product idea, or to review an existing epic document for structural and consistency issues.

Frequently Asked Questions about prd-epic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an Epic PRD for a large SaaS product?▼

Start by confirming the epic structure and classifying each epic as Platform, Engine, or Domain before drafting. The skill then generates a Markdown PRD with goal, personas, journeys or integration contract, requirements, metrics, scope, and business value, saved to docs/product/{epic-name}/epic.md.

What is the difference between platform, engine, and domain epics?▼

Platform epics cover shared infrastructure with developer/operator personas, engine epics cover reusable computation layers with developer personas, and domain epics cover user-facing verticals with full user journeys. Platform and engine epics replace journeys with a Domain Integration Contract.

How do I review an existing Epic PRD for quality issues?▼

Request a review and the skill applies a checklist covering type classification, integration contracts, journey completeness, requirement limits, metric quality, scope gaps, and internal consistency. Findings are returned with severity labels: Critical, High, Medium, Low, or Act Now.

When should I use prd-epic versus prd-feature?▼

Use prd-epic for epic-level documents spanning an entire layer or work stream of a product. Use prd-feature for feature-level PRDs derived from an epic; the epic skill explicitly delegates feature-level work to prd-feature.

What are the requirement limits in an Epic PRD?▼

Functional requirements are capped at 15 one-sentence items grouped by concern, and non-functional requirements at 8 covering performance, security, accessibility, and data privacy. Exceeding these limits is flagged as Critical or High severity during review.