implement-task

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 CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/rhecosystemappeng/sdlc-plugins/implement-task
Any agent
npx skills add RHEcosystemAppEng/sdlc-plugins --skill implement-task
Clone the repo
git clone --depth 1 https://github.com/RHEcosystemAppEng/sdlc-plugins

Made for: Claude Code, Codex.

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,378 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00023 $0.10378
Opus 5 $0.00012 $0.05189
Sonnet 5 $0.00005 $0.02076
Haiku 4.5 $0.00002 $0.01038

Measured 2d ago against content hash 0276a52292d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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 · 961 lines

How it starts

The opening of the file, as written. The whole thing — 961 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 · 961 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. 2d 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 (11 stars, last pushed 8d ago), licensed Apache-2.0. It adds 23 tokens to every session and 10,378 once invoked, about $0.0001 per session on Opus 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens