Examples

Learn from real-world Faber use cases and example implementations.

Example 1: GitHub Issue Manager

A role that manages GitHub issues with automated triaging, labeling, and assignment.

Agent Definition

org: acme
system: devops
name: issue-manager
type: role
platforms: [github-issues]
description: Automated GitHub issue management and triage

Context Structure

roles/issue-manager/
  contexts/
    specialists/
      issue-triage.md         # How to triage issues
    platforms/
      github-issues.md        # GitHub API usage
    playbooks/
      bug-handling.md         # Bug handling procedures
      feature-requests.md     # Feature request workflow

Build for Multiple Frameworks

# Build for Claude Code
fractary faber build claude role issue-manager

# Build for LangGraph
fractary faber build langgraph role issue-manager

# Build for CrewAI
fractary faber build crewai role issue-manager

Usage

In Claude Code:

"Triage the last 10 issues in the repository"
"Label this issue based on its content"
"Assign this bug to the appropriate team member"

Example 2: DevOps Team

A multi-agent team composition for DevOps workflows.

Team Definition

org: acme
name: devops
type: team
description: DevOps automation team

roles:
  - issue-manager
  - code-reviewer
  - deployment-coordinator

workflows:
  - release-management
  - incident-response

Team Workflow

name: release-management
triggers:
  - github_release_created

steps:
  - role: code-reviewer
    task: final-review

  - role: deployment-coordinator
    task: deploy-staging

  - role: issue-manager
    task: update-release-issues

Example 3: Custom Organization Overlay

Customize Faber agents for your organization without forking.

Overlay Structure

contexts:
  specialists:
    - acme-domain-knowledge
  standards:
    - acme-issue-conventions
    - acme-labeling-scheme

bindings:
  organization: "acme-corp"
  default_repo: "acme-corp/main-product"
  priority_labels:
    - "P0-critical"
    - "P1-high"
    - "P2-medium"
    - "P3-low"
  team_assignments:
    backend: ["alice", "bob"]
    frontend: ["charlie", "diana"]
    infrastructure: ["eve", "frank"]

Apply Overlay During Build

fractary faber build claude role issue-manager --overlay acme

Example 4: Platform-Agnostic Issue Tracking

Define a role that works with multiple issue tracking platforms.

Multi-Platform Agent

org: acme
system: devops
name: universal-issue-manager
type: role
platforms:
  - github-issues
  - linear
  - jira

platform_bindings:
  github-issues:
    repo: "acme-corp/product"
  linear:
    team: "ACME"
  jira:
    project: "ACME"

Usage

The same agent works across platforms:

# Deploy to GitHub projects
fractary faber build claude role universal-issue-manager

# Agent automatically detects which platform to use based on context
# Works with GitHub, Linear, or Jira without code changes

Example 5: Continuous Deployment Workflow

Cross-team workflow for automated deployments.

Workflow Definition

name: continuous-deployment
type: workflow

teams:
  - devops
  - qa
  - operations

trigger:
  type: github_push
  branch: main

stages:
  - name: validate
    team: devops
    roles:
      - code-reviewer
    tasks:
      - lint-check
      - test-coverage

  - name: test
    team: qa
    roles:
      - test-coordinator
    tasks:
      - run-integration-tests
      - verify-staging

  - name: deploy
    team: operations
    roles:
      - deployment-coordinator
    tasks:
      - deploy-production
      - verify-health

  - name: notify
    team: devops
    roles:
      - issue-manager
    tasks:
      - close-deployed-issues
      - notify-stakeholders

Example 6: Using Evals for Testing

Test your agents with evaluation scenarios.

Eval Definition

name: triage-accuracy
description: Test issue triaging accuracy

scenarios:
  - name: bug-identification
    input: |
      Title: "Application crashes on login"
      Body: "Steps to reproduce..."
    expected:
      labels: ["bug", "P1-high", "backend"]
      assigned: true

  - name: feature-request
    input: |
      Title: "Add dark mode support"
      Body: "Would be great to have..."
    expected:
      labels: ["enhancement", "frontend"]

  - name: security-issue
    input: |
      Title: "Potential XSS vulnerability"
      Body: "Found a security issue..."
    expected:
      labels: ["security", "P0-critical"]
      assigned: true
      priority: immediate

Run Evals

fractary faber eval role issue-manager --scenario triage-accuracy

Next Steps

View source code → - Browse the full implementation
Contribute examples → - Share your use cases
CLI Reference → - Complete command reference

Community Examples

Looking for more examples? Check out: