jira-best-practices

Map Jira work items to role-based container, deliverable, and breakdown hierarchies.

5|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/air-gapped/skills --skill jira-best-practices
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-best-practices
Source: https://github.com/air-gapped/skills/tree/main/.claude/skills/jira-best-practices
Command: npx skills add https://github.com/air-gapped/skills --skill jira-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Jira best-practices addresses the common Jira dread: bloated configurations, inconsistent hierarchy mappings, and drift in governance. It provides a framework to reason in roles (container/ deliverable/ breakdown) and to map org-specific names to Jira concepts while staying Data Center aware. This skill guides humans to craft lean, auditable Jira setups and provide actionable steps for admins and agents.

Core Features & Use Cases

  • Lean hierarchy mapping and role-based guidance for Epic/Story/Task/Sub-task across DC and non-software domains.
  • Admin handoff prompts: how to debloat screens, fields, workflows, and automation; how to perform language-safe discovery and discovery reports.
  • Use cases include standardizing epics, splitting big migrations, and de-software-izing Jira for non-software teams.

Quick Start

Explain your organization's Jira hierarchy and request a lean, role-based mapping to container/deliverable/breakdown with DC considerations.

Frequently Asked Questions about jira-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map Jira epics and stories to a role-based hierarchy for lean governance?▼

Jira hierarchy mapping assigns work items to container, deliverable, and breakdown roles. This role-based approach adapts to org-specific terminology and accounts for Epic Link and Parent Link in Data Center environments.

What is the best way to debloat Jira screens, fields, and workflows?▼

Lean Jira governance provides admin handoff prompts to debloat screens, fields, workflows, and automation. It generates actionable configuration cleanup steps and language-safe discovery reports.

Can I use Jira for non-software teams without software-centric defaults?▼

Yes, Jira governance supports non-software domains by de-software-izing configurations. It maps work items via jira-cli and mcp-atlassian while adapting terminology for non-dev teams.

Does lean Jira governance work with Data Center deployments and Epic Link?▼

Yes, lean Jira governance explicitly accounts for Data Center specifics like Epic Link and Parent Link. It maps hierarchy roles correctly across DC and non-software domains.

Why does my Jira epic and sub-task hierarchy drift from org-aligned governance?▼

Jira hierarchy drift happens when configurations become bloated and inconsistent. Role-based mapping to container, deliverable, and breakdown roles corrects this drift and restores auditable governance.