From TFA, emphasis mine:

What veans is for#

Coding agents keep their own to-do lists. Claude Code has TodoWrite, other tools have their own scratch files, and either way that list lives inside a single session and disappears when the session ends. You can’t see it while the agent is working, your teammates can’t see it at all, and nothing survives to the next session.

veans replaces that ephemeral list with real tasks in a Vikunja project. The agent claims a task before it starts, moves it along as it works, and leaves it in review when it’s done. The result is that the agent’s work is visible in the same place you already track everything else: you can watch a task move across the board in real time, comment on it, reprioritize it, or pick up where the agent left off. When the session ends, the trail is still there.

veans itself is built for machines, not people . Everything prints JSON, so it’s made to be consumed by an agent or a script. The human side of the workflow happens in Vikunja.

What Taskwarrior lets you do is something like this for people:

task add priority:high due:thursday depends:32 something I need to do
task ready   # shows all of my tasks that aren't waiting on something or depending on something
task project:home-repairs export > home-repairs.json # export my entire home repair project to a json file to process into a gantt chart, budget (since I can add a price tag to each task) and whatever else

but then I can also have a script that looks like:

# add-tasks.sh
infile="$1"
proj ="$2"

while IFS= read -r line; do
    [ -z "$line" ] && continue
    [[ "$line" =~ ^[[:space:]]*# ]] && continue
    echo "Adding task: $line"
    if [ -n "$proj" ]; then
        task add "$line" "$proj"
    else
        task add "$line"
    fi
done < "$input_file"

which lets me have preset task lists for various things, like:

add-tasks.sh ~/tasks/packing-list.txt proj:work-trip
add-tasks.sh ~/tasks/xmas-list.txt proj:xmas-presents