That's a great idea. This works as an on-add script that does the right thing: ```

!/usr/bin/env python3

import sys import json import os

def main(): data = sys.stdin.read().strip()

decoder = json.JSONDecoder()

new_task, offset = decoder.raw_decode(data)

# debug logging
with open('log', 'w') as f:
    print(data, file=f)
    print(sys.argv, file=f)
    print(json.dumps(new_task), file=f)


if 'blocks' not in new_task:
    with open('log', 'a') as f:
        print("No `blocks` UDA found", file=f)
    # print out the task as we received it
    print(json.dumps(new_task))
    sys.exit(0)

blocked_task = new_task['blocks']
with open('log', 'a') as f:
    print(f"blocks task {blocked_task}", file=f)

new_task_id = new_task['uuid']
del new_task['blocks']
# output the new task without the `blocks` UDA
print(json.dumps(new_task))

os.system(f"task {blocked_task} mod depends:{new_task_id}")

sys.exit(0)

if name == "main": main() ```

I'm a little surprised it works, since the Taskwarrior docs say that on-add hooks are executed after the new task is processed but before it's saved. So I worry that it might be unreliable, or work inconsistently across different systems, and instead the hook might need to spawn a child process that waits for the initial invocation of taskwarrior to exit before running the task {blocked_task} mod depends:{new_task_id} command.

But for now, this is working for me. Thanks for the suggestion!