RHEcosystemAppEng/sdlc-plugins
Skill Claude Code needs its repo
Interactively define a Jira Feature by walking through all description template sections and creating the issue.
Claude Code plugin for AI-assisted SDLC workflows — plan features, implement tasks, triage bugs, and verify PRs with full Jira traceability
This repository also configures its own agents. See what sdlc-plugins tells them →
RHEcosystemAppEng/sdlc-plugins
Skill Claude Code needs its repo
Interactively define a Jira Feature by walking through all description template sections and creating the issue.
RHEcosystemAppEng/sdlc-plugins
Skill Claude Code needs its repo
Implement a Jira task by reading its structured description, modifying code, running tests, and updating Jira.
RHEcosystemAppEng/sdlc-plugins
Skill Claude Code needs its repo
Generate an implementation plan and Jira tasks from a Jira feature and Figma mockups.
RHEcosystemAppEng/sdlc-plugins
Skill Claude Code needs its repo
Interactively define a Jira Bug by walking through project-configured template sections, or accept structured input programmatically from other skills. Creates the issue and suggests triage.
RHEcosystemAppEng/sdlc-plugins
Skill Claude CodeCodex
Run skill evals with deterministic output layout and CI-compatible results. Grades assertions, aggregates benchmark.json, and renders summary.md via Python scripts. NOT skill-creator — this skill produces fixed output paths for automated pipelines. Triggers on "run evals", "eval ", "benchmark", or "grade evals".
RHEcosystemAppEng/sdlc-plugins
Skill Claude CodeCodex needs its repo
Set up or update the Project Configuration in your CLAUDE.md for use with sdlc-workflow skills.
RHEcosystemAppEng/sdlc-plugins
Skill Claude Code needs its repo
Use when a Jira Bug issue needs investigation to identify root cause and produce a fix task. Covers bug triage, codebase investigation, root cause analysis, reproducer test guidance, and linked Task creation for implement-task consumption.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: