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.
“Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.”
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.
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.
- 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
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
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 ↗Checked
https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE
Supports: Redistribution and attribution
https://code.claude.com/docs/en/sub-agents.md
Supports: Host loading and effective permission boundaries