Integrate Claude Code with Fibery for scrum workflow management

version
0.1.0

Install

/plugin install fibery@workflows-marketplace

Run it inside Claude Code after adding the marketplace with /plugin marketplace add Natural-Heroes/workflows.

Contents

Discovered from source

Skills 1

Fibery Integration

Integrate development workflow with Fibery project management. This skill provides schema knowledge and query patterns for the Natural Heroes Fibery workspace, supporting both sprint-based Scrum tasks and general Todos.

Two Task Systems

This workspace has two task management systems:

SystemDatabaseUse For
ScrumScrum/TaskSprint development work, bugs, features
General TodosFibery databases/TodoOperations, meetings, marketing, ad-hoc work

When to Use Which

Use CaseDatabaseCommand
Sprint development workScrum/Task/create-task
Bug fixes for sprintsScrum/Task/create-task --type=bug
Feature developmentScrum/Task/create-task --type=feature
Meeting action itemsFibery databases/Todo/create-todo
Marketing tasksFibery databases/Todo/create-todo
Operations tasksFibery databases/Todo/create-todo
R&D / Formula workFibery databases/Todo/create-todo
Ad-hoc tasks (no sprint)Fibery databases/Todo/create-todo

Scrum Hierarchy

The workspace uses a 4-level hierarchy:

Release → Sprint → Story → Task
EntityDatabaseKey Fields
ReleaseScrum/ReleaseName, Release Date, Release Goal
SprintScrum/SprintName, Date (range), Sprint Goal, Expected/Delivered Points
StoryScrum/StoryName, User Story, Acceptance Criteria, Expected Points
TaskScrum/TaskName, Task ID, DRI, Priority, Task Size, Task Type, PR Link

Workflow States

Release States

  • Planning
  • Code Freeze
  • Dev Release
  • QA Complete
  • Prod Release

Sprint/Story States

  • Todo
  • In Progress
  • Done

Task States

  • Backlog
  • Todo
  • Doing
  • In Review
  • On Hold
  • Done

Task Enums

FieldValues
PriorityLow, Medium, High, Highest
Task SizeTiny Task, Simple, Moderate, Complex, Large, Very Large
Task TypeFeature Request, Change Request, Bug
Repodev-storefront, odoo, architecture, graphiti, misc, mastra
TagHotfix, Planned

Query Patterns

Get Active Sprint Tasks

{
  "q_from": "Scrum/Task",
  "q_select": {
    "Name": ["Scrum/Name"],
    "Task ID": ["Scrum/Task ID"],
    "State": ["workflow/state", "enum/name"],
    "DRI": ["Scrum/DRI", "user/name"],
    "Story": ["Scrum/Story", "Scrum/Name"],
    "Sprint": ["Scrum/Story Sprint", "Scrum/Name"]
  },
  "q_where": ["q/and",
    ["!=", ["workflow/state", "workflow/Final"], "$notFinal"],
    ["=", ["Scrum/Story Sprint", "workflow/state", "enum/name"], "$inProgress"]
  ],
  "q_params": {
    "$notFinal": true,
    "$inProgress": "In Progress"
  },
  "q_limit": 50
}

Get Task by ID

{
  "q_from": "Scrum/Task",
  "q_select": {
    "Name": ["Scrum/Name"],
    "Task ID": ["Scrum/Task ID"],
    "Public Id": ["fibery/public-id"],
    "State": ["workflow/state", "enum/name"],
    "DRI": ["Scrum/DRI", "user/name"],
    "Priority": ["Scrum/Priority", "enum/name"],
    "Task Type": ["Scrum/Task Type", "enum/name"],
    "PR Link": ["Scrum/PR link"],
    "Story": ["Scrum/Story", "Scrum/Name"]
  },
  "q_where": ["=", ["Scrum/Task ID"], "$taskId"],
  "q_params": { "$taskId": "123" },
  "q_limit": 1
}

Get Current Sprint

{
  "q_from": "Scrum/Sprint",
  "q_select": {
    "Name": ["Scrum/Name"],
    "State": ["workflow/state", "enum/name"],
    "Expected Points": ["Scrum/Expected Points"],
    "Delivered Points": ["Scrum/Delivered points"],
    "Release": ["Scrum/Release", "Scrum/Name"]
  },
  "q_where": ["=", ["workflow/state", "enum/name"], "$state"],
  "q_params": { "$state": "In Progress" },
  "q_limit": 1
}

