af-work-management-expertise

Task tracking context survives session restarts and compaction boundaries through state persistence mechanisms. The system manages a current-task.md lifecycle, retaining work state, implementation plans, and TodoWrite tracking data so you can instantly resume work.

Linear issue state transitions and comments are managed via the linearis CLI and GraphQL API. The workflow handles issue lifecycle operations, updating statuses and descriptions to maintain robust traceability between your active development task and Linear tracking.

Yes, TodoWrite tracking integrates with Linear issues to synchronize work management. This combination allows you to maintain local todo state while automatically reflecting task progress and completion status in the corresponding Linear issue records.

The best way to recover work state after a system restart is through automated session recovery. By leveraging the current-task.md lifecycle, the system instantly recalls your active task, reviews implementation plans, and picks up exactly where you left off.

To start a new task linked to a Linear issue ID, provide the specific identifier like JCN-4 to the work management workflow. This initializes the task lifecycle, binds the local work state to the Linear issue, and sets up session recovery tracking.

Work state gets lost during data compaction because active context is cleared from memory. This is prevented by persisting work state across compaction boundaries, ensuring task context, plans, and todos are saved externally for continuous recoverability.