Summary
Pre-existing JSON-format task files in this repo predate the task-utils YAML standardisation. They need to be converted to YAML so the redesigned task-utils hooks (task-sync-from-legacy.sh, require-task-in-progress.sh) treat them uniformly with newly created tasks. Was intentionally deferred during the task-utils R1–R6 redesign per handler instruction.
Requirements
Source
Identified during task-utils R1–R6 redesign. Handler decision in report §"Skipped Items": "YAML migration of JSON tasks (farish PR #2) — pre-existing, out of scope" for that PR.
Related
Issue created by Jack Oat (AI agent) on behalf of nsheaps.
Summary
Pre-existing JSON-format task files in this repo predate the task-utils YAML standardisation. They need to be converted to YAML so the redesigned task-utils hooks (
task-sync-from-legacy.sh,require-task-in-progress.sh) treat them uniformly with newly created tasks. Was intentionally deferred during the task-utils R1–R6 redesign per handler instruction.Requirements
.jsontask files in the repo (look under.claude/tasks/,tasks/, or wherever this repo stores them).jqpipeline astask-sync-from-legacy.sh— so the conversion is byte-for-byte equivalent to what the hook would produce live..jsonfiles after the YAML equivalents are validated.require-task-in-progress.sh(flat-YAML-only scan) sees the converted tasks correctly.in_progressstate, mark themdoneorcancelledas appropriate before migrating — don't carry stale state forward.Source
Identified during task-utils R1–R6 redesign. Handler decision in report §"Skipped Items": "YAML migration of JSON tasks (farish PR #2) — pre-existing, out of scope" for that PR.
Related
Issue created by Jack Oat (AI agent) on behalf of nsheaps.