fabrik-setuplisted

# Bootstrapping Fabrik This skill guides a user through installing Fabrik and standing it up for the first time in their project. Don't run any of these steps yourself unsolicited — walk the user through them, confirm their environment, and let them execute. Authoritative docs live at https://fabrik.handarbeit.io — link the user there rather than reproducing details that may drift. ## Before you start Confirm the user has — or help them obtain — each of these. Don't proceed past step 0 until prerequisites are in place. 1. **Claude Code CLI installed and authenticated.** They almost certainly have this if they're talking to you, but check with `claude --version` if uncertain. 2. **A GitHub repo and a GitHub Project (v2) board.** The board is non-optional — Fabrik *is* a board orchestrator. `fabrik init --create-board --owner <org> --repo <repo>` (organization-owned repos) creates one directly from the stage configs, with columns guaranteed to match — prefer this over hand-building one in GitHub's UI. See Step 4. 3. **A GitHub token with `repo`, `project`, and `workflow` scopes.** The real constraint is narrower than "classic only": fine-grained tokens (`github_pat_...`) don't work with GitHub Projects v2 GraphQL, but both classic PATs (`ghp_...`) and `gh` CLI OAuth tokens (`gho_...`) do. Since `gh auth login` is already a prerequisite (next item), the shortest path is usually: ```bash FABRIK_TOKEN=$(gh auth token) ``` Note this value rotates whenever the user r