prd-feature

Generates type-aware feature PRDs that inherit structure from a parent epic.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing feature-level PRDs that stay consistent with their parent epic is hard: personas, workflows, and requirement depth often drift from the epic's type. This Skill enforces that inheritance so Platform, Engine, and Domain features each get the right structure. ## Core Features & Use Cases - Type-Aware PRD Generation: Classifies the parent epic as Platform, Engine, or Domain and adapts personas, workflows, and UX depth accordingly. - Structured PRD Output: Produces a complete Markdown PRD with goal, personas, user stories, functional and non-functional requirements, acceptance criteria, and out-of-scope sections, saved to docs/product/{epic-name}/{feature-name}/prd.md. - Use Case: A product manager breaking an epic into features asks the assistant to draft a feature PRD; the Skill reads the parent epic, inherits its type, and produces a consistent, engineering-ready requirements document. ## Quick Start Write a feature PRD for the notifications feature under the messaging epic, inheriting the epic's type and saving it to the docs/product directory.

Frequently Asked Questions about prd-feature

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

FAQPage Schema
How do I write a feature PRD from a parent epic?▼

Read the parent epic first and classify it as Platform, Engine, or Domain, then draft the feature PRD inheriting that type. The Skill generates the full PRD structure including goal, personas, requirements, and acceptance criteria in Markdown.

What is the difference between Platform, Engine, and Domain feature PRDs?▼

Platform features use Developer/Operator personas and operational workflows, Engine features use Developer personas and integration workflows, and Domain features use direct user roles with standard user stories. The feature always inherits its parent epic's type.

When should a UX discovery session run before writing requirements?▼

For Domain features involving a meaningful user workflow, run a UX discovery session first covering JTBD analysis, journey mapping, and edge cases. Platform and Engine features rarely need UX discovery since they focus on contracts and operations.

What are the limits on requirements in a feature PRD?▼

Functional requirements are capped at 12 one-sentence items grouped by concern, and non-functional requirements at 6 covering performance, accessibility, and security. Avoid per-entity sub-tables; combine CRUD operations into single requirements.

Where is the generated feature PRD saved?▼

The PRD is saved as Markdown to docs/product/{epic-name}/{feature-name}/prd.md, keeping feature documents organized under their parent epic directory.