session-lifecycle

To maintain context across git repositories, you can coordinate orientation, planning, and persistence tasks to automatically aggregate memory, git status, and GitHub activity into a persistent knowledge vault for project continuity.

Automating a daily development briefing involves aggregating memory, git status, GitHub activity, and TODOs to provide a comprehensive morning briefing, ensuring you get caught up on current projects and pending tasks without manual tracking.

Generating prioritized and time-budgeted task lists requires using a planning phase within your workflow that structures session goals, ensuring focus and preventing scope creep by capturing completed work and decisions systematically.

Yes, effective session management requires integration with local shell tools and a configured knowledge-system directory to execute memory aggregation and state tracking across your development environments.

Yes, the workflow automation operates across git repositories and GitHub issues using gh, while requiring uv to manage the local execution environment for scripts that handle memory aggregation and state tracking.

To capture completed work and learnings into a persistent knowledge vault, execute the persistence lifecycle phase which automatically records decisions and project state, solving the problem of cognitive fragmentation between work sessions.