AI Skill Source Integrations
JIRAJIRA

Turn JIRA issue history into AI Agent Skills

Develop AI Agent Skills from the investigation notes, review decisions, and acceptance criteria in JIRA. Preserve what changed the team’s understanding, how the resolution was verified, and where the answer still has limits.

Keep the reasoning behind the resolution

Issue replayIllustrative JIRA workflow
DEL-284Bug

Duplicate orders after a retry

Order serviceRetry behavior
TriageInvestigatingIn reviewResolvedE
Support report
“Two order records share the same customer reference. The customer reports submitting once.”
Reasoning to retain

Start with the observed behavior

The issue records a symptom. The trigger still needs investigation. Keep the observation separate from an early explanation.

Reproduction note
“Reproduces after a timed-out request is retried. A normal submission creates one order.”
Reasoning to retain

Retain what made the failure reproducible

The useful reasoning connects the symptom to a specific condition. Preserve the contrasting case where the failure does not occur.

Reviewer comment
“Cover both immediate and delayed retries. The current acceptance criteria only test a normal submission.”
Reasoning to retain

Keep the challenge that improved the fix

The reviewer expands what the team must prove. That change explains why passing the first test was not enough.

Resolution note
“Immediate and delayed retries verified in the tested configuration. A related issue covers retries after an interrupted session.”
Reasoning to retain

Preserve the boundary of the result

Retain the tested conditions and the linked case that still needs its own investigation. A resolved issue is evidence within a scope.

Select a stage to inspect the reasoning behind the status change.

The opportunity

The status changed.
What changed the team’s mind?

A closed issue gives you an outcome. The discussion, changed criteria, and verification notes explain how the team got there. That is the reasoning worth developing into an AI Agent Skill.

01 / Examine the revision

A better question changes what “done” means

The first criterion covered a normal submission. A reviewer asked about retries. The revised criteria made the overlooked conditions explicit.

Preserve that change so an agent can help identify a missing test or ask a more useful follow-up question.

Explore reasoning analysis
DEL-284 / Acceptance criteria
Initial acceptance criterionRevision 1

A normal submission creates one order.

Question still open

What happens when the request is retried?

The original criterion does not establish the behavior after a timeout.

The review that expanded the testReview note

A normal submission creates one order.

Reviewer
“Cover both immediate and delayed retries. The current acceptance criteria only test a normal submission.”
The criterion becomes more specificRevision 2

A normal submission creates one order.

+

An immediate retry creates no additional order.

+

A delayed retry creates no additional order.

Reasoning preserved

The test now covers the conditions raised in review. The verification record still needs to show the result.

Illustrative revision history. An acceptance criterion states what must be proved.

02 / Connect the source evidence

An issue is one record.
Its reasoning reaches further

Keep reproduction notes, review comments, verification, and related issues connected. Each contributes a different question for the expert developing the skill.

Evidence around DEL-284
AI Agent Skill candidate

Investigate a retry-related defect

Reproduction

Which conditions reproduce the problem?

Retain the failed case and the normal submission that behaved differently. An expert can establish which conditions matter to the diagnosis.

Review

What did the first test leave out?

Connect the reviewer’s challenge to the revised acceptance criteria. Preserve why the team expanded the test alongside the final wording.

Verification

Where does the resolution hold?

Keep the verification evidence and its configuration attached. Ask the owner which assumptions must be rechecked in a different environment.

Related issue

What changes in the related case?

A linked issue identifies another investigation. Compare its conditions with the original before treating both as the same defect pattern.

Develop with an expert
Select a source to see the question it contributes. Linked records provide context. An expert establishes which reasoning can be reused.

Begin with an issue worth revisiting

Give the next issue a better starting point

Bring a resolved issue, the review that changed the answer, and a related case that tested its limits. Work with an expert to turn that reasoning into an AI Agent Skill.

Discuss your JIRA sources