Skip to main content

tasks-toolkit

A small, self-contained task tracker (sprints → tasks → subtasks) with a CLI and an MCP server.

Contents

  • scripts/ — all tracker code (see table below).
  • pyproject.toml — ruff/mypy/pytest configuration.

Installation

pipx install tasks-toolkit
# or: uv tool install tasks-toolkit
tasks-init
tasks overview

From source

git clone https://github.com/prachwal/tasks-toolkit.git
cd tasks-toolkit
python -m pip install -e .
tasks-init
tasks overview

Docker

docker build -t tasks-toolkit .
docker run --rm -i -v tasks-data:/data tasks-toolkit

Quick start (from source)

python3 scripts/tasks_init.py          # create tasks/tasks.db
python3 scripts/tasks.py overview      # show sprints
python3 scripts/tasks.py next          # next ready task

Data belongs to the current Git project (the main checkout when invoked from a worktree). Outside Git, it belongs to the current directory. Installed commands never use their installation directory for data. Override the location with TASKS_ROOT:

export TASKS_ROOT=/path/to/data
python3 scripts/tasks.py overview

MCP (OpenCode)

"tasks": {
  "type": "local",
  "command": ["python3", "{env:HOME}/src/tasks-toolkit/scripts/tasks_mcp.py"],
  "cwd": "{env:HOME}/src/tasks-toolkit",
  "environment": { "TASKS_ROOT": "{env:HOME}/src/tasks-toolkit" }
}

Verified task and sprint execution

Copy .tasks-toolkit.example.json to .tasks-toolkit.json, choose the checks for your project, and commit the configuration. Commands are argument arrays; no shell interpolation is performed. Every configured check must pass. Keep tmp/ and generated tasks/ files in .gitignore, as in this repository.

The default coder uses Codex non-interactive mode: codex exec --sandbox workspace-write -. Install and authenticate its CLI separately. To use Junie or Kilo, set runners.junie or runners.kilo to the argument array for your local adapter. Adapters receive the spec on stdin, edit files in their current working directory, leave changes uncommitted, and return nonzero on failure. The same runners.codex setting can select a custom Codex adapter.

Installed commands are tasks-run and tasks-sprint; from source, the corresponding wrappers are scripts/run-task.sh and scripts/sprint-auto.sh.

Run one task in a clean working tree, with an explicit allowed scope:

tasks-run result \
  --file tmp/tasks/result.md --scope src/ --runner codex

Alternatively, --task-id 1.1 reads scope links from the tracker. The runner checks all actual tracked changes, deletions and untracked files, runs the configured checks and commits only verified changes. Input flags such as checks_green and tracker_done are never evidence. Failures preserve the working tree and write a report to tmp/runs/<name>.result.json. Exit codes: 0 verified, 1 rejected, 3 runner/configuration failure. Optional fallback runs only after a runner failure that left the working tree clean.

For a complete sprint, supply a plan containing sprint (slug, title, goal) and tasks (key, title, scope, spec_name, spec, depends_on). Specs must pass scripts/spec-lint.sh; dependencies reference earlier task keys. An answers file binds the reviewed goal, allowed paths and execution policy:

{
  "goal_reviewed": true,
  "allowed_scopes": ["src/"],
  "policy": {
    "runner": "codex", "serial": true, "fallback": "none", "retries": 0,
    "push": false, "accept_flags": false, "reset": false, "clean": false
  }
}

Start from a clean main branch:

tasks-sprint --yolo-force \
  --goal "Implement the feature" --run-name feature \
  --answers tmp/plans/feature.answers.json --plan tmp/plans/feature.json

The lifecycle imports the plan, creates a sprint branch and worktree, executes tasks serially, checks the diff against task and approved scopes, and records verified commits in the tracker. Final checks precede a fast-forward into the unchanged approved main; no push is performed. Worktrees and checkpoints remain available for inspection.

Use the same command with --resume to continue a clean checkpoint. Goal, answers, plan, configuration and Git refs must still match. A dirty or unexpectedly advanced worktree requires inspection; it is never reset, cleaned or blindly rerun.

Development checks

python3 -m pip install -e '.[dev]'
bash scripts/test_python_lint.sh
python3 -m pytest -q
bash scripts/test_spec_lint.sh

