skills.rest
Elmanuel1
Elmanuel1COMMUNITY
Explore all skills by this author →
GitHub

prd-to-features

Convert Confluence PRDs into per-repo story specs and synchronized Jira tickets.

Updated Apr 26, 2026
Search Tags:#jira#confluence#prd#design decisions#source code audit#engineering breakdown#story specs
One-click install
npx skills add https://github.com/Elmanuel1/skills --skill prd-to-features-elmanuel1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-to-features
Source: https://github.com/Elmanuel1/skills/tree/main/prd-to-features
Command: npx skills add https://github.com/Elmanuel1/skills --skill prd-to-features-elmanuel1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard PRD-to-ticket workflows fail due to premature decomposition, sizing based on PRD text instead of actual code, stale PRDs out of sync with codebases, and endless rounds of clarification questions that delay engineering kickoff.

Core Features & Use Cases

  • Source-grounded story sizing: Decomposes PRDs into per-repo markdown story specs sized based on actual code changes, not PRD section counts, to avoid incorrect release estimates.
  • End-to-end Jira integration: Creates a matching Jira Epic with linked Stories and Tasks, back-writing Jira keys directly into story files for traceability.
  • PRD reconciliation: Surfaces every discrepancy between PRD claims and source code, resolves them with user input, and writes updates back to Confluence to keep the PRD truthful over time.
  • Use Case: A product manager with a grilled, finalized Confluence PRD can use this skill to generate a complete, engineer-ready breakdown with zero manual ticket creation, ensuring all prior design decisions are respected.

Quick Start

Use the prd-to-features skill to break down the linked Confluence PRD into structured engineering stories and synchronized Jira tickets.

Frequently Asked Questions about prd-to-features

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

FAQPage Schema
How do I break down a Confluence PRD into engineering specs and Jira tickets?▼

To break down a Confluence PRD, this skill decomposes the document into per-repo markdown story specs and synchronizes Jira Epics, Stories, and Tasks by sizing work based on actual source code changes rather than text sections.

How do I size Jira stories based on actual codebase state instead of PRD text?▼

Sizing Jira stories based on actual codebase state involves auditing the source code to determine real engineering effort, avoiding incorrect release estimates that happen when sizing relies solely on PRD section counts.

Can I automatically sync Jira tickets back to my Confluence PRD and source code?▼

Yes, you can sync Jira tickets by back-writing Jira keys directly into per-repo story files for traceability, and writing PRD reconciliations back to Confluence to keep the document accurate over time.

How do I reconcile stale PRDs that are out of sync with the codebase before implementation?▼

Reconciling stale PRDs involves surfacing every discrepancy between PRD claims and source code, resolving them with user input, and writing the updated design decisions back to Confluence to keep the PRD truthful.

Does this PRD to Jira workflow work for per-repo story specifications across multiple repositories?▼

Yes, this workflow supports per-repo story specifications by decomposing a finalized Confluence PRD into structured engineering deliverables that align work with the actual state of each specific repository.

Why do standard PRD to ticket workflows fail during engineering breakdown?▼

Standard PRD to ticket workflows fail due to premature decomposition, sizing based on PRD text instead of actual code, stale PRDs out of sync with codebases, and endless clarification questions that delay engineering kickoff.

Related Skills

Explore More Product & Management Skills→
lekmanlekman

refine

Convert rough requirements or Jira tickets into a draft PRD with frontmatter.

Community
Advanced
ArvorCoArvorCo
96

prd

Generate a structured PRD with goals, user stories, and acceptance criteria.

Community
Basic
nroze22nroze22
1

requirements-test-matrix

Generate categorized test case matrices from PRD text, Confluence URLs, or Jira story keys.

Community
Advanced
igmarinigmarin
22

create-prd

Generate a structured PRD Markdown document from a feature description.

Community
Advanced