flux-work

Orchestrate Flow epics with git-backed task tracking and phase-based workflows.

7|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Nairon-AI/flux --skill flux-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flux-work
Source: https://github.com/Nairon-AI/flux/tree/main/skills/flux-work
Command: npx skills add https://github.com/Nairon-AI/flux --skill flux-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flow work coordinates end-to-end execution of Flow epics with git-backed task tracking, ensuring fidelity and fast feedback loops.

Core Features & Use Cases

  • Flow work orchestrates the planning, task execution, and quality gates for Flow epics using .flux task tracking and fluxctl-driven workflow.
  • It supports session phase tracking, built-in hard rules, and optional review steps to ship reliably.
  • Real-world example: Manage implementing a plan by creating an epic, spawning a worker per task, and iterating until the epic ships.

Quick Start

Begin Flux-work on a chosen epic by answering setup questions, then let the worker iterate through tasks until completion.

Frequently Asked Questions about flux-work

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

FAQPage Schema
How do I coordinate git-backed task tracking for epic workflows?

Epic workflows with git-backed task tracking are coordinated by orchestrating phase-based execution, mandatory reviews, and continuous feedback loops using fluxctl. It enforces plan fidelity by syncing task creation and status with Linear.

What is the best way to manage plan implementation through structured task execution?

Plan implementation is managed by creating a Flow epic, spawning a worker per task, and iterating until the epic ships. This structured execution applies phase-based workflows and optional TDD to ensure reliable delivery.

Do I need fluxctl and Linear to orchestrate Flow epics?

Yes, orchestrating Flow epics requires fluxctl for workflow orchestration and Linear for epic and task creation plus status syncing. These dependencies enforce plan fidelity and drive structured execution.

How does Flux-work enforce plan fidelity during task execution?

Plan fidelity is enforced through session phase tracking, built-in hard rules, and optional review steps within the Flux workflow. Continuous feedback loops and mandatory reviews ensure tasks ship reliably.

Can I use test-driven development with git-backed task management workflows?

Yes, test-driven development is supported as an optional feature within the worker orchestration workflow. It integrates with the phase-based task execution and plan-sync features to iterate until completion.

When should I not use phase-based workflows for epic task management?

Phase-based workflows for epic task management are not suited for ad-hoc or unstructured development lacking a defined plan. The system enforces mandatory reviews and hard rules, which requires a structured specification to function correctly.