AI-Assisted Backlog Management and Prioritization

Convert this feature idea into properly formatted user stories:

Feature idea: Let AP managers approve invoices from their mobile phone
without having to log into the desktop system.

For this feature:
1. Write a parent epic (1-2 sentences, business outcome focused)
2. Break it into 4-6 user stories, each independently deliverable
3. For each story:
   - Title
   - Story: As a [role], I want [action], so that [benefit]
   - Acceptance Criteria (numbered, specific, testable)
   - Out of Scope: what this story does NOT include
4. Identify dependencies between stories
5. Flag any stories that need technical investigation before estimating

Roles available: AP Clerk, AP Manager, Finance Controller, System Admin.
Constraint: no story should take more than 5 days to implement.

Review and improve the acceptance criteria for these user stories: [paste]

For each story, check whether criteria are:
1. Specific: no vague qualifiers ("should be fast", "easy to use")
2. Measurable: can a QA engineer verify pass/fail without interpretation?
3. Complete: covers happy path, error states, and at least 2 edge cases
4. User-centered: describes what the user experiences, not how the system works
5. Unambiguous: only one reasonable interpretation

Rewrite criteria that fail any check. If any criteria require a
technical decision (performance targets, data retention rules), flag
them as "TBD — requires PO decision on [specific parameter]."

Score the following backlog items using the RICE framework:
Reach × Impact × Confidence ÷ Effort

Items: [paste backlog items with descriptions]

For each item, provide:
- Reach estimate (users affected per quarter — explain assumption)
- Impact (0.25 / 0.5 / 1 / 2 / 3 — explain rationale)
- Confidence (% certainty in reach and impact estimates)
- Effort (person-weeks — explain assumption)
- RICE score
- Ranking by RICE score

Then: identify any items where RICE score contradicts your intuition about priority, and explain why (suggests the intuition may be wrong, or the score inputs need revision).

Place these backlog items on a 2x2 value/effort matrix:

Items: [paste]

Categorize as:
- Quick wins (high value, low effort) — do first
- Strategic investments (high value, high effort) — plan carefully
- Fill-ins (low value, low effort) — do if capacity allows
- Time sinks (low value, high effort) — do not do

For each item, explain the value assessment (what problem it solves
and for how many users) and the effort assessment (why high/low).
Identify any item where there is significant uncertainty in either dimension.

Here is our product backlog: [paste]

Perform a backlog health analysis:
1. Stories at the top (next 2 sprints) — are they sprint-ready?
   (Clear acceptance criteria, appropriately sized, dependencies resolved)
2. Stories without acceptance criteria — list them
3. Stories that appear too large for one sprint — list them and
   suggest split approaches
4. Duplicate or highly similar stories — flag for consolidation
5. Stories referencing technical decisions that haven't been made —
   flag for design/architecture review
6. Stories in the backlog for more than 6 months with no progress —
   should they be closed or deprioritized?

Recommendations: top 5 backlog hygiene actions for this week.

I need to explain to the Procurement Director why the vendor
self-service portal is deprioritized until Phase 2.

Context:
- Phase 1 capacity is fully committed to core AP automation,
  invoice matching, and approval workflow
- The vendor portal is valuable but affects external users
  who are not part of the compliance requirement driving Phase 1
- Adding it to Phase 1 would push the go-live date by 3 weeks

Draft an explanation that:
1. Acknowledges the value of the vendor portal (don't dismiss it)
2. Explains the capacity constraint clearly (not as an excuse —
   as a real trade-off decision)
3. Explains what the Phase 2 commitment means (timeline, not vague deferral)
4. Invites input on whether the trade-off is correct
   (make them a partner in the decision, not a victim of it)

Tone: direct, respectful, not defensive. 150 words maximum.