[OneDev #1] feat(workflow): daily dev focus rotation — one priority per day #34

Closed
opened 2026-05-24 04:46:40 +00:00 by joseph · 1 comment
Owner

Imported from OneDev issue #1 (id 35177)
Original project: internal-joseph
Original state: Closed
Original submitterId: 5
Original submitDate: 2026-04-08T14:36:52.043+00:00
Original lastActivity: {'date': '2026-04-08T18:48:56.158+00:00', 'description': "changed state to 'Closed'", 'userId': -1}

Original fields:

  • Type: New Feature
  • Priority: Normal
  • Assignees: None

Idea

Adopt a daily focus rotation so each weekday has exactly one dominant lens. Reduces decision fatigue and prevents the "do a little of everything, finish nothing" trap.

Proposed rotation

  • Mon — Frontend / Usefulness: UI polish, UX wins, surfacing existing capabilities better
  • Tue — Backend / Stability: bug bash, error paths, retries, idempotency, observability
  • Wed — Security: audits, secrets hygiene, IP restrictions, SSO drift, posture reviews
  • Thu — Research: spike days, evaluate tools, read docs, prototype throwaway code
  • Fri — Free day: whatever pulls hardest, or rest

Open questions

  • Hard rule or default-with-overrides?
  • Should Day Shepherd (sister issue) surface today's lens in its 15-min phase popup?
  • Track adherence anywhere, or just vibes?

Why

Solo dev. Context switching is the silent productivity killer. A single named lens per day gives Claude sessions a known frame too.

Imported from OneDev issue #1 (id 35177) Original project: internal-joseph Original state: Closed Original submitterId: 5 Original submitDate: 2026-04-08T14:36:52.043+00:00 Original lastActivity: {'date': '2026-04-08T18:48:56.158+00:00', 'description': "changed state to 'Closed'", 'userId': -1} Original fields: - Type: New Feature - Priority: Normal - Assignees: None ## Idea Adopt a daily focus rotation so each weekday has exactly one dominant lens. Reduces decision fatigue and prevents the "do a little of everything, finish nothing" trap. ## Proposed rotation - **Mon — Frontend / Usefulness**: UI polish, UX wins, surfacing existing capabilities better - **Tue — Backend / Stability**: bug bash, error paths, retries, idempotency, observability - **Wed — Security**: audits, secrets hygiene, IP restrictions, SSO drift, posture reviews - **Thu — Research**: spike days, evaluate tools, read docs, prototype throwaway code - **Fri — Free day**: whatever pulls hardest, or rest ## Open questions - Hard rule or default-with-overrides? - Should Day Shepherd (sister issue) surface today's lens in its 15-min phase popup? - Track adherence anywhere, or just vibes? ## Why Solo dev. Context switching is the silent productivity killer. A single named lens per day gives Claude sessions a known frame too.
Author
Owner

Imported from OneDev comment id 184 on issue #1
Original userId: -1
Original date: 2026-04-08T18:48:55.158+00:00

State changed as code fixing the issue is committed (118feff556)

Imported from OneDev comment id 184 on issue #1 Original userId: -1 Original date: 2026-04-08T18:48:55.158+00:00 State changed as code fixing the issue is committed (118feff5560d3f1100e9e1f5b15c069a44b21d5b)
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
joseph/internal-joseph#34
No description provided.