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.
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
The canonical home for this skill is prd in flightctl/ai-workflows
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The PRD workflow ingests Jira issues, linked issues, and comments, and later fetches PR review comments from GitHub. Both Jira inputs and GitHub PR review comments are outsider-authored free text that flows directly into agent workflows without prior item selection.
- Repository
amir-yogev-gh/ai-workflows
- Path
prd/SKILL.md
- Revision
7b2b8de
- Audited
- Security analysis
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.