For humans and coding agents

Pick up with
less re-explanation.

Keep project docs, tasks, and working instructions together in your repository. Your coding agent can use what the last change taught the project, while you review what changed, why, and what was checked.

Install both commands with Homebrew. No separate Bun, Node or npm setup.

brew install gitdocket/tap/gitdocket

Supported platforms and npm alternative · 0.4.1

Local-first · Plain Markdown · Reviewed through Git

Pick up where you left off

The project, in context.

See what changed, what matters, and what’s ready next. The interface reads the same files your agent works with.

Current GitDocket Home: Home and Board lead the navigation; a project re-entry note summarizes the completed Harbor guide, and a compact board shows feedback ready next.
Current development UI · Synthetic Harbor project · View full size
Explore the current Board view
Current Harbor Board with one todo task, two done tasks, collapsed empty columns, and filtering controls.
Filter the work and collapse empty columns to keep the next step visible.

A repeatable loop

Finish the work. Keep the knowledge.

“Track and complete one small contributor-guide change.”

  1. 01

    Read & choose

    Read the project docs and choose one useful change. A task records the intended result and checks.

  2. 02

    Build & verify

    Make the change and check it against the task’s acceptance criteria.

  3. 03

    Record & reuse

    Update affected docs and record the checks. In the next session, use that knowledge to guide another change.

For example, a contributor-guide task records an offline-link decision. The next session uses it to plan a troubleshooting guide with relative links. Docket records task state and calculates what is ready. Your coding agent is responsible for checking changes and updating affected docs, following editable workflows, then reporting evidence or a blocker. Review the result: status alone does not prove the work is correct.

See one task help the next session

Workflow extensions · 0.4.1 preview

Make your process part of the project.

Give your coding agent a repeatable path from request to reviewed delivery. Adapt the reviews and checks to your team, and keep the decisions available for the next change—all in Git.

  1. Request
  2. Reviewed proposal
  3. Verified feature
  4. Retained decision
  5. Next plan

Reuse your process. Work with tools already connected to your agent. Retain what the project learns.

Explore your team's workflow

Extensions are included in 0.4.1. See the Beacon example or start with one task.

An open foundation

Your knowledge stays yours.

Run Docket locally with your own coding agent. Start with docs and one task; add epics or specs when useful. Built on Open Knowledge Format v0.1, introduced by Google Cloud. Linked Markdown holds the context; Docket adds tasks, dependencies, agent workflows, and evidence.

Read and edit the Markdown in your editor. Supplied workflows can be customized and merged during upgrades. Optional project standards and the shared browser editor are included in 0.3.0. The 0.4.1 preview includes reusable workflow packages.

Start with one task