sizing
Pre-cycle Feature sizing workflow that assesses Features from Jira using T-shirt sizes (XS–XXL), produces per-team effort breakdowns (DEV, QE, UX, UI, DOCS), and writes results back to Jira. Accepts a single Feature or all Features in a Fix Version for batch sizing. Use when sizing Features for cycle planning, prioritizing a release backlog, or evaluating whether a Feature fits in a cycle. Activated by commands: /ingest, /assess, /apply.
82%
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 sizing 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 workflow reads and ingests Jira issue keys/URLs and Fix Version batches via the Jira CLI or REST API, which are outsider-authored ticketing sources under the threat model.
- Repository
amir-yogev-gh/ai-workflows
- Path
sizing/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.