prd

Convert vague feature ideas into Linear EPICs with requirements and success criteria.

142|19|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/joa23/linear-cli --skill prd-joa23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/joa23/linear-cli/tree/main/internal/skills/prd
Command: npx skills add https://github.com/joa23/linear-cli --skill prd-joa23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PRD Skill helps teams transform vague ideas into structured Linear tickets with well-defined requirements, success criteria, and dependencies to guide agent-driven development.

Core Features & Use Cases

  • Create epic/parent tickets with clear problem context, must-have vs nice-to-have requirements, and testable success criteria.
  • Break work into sub-issues with scoped work units and explicit verification steps.
  • Establish dependencies using --depends-on and --blocked-by to manage work order.

Quick Start

Create a new feature epic with a clear problem, then break it into sub-issues and dependencies to guide implementation.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I convert vague feature ideas into structured Linear epics with clear requirements?

To convert vague feature ideas into Linear epics, this Skill structures tickets with defined sections for Problem/Context, must-have Requirements, Success Criteria, Verification, and Boundaries to ensure fully scoped work items.

What is the best way to break down a Linear epic into sub-issues with dependencies?

Breaking down a Linear epic into sub-issues is handled by creating scoped work units with explicit verification steps, then establishing work order and dependency chains using Linear commands like --depends-on and --blocked-by.

How does structuring Linear tickets help with agent-driven development?

Structured Linear tickets guide agent-driven development by providing clear context, measurable success criteria, and explicit verification steps, making the work items auditable and fully agent-ready for automated implementation.

Can I define must-have versus nice-to-have requirements when planning product features in Linear?

Yes, you can define must-have versus nice-to-have requirements when planning product features in Linear. The Skill enforces a structured ticket format that separates core requirements from optional ones within the parent epic.

Do I need to manually format Linear tickets or does the PRD process enforce a specific structure?

You do not need to manually format Linear tickets. The PRD process automatically enforces a structured ticket format containing dedicated sections for Problem/Context, Requirements, Success Criteria, Verification, and Boundaries.

When should I establish dependency chains for Linear sub-issues?

You should establish dependency chains for Linear sub-issues when breaking work into smaller units to manage work order. This ensures sequential execution and prevents blocked tasks from starting prematurely.