Definition of Ready AI for Jira

Review generated work orders

Generated work orders are designed to make issue review faster, but they should still be checked by a human before implementation or Jira write-back.

1. What a work order should contain

  • Objective
  • Background
  • In scope and out of scope
  • Assumptions
  • Suggested components
  • Acceptance criteria
  • Implementation notes
  • Test plan
  • Risks
  • Rollout and rollback notes
  • Agent prompt for a developer or AI coding agent

2. Review checklist

  • Confirm the work order does not broaden the Jira issue scope.
  • Remove assumptions that are wrong or unverified.
  • Check acceptance criteria are testable and pass/fail.
  • Confirm the test plan covers happy paths, failure states, permissions, regressions, and relevant edge cases.
  • Confirm risky areas have explicit review, rollout, and rollback notes.

3. Jira write-back

Definition of Ready AI for Jira should never autonomously modify Jira. A user must explicitly approve generated comments or subtasks, and project settings or edition gates may disable those actions.

4. AI coding agent use

When pasting a generated work order into an AI coding tool, the agent prompt should instruct the tool to inspect the codebase first, follow existing patterns, avoid unrelated refactors, and stop for clarification if the codebase contradicts the issue assumptions.