Metadata-Version: 2.4
Name: drift-tasks
Version: 0.1.0
Summary: Keep Claude planning conversations in sync with your codebase
Author: Vineet
License-Expression: MIT
Project-URL: Homepage, https://github.com/vineet16/drift-tasks
Project-URL: Repository, https://github.com/vineet16/drift-tasks
Keywords: claude,cli,task-tracking,developer-tools,ai
Classifier: Development Status :: 3 - Alpha
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Topic :: Software Development :: Build Tools
Requires-Python: >=3.10
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: typer>=0.9.0
Requires-Dist: openai>=1.0.0
Requires-Dist: gitpython>=3.1.0
Requires-Dist: tomli>=2.0.0; python_version < "3.11"
Requires-Dist: rich>=13.0.0
Dynamic: license-file

# Drift

**Keep Claude planning conversations in sync with your codebase.**

Drift is a CLI tool for solo devs who plan with Claude and build with Claude Code. It closes the gap between "what we decided" and "what exists in the repo."

## Install

```bash
pip install drift-tasks
```

## Commands

- `drift import` — Extract tasks from Claude Code session logs or pasted text into `TODO.md`
- `drift check` — Detect which tasks are likely done based on your repo
- `drift next` — Get the single most logical next action
- `drift focus` — Daily entry point: where you left off + what's next
- `drift done <id>` — Mark tasks done manually
- `drift skip <id>` — Move a task to Skipped
- `drift sharpen <id>` — Turn a vague task into an actionable one

## Workflow

1. **Plan in Claude chat.** Have your design conversation as usual.
2. **Ask for a summary** at the end of the planning session.
3. **`drift import --paste`** — paste the summary, Drift extracts tasks into `TODO.md`.
4. **Build in Claude Code.** `TODO.md` at the repo root is picked up automatically.
5. **`drift focus`** at the start of each session. No re-reading old conversations.
6. **`drift check`** periodically to reconcile progress against the repo.

## How it works

- Tasks live in a single `TODO.md` file at your repo root. No database, no config server.
- Each task has 2-3 completion signals — concrete, code-level indicators Drift uses to verify progress.
- Drift never auto-marks tasks done. It proposes, you confirm.
- The file is human-editable. Hand-edits are preserved across runs.

## Requirements

- Python 3.10+
- Anthropic API key (set `ANTHROPIC_API_KEY` in your environment)

## License

MIT
