User Stories & Acceptance Criteria · v1.0
Backlog, in Gherkin
Five epics, mapped to PRD requirements, with Given/When/Then acceptance criteria — the format engineering estimates against.
14 stories across 5 epics · ~78 points · MVP cut = all P0 (13 stories, ~72 pts), deferring 3 P1 stories to Phase 2.
Backlog by epic
Account Connection2 stories · 8 pts
Creative Generation3 stories · 18 pts
Monitoring2 stories · 13 pts
Review Lanes & HITL4 stories · 21 pts
Cost Controls3 stories · 18 pts
Story format — two representative examples
US-1Connect ad account
As a performance marketer, I want to connect my Meta Ads account via OAuth so that Ad Copilot can read my campaign data.
P05 ptsEpic 1
- GIVEN I click "Connect Meta Ads," WHEN I grant OAuth permission, THEN my last 90 days of campaign data begins syncing.
- GIVEN the sync is in progress, WHEN I view the dashboard, THEN I see a sync-status indicator, not an empty state.
- GIVEN OAuth fails, WHEN I return to Ad Copilot, THEN I see a clear error and a retry option.
US-9Review and act on a queued recommendation
As a performance marketer, I want to approve, reject, or edit a queued recommendation so that I retain control over budget-impacting actions.
P05 ptsEpic 4 · FR-10
- GIVEN a Suggest-lane item, WHEN I click Approve, THEN it executes against the platform API and is logged.
- GIVEN a Suggest-lane item, WHEN I click Edit, THEN I can modify the value before approving.
- GIVEN I reject a recommendation, WHEN I do so, THEN I can optionally add a reason stored for future scoring.