beads

To preserve task context across multiple conversation sessions after compaction, use git-backed issue tracking to store decisions, dependencies, and progress notes that survive session boundaries and restarts.

Track complex task dependencies in a multi-session workflow by enforcing four dependency types: blocks, related, parent-child, and discovered-from, ensuring work moves forward without losing context.

The best way to manage persistent issue tracking for AI conversations is applying git-backed persistence to maintain decisions and context, preventing knowledge loss during session compaction.

Yes, git-backed persistence works for coordinating cross-skill collaboration by providing integration points for advanced workflows and session handoffs to orchestrate end-to-end projects.

To start tracking immediate actions after creating an issue, describe the current work, create the issue, and begin tracking the immediate actions using a todo tool for that session.