fabrik-setup

Guides first-time installation and initialization of the Fabrik GitHub Project board orchestrator.

22|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/handarbeit/fabrik --skill fabrik-setup-handarbeit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fabrik-setup
Source: https://github.com/handarbeit/fabrik/tree/main/plugin/fabrik/skills/fabrik-setup
Command: npx skills add https://github.com/handarbeit/fabrik --skill fabrik-setup-handarbeit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up Fabrik — the GitHub-Project-driven SDLC pipeline that drives Claude Code workers through Specify/Research/Plan/Implement/Review/Validate stages — involves several failure-prone steps: choosing a compatible GitHub token, creating a Project v2 board with exactly matching column names, and configuring secrets safely. This Skill walks users through the entire bootstrap process so nothing is missed. ## Core Features & Use Cases - Prerequisite verification: Checks Claude Code CLI, gh CLI authentication, Go version, and GitHub token compatibility (classic PAT or gh OAuth token; fine-grained tokens do not work with Projects v2 GraphQL). - Guided installation and init: Walks through release-binary download or source build, then fabrik init — including --create-board to generate a correctly columned Project board automatically. - Board validation and first run: Ensures all nine stage columns (Backlog through Done, including the easily missed Queued) match stage YAML names exactly, configures a gitignored .env, and covers the safe first run. - Use Case: A user asks "how do I get started with Fabrik" in a repo with no .fabrik/ directory; the Skill confirms prerequisites, helps them install the binary, runs fabrik init --create-board, sets up the token, and verifies the board before the first poll. ## Quick Start Ask the assistant to help you install and set up Fabrik in this project for the first time.

Frequently Asked Questions about fabrik-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install and set up Fabrik for the first time?

Download the release binary with gh release download or build from source with Go 1.26.1+, then run fabrik init from your project checkout. Use fabrik init --create-board --owner <org> --repo <repo> to also create a correctly columned Project board automatically.

What GitHub token does Fabrik need for Projects v2?

Fabrik needs a classic PAT (ghp_...) or a gh CLI OAuth token (gho_...) with repo, project, and workflow scopes. Fine-grained tokens (github_pat_...) do not work with GitHub Projects v2 GraphQL. The shortest path is FABRIK_TOKEN=$(gh auth token).

Why does Fabrik fail with NOT_FOUND: Could not resolve to a ProjectV2?

This usually means the token belongs to a different GitHub account than the one owning the Project board, not a wrong project number. Verify identity with gh api graphql -f query='{ viewer { login } }' and confirm it matches the user in config.yaml.

What columns does the Fabrik Project board need?

The board needs nine status columns matching stage YAML names exactly and case-sensitively: Backlog, Specify, Research, Plan, Implement, Review, Validate, Queued, and Done. Missing columns cause startup validation failure; run fabrik repair-board --apply to add them.

Why does Fabrik refuse to start with a .env file present?

When a .git directory exists, Fabrik refuses to start unless .env is listed in .gitignore. This is a deliberate token-leak guard, not a bug — add .env to .gitignore and commit the change.

When should I not use the Fabrik setup skill?

Skip setup if a .fabrik directory already exists — Fabrik is already initialized and you want the supervisor skill instead. For re-initialization or upgrades, use fabrik upgrade rather than re-running fabrik init.