Convert PRDs into dependency-aware Linear issue hierarchies with epics and stories.
npx skills add https://github.com/Alfie728/my-skills --skill prd-to-issues-alfie728
Please help me install this Agent Skill. Skill: prd-to-issues Source: https://github.com/Alfie728/my-skills/tree/main/prd-to-issues Command: npx skills add https://github.com/Alfie728/my-skills --skill prd-to-issues-alfie728
Many product requirements documents (PRDs) remain high-level and unexecutable, causing ambiguity, duplicated effort, and poor parallelization across engineers and agents. This Skill provides a repeatable method to convert a PRD into a parent -> epic -> story hierarchy that is dependency-aware and ready for implementation. It enforces concrete file paths, acceptance criteria, and verification steps so work can be run in parallel or handed off to autonomous agents.
Break the approved PRD into a parent, epics, and stories optimized for Linear and present the proposed breakdown for user approval.
High-intent search queries and answers about installing and using this skill.
Breaking down a PRD into Linear issues involves structuring work into a parent, epics, and stories with acceptance criteria and estimates. This Skill maps the hierarchy into dependency-aware DAGs with workspace sequencing, enabling parallel execution across engineers and agents.
A dependency-aware DAG sequences Linear epics and stories so independent workstreams run without conflicts. It maps parent-to-child relationships and workspace ordering, allowing teams to parallelize implementation tickets safely across multiple agents or engineers.
Yes, PRD breakdown can be applied to existing Linear issue bodies, comments, or project descriptions. The Skill extracts requirements from those sources and generates structured implementation tickets with story-level file paths and verification steps.
Yes, the Skill produces metadata compatible with Linear CLI or MCP tools. Each story includes file paths, change instructions, and verification steps formatted for direct ingestion, supporting automated workspace creation and issue import.
The best way is to give each Linear story exact file paths, change instructions, patterns to follow, and verification steps. This Skill enforces those implementation-ready attributes so work can be handed off to autonomous agents for AFK execution.
You need to break a PRD into epics and stories when work requires parallelization across multiple workspaces or agents. Single Linear issues lack the dependency-aware sequencing and granular acceptance criteria needed to prevent duplicated effort and conflicts.
roderikTurn project ideas into a structured PRD stored in Linear.
dhar174Manage Linear issues and projects through MCP read, create, and update operations.
ilamanovCreate Linear issues with structured titles and bodies after user approval.
GustavoGutierrezDecompose features into sequenced tasks with dependencies and acceptance signals.