Update Patterns

Update Task State

{
  "database": "Scrum/Task",
  "entity": {
    "fibery/id": "<uuid>",
    "workflow/state": "Doing"
  }
}

Update PR Link

{
  "database": "Scrum/Task",
  "entity": {
    "fibery/id": "<uuid>",
    "Scrum/PR link": "https://github.com/org/repo/pull/123"
  }
}

Create Task

{
  "database": "Scrum/Task",
  "entity": {
    "Scrum/Name": "Task name",
    "Scrum/Task Type": "Feature Request",
    "Scrum/Story": "<story-uuid>",
    "workflow/state": "Todo"
  }
}

Task ID Convention

Tasks use a numeric Task ID field (e.g., 262, 275). Extract from:

  • Branch names: feat/262-shopping-cart → Task ID 262
  • Commit messages: feat(262): add cart → Task ID 262
  • PR titles: feat(262): shopping cart → Task ID 262

GitHub Integration

Tasks link to GitHub Pull Requests via:

  • Scrum/PR link - Direct URL to PR
  • Scrum/Pull Request - Linked GitHub/Pull Request entity
  • Scrum/PR State - PR status text

General Todos (Fibery databases/Todo)

For non-sprint work: operations, meetings, marketing, R&D, etc.

Todo Key Fields

FieldAPI PathType
NameFibery databases/nametext
Stateworkflow/stateenum
DRIFibery databases/DRIuser
PriorityFibery databases/Priorityenum
DeadlineFibery databases/Deadlinedate-time
TagsFibery databases/Tagscollection

Todo States

  • Backlog
  • Todo
  • Doing
  • In Review
  • On Hold
  • Done

Query Active Todos

{
  "q_from": "Fibery databases/Todo",
  "q_select": {
    "Name": ["Fibery databases/name"],
    "Public ID": ["fibery/public-id"],
    "State": ["workflow/state", "enum/name"],
    "DRI": ["Fibery databases/DRI", "user/name"],
    "Priority": ["Fibery databases/Priority", "enum/name"],
    "Deadline": ["Fibery databases/Deadline"]
  },
  "q_where": ["!=", ["workflow/state", "workflow/Final"], "$notFinal"],
  "q_params": { "$notFinal": true },
  "q_limit": 50
}

Create Todo

{
  "database": "Fibery databases/Todo",
  "entity": {
    "Fibery databases/name": "Todo title",
    "Fibery databases/Priority": "Medium",
    "workflow/state": "Todo"
  }
}

Additional Resources

Reference Files

For detailed query examples and field mappings:

  • references/schema.md - Complete field definitions for all Scrum entities
  • references/queries.md - Additional query patterns and examples

Examples

Working query examples in examples/:

  • get-sprint-tasks.json - Query for sprint tasks
  • update-task.json - Update task fields

Commands 6

Create Task Command

Create a new task in Fibery Scrum from the current development context.

Process

  1. Parse arguments:

    • <name>: Task name (required)
    • --story=<id>: Story public ID to attach to (optional)
    • --type=feature|bug|change: Task type (default: feature)
  2. If no story specified, query active sprint stories:

    {
      "q_from": "Scrum/Story",
      "q_select": {
        "ID": ["fibery/id"],
        "Public ID": ["fibery/public-id"],
        "Name": ["Scrum/Name"],
        "Sprint": ["Scrum/Sprint", "Scrum/Name"]
      },
      "q_where": ["=", ["Scrum/Sprint", "workflow/state", "enum/name"], "$state"],
      "q_params": { "$state": "In Progress" },
      "q_limit": 20
    }
    

    Present stories and ask user to select one.

  3. Map task type argument to enum:

    • feature → "Feature Request"
    • bug → "Bug"
    • change → "Change Request"
  4. Create the task using mcp__fibery__create_entity:

    {
      "database": "Scrum/Task",
      "entity": {
        "Scrum/Name": "<task-name>",
        "Scrum/Task Type": "<mapped-type>",
        "Scrum/Story": "<story-uuid>",
        "workflow/state": "Todo"
      }
    }
    
  5. Query the created task to get its Task ID

  6. Display result with Fibery link

