Jira Refinement Assistant
Review Jira backlog items for clarity, completeness, dependencies, risks and refinement readiness.
Act as an experienced Product Owner, Business Analyst and Agile refinement facilitator.
Review the following Jira backlog items:
{{backlog_items}}
Product objective:
{{product_objective}}
Definition of Ready:
{{definition_of_ready}}
Known dependencies and constraints:
{{dependencies_and_constraints}}
For every backlog item, evaluate:
1. Business Purpose
2. User or Stakeholder Value
3. Clarity
4. Scope
5. Acceptance Criteria
6. Business Rules
7. Testability
8. Dependencies
9. Risks
10. Data Requirements
11. Integration Requirements
12. Non-Functional Requirements
13. UX or Accessibility Considerations
14. Security and Privacy Considerations
15. Estimation Readiness
16. Delivery Readiness
Assign one refinement status:
- Ready for Estimation
- Ready for Sprint Planning
- Requires Clarification
- Requires Discovery
- Too Large
- Blocked
- Duplicate or Overlapping
For every item, provide:
- Jira Issue Key, if provided
- Current Issue Type
- Current Summary
- Recommended Summary
- Missing Information
- Ambiguities
- Suggested Acceptance Criteria
- Dependencies
- Risks
- Clarification Questions
- Recommended Next Action
- Suggested Labels
- Suggested Component
- Suggested Priority
- Refinement Status
Identify items that should be:
- Split
- Merged
- Rewritten
- Moved to another epic
- Removed from the backlog
- Sent for technical investigation
- Sent for product discovery
Do not invent business rules, estimates or technical solutions.
Do not mark an item as ready if critical information is missing.
Return:
1. A refinement-assessment table
2. Improved versions of the backlog items
3. Questions for the refinement session
4. Blockers and dependencies
5. A recommended refinement-session agendaWorks with ChatGPT, Claude, Gemini and Copilot.
Example in action
See how this prompt transforms a real input into a structured result.
Product objective: Reduce customer-service contacts related to forgotten passwords. Backlog item: Summary: Password reset Description: Users should be able to reset their password. Definition of Ready: - User value is clear - Acceptance criteria exist - Dependencies are identified - The item is small enough for one sprint Known constraints: Password-reset links must be secure and time-limited.
Refinement Status: Requires Clarification Current Summary: Password reset Recommended Summary: Enable registered customers to reset a forgotten password through email verification Business Purpose: Reduce customer-service contacts and allow customers to recover account access independently. Missing Information: - Reset-link expiration time - Password-complexity rules - Behavior for unknown email addresses - Maximum number of reset requests - Audit and monitoring requirements Suggested Acceptance Criteria: Given a registered customer requests a password reset When the request is accepted Then the system sends a single-use reset link to the registered email address. Given an unknown email address is submitted When the user requests a reset Then the system displays a generic confirmation without revealing whether the account exists. Dependencies: - Email service - Authentication service - Security review Risks: - Account enumeration - Reuse of reset tokens - Excessive reset requests Recommended Next Action: Confirm the security rules before estimation.