prd

Create Linear tickets with PRDs, sub-issues, and success criteria.

Updated Apr 8, 2024

Search Tags:#planning #linear #prd #subtasks #acceptance-criteria #ticketing

Ready to run

npx skills add https://github.com/tumes/dotfiles-nvim --skill prd-tumes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/tumes/dotfiles-nvim/tree/main/claude/skills/prd
Command: npx skills add https://github.com/tumes/dotfiles-nvim --skill prd-tumes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create structured, agent-friendly PRDs and sub-issues from loosely defined feature requests to improve planning clarity and execution.

Core Features & Use Cases

Generate an Epic/Parent Issue with a concise title, problem/context, and must-have vs nice-to-have requirements.
Break work into sub-issues with explicit success criteria, verification commands, and boundaries.
Establish dependencies between tickets using --depends-on and --blocked-by to enforce work order.

Quick Start

Create a parent PRD ticket and automatically break it into sub-issues with defined success criteria and dependencies.

Frequently Asked Questions about prd

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

FAQPage Schema

How do I break down a high-level feature request into Linear subtasks?▼

To break down a feature request into Linear subtasks, this Skill atomizes the request into an Epic parent issue and sub-issues, each with explicit success criteria and verification commands for engineering planning.

How do I generate acceptance criteria for Linear tickets automatically?▼

Generating acceptance criteria for Linear tickets is handled by defining explicit success criteria and boundaries for each sub-issue, ensuring the resulting tickets are agent-ready and have clear scope for verification.

How do I enforce work order and dependencies when creating Linear tickets?▼

You can enforce work order when creating Linear tickets by establishing dependencies between issues using the --depends-on and --blocked-by parameters, ensuring subtasks are executed in the correct sequence.

What is the best way to structure PRDs for agent-friendly ticketing workflows?▼

The best way to structure PRDs for agent-friendly ticketing is to separate must-have and nice-to-have requirements within a parent Epic, then break the work into atomized sub-issues with explicit verification commands.

Can I create a parent Epic and sub-issues simultaneously from a loosely defined feature request?▼

Yes, you can create a parent Epic and sub-issues simultaneously from a loosely defined feature request. The Skill generates the parent PRD and automatically breaks it into sub-issues with defined success criteria.

Does this PRD generation approach require any specific ticketing framework dependencies?▼

No specific ticketing framework dependencies are required to generate these PRDs. The Skill operates independently to produce structured, agent-ready Linear tickets with explicit success criteria from your feature requests.