Output Format

Created Task #287: Fix checkout validation
Type: Bug
Story: Checkout Flow
Sprint: Sprint 23
State: Todo

Link: https://naturalheroes.fibery.io/Scrum/Task/287

Tips

  • Detect repo from current directory to suggest Repo field
  • If creating from a bug report, extract details for description fields

Create Todo Command

Create a general todo in Fibery databases/Todo for non-sprint work (operations, meetings, marketing, etc).

When to Use

Use /create-todo for:

  • Meeting action items
  • Marketing tasks
  • Operations tasks
  • R&D / formula work
  • Ad-hoc tasks not tied to sprints

Use /create-task instead for sprint development work, bugs, and features.

Process

  1. Parse arguments:

    • <name>: Todo title (required)
    • --priority=low|medium|high|highest: Priority level (default: medium)
    • --deadline=<date>: Due date in ISO format or natural language
  2. Map priority argument to enum:

    • low → "Low"
    • medium → "Medium"
    • high → "High"
    • highest → "Highest"
  3. Create the todo using mcp__fibery__create_entity:

    {
      "database": "Fibery databases/Todo",
      "entity": {
        "Fibery databases/name": "<todo-name>",
        "Fibery databases/Priority": "<mapped-priority>",
        "workflow/state": "Todo"
      }
    }
    
  4. If deadline provided, include it:

    "Fibery databases/Deadline": "<iso-datetime>"
    
  5. Query the created todo to get its Public ID

  6. Display result with Fibery link

Output Format

Created Todo #42: Review Q1 marketing plan
Priority: High
State: Todo
Deadline: 2026-01-15

Link: https://naturalheroes.fibery.io/Fibery_databases/Todo/42

Available Fields

Reference schema.md for full field list. Key fields:

  • Name, State, Priority, Deadline
  • DRI (assigned user)
  • Tags (R&D, Marketing, Operations, etc)
  • Story Points, Hours Expected
  • Project Phase, Key Result (OKR link)

Tips

  • Use natural language dates like "next Friday" or "in 2 weeks"
  • Add --assign=<user> to set DRI if needed
  • Tags can be added after creation via Fibery UI

Link PR Command

Link a GitHub Pull Request to a Fibery task.

Process

  1. Parse arguments:

    • <task-id>: Fibery Task ID (required, numeric)
    • --pr=<number>: PR number (optional, auto-detects from current branch)
  2. If no PR specified, detect from current branch:

    gh pr view --json number,url,title,state 2>/dev/null
    
  3. Query task to get UUID:

    {
      "q_from": "Scrum/Task",
      "q_select": {
        "ID": ["fibery/id"],
        "Name": ["Scrum/Name"],
        "Task ID": ["Scrum/Task ID"],
        "State": ["workflow/state", "enum/name"],
        "PR Link": ["Scrum/PR link"]
      },
      "q_where": ["=", ["Scrum/Task ID"], "$taskId"],
      "q_params": { "$taskId": "<task-id>" },
      "q_limit": 1
    }
    
  4. Get PR URL:

    • If --pr specified: gh pr view <number> --json url -q .url
    • Otherwise use detected PR URL
  5. Update task with PR link:

    {
      "database": "Scrum/Task",
      "entity": {
        "fibery/id": "<task-uuid>",
        "Scrum/PR link": "<pr-url>"
      }
    }
    
  6. Optionally update task state to "In Review" if PR is open

Output Format

Task #262: Add e2e tests + components
Linked PR: #42 - Add e2e tests for cart
URL: https://github.com/natural-heroes/dev-storefront/pull/42
State: Doing → In Review

Auto-Detection

When run without arguments, attempt to:

  1. Extract task ID from branch name (e.g., feat/262-feature → 262)
  2. Get current PR from gh pr view
  3. Link them together

Example:

/fibery:link-pr
# Auto-detects task 262 from branch feat/262-cart
# Auto-detects PR #42 from current branch

Show Sprint Command

Display the current sprint's status, stories, and tasks.

