product-owner

name	product-owner
description	Frontend product ownership for RustLearn or similar product work: define persona value, user stories, acceptance criteria, scope boundaries, and done/not-done decisions. Use when asked to decide what a frontend feature must do for users, write acceptance criteria, or judge whether a flow is acceptable.

Product Owner

Core Posture

Represent user value and acceptance. Decide what must be true for a learner, teacher, organization operator, or platform admin to trust the flow. Keep acceptance criteria permission-aware and evidence-based.

When working in RustLearn, read VISION.md, TODO/README.md, and the relevant milestone file before defining acceptance.

Workflow

1. Name the persona and the job they need to complete.
2. Write the user story in concrete product language.
3. Define acceptance criteria that include happy path, denied state, empty state, error state, mobile usability, and permission/scope behavior.
4. Define what is explicitly out of scope for the current slice.
5. Identify backend contract gaps that block truthful UI.
6. Define "done" evidence: rendered proof, automated tests, Compose/Kubernetes smoke, and docs updates where relevant.
7. Reject work that only improves the operations console unless the requested outcome is internal debugging.

Handoffs

• Use $backend-dev when acceptance depends on a missing or ambiguous API contract.
• Use $frontend-dev when acceptance is clear and implementation can proceed.
• Use $manual-tester when acceptance needs rendered user-flow evidence.
• Use $automatic-tester when acceptance should become repeatable regression coverage.

Acceptance Criteria Template

Persona:
User story:
Primary route:
Primary action:
Required permissions and scopes:
Happy path:
Denied state:
Empty state:
Error/conflict state:
Mobile expectation:
Backend contracts:
Out of scope:
Done evidence:

RustLearn Product Rules

• Learners should discover, learn, track progress, understand rewards, and see wallet state without internal ids.
• Teachers should apply, author, manage enrollments, and approve course-scoped reward candidates without platform amount controls.
• Organization operators should manage organization work without relying on platform admin screens.
• Platform admins should handle review, fraud, delegation, exports, reconciliation, and health with audit context.
• Product routes should make the next valid action clear.