Loaf — Development skill for Claude Code

🍞 Loaf

"Why have just a slice when you can get the whole loaf?"

Loaf brings shared skills, a native Go CLI, and tracker-native workflows to Claude Code, OpenCode, Cursor, Codex, and Amp. Skills guide judgment, the CLI handles deterministic checks and private continuity, and your tracker owns shared work.

This README describes the current source tree. Until its next release is published, installation from GitHub Releases or Homebrew may provide an earlier version; see the [published releases](https://github.com/levifig/loaf/releases) and [unreleased changes](CHANGELOG.md#unreleased).

Why Loaf?

**Portable knowledge** — Skills cover workflows, engineering standards, and language expertise. Build once, deploy to supported AI coding tools without rewriting anything.

**Private continuity** — A project-scoped SQLite journal records decisions, discoveries, and optional wrap summaries across conversations and worktrees. There is no session entity to open or close. Startup context is derived from the journal and Git; useful resumption depends on recording meaningful context, not retaining a second work queue.

**Tracker-native workflow** — Pitch → shape → implement → ship → release keeps discovery, selected work, review, and publication distinct. GitHub and Linear provider skills use connections already available in your harness; Loaf never synchronizes a parallel local issue database, and does not configure their credentials. On GitHub, the selected board's Status distinguishes noncommittal Backlog from selected Todo work.

**Profile-based agents** — Functional profiles are defined by tool access, not job titles. A Smith with `python-development` skills becomes a backend engineer; the same Smith with `infrastructure-management` becomes a DevOps engineer. Skills determine what an agent knows; the profile determines what it can touch.

**Living architecture** — Keep current design and rationale in topic-based `docs/architecture/` documents. Architecture and Refle