fabrik

Supervise Fabrik-driven GitHub Project pipelines and advise on issue authoring, labels, and stage failures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Teams running Fabrik (a GitHub-Project-driven SDLC orchestrator that dispatches Claude Code workers through Specify/Research/Plan/Implement/Review/Validate stages) need a way to supervise the pipeline without reading engine internals. This Skill gives Claude ambient awareness of the board, labels, and stage semantics so it can answer PM-style questions and advise on interventions. ## Core Features & Use Cases - Board and issue inspection: Bundled bash scripts (board.sh, issue.sh, comments.sh, stage-output.sh) query the GitHub Project board, issue state, comments, and stage output via the gh CLI, auto-locating .fabrik/config.yaml. - Label-based control guidance: Explains engine-managed labels (fabrik:locked, stage:X:failed) versus user-set control labels (fabrik:yolo, fabrik:cruise, fabrik:paused, model:opus, base:<branch>) so users steer the pipeline correctly. - Issue authoring and dependency wiring: Coaches users to write worker-actionable issue specs and safely wire blocked_by dependencies via the GitHub API before moving issues into Specify. - Use Case: A user asks "why is #42 stuck?" — Claude runs scripts/issue.sh 42, sees stage:plan:failed, reads the worker output via stage-output.sh, and recommends applying fabrik:extend-turns or commenting to redirect. ## Quick Start Ask Claude what's currently on the Fabrik board or why a specific issue number is stuck, and it will inspect the project state and explain what to do next.

Frequently Asked Questions about fabrik

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

FAQPage Schema
How do I check what's on my Fabrik project board?

Run the bundled board.sh script, which lists one line per issue with column, title, and active fabrik/stage/model labels. It hides Done items and stage:*:complete labels by default; pass --all or --column to filter the view.

How do I control a Fabrik pipeline with GitHub labels?

Apply user-set labels to steer the engine: fabrik:paused halts processing, fabrik:yolo auto-advances all stages and auto-merges, fabrik:cruise stops at Validate, and model:opus or effort:high override per-issue model settings. Engine-managed labels like stage:X:failed should not be edited by hand.

Why is my Fabrik issue stuck and not progressing?

Check the issue's labels and column with issue.sh. Common causes are stage:X:failed after max retries, fabrik:awaiting-input waiting on a comment, fabrik:blocked on an open dependency, or fabrik:awaiting-ci waiting for checks. Read the worker output with stage-output.sh before intervening.

How do I wire blocked_by dependencies between GitHub issues for Fabrik?

Create all issues in Backlog first, then wire dependencies via the GitHub API using POST to issues/{B}/dependencies/blocked_by with the blocking issue's database ID. Fabrik only reads the Issue Dependencies API, never prose in the issue body, so wire links before moving issues into Specify.

When should I not use the Fabrik supervisor skill?

Do not use it to bootstrap Fabrik in a new project (use fabrik-setup when no .fabrik directory exists) or for worker-side stage execution, which uses the separate fabrik-workflows plugin. This skill is strictly for user-facing supervision and PM advice.