Show developers where they can contribute first without needing the entire implementation stack to be settled.
- Personal Operations hero loop design (capture -> triage -> plan -> execute -> review).
- Shared contracts for entities/events across CLI, web, and mobile.
- Reminder and approval flow reliability (including degraded dependency handling).
- Inbox triage and review UX clarity for daily/weekly usage.
- Contributor onboarding and docs refinement for first-run success.
- Local integration improvements that directly support the hero loop.
- Mobile companion capabilities (fast capture, notifications, approvals).
- hero loop user stories with reproducible command sequences
- contract proposals (
capture,inbox,plan,reminder,review) - integration test cases for happy path and failure mode
- UI sketches for mobile capture and approval interactions
- docs edits that reduce first-run ambiguity
- error-code mapping proposals for user-facing failures
Contributions should reduce ambiguity in the active Personal Operations MVP, improve daily reliability, or tighten cross-surface consistency without inflating scope.