prd

Transform Linear tickets into structured PRDs and upload them back.

6|2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/v1-io/v1tamins --skill prd-v1-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/v1-io/v1tamins/tree/main/claude/skills/prd
Command: npx skills add https://github.com/v1-io/v1tamins --skill prd-v1-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform Linear tickets or feature requests into concise, implementation-ready PRDs that guide engineering and product teams.

Core Features & Use Cases

  • Gather inputs from Linear (title, description, acceptance criteria) and linked designs or context.
  • Analyze context to produce a structured PRD with sections like Description, Features, Acceptance Criteria, Technical Requirements, UI/UX, Dependencies, and Risks.
  • Upload the PRD back to the Linear ticket and add a confirmation comment (PRD uploaded) to close the loop.

Quick Start

Provide a Linear ticket URL or ID to generate the PRD.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate a PRD from a Linear ticket automatically?▼

The automation workflow extracts titles, descriptions, and acceptance criteria from your Linear ticket URL to produce a structured product requirements document.

What sections are included in an automated product requirements document?▼

The generated product requirements document features structured sections for Description, Features, Acceptance Criteria, Technical Requirements, UI/UX, Dependencies, and Risks.

Can I upload a generated PRD directly back to my Linear ticket workflow?▼

The workflow uploads the completed product requirements document directly back to the Linear ticket and posts a confirmation comment to close the loop.

Does this PRD automation work with existing Linear project requests?▼

This PRD automation applies to existing Linear ticket workflows and project requests, analyzing provided ticket context to output implementation-ready specifications.

What is the best way to turn feature requests into implementation-ready specifications?▼

Using an automation workflow to extract Linear ticket context and structure it into a comprehensive PRD is the best way to turn feature requests into implementation-ready specifications.