skills.rest
flightctl
flightctlOFFICIAL
Explore all skills by this author →
GitHub

prd

Convert Jira feature requirements into structured PRDs with GitHub review cycles.

6|16|Updated Mar 9, 2026
Search Tags:#requirements#technical writing#jira#prd#product planning#github pull requests
One-click install
npx skills add https://github.com/flightctl/ai-workflows --skill prd-flightctl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/flightctl/ai-workflows/tree/main/prd
Command: npx skills add https://github.com/flightctl/ai-workflows --skill prd-flightctl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns ambiguous or fragmented Jira feature requirements into a structured, traceable PRD that stakeholders can review with confidence, reducing rework caused by misunderstandings and missing details.

Core Features & Use Cases

  • Ingest requirements from Jira: gathers descriptions, acceptance criteria/definition of done, comments, linked issues (one level deep), and attachments as raw source material.
  • Clarify gaps via iterative Q&A: identifies missing scope, contradictions, edge cases, and assumptions and records user answers as clarification logs with locked decisions.
  • Draft, revise, and publish: generates a template-based PRD, applies requested revisions, then creates a draft GitHub PR for review and coordinates responses back into the PRD when approved.

Quick Start

Run the PRD workflow by asking for a PRD for Jira issue EDM-2324 using the command /ingest EDM-2324.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I turn Jira requirements into a review-ready PRD?▼

To turn Jira requirements into a PRD, ingest Jira issue descriptions and linked items, clarify ambiguities via Q&A, and draft a template-conformant document with traceable functional requirements. This process ensures the final PRD is review-ready for stakeholders.

Does the PRD generation process support publishing reviews via GitHub pull requests?▼

Yes, the PRD generation process coordinates review comment handling and approved-only publishing by creating a draft GitHub pull request. Reviewer decisions and comments are integrated back into the PRD to maintain traceability and finalize the document.

What is included in a structured Product Requirements Document generated from Jira?▼

A structured Product Requirements Document generated from Jira includes functional and non-functional requirements with stable IDs, acceptance criteria, assumptions, dependencies, risks, and open reviewer decisions. It transforms fragmented Jira inputs into a traceable stakeholder-ready format.

How do I handle missing scope and edge cases when drafting a PRD from Jira issues?▼

You handle missing scope and edge cases through an iterative clarification Q&A cycle that identifies contradictions and assumptions during ingestion. User answers are recorded as locked clarification logs to ensure the drafted PRD accurately reflects resolved decisions.

Can I automatically advance through the PRD drafting phases without user input?▼

No, the PRD workflow enforces non-auto-advancing phase control across ingest, clarification, drafting, and publishing cycles. This ensures users explicitly approve revisions and review decisions before the document advances to the next stage.

Related Skills

Explore More Product & Management Skills→
kvnxiaokvnxiao

linear-fix

Create per-ticket git worktrees and generate GitHub PRs for Linear tickets.

Community
Advanced
bacchus-labsbacchus-labs

docs-audit-review

Review documentation pull requests against issue requirements and code accuracy.

Official
Advanced
thomfilgthomfilg

create-jira-wiki

Automate publishing design documents to Jira Wiki with Git version control.

Community
Intermediate
takemo101takemo101

basic-design-workflow

Generate and refine basic design documents from requirement specifications.

Community
Advanced