Documentation

A project plan agents can continue.

Ajiya is a CLI task manager for coding agents. It stores project structure, ticket state, dependencies and completion evidence in your repository, so work can continue across agent sessions.

Early developmentAjiya is not yet ready for general use. The CLI is being built; the local dashboard and ajiya serve are still in development. Check the roadmap before relying on a planned feature.

Getting started

Build the CLI from the source repository with Go. Run commands from the root of the project you want to manage.

go build -o ajiya ./cmd/ajiya
./ajiya init --name "Learning Platform" --prefix LP

init creates ajiya.toml and the ajiya/ project-data directory. Use --yes to accept detected defaults when setting up non-interactively. No packaged installer is available yet.

Existing checkoutCommit or back up your project before trying an early development build. Ajiya writes project planning files in the repository.

Project concepts

Project: The repository and its ajiya.toml configuration.
App: A named part of the codebase, such as api or web. Shared libraries can be registered too.
Phase: A project outcome or body of work. A phase is stored as a Markdown file under ajiya/.
Ticket: A task with an app, completion condition, status and optional dependencies or human-review reason.
Dependency: A ticket that must be completed before another ticket is ready.
Milestone: A named release target that groups related work. Launch work is tracked separately as a dependency-aware target.

Use stable ticket IDs in agent handoffs and commit messages. The configured prefix is followed by a numeric ID, for example LP-0042.

Agent workflow

Keep each session small: inspect the plan, select a ready ticket, update its status, do the work, then record the commit and completion evidence.

ajiya next
ajiya ticket start LP-0007
# make the change
git add .
git commit -m "Add course catalog endpoint" -m "Ajiya: LP-0007"
ajiya ticket done LP-0007 --test

ajiya next reports work that can start, with options to filter by app or focus on launch/milestone work. A ticket may also be marked blocked or dropped, or its details edited. Use ajiya ticket show LP-0007 to inspect its requirements.

Across sessionsBecause the plan is stored in the repo, the next agent session can inspect the same ticket state and dependencies using the CLI. Commit or share the project data with the repository to make that handoff available to another checkout.

Launch work and milestones

Set a launch target when you want next and project checks to focus on the work needed for a release. Ajiya follows ticket dependencies so prerequisite work is included.

ajiya launch set LP-0009
ajiya launch show
ajiya next --launch

Milestones let you group and order release work:

ajiya milestone add "Beta" --targets tickets
ajiya milestone list
ajiya milestone show "Beta"

Milestone commands also support moving and removing milestones. Check ajiya milestone --help for the exact flags supported by your build.

Checks and completion evidence

Ajiya uses Git commits as evidence for completed tickets. Commit messages should include one to three ticket references, commonly in a trailer such as Ajiya: LP-0007. Git hooks can check commit messages; ajiya check checks project consistency and evidence.

ajiya check
ajiya check --strict
ajiya check --commits HEAD~5..HEAD
ajiya hooks install

Where a project has a test command configured, ajiya ticket done ID --test runs it before marking the ticket done. A failed command prevents completion. Merge commits, reverts and the documented chore form are treated specially by commit checks.

Import existing work

Importers are available for TODO lists, GitHub issues and the legacy collate.py format. Review imported tickets and organize them into phases, apps and dependencies before using them as an execution plan.

ajiya import todo
ajiya import github
ajiya import legacy

The GitHub importer uses the GitHub CLI (gh) and the authentication available to it. The legacy WBS mapping is still being refined for v0.1, so verify the result before relying on it.

Command reference

Run ajiya --help or a command's --help for the flags supported by your installed build.

Command	Purpose
`ajiya init`	Set up project configuration and planning files.
`ajiya app add\|move\|remove`	Register or change project apps and libraries.
`ajiya phase add\|rename\|move\|list`	Create and organize phases.
`ajiya phase order --suggest\|--apply`	Review or apply a suggested phase ordering.
`ajiya ticket add`	Create a ticket with a phase, app and completion condition.
`ajiya ticket start\|done\|block\|drop`	Change ticket status.
`ajiya ticket show\|edit`	Inspect or edit a ticket.
`ajiya next`	Find ready work, optionally filtered by app, launch or milestone.
`ajiya launch set\|show`	Set or inspect the launch target.
`ajiya milestone add\|list\|show\|move\|remove`	Manage release milestones.
`ajiya import todo\|github\|legacy`	Import existing task sources.
`ajiya changelog`	Generate a changelog from project work.
`ajiya build`	Generate `ajiya/PROGRESS.md` and `ajiya/data.js`.
`ajiya check`	Check project data, dependencies, evidence and commits.
`ajiya hooks install\|run`	Install or run repository commit hooks.
`ajiya version`	Print the CLI version.

For ticket creation, provide --phase, --app and --done-when. Optional flags include --depends and --human.

Project files and data

ajiya.toml stores project configuration, app paths and launch settings.
ajiya/*.md stores the phase plans and ticket records.
ajiya/PROGRESS.md and ajiya/data.js are generated by ajiya build.

Ajiya is a local CLI and does not provide its own hosted account or AI model. Agents run separately. Some integrations can use their own network access; for example, GitHub import runs through gh.

Roadmap and availability

These are roadmap items, not available CLI commands. The roadmap can change as implementation progresses.

v0.1 · in progress

Finish the first usable workflow

Complete the local dashboard and server, improve legacy WBS import mapping, then sign off the release.

v0.2 · planned

Connect agents and simplify setup

Add status output, an MCP server with structured tools and agent registration, installation channels, and a Claude Code plugin.

v0.3 · planned

Track decisions and change impact

Add optional tags, changed-file reporting, decision records, superseded history and a change-request workflow with human approval.

The dashboard is part of the product direction, but it is not a macOS app. Ajiya is CLI-only at this stage; ajiya serve is still in development.