Taskroot
Taskroot keeps project work in structured Markdown files under .tasks/. The
files stay readable, reviewable in Git, and available to both people and coding
agents without a hosted issue tracker.
Taskroot provides:
- project-local domains and task identities
- configurable prefixes, task types, and tags
- task dependencies, milestones, and acceptance criteria
- lifecycle commands for ready, active, blocked, and completed work
- human-readable and JSON output
- a Rust library for applications that need the same task contract
Install
Install the command from crates.io:
Start a task project
Run init at the root of any project:
This creates .tasks/config.json. Domain directories are created when you add
their first task.
Commands discover the nearest ancestor containing .tasks/. Use --root to
operate on another project explicitly:
Use the library
Library callers open an explicit task project. Discovery remains optional so a long-lived process can work with several projects safely.
use ;
let root = discover_project_root?;
let project = open?;
println!;
# Ok::
See the task tracking guide for the configuration format and command reference.
Migrate from filer-task
Taskroot retains the .tasks/ project format. Replace the old executable and
continue using the same task files:
Rust consumers should rename the dependency and imports from filer_task to
taskroot.
License
Taskroot is available under the MIT License.