skills.rest
cman131
cman131COMMUNITY
Explore all skills by this author →
GitHub

prd-to-feature

Converts PRD documents into GitHub Issues Feature work items under a target Epic.

Updated May 2, 2024
Search Tags:#issue tracker#PRD#github issues#feature#product planning#work item#epic
One-click install
npx skills add https://github.com/cman131/EatSomethingSourWhenYoureTired --skill prd-to-feature-cman131
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-to-feature
Source: https://github.com/cman131/EatSomethingSourWhenYoureTired/tree/main/.claude/skills/prd-to-feature
Command: npx skills add https://github.com/cman131/EatSomethingSourWhenYoureTired --skill prd-to-feature-cman131

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a product requirements document into a tracked work item in an issue tracker is repetitive and error-prone: titles get inconsistent, descriptions lose key context, and parent-child links to Epics are forgotten. This Skill standardizes the conversion of a PRD into a confirmed, correctly linked Feature work item. ## Core Features & Use Cases - PRD Extraction: Reads a PRD file and extracts product area, problem, goals, scope, and out-of-scope sections to build a structured Feature description. - Draft Confirmation Workflow: Presents a proposed title and HTML-formatted description for user approval before creating anything in the issue tracker. - Epic Verification and Linking: Validates that the supplied parent ID is actually an Epic, creates the Feature as its child, and repairs the description or parent link if the tracker did not store them. - Use Case: A product manager finishes a PRD for a home-page health score feature and needs a Feature work item created under Epic 3701585 before story decomposition begins. ## Quick Start Run the prd-to-feature skill with the path to your PRD file and the target Epic ID, for example: plans/home-page-health-score-addin/prd.md 3701585.

Frequently Asked Questions about prd-to-feature

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

FAQPage Schema
How do I create a GitHub Issues Feature from a PRD document?▼

Provide the PRD file path and the target Epic ID as arguments. The skill reads the PRD, drafts a title and HTML description covering problem, goals, scope, and out-of-scope, waits for your confirmation, then creates the Feature as a child of the Epic.

What input format does the PRD to Feature workflow expect?▼

It expects two arguments: the path to the PRD markdown file and the numeric Epic ID, in the form '<path-to-prd> <epic-id>'. If either argument is missing, the skill asks for it before proceeding.

Does this skill work with Jira or Azure DevOps instead of GitHub Issues?▼

The instructions are written generically around an issue tracker's lookup, create-child, update, and link tools. You swap in the equivalent tool names and field paths for Jira (issue/epic/description) or Azure DevOps (System.Description).

What happens if the Epic ID I provide is not an Epic?▼

The skill verifies the parent work item before creating anything. If the work item does not exist or its type is not Epic, it stops and tells you rather than creating a mislinked Feature.

Why was my Feature created without a description or parent link?▼

Some trackers do not store the description or parent relation on creation. The skill checks the returned item and repairs missing descriptions via an update call and missing parent links via an explicit link call with type 'parent'.

Does the skill automatically create user stories after the Feature?▼

Yes. After creating the Feature, it automatically invokes the feature-to-stories skill with the new Feature ID and the PRD path, without asking for confirmation. The Epic ID is not passed to that step.

Related Skills

Explore More Product & Management Skills→
chelleboyerchelleboyer

feature-spec

Generate structured PRDs and feature specifications from a PRD template.

Community
Intermediate
nashirabbashnashirabbash

task-planning

Break down features into INVEST-based user stories and backlog tasks.

Community
Intermediate
pssah4pssah4
37

requirements-engineering

Transforms BA analyses into backlog Epics, Features, architect-handoff.md artifacts.

Community
Advanced
christopher-busschristopher-buss
6

to-prd

Generate a Product Requirements Document from conversation context and codebase understanding.

Community
Intermediate