🏭 Free CLI Tool

Your SDLC,
on autopilot

Fabrik watches your GitHub Project board and drives Claude Code through a full software development pipeline — Specify, Research, Plan, Implement, Review, Validate — automatically. File an issue. Drag a card. Ship.

★ View on GitHub Get Started →

📋 GitHub Project Board source of truth

↓ GraphQL poll

🏭 Fabrik Go CLI, runs locally

↓ stage config match

🤖 Claude Code invoked per stage, isolated worktree

↓ output

💬 GitHub Comments + Labels + PRs durable state

How It Works

Issues in. Code out.

Each issue moves through board columns that map to pipeline stages. Fabrik polls the board, matches the issue's column to a stage config, spins up an isolated git worktree, and invokes Claude Code with the stage's prompt.

Specify

Refines rough issues into clear specs via Q&A

Research

Explores codebase, identifies scope

Plan

Designs approach, breaks into tasks

Implement

Writes code, tests, and commits to branch

Review

Rebases, reviews, and fixes the PR

Validate

Runs tests, verifies requirements

The Fabrik TUI Control Panel

Active jobs, history, cost tracking — live in your terminal

GitHub Project Board with Fabrik pipeline stages

GitHub Project Board in Action

Drag issues across columns to control the pipeline; comment to steer Claude

Features

Everything you need to automate your SDLC

Fabrik gives Claude Code the structure, context, and tooling to work reliably through a full software lifecycle — with you in the loop at every step.

📋

GitHub-Native Pipeline

Board columns define stages and labels define state.

🌿

Isolated Git Worktrees

Every issue gets a dedicated branch and worktree with zero cross-contamination.

💬

Comment-Driven Steering

Comment on any issue mid-stage to redirect the work in progress.

⚡

Yolo Mode & Auto-Merge

Auto-advances through every stage and merges the PR on Validate completion.

🔧

Configurable Stages

Customize each stage's prompt, model, tools, and turn budget in YAML.

👥

Multi-User Safe

Multiple Fabrik instances share one project board without conflicts.

✅

Startup Board Validation

Stage configs are validated against board columns on every startup.

🔄

Self-Upgrade

Detects and installs the latest release automatically at startup and when idle.

🔀

PR Lifecycle Management

Draft PR created at Implement and marked ready to merge at Validate.

🖥️

Terminal UI

Live dashboard shows active jobs, stage progress, token costs, and history.

🗂️

Multi-Repo Support

One Fabrik instance manages issues across every repo on the board.

🧩

Plugin & Skills

Inject custom methodology per stage with plain markdown skill files.

🔗

Formations

Chain issues with GitHub's blocked-by relationships for automatic parallel execution.

👁️

Pending Reviewer Gate

Waits for all requested PR reviewers then re-invokes the stage to address comments.

✅

CI Gate

Blocks merge until CI passes and auto-fixes failing checks each cycle.

🔁

The Self-Evolving Factory

Fabrik is built with Fabrik

Issues filed against this repository go through the same Specify → Research → Plan → Implement → Review → Validate pipeline that Fabrik orchestrates. When we filed an issue to add fabrik watch, Fabrik researched its own log format, designed the per-issue monitoring command, and implemented the live log streaming and CI check UI — building the observatory it now uses to watch itself build features. This page was written by Fabrik too.

The human's role is product manager: file issues, answer clarifying questions, drag cards, and occasionally comment to redirect the work. The factory does the rest.

Quickstart

From zero to pipeline in minutes

Fabrik runs as a local CLI. You need Claude Code, a GitHub token, and either gh CLI or Go.

Prerequisites

For binary install: gh CLI with gh auth login (repo access required). For source build: Go 1.26.1+. Both paths need Claude Code CLI and a GitHub token with repo and project scopes.

Install & initialize

Download a pre-built binary via gh, or clone and build from source. Then run fabrik init to scaffold stage configs into your project.

Configure & run

Edit .fabrik/config.yaml with your project settings, add your token to .env, and run ./fabrik.

File an issue, drag a card

Add an issue to your GitHub Project board. Drag it to the first stage column. Watch the factory run.

terminal

# Option A: Install binary (requires gh)
# Requires: gh auth login with access to handarbeit/fabrik
# Extracts to current directory — cd to ~/bin first, or move binary afterwards
cd ~/bin
gh release download --repo handarbeit/fabrik \
  --pattern "fabrik_*_$(uname -s | tr A-Z a-z)_$(uname -m | sed 's/x86_64/amd64/' | sed 's/aarch64/arm64/').tar.gz" \
  -O - | tar xz
# Platform-specific alternatives:
# darwin/arm64:  --pattern "fabrik_*_darwin_arm64.tar.gz"
# darwin/amd64:  --pattern "fabrik_*_darwin_amd64.tar.gz"
# linux/amd64:   --pattern "fabrik_*_linux_amd64.tar.gz"
# linux/arm64:   --pattern "fabrik_*_linux_arm64.tar.gz"

# Option B: Build from source (requires Go)
git clone https://github.com/handarbeit/fabrik
cd fabrik
go build -o fabrik .

# 2. Initialize your project (pass your GitHub Project URL to skip manual config)
./fabrik init --user you https://github.com/orgs/your-org/projects/5
# Creates .fabrik/stages/, .fabrik/config.yaml
# URL auto-populates owner, project, and owner_type; --user sets your username
# Without a URL: prompts interactively (TTY) or writes a blank template (non-TTY)

# 3. Add your GitHub token
echo 'FABRIK_TOKEN=ghp_...' >> .env
echo '.env' >> .gitignore

# 4. Run
./fabrik

# Optional: yolo mode (auto-advance all stages)
./fabrik --yolo

# Optional: self-upgrade from handarbeit/fabrik GitHub Releases at startup and when idle
./fabrik --auto-upgrade