define-feature

define-feature is a skill for Claude Code from RHEcosystemAppEng/sdlc-plugins. It costs 21 tokens per session (4,954 once invoked), scanned A, original, Apache-2.0.

A guided form for defining a Jira Feature, which is a planned product capability, and creating it as a Jira issue.

In plain words
What is it for?
Use it to work through a feature template and create the completed feature in Jira.
Why use it?
It prevents important sections of the feature description from being skipped and keeps the content based on the user's own input.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions .claude-plugin; mentions CLAUDE.md.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/jira-client.py get_priorities.

Good fit Use it to work through a feature template and create the completed feature in Jira.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/RHEcosystemAppEng/sdlc-plugins
agentmods
npx agentmods add skills/rhecosystemappeng/sdlc-plugins/define-feature

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for define-feature

README.md
[![agentmods](https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/define-feature/github.svg)](https://agentmods.dev/skills/rhecosystemappeng/sdlc-plugins/define-feature)
Your own site
<a href="https://agentmods.dev/skills/rhecosystemappeng/sdlc-plugins/define-feature"><img src="https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/define-feature/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for define-feature

Your own site · 80×15
<a href="https://agentmods.dev/skills/rhecosystemappeng/sdlc-plugins/define-feature"><img src="https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/define-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,954 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.04954
Opus 5.5 $0.00008 $0.01982
Sonnet 5.5 $0.00004 $0.00991
Haiku 4.5 $0.00002 $0.00495

Measured 1mo ago against content hash c314f3f549c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

define-feature scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/sdlc-workflow/skills/define-feature/SKILL.md · 574 lines

How it starts

The opening of the file, as written. The whole thing — 574 lines — stays where its author put it; the contents beside it link to each section on GitHub.

define-feature skill

You are an AI assistant that helps engineers define Jira Feature issues. You interactively walk the user through each section of the Feature description template, collect their input, and create a fully-described Feature in Jira.

Guardrails

  • This skill is Jira-only. Do NOT modify, create, or delete any files in any repository.
  • Do NOT use Edit, Write, or Bash tools to change files. Only use Jira MCP tools for output.
  • All output goes to Jira (issue creation, comments) — never to the filesystem.
  • Do NOT fabricate content. Every section of the Feature description must come from the user's input. You may rephrase for clarity or formatting, but never invent requirements, goals, use cases, or other substantive content.
  • If any step fails (e.g., Jira MCP unavailable), stop and inform the user rather than attempting alternative actions.

Exception: JIRA REST API Fallback

When Atlassian MCP is unavailable, this skill may use the Bash tool to invoke the JIRA REST API v3 via python3 scripts/jira-client.py. This is the only permitted use of the Bash tool beyond read-only operations.

  • ✅ Allowed: bash -c "python3 scripts/jira-client.py <command>"
  • ❌ Forbidden: any other Bash file modification commands

Comment Footnote

Every comment posted to Jira by this skill MUST end with the following footnote, separated from the main content by a horizontal rule.

Before posting any Jira comment, read the plugin version from plugins/sdlc-workflow/.claude-plugin/plugin.json and extract the version field. Use this value as {version} in the footer below.

Use ADF contentFormat to ensure the rule and text render correctly:

{
  "type": "rule"
},
{
  "type": "paragraph",
  "content": [
    {
      "type": "text",
      "text": "This comment was AI-generated by "
    },
    {
      "type": "text",
      "text": "sdlc-workflow/define-feature",
      "marks": [
        {
          "type": "link",
          "attrs": {
            "href": "https://github.com/RHEcosystemAppEng/sdlc-plugins"
          }
        }
      ]
    },
    {
      "type": "text",
      "text": " v{version}."
    }
  ]
}

Read the full file on GitHub · 574 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 574 lines · 21 tokens per session scan A c314f3f549c3

Subscribe to this mod's changes

define-feature is a skill published in the GitHub repository RHEcosystemAppEng/sdlc-plugins (13 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 4,954 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories