---
title: "Jira delivery traceability steward: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/agency-project-management-jira-workflow-steward/
description: "A delivery-planning profile linking a confirmed Jira ticket to branch, commit, PR and release evidence."
---

# Jira delivery traceability steward: review, role & definition · Undominated.ai

> A delivery-planning profile linking a confirmed Jira ticket to branch, commit, PR and release evidence.

[← Explore all agents](/agents/)

PROJECT PLANNING / Agency Agents community

# Jira delivery traceability steward

A delivery-planning profile linking a confirmed Jira ticket to branch, commit, PR and release evidence.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/project-management/project-management-jira-workflow-steward.md)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher Agency Agents community
 Licence [MIT ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE)
 Revision bd956db032d9
 [Read what was—and wasn’t—checked ↓](#review)

“Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.”

 [Agency Agents community · upstream description ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/project-management/project-management-jira-workflow-steward.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The profile refuses to invent ticket identifiers and separates Git-facing work from unrelated tasks that need no Jira process.
- Its PR template keeps risk, rollback and testing evidence visible alongside the ticket link.

### A good fit for

 - Supply a real Jira task ID, repository branching conventions and intended change.
- Produce a delivery packet with atomic commit scope, review context and validation evidence.

### Weigh up before choosing

 - The supplied hook only checks name patterns; it does not verify a Jira issue exists or that branch and commit IDs match, and release subjects bypass its commit regex. Its develop/main convention is not universal.
- Source-only component: inspect its upstream context and dependencies before adapting it; no standalone runnable bundle is offered.
- Native-host parsing and loading of the original Agency frontmatter were not tested. Check the installed host requirements; optional metadata may be ignored rather than enforced.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - project-management/project-management-jira-workflow-steward.md (pinned complete source retained)
- LICENSE
- Repository README and current official host configuration documentation

### Our findings

 - The profile refuses to invent ticket identifiers and separates Git-facing work from unrelated tasks that need no Jira process.
- Its PR template keeps risk, rollback and testing evidence visible alongside the ticket link.

### Not established by this review

 - Source review only: no agent was installed or invoked. Task correctness, effective host restrictions and integration behaviour were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/project-management/project-management-jira-workflow-steward.md)
 - Read the pinned source and its licence, then configure an explicitly bounded host context.
- Check the original display-style name and optional color/emoji/vibe metadata against the installed host requirements before loading a working copy. Current Claude Code documentation says unknown frontmatter fields are ignored; it does not establish a need to rewrite these names. Keep the archived/downloaded original unchanged.
- Adapt the branching rules and inspect the sample hook before installation; use placeholders only for templates and never copy example test passes as real evidence.
- Supply a real Jira task ID, repository branching conventions and intended change.

### Before you start

 - Confirmed Jira issue and repository policies
- Git and optional Jira integration for authorized execution

### Compatibility

Claude Code

### Implementation

Markdown

### Host-mediated agent profile

 - No tools allowlist is declared. Claude Code can inherit or expose the host’s available tools by default; restrict file, shell and network access in the host.

### Cost model

The definition has the stated open-source licence. Model/host usage and any connected service or execution environment can incur separate costs.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned upstream agent definition ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/project-management/project-management-jira-workflow-steward.md) Checked 2026-10-14 https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/project-management/project-management-jira-workflow-steward.md Supports: Workflow, inputs, outputs and stated boundaries
- [Applicable licence ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE) Checked 2026-10-14 https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE Supports: Redistribution and attribution
- [Host configuration and tool inheritance ↗](https://code.claude.com/docs/en/sub-agents.md) Checked 2026-10-14 https://code.claude.com/docs/en/sub-agents.md Supports: Host loading and effective permission boundaries

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
