prd
Requirements-to-PRD workflow that ingests requirements from Jira, clarifies ambiguities through iterative Q&A, drafts a Product Requirements Document, and manages review via GitHub PRs. Use when creating PRDs, analyzing requirements, or preparing feature specifications for review. Activated by commands: /ingest, /clarify, /draft, /revise, /publish, /respond.
The canonical home for this skill is prd in flightctl/ai-workflows
PRD Workflow Orchestrator
Quick Start
- If the user invoked a specific command (e.g.,
/draft,/clarify), readcommands/{command}.mdand follow it. - Otherwise, read
skills/controller.mdto load the workflow controller:- If the user provided a Jira issue key or URL, execute the
/ingestphase - Otherwise, execute the first phase the user requests
- If the user provided a Jira issue key or URL, execute the
If a step fails or produces unexpected output (e.g., Jira MCP errors, network failures, invalid issue keys), stop and report the error to the user. Do not advance to the next phase. Offer to retry the failed step or escalate.
For principles, hard limits, safety, quality, and escalation rules, see guidelines.md.
- Repository
- amir-yogev-gh/ai-workflows
- Path
prd/SKILL.md
- Commit
2bd6607
- Last updated
- First committed
Canonical home
since Sep 11, 2026
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.