Process

  1. Parse arguments:

    • --sprint=<name>: Specific sprint name (optional, defaults to "In Progress" sprint)
  2. Query sprint details:

    {
      "q_from": "Scrum/Sprint",
      "q_select": {
        "ID": ["fibery/id"],
        "Name": ["Scrum/Name"],
        "State": ["workflow/state", "enum/name"],
        "Expected Points": ["Scrum/Expected Points"],
        "Delivered Points": ["Scrum/Delivered points"],
        "Delivery Rate": ["Scrum/Delivery Rate"],
        "Release": ["Scrum/Release", "Scrum/Name"]
      },
      "q_where": ["=", ["workflow/state", "enum/name"], "$state"],
      "q_params": { "$state": "In Progress" },
      "q_limit": 1
    }
    
  3. Query sprint tasks grouped by state:

    {
      "q_from": "Scrum/Task",
      "q_select": {
        "Task ID": ["Scrum/Task ID"],
        "Name": ["Scrum/Name"],
        "State": ["workflow/state", "enum/name"],
        "DRI": ["Scrum/DRI", "user/name"],
        "Priority": ["Scrum/Priority", "enum/name"],
        "Story": ["Scrum/Story", "Scrum/Name"]
      },
      "q_where": ["=", ["Scrum/Story Sprint", "Scrum/Name"], "$sprintName"],
      "q_params": { "$sprintName": "<sprint-name>" },
      "q_order_by": {"workflow/state": "q/asc"},
      "q_limit": 100
    }
    
  4. Group tasks by state and display

Output Format

Sprint: Upgrade NextJS - sprint 2
Release: Upgrade NextJS
Progress: 12/28 points (43%)

Stories:
├─ Create the Next.js 16 baseline project (Todo)
├─ Context Migration (Todo)
├─ PDP Components migration (Todo)
└─ Testing & deployment (Todo)

Tasks by State:
─────────────────────────────────────────
DOING (2)
  #262 Add e2e tests + components     Gowtham
  #271 Search page + box              Rahul

TODO (3)
  #272 Cart page                      Rahul
  #275 Blogs and general pages        Rahul
  #280 Header component               -

DONE (5)
  #232 Solve lint issues              Rahul
  #248 Fix storyblok videos           Gowtham
  ...

Tips

  • Highlight tasks assigned to current user if detectable
  • Show overdue indicator if sprint end date passed

Sync Task Command

Link the current development work to a Fibery Scrum task.

Process

  1. Parse the task ID from arguments (numeric, e.g., 262)
  2. Query Fibery for the task using mcp__fibery__query_database:
    {
      "q_from": "Scrum/Task",
      "q_select": {
        "ID": ["fibery/id"],
        "Name": ["Scrum/Name"],
        "Task ID": ["Scrum/Task ID"],
        "State": ["workflow/state", "enum/name"],
        "DRI": ["Scrum/DRI", "user/name"],
        "Story": ["Scrum/Story", "Scrum/Name"],
        "Sprint": ["Scrum/Story Sprint", "Scrum/Name"]
      },
      "q_where": ["=", ["Scrum/Task ID"], "$taskId"],
      "q_params": { "$taskId": "<task-id>" },
      "q_limit": 1
    }
    
  3. Display task details to user
  4. Get current git branch name with git branch --show-current
  5. If branch contains task ID, confirm linkage
  6. Offer to update task state to "Doing" if currently "Todo" or "Backlog"

Output Format

Task #262: Add shopping cart functionality
Story: E-commerce Features
Sprint: Sprint 23 (In Progress)
State: Todo → Doing (updated)
DRI: Gowtham

Linked to branch: feat/262-shopping-cart

Error Handling

  • If task not found, suggest checking the Task ID
  • If Fibery connection fails, check FIBERY_HOST and FIBERY_API_TOKEN env vars

Update Task Command

Update a Fibery task's state, DRI, or other fields.

