jira

Name: jira
Availability: InStock
Author: mthang1801

Automates Data Visualizer task tracking and dependency management via a graph of linked items.

Updated Aug 23, 2026

Search Tags:#dependencies #backlog #jira #task-management #sprint-planning #progress.md #data-visualizer

Ready to run

npx skills add https://github.com/mthang1801/go-domain-driven-design --skill jira-mthang1801

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/mthang1801/go-domain-driven-design/tree/main/.claude/skills/jira
Command: npx skills add https://github.com/mthang1801/go-domain-driven-design --skill jira-mthang1801

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tasks and dependencies in large DV projects can become noisy and hard to track over time. This skill preserves historical task lists, constructs a dependency graph (depends_on, blocks, related_to, epic_link), and guides planning with readiness and priority.

Core Features & Use Cases

Build and maintain a dependency graph across tasks, bugs, and epics to reflect real work relationships.
Automatically suggest the next task to start based on dependency completion, priority, and progress.
Update progress-related documents (progress.md/backlog.md) while preserving history and linking related items.
Integrate with DV-Orchestrator to prioritize ready-to-start tasks during planning.

Quick Start

Provide backlog and progress context to the agent, generate the dependency graph, and propose the next task to start.

Frequently Asked Questions about jira

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

FAQPage Schema

How do I track task dependencies and backlog history in Data Visualizer projects?▼

Track task dependencies and backlog history in Data Visualizer projects by constructing a dependency graph using depends_on, blocks, related_to, and epic_link references. This preserves historical task lists while reflecting real work relationships across epics and bugs.

How do I automatically suggest the next task to start during sprint planning?▼

Suggest the next task to start during sprint planning by applying readiness-based gating. The system evaluates dependency completion, priority, and progress to enforce ready-to-start sequencing and propose the most actionable task.

Can I update progress.md and backlog.md without losing previous task records?▼

You can update progress.md and backlog.md without losing previous task records because the system preserves history while applying dependency references. It maintains a historical task list and links related items as progress evolves.

What is the best way to sequence tasks when blockers prevent starting new work?▼

The best way to sequence tasks when blockers prevent starting new work is to map depends_on and blocks relationships across the backlog. This dependency graph identifies blocked items and surfaces ready-to-start tasks that have no unresolved dependencies.

How does readiness-based task gating work for backlog prioritization?▼

Readiness-based task gating for backlog prioritization works by checking whether all depends_on references for a task are completed. Only tasks with resolved dependencies pass the gate, ensuring sprint planning excludes blocked work and focuses on actionable items.

Does this task management approach integrate with DV-Orchestrator for sprint planning?▼

This task management approach integrates with DV-Orchestrator to prioritize ready-to-start tasks during sprint planning. The orchestrator uses the constructed dependency graph and readiness gating to sequence actionable work automatically.