You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goal\n\nTurn CodingBuddy into a calm attention cockpit for solo developers who juggle many repositories and local developer systems. The app should reduce decision fatigue by showing one understandable next action, a short ordered queue, and an explicit place for signals that can safely wait.\n\n## User problem\n\nCodingBuddy already exposes useful state, but developers still have to scan several surfaces and mentally decide what deserves attention. With many projects, this creates context switching, false urgency, and forgotten blockers.\n\n## Product principles\n\n- One recommended next action, not a wall of red badges.\n- Deterministic and explainable ranking; no opaque score and no LLM dependency.\n- Separate urgency from importance and from freshness.\n- Healthy, waiting, stale, and unavailable states must not create false urgency.\n- Every queue item explains what happened, why it matters, and the expected result of the suggested action.\n- Native, dense macOS UI without decorative dashboard cards.\n- Source features retain execution ownership and safety confirmations.\n\n## Child work\n\n1. Rank monitored pull requests into one explainable cross-repository attention queue.\n2. Add Health & Security signals after their guidance PR lands.\n3. Add package-maintenance signals after its guidance PR lands.\n4. Add deliberate parking/snoozing and a bounded focus lane.\n5. Add a lightweight resume context for returning to a project without becoming a general task manager.\n\n## Definition of done\n\n- The cockpit can aggregate supported signals without duplicating source-store persistence.\n- Ranking is deterministic, unit-tested, and exposed in plain language.\n- The first visible item is actionable or explicitly explains why waiting is correct.\n- Users can navigate to or invoke only existing safe source actions.\n- Long German copy, minimum window size, keyboard use, and VoiceOver are covered.\n- Feature flag, EN/DE localization, wiki sources, Swift tests, build, and repository checks pass.\n\n## Out of scope\n\n- Running coding agents.\n- Autonomous fixes or background updates.\n- Calendar/task-manager replacement.\n- AI-generated prioritization.\n- Notifications before the ranking and parking model has been validated.\n
Goal\n\nTurn CodingBuddy into a calm attention cockpit for solo developers who juggle many repositories and local developer systems. The app should reduce decision fatigue by showing one understandable next action, a short ordered queue, and an explicit place for signals that can safely wait.\n\n## User problem\n\nCodingBuddy already exposes useful state, but developers still have to scan several surfaces and mentally decide what deserves attention. With many projects, this creates context switching, false urgency, and forgotten blockers.\n\n## Product principles\n\n- One recommended next action, not a wall of red badges.\n- Deterministic and explainable ranking; no opaque score and no LLM dependency.\n- Separate urgency from importance and from freshness.\n- Healthy, waiting, stale, and unavailable states must not create false urgency.\n- Every queue item explains what happened, why it matters, and the expected result of the suggested action.\n- Native, dense macOS UI without decorative dashboard cards.\n- Source features retain execution ownership and safety confirmations.\n\n## Child work\n\n1. Rank monitored pull requests into one explainable cross-repository attention queue.\n2. Add Health & Security signals after their guidance PR lands.\n3. Add package-maintenance signals after its guidance PR lands.\n4. Add deliberate parking/snoozing and a bounded focus lane.\n5. Add a lightweight resume context for returning to a project without becoming a general task manager.\n\n## Definition of done\n\n- The cockpit can aggregate supported signals without duplicating source-store persistence.\n- Ranking is deterministic, unit-tested, and exposed in plain language.\n- The first visible item is actionable or explicitly explains why waiting is correct.\n- Users can navigate to or invoke only existing safe source actions.\n- Long German copy, minimum window size, keyboard use, and VoiceOver are covered.\n- Feature flag, EN/DE localization, wiki sources, Swift tests, build, and repository checks pass.\n\n## Out of scope\n\n- Running coding agents.\n- Autonomous fixes or background updates.\n- Calendar/task-manager replacement.\n- AI-generated prioritization.\n- Notifications before the ranking and parking model has been validated.\n