I wanted a task tracker that doesn’t require a server, account, or internet connection. Something that stores tasks as plain YAML files right in the project directory, versioned alongside code. So I built tsk . tsk init --defaults tsk add “Build auth module” -p p1 -t backend,security tsk add “Write API docs” --milestone 1 tsk move 1 in_progress tsk list --group Tasks are stored in .tsk/tasks/ as individual YAML files — one per task. You can grep them, commit them, diff them, pipe them. What it does 13 commands: add, view, list, move, edit, note, log, archive, rm, summary, milestone, web Milestones for grouping tasks into releases Subtasks via --parent Activity log on every task (append-only, tracks all changes) –by flag on mutations for attribution (“who did this?”) tsk web launches a local kanban board with auto-refresh Priorities (p0–p3), tags, custom status workflows Pretty output for terminals, JSON for pipes — auto-detected What it doesn’t do No cloud sync, no accounts, no subscriptions No database — just YAML files in a .tsk/ folder No Electron app The core layer has zero stdout calls, so it can be wrapped by other tools (working on an MCP server next). MIT licensed, zero heavy dependencies (just commander + yaml + chalk). GitHub: https://github.com/tskrun/tskrun Website: https://tsk.run/ Would love feedback — especially on whether the YAML-file-per-task approach works for your workflow vs a single file. submitted by /u/vikasprogrammer
Originally posted by u/vikasprogrammer on r/ClaudeCode
You must log in or # to comment.