implement-task

implement-task is a skill for Claude Code from RHEcosystemAppEng/sdlc-plugins. It costs 23 tokens per session (10,647 once invoked), scanned A, original, Apache-2.0.

A Jira-based workflow for taking a feature request through planning and code implementation, with work recorded back in Jira.

In plain words
What is it for?
Use it to plan features, implement their Jira tasks, run tests, and update the related Jira records.
Why use it?
It keeps feature planning, task execution, testing, and Jira traceability connected in one process.

Skill for Claude Code

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

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/sha256-digest.py /tmp/desc-<task-key>.txt.

Good fit Use it to plan features, implement their Jira tasks, run tests, and update the related Jira records.

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/implement-task

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 implement-task

README.md
[![agentmods](https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/implement-task/github.svg)](https://agentmods.dev/skills/rhecosystemappeng/sdlc-plugins/implement-task)
Your own site
<a href="https://agentmods.dev/skills/rhecosystemappeng/sdlc-plugins/implement-task"><img src="https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/implement-task/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 implement-task

Your own site · 80×15
<a href="https://agentmods.dev/skills/rhecosystemappeng/sdlc-plugins/implement-task"><img src="https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/implement-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 10,647 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.00023 $0.10647
Opus 5.5 $0.00009 $0.04259
Sonnet 5.5 $0.00005 $0.02129
Haiku 4.5 $0.00002 $0.01065

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

Security

Grade A, and why

implement-task 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/implement-task/SKILL.md · 988 lines

How it starts

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

implement-task skill

You are an AI implementation assistant. You take a Jira task with a structured description and implement it.

Step 0 – Validate Project Configuration

Before proceeding, read the project's CLAUDE.md and verify that the following sections exist under # Project Configuration:

  1. ## Repository Registry — must contain a table with at least one entry
  2. ## Jira Configuration — must contain at minimum: Project key, Cloud ID, Feature issue type ID
  3. ## Code Intelligence — must exist with the tool naming convention

If any of these sections are missing or incomplete, inform the user:

"This skill requires Project Configuration in your CLAUDE.md. Please run /setup first to configure your project, then re-run this skill."

Stop execution immediately. Do not attempt to gather the missing information or proceed without it.

Step 0.5 – JIRA Access Initialization

Before attempting any JIRA operations (Steps 1, 1.5, 2, 3, 11), determine the access method.

For every JIRA operation:

  1. Attempt MCP first (preferred method)

  2. If MCP fails, always prompt user:

    ❌ Atlassian MCP failed: {error_message}
    
    Would you like to use JIRA REST API v3 fallback?
    
    Options:
    1. Yes - Use REST API (requires credentials)
    2. No - Skip this JIRA operation
    3. Retry - I'll fix MCP configuration and retry
    
    Choose (1/2/3):
    
  3. If "1. Yes": Check CLAUDE.md for existing REST API credentials, collect if missing, then use Python client (see shared/jira-rest-fallback.md)

  4. If "2. No": Skip the JIRA operation and inform user

  5. If "3. Retry": Retry MCP once

REST API equivalents for this skill's operations:

  • jira.get_issue(id) → python3 scripts/jira-client.py get_issue <id> --fields "*all"
  • jira.get_issue_comments(id) → python3 scripts/jira-client.py get_comments <id>
  • jira.user_info() → python3 scripts/jira-client.py get_user_info
  • jira.edit_issue(id, assignee=accountId) → python3 scripts/jira-client.py update_issue <id> --fields-json '{"assignee": {"id": "<accountId>"}}'
  • jira.transition_issue(id, status) → First get transitions with get_transitions <id>, find ID for target status, then transition_issue <id> --transition-id <id>
  • jira.update_issue(id, fields) → python3 scripts/jira-client.py update_issue <id> --fields-json '<json>'
  • jira.add_comment(id, text) → python3 scripts/jira-client.py add_comment <id> --comment-md "<text>"

Read the full file on GitHub · 988 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 Changed · +27 lines bd4ea474c250
  2. 1mo ago First seen · 961 lines · 23 tokens per session scan A 0276a52292d6

Subscribe to this mod's changes

implement-task is a skill published in the GitHub repository RHEcosystemAppEng/sdlc-plugins (13 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 10,647 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