day-open

To generate a daily plan from GitHub issues and git commits, the Skill scans your local workspace and connected repositories to triage actionable items and correlate them with previous plans. It synthesizes yesterday's commits and issues into a prioritized DayPlan markdown file and a compact VS Code dashboard.

The best way to triage carry-over tasks from previous day plans is to run an automated aggregation protocol that cross-references yesterday's DayPlan and WeekPlan. This protocol surfaces incomplete carry-over tasks and allocates daily budgets based on your day-rhythm-config settings.

This daily planning tool works with connected repositories but explicitly filters out read-only and upstream-only repositories during its scan. It ensures only actionable local workspace and connected repositories are included in your triage and DayPlan generation.

To prepare an automated daily standup, the Skill collects and synthesizes scattered signals like development notes, calendar events, and QA bot reports. It aggregates these inputs into a single prioritized plan so you start the day with clear priorities and no lost context.

Yes, you can use TodoWrite gating for stepwise daily plan generation. The Skill operates stepwise under TodoWrite gating, reading configuration from day-rhythm-config.yaml and requiring verification checks before any commit and push actions are executed.

When aggregating system updates and Scout findings, the Skill requires a day-rhythm-config.yaml file to allocate daily budgets and respects operational guardrails. It limits actions to read-only and upstream-only repository filtering and mandates verification checks before committing or pushing changes.