sprint-task-lifecycle

Sprint task automation moves tasks through status transitions (pending to in_progress, in_progress to completed, or in_progress to deferred) by reading and editing your ACTIVE_SPRINT.toml file. The Skill locates task blocks by ID, updates status fields, enforces completion_notes when marking tasks complete, and returns structured confirmation of changes made.

Marking a task complete transitions its status from in_progress to completed, automatically adds the current date to completed_date, and requires completion_notes to be present. The Skill validates these required fields before confirming the update, ensuring task records are fully documented.

Yes, you can defer in_progress tasks by moving them to deferred status and providing a reason. The Skill records this state change in your ACTIVE_SPRINT.toml file and returns explicit confirmation of the deferral for team visibility.

Completion notes are enforced when transitioning a task to completed status. The Skill will not mark a task complete without them, ensuring every finished task includes context about the work performed.

Use the start command with the task ID to move a task from pending to in_progress status. The Skill updates the status in ACTIVE_SPRINT.toml and returns the task location and updated state for confirmation.

Sprint task automation works with TOML-formatted sprint files, specifically internal/sprints/ACTIVE_SPRINT.toml. Tasks are organized in named blocks identified by task IDs, with status and metadata fields the Skill reads and updates.