claude-tasks

You can automate task file creation and lifecycle management by using a skill that generates standardized markdown task files with required frontmatter in a .claude/tasks/ directory. It handles creation and safely archives completed tasks based on git merge status.

The best way to archive completed tasks is to use a skill that verifies the associated feature branch has been merged to main. It then automatically archives the task file and updates the project index to keep the board synchronized with git history.

Standardized markdown task files help with project tracking by enforcing required frontmatter and phase labels based on project standards. This ensures consistent task representation and automated board state maintenance within the Claude environment.

Yes, task lifecycle management requires integration with git worktree roots to ensure consistent file operations. Strict adherence to project-specific task standards and the .claude/tasks/ directory structure is also required for automated archival.

Task board state becomes fragmented without automated task file management because manual maintenance often fails to synchronize with git history. Automating the lifecycle of task files prevents fragmented tracking and keeps the project index clean after merges.

No, you cannot use this task management skill without strict project-specific task standards. The skill requires predefined frontmatter and phase labels to generate standardized markdown task files and properly update the project index upon archival.