Weft

weft

Deterministic workflow tracking for Claude Code — smart skills, template management, dashboard auto-refresh.

Weft turns ad-hoc agent sessions into auditable, event-sourced workflows. Define a template (plan → implement → verify, or an 11-step ticket-to-PR cycle), and weft enforces the order, blocks tools that violate the current step's guards, and refuses to let you Stop with steps still pending.

Why this exists

Multi-step engineering work needs structure that survives compaction, retries, and the agent forgetting what step it's on. Weft solves three problems:

- Skills fire reliably — /wf-start, /wf-step, /wf-status read state from disk, not memory.
- Templates apply consistently — workflows live in JSON, version-controlled with your project.
- Hooks enforce the contract — PreToolUse, PreCompact, and Stop block out-of-order actions or premature exits.

State is an append-only event log under .claude/weft/, so every workflow is fully reconstructible.

Why not just use TODOs or Claude's task list?

Built-in TODOs and ad-hoc checklists live in the agent's context window. They're advisory — the model can ignore them, lose them across compaction, or skip steps it judges unnecessary. They have no enforcement, no replay, no per-step guards. Weft is the opposite tradeoff: a small contract written to disk, enforced by hooks, with an event log you can audit after the fact. Use TODOs when "the model probably remembers" is good enough. Use weft when it isn't.

Requirements

- Python 3.10+ (stdlib only — no runtime dependencies)
- Claude Code with plugin support
- macOS or Linux (the dashboard uses curses; Windows is untested)

Quick Start

Weft ships as a Claude Code plugin. Install via the marketplace:

Or, for development / hacking on weft itself:

The plugin…