skills.rest
TWoolff
TWoolffCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prd-to-issues

Parse PRD markdown files to generate scoped GitHub issues with acceptance criteria.

Updated Aug 27, 2026
Search Tags:#project management#developer workflow#task breakdown#agile#github issues#prd
One-click install
npx skills add https://github.com/TWoolff/strata-training-data --skill prd-to-issues-twoolff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-to-issues
Source: https://github.com/TWoolff/strata-training-data/tree/main/.claude/skills/prd-to-issues
Command: npx skills add https://github.com/TWoolff/strata-training-data --skill prd-to-issues-twoolff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of converting complex Product Requirement Documents (PRDs) into manageable, developer-ready GitHub issues, ensuring clear scope and efficient task allocation.

Core Features & Use Cases

  • PRD Parsing: Analyzes PRD markdown files to identify features, dependencies, and acceptance criteria.
  • Issue Scoping: Breaks down large features into individual issues, adhering to a one-developer-per-day work limit.
  • Dependency Mapping: Orders issues logically based on interdependencies within the development pipeline.
  • Use Case: A product manager can provide a PRD for a new feature, and this Skill will generate a structured list of GitHub issues, complete with technical requirements, acceptance criteria, and estimated effort, ready for the engineering team to pick up.

Quick Start

Use the prd-to-issues skill to break down the PRD document located at './claude/prd/feature_x.md'.

Frequently Asked Questions about prd-to-issues

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

FAQPage Schema
How do I break down a PRD into actionable GitHub issues?▼

To break down a PRD into GitHub issues, this skill parses your markdown file to identify features and dependencies, then scopes tasks into individual issues with functional requirements, implementation notes, and acceptance criteria.

What is the best way to scope agile tasks for a single developer's daily capacity?▼

The best way to scope agile tasks for a developer's daily capacity is to parse the PRD and break down large features into individual GitHub issues that strictly adhere to a one-developer-per-day work limit.

Can I map technical dependencies when generating GitHub issues from a PRD?▼

Yes, you can map technical dependencies when generating GitHub issues. The skill analyzes PRD content to order issues logically based on interdependencies within the development pipeline.

Does this skill generate acceptance criteria for developer workflow tasks?▼

Yes, this skill ensures generated GitHub issues are technically defined with functional requirements, implementation notes, and acceptance criteria, facilitating efficient developer workflow execution.

Do I need a markdown file to parse a PRD for project management?▼

Yes, you need a markdown file containing your PRD to parse it for project management. The skill analyzes the markdown content directly to extract features and generate structured GitHub issues.

Related Skills

Explore More Product & Management Skills→
posit-devposit-dev
4.2k

positron-issue-creator

Drafts complete GitHub issue drafts for the Positron repository with duplicate checking.

Official
Basic
amdmaxamdmax
2

github:tidy-board

Move stale GitHub Project V2 items to Done when linked issues or pull requests close.

Community
Intermediate
santychuycomsantychuycom

github-cli

Manage GitHub repositories, pull requests, issues, and workflows via the gh CLI.

Official
Intermediate
AgLyx3AgLyx3

agile-product-owner

Generate user stories and acceptance criteria for agile backlog management.

Community
Advanced