CI requires lint, type checking, all Python tests, shell tests and distribution builds to pass. VS Code tracker commands are provided in .vscode/tasks.json.

Scripts

Core tracker

File Purpose
tasks.py Task tracker CLI: sprints → tasks → subtasks, SQLite-backed (tasks/tasks.db).
tasks_init.py Create an empty task database from scratch.
tasks_mcp.py MCP server (stdio) exposing tracker operations as tools.
tasks_cli.py CLI parser and entry point for the tracker.
tasks_commands.py Command handlers for the tracker.
tasks_model.py Core data model (nodes, statuses, walk/find/effective).
tasks_storage.py SQLite storage layer.
tasks_render.py Markdown rendering of the task view.
tasks_watch.py Background watcher keeping the view and snapshot in sync with the DB.
tasks_plan_import.py Atomic plan import for the sprint planner.

Sprint automation

File Purpose
sprint_plan.py Sprint plan tooling for the planner agent.
sprint-auto.sh / sprint_auto.py Verified sprint execution and fast-forward integration (--yolo-force, --resume).
sprint_auto_state.py Durable state, checkpoint and process-supervision primitives.
sprint_auto_preflight.py Read-only approval preflight for the automated lifecycle.
sprint_auto_prepare.py Prepare approved plans and branches.
sprint_auto_execute.py Execute and accept guarded tasks.
sprint_auto_resume.py Resume and finish owned sprints.
apply-plan.sh Import a validated sprint plan (tmp/plans/<name>.json) into the tracker.
run-task.sh / task_runner.py Run configured coders and verify actual changes before committing.
task-report.sh Report delegation progress to the tracker.
run_summary.py Write a run summary JSON for finished runs.
run_stats.py Delivery-speed statistics for delegation runners.

Spec / quality

File Purpose
spec-lint.sh Quality gate for delegated task specs.

Tests

File Purpose
test_tasks.py Tests for tasks.py.
test_tasks_mcp.py Tests for tasks_mcp.py.
test_tasks_storage.py Tests for tasks_storage.py.
test_tasks_plan_import.py Tests for tasks_plan_import.py.
test_tasks_watch.py Tests for tasks_watch.py.
test_run_stats.py Tests for run_stats.py.
test_sprint_auto.py Tests for sprint-auto.sh.
test_sprint_auto_state.py Tests for sprint_auto_state.py.
test_sprint_auto_preflight.py Tests for sprint_auto_preflight.py.
test_sprint_auto_prepare.py Tests for sprint_auto_prepare.py.
test_sprint_auto_execute.py Tests for sprint_auto_execute.py.
test_sprint_auto_resume.py Tests for sprint_auto_resume.py.
test_spec_lint.sh Tests for spec-lint.sh.

Test runners

File Purpose
test_python_fast.sh Fast Python tests (in-process).
test_python_slow.sh Slow/subprocess-heavy Python tests.
test_python_lint.sh Ruff + mypy.

License

MIT — see LICENSE.

Metadata

Release files for tasks-toolkit 0.1.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tasks-toolkit 0.1.4
File Size Uploaded
tasks_toolkit-0.1.4.tar.gz 98.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for tasks-toolkit 0.1.4
File Interpreter ABI Platform
tasks_toolkit-0.1.4-py3-none-any.whl Python 3 none any Details

Total release size: 216.6 kB

Release files / tasks_toolkit-0.1.4.tar.gz

Download URL tasks_toolkit-0.1.4.tar.gz
Size 98.6 kB
Tags Source
SHA-256 checksum
How to use checksums
bdef9b81fa23f75f064491516f61a27de548eb75e13fbd50e0e6c00d37099c25
BLAKE2b-256 checksum
How to use checksums
4bb74c0c585ec481734dc4c21c2b3b3b3aea74c7df984f69c3b2d0a285cee57d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / tasks_toolkit-0.1.4-py3-none-any.whl

Download URL tasks_toolkit-0.1.4-py3-none-any.whl
Size 118.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a90d442f016cb92ee8f49ff112be2bd669a273b29720c5f9bd110e1f175b3741
BLAKE2b-256 checksum
How to use checksums
1a33b64b877f21517bbf23577d2ebefd684cc7e8d897790f1aae54339af66733
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release history Release notifications | RSS feed

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

This release

0.1.4 This release

2 release files

0.1.3

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page