project_tasks

Persistent project tasks track high-level deliverables across multiple sessions by storing plan files under .local/tasks/. This mechanism ensures progress visibility and cross-agent coordination for long-running features that require continuous state management.

Create a project task by writing a plan file to the .local/tasks/ directory and presenting it to the user for approval. This plan-based task definition establishes a persistent, user-visible record for managing milestones and deliverables.

Yes, this supports cross-agent coordination for long-running features by enabling the creation, updating, and searching of user-facing project tasks. It allows multiple agents to maintain progress visibility and manage dependencies across different sessions.

The best way to manage user-visible project milestones is using plan-based task definitions stored in .local/tasks/. This method provides a persistent state that users can track, search, and update as features span across multiple sessions and agents.

No specific dependencies are required to enable task synchronization and dependency management. The system operates independently using plan files stored under .local/tasks/ to manage persistent state and optional task-synchronization features.