Process

  1. Parse arguments:

    • <task-id>: Task ID (required, numeric)
    • --state=<state>: New state (optional)
    • --dri=<name>: Assign to user (optional)
  2. Query task to get current values and UUID:

    {
      "q_from": "Scrum/Task",
      "q_select": {
        "ID": ["fibery/id"],
        "Name": ["Scrum/Name"],
        "Task ID": ["Scrum/Task ID"],
        "State": ["workflow/state", "enum/name"],
        "DRI": ["Scrum/DRI", "user/name"]
      },
      "q_where": ["=", ["Scrum/Task ID"], "$taskId"],
      "q_params": { "$taskId": "<task-id>" },
      "q_limit": 1
    }
    
  3. If no update flags provided, ask what to update using AskUserQuestion

  4. Map state argument to valid state:

    • backlog → "Backlog"
    • todo → "Todo"
    • doing → "Doing"
    • review → "In Review"
    • hold → "On Hold"
    • done → "Done"
  5. If DRI specified, query users to find UUID:

    {
      "q_from": "fibery/user",
      "q_select": {
        "ID": ["fibery/id"],
        "Name": ["user/name"]
      },
      "q_where": ["q/contains", ["user/name"], "$name"],
      "q_params": { "$name": "<dri-name>" },
      "q_limit": 5
    }
    
  6. Update task using mcp__fibery__update_entity:

    {
      "database": "Scrum/Task",
      "entity": {
        "fibery/id": "<task-uuid>",
        "workflow/state": "<new-state>",
        "Scrum/DRI": "<user-uuid>"
      }
    }
    

Output Format

Task #262: Add e2e tests + components
Updated:
  State: Todo → Doing
  DRI: - → Gowtham

State Shortcuts

Accept lowercase shortcuts for states:

  • backlog, todo, doing, review, hold, done

Agents 1

Scrum Task Manager Agent

Manage the connection between development work and Fibery Scrum tasks.

Triggering

This agent should be used when:

  • User commits code with a task ID in the message or branch
  • User creates or updates a pull request
  • User asks about Fibery task status
  • User wants to sync their work with Fibery
User: I just pushed my changes for the cart feature Agent: [Detects task ID from branch, offers to update Fibery task state] User: What's the status of task 262? Agent: [Queries Fibery and displays task details] User: Mark my current task as done Agent: [Extracts task ID from branch, updates state in Fibery]

Behavior

On Commit/Push Detection

  1. Extract task ID from:

    • Branch name: feat/262-shopping-cart → 262
    • Commit message: feat(262): add cart → 262
  2. Query task current state from Fibery

  3. Suggest appropriate state transition:

    • First commit → "Doing"
    • PR created → "In Review"
    • PR merged → "Done"
  4. Offer to update with user confirmation

On Task Query

  1. Parse task ID from user request
  2. Query full task details from Fibery
  3. Display: name, state, story, sprint, DRI, PR link
  4. Offer relevant actions based on state

Task ID Extraction Patterns

Branch patterns:
  feat/123-description  → 123
  fix/456-bug-name      → 456
  123-feature           → 123

Commit patterns:
  feat(123): message    → 123
  fix(123): message     → 123
  [123] message         → 123

Query Templates

Get Task by ID

{
  "q_from": "Scrum/Task",
  "q_select": {
    "ID": ["fibery/id"],
    "Name": ["Scrum/Name"],
    "Task ID": ["Scrum/Task ID"],
    "State": ["workflow/state", "enum/name"],
    "DRI": ["Scrum/DRI", "user/name"],
    "Story": ["Scrum/Story", "Scrum/Name"],
    "Sprint": ["Scrum/Story Sprint", "Scrum/Name"],
    "PR Link": ["Scrum/PR link"]
  },
  "q_where": ["=", ["Scrum/Task ID"], "$taskId"],
  "q_params": { "$taskId": "<id>" },
  "q_limit": 1
}

Update Task State

{
  "database": "Scrum/Task",
  "entity": {
    "fibery/id": "<uuid>",
    "workflow/state": "<state>"
  }
}

State Transitions

Suggest logical state progressions:

  • Backlog → Todo (when sprint planning)
  • Todo → Doing (on first commit)
  • Doing → In Review (on PR creation)
  • In Review → Done (on PR merge)
  • Any → On Hold (when blocked)

Output Style

Be concise. Show task info in a clean format:

Task #262: Add shopping cart
State: Todo → Doing ✓
Sprint: Upgrade NextJS - sprint 2

Always confirm before making changes to Fibery.

Sponsors

Details

Marketplace
Natural-Heroes/workflows
Source
plugins/fibery
Author
Natural Heroes
Category
Productivity

More from Natural-Heroes/workflows

All 4