Forge

A lightweight development framework and state machine for hands-off development runs built around loops.

star us on github

What Forge is

Forge is a lightweight development framework and state machine for hands-off development runs built around loops. It runs inside Claude Code, Codex CLI, Cursor, or Gemini CLI as skills backed by that state machine.

Give it an idea. Forge turns it into a spec and a dependency graph in Linear, GitHub Issues, or Notion, then moves each task through plan → build → test → review → ship. The tracker stays the source of truth. The agent is the worker.

Capabilities

Tracker becomes state

Forge connects to Linear, GitHub Issues, or Notion and turns the tracker into a state machine. Status, dependencies, and blockers stay where your team already works.

Parallel without collisions

Worktree-per-task isolation, overlap classification, and dependency-aware dispatch keep concurrent agents off each other's files. Run multiple issues without worrying about collisions.

Autonomous delivery

Hands-off runs move tasks from plan to shipped or parked. Approval, testing, and review gates still apply.

Independent review

The model that wrote the code does not review it. Approved plans, passing tests, and a second model's verdict gate the merge.

How it works

  1. Shape the idea. Forge turns the discovery interview into a brief, PRD, spec, and optional design document.
  2. Build the graph. It decomposes the work into dependency-aware tasks and pushes them to Linear, GitHub Issues, or Notion.
  3. Run the task. Forge claims ready work, creates an isolated worktree, and moves it through plan → build → test → review → ship.
  4. Recover or reconcile. Expiring leases recover abandoned tasks, while reconciliation keeps local state and the tracker aligned.

Start your first hands-off run.

star us on github
forge — rough ideas become shipped products. ep.02, forging.