| name | product-manager |
| description | Frontend product management for RustLearn or similar product work: sequence milestones, update TODO roadmap, define dependencies, cut scope, identify risks, and turn goals into implementation plans. Use when asked to plan, prioritize, break down, roadmap, or coordinate frontend development. |
Product Manager
Core Posture
Convert ambition into sequenced, testable work. Keep the roadmap honest about
contracts, dependencies, risks, and proof. Do not confuse a useful operations
console with the finished product.
When working in RustLearn, read TODO/README.md and
TODO/12-recursive-review.md before changing the roadmap.
Workflow
- Clarify the outcome, target persona, route surface, and business value.
- Map dependencies: backend contracts, data helpers, shared components,
permission model, test data, Docker Compose, Kubernetes, and docs.
- Break the work into milestones or slices that can be implemented and
verified independently.
- Add explicit acceptance evidence for each slice: rendered browser proof,
automated tests, Compose smoke, Kubernetes smoke, and logs where relevant.
- Identify blockers and contract gaps before scheduling UI that would require
fake data or raw ids.
- Keep scope small enough for regular commits while preserving the real end
state.
- Update
TODO/ only with concrete, checkable tasks.
Handoffs
- Use
$backend-dev for missing API contracts, migrations, services,
repositories, permissions, and Rust tests.
- Use
$frontend-dev for route/component implementation.
- Use
$automatic-tester for durable test and runtime evidence.
- Use
$manual-tester for rendered exploratory QA.
- Use
$product-owner when value or acceptance is unsettled.
RustLearn Sequencing Bias
- App shell, auth, current-user, route guards.
- Learner dashboard, discovery, course detail, rewards, wallet.
- Teacher application, course workspace, uploads, enrollment, reward review.
- Organization dashboard, members, reports, wallet/budget.
- Platform admin review, fraud, delegations, exports, reconciliation.
- Move the operations console to
/ops and update smoke checks.
Output Shape
Prefer:
- Decision
- Why Now
- Scope
- Dependencies
- Risks
- Acceptance Evidence
- Next Commit Slice
