GitDocket docs

A small first run.

Install Docket, connect your coding agent, and try one scoped epic in a scratch repository.

1. Install & initialize

Requires Git and Bun 1.3.14 or newer on macOS or Linux. Published CLI and MCP packages are version 0.2.1.

bun add --global @gitdocket/cli @gitdocket/mcp
docket --version
mkdir docket-playground
cd docket-playground
git init
docket init --agent codex

Use --agent claude for Claude Code, or omit the agent flag for portable AGENTS.md guidance. Init adds a docket/ Markdown bundle and project configuration. Review and commit the generated files.

2. Give your agent a small outcome

Open the initialized repository in your coding agent and ask:

Create a “Welcome guide” epic with two dependent tasks: write a short contributor guide, then link it from README. Give each task concrete acceptance criteria. Run that epic through completion, verify the guide and links, and reconcile the docs.

The workflow runs in your agent session with its available tools and permissions. It completes the work and reports its checks, or identifies a concrete blocker and what is needed to resume.

3. Inspect the result

docket task list --all
docket ready
docket serve

Open the local URL printed by docket serve. For a successful run, check that the epic and both tasks are done, criteria are checked, and their Outcomes explain verification. Review the Git changes and open the README’s guide link.

In a later session, ask “Where did we leave off?” The agent can recover context from the repository. Authored re-entry notes may need refreshing; current readiness comes from Docket.