Ank CLI
A CLI that keeps tasks and architecture decisions in the repo so any coding agent can read them and take work.
- 93 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Writes and changes task and decision files in `.ank/` and runs declared verifiers with `ank done`
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/ankDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Writes and changes task and decision files in `.ank/` and runs declared verifiers with `ank done`
This is third-party code. Review the repository files before installing.
What it does
Ank keeps decisions and tasks in the `.ank/` folder next to the code they constrain and serves them through one CLI. An agent can read every line of code while the tracker, the wiki and the thread where it was decided that sessions must never be self-contained JWTs stay out of reach. Ank makes such decisions available in the working loop. The loop is made of commands: `ank context <path>` shows what binds the perimeter and what is takeable, `ank claim <id>` takes a task and freezes its criterion, `ank show <id>` prints the entity whole, `ank log` records what was learned along the way, `ank done` runs the declared verifiers and records the proof and `ank release` hands the task back. The file format and exit codes are specified, the version is 0.x and the format may change before 1.0 through a new `schema` value.
Who it is for. Teams and solo developers who work with agents and want to keep decisions and tasks in the repository next to code.
Good fit when
- An architecture decision must not get lost: the agent has to see the constraint before editing the code it covers.
- Agents need a shared task queue in the repository with an acceptance criterion frozen at claim time.
- Task verifiers should run with `ank done` and leave proof.
- You want to hand a task back with a reason through `ank release --reason`.
Not a fit when
- You need a tracker with sprints, estimates and a roadmap: Ank deliberately has none.
- You need a wiki for general knowledge: only what binds or requires an agent goes here.
- You need a security boundary: the tool guards against drift and will not stop an attacker.
Example request
Show ank context for the auth folder and take an available task with its acceptance criterion.Limitations
Version 0.x: the author reserves the right to change the file format before 1.0, a change arrives as a new `schema` value. Git 2.34 or newer is required, platforms are Linux, macOS and Windows. The binary is installed with `npm install -g @haksolot/ank` and the skills separately with `npx skills add haksolot/ank`. Ank is no tracker, wiki or security boundary: it guards against drift between decisions and code and offers no protection from malicious edits. The license is Apache-2.0. Start with the quickstart, which walks the loop from `ank init`.
How to disable. Uninstall the package with `npm uninstall -g @haksolot/ank` and the skills from the agent directory. The `.ank/` folder stays in the repository as ordinary Markdown files.
FAQ
Which commands make up the loop?
`ank context`, `ank claim`, `ank show`, `ank log`, `ank done` and `ank release`.
Where is the data stored?
In the repository `.ank/` folder, including an entity archive in `.ank/archive/entities/`. They are ordinary files under git.
What does Ank not replace?
A tracker, wiki or security boundary. It holds only what binds an agent or requires action.
What does `ank done` do?
Runs the verifiers declared for the task and records proof of their result.
How do I install it?
`npm install -g @haksolot/ank` for the binary and `npx skills add haksolot/ank` for the agent skills. Git 2.34 or newer is needed.
Discussion
No questions or reviews yet.
Related
CLI toolsTasks, docs, specs and decisions live as markdown files in your repository, and the agent reads them through the CLI and MCP
Work modes for AI coding agents: a light solo mode for daily tasks and /man with a plan, checks and review for big changes
Git-native project context for agents: specs, decisions and rules live in Markdown beside the code and are read before edits
A desktop board turns a card into an agent session in its own git worktree, flags the agent waiting on you, offers an MCP server
A CLI records coding agent sessions locally, replays what happened and shows what the trace could not prove.
Kanban from Cline launches a local web board where each card gets its own terminal and git worktree for a CLI agent.
README in short
The README explains the idea of keeping decisions next to code, shows installation, the command loop and what the tool is not. The format spec and docs are linked separately.