This handles Jira task creation for Prowler's development workflow, with opinionated guidance on splitting multi-component work into separate tickets. It distinguishes between bugs (which get sibling tasks per component) and features (which get a parent task for stakeholders plus technical child tasks). The templates are prescriptive about title conventions, file paths, and acceptance criteria format. Worth noting: it's built around a specific Jira custom field setup including a required Team field and a non-standard Work Item Description field that uses Wiki markup instead of Markdown. If you're working on Prowler or have a similar multi-component codebase with API, UI, and SDK layers, the splitting logic is solid. Otherwise, you'll need to adapt the field mappings.
- skills.sh installs
- 216
- GitHub stars
- 665
- last updated
- Aug 21, 2026
Install
$ npx -y skills add gentleman-programming/gentleman-skills --skill jira-task --agent claude-codeInstalls into .claude/skills of the current project.
Files
When to Use
Use this skill when creating Jira tasks for:
- Bug reports
- Feature requests
- Refactoring tasks
- Documentation tasks
Multi-Component Work: Split into Multiple Tasks
IMPORTANT: When work requires changes in multiple components (API, UI, SDK), create separate tasks for each component instead of one big task.
Why Split?
- Different developers can work in parallel
- Easier to review and test
- Better tracking of progress
- API needs to be done before UI (dependency)
Bug vs Feature: Different Structures
For BUGS: Create separate sibling tasks
Bugs are typically urgent fixes, so create independent tasks per component:
Task 1 - API:
- Title:
[BUG] Add aws_region field to AWS provider secrets (API) - Must be done first (UI depends on it)
Task 2 - UI:
- Title:
[BUG] Add region selector to AWS provider connection form (UI) - Blocked by API task
For FEATURES: Create parent + child tasks
Features need business context for stakeholders, so use a parent-child structure:
Sponsors
Details
- Repository
- github.com/gentleman-programming/gentleman-skills
- Categories
- Git & Pull Requests, Code Review & Quality
- First seen
- Jun 3, 2026
