task

To synchronize task state across multiple AI agents, this Skill maintains a consistent task.json file and a global _index.jsonl registry, ensuring context and workflow status remain aligned without state drift.

You can bind a development task to a specific git branch during task initialization, ensuring all subsequent AI actions like planning and coding reference the correct task context for that branch.

The best way to prevent state drift is by using a single source of truth for task records, which synchronizes context, workflow status, and git branch bindings across the entire development lifecycle.

Yes, task management supports multi-agent environments safely by requiring atomic file operations and fcntl locking to ensure data integrity when multiple agents access task records simultaneously.

Yes, you can use JSON-based storage for task lifecycle management, as the system handles task creation, resumption, and finalization by synchronizing state across JSON files and global index registries.

Atomic file operations are needed for development task tracking to ensure data integrity in multi-agent environments, preventing corrupted states when multiple processes attempt to update the task.json file or index simultaneously.