flux

name	flux
description	Manage .flux/ tasks, epics, and config. Triggers: 'show me my tasks', 'list epics', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth', 'show my Flux config', 'what did setup configure', 'edit Flux settings'. NOT for /flux:plan or /flux:work.

Flux Management

Quick task, epic, and config operations in .flux/. For planning features use /flux:plan, for executing use /flux:work.

Setup

CRITICAL: fluxctl is BUNDLED — NOT installed globally. which fluxctl will fail (expected). Always use:

PLUGIN_ROOT="${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}}"
[ ! -d "$PLUGIN_ROOT/scripts" ] && PLUGIN_ROOT=$(ls -td ~/.claude/plugins/cache/nairon-flux/flux/*/ 2>/dev/null | head -1)
FLUXCTL="${PLUGIN_ROOT}/scripts/fluxctl"

Then run commands with $FLUXCTL <command>.

Approval gate for creation:

• Before any epic create or task create, get explicit developer approval first.
• Prefer the question tool / AskUserQuestion when available.
• Fallback: require the developer to type exactly I_APPROVE_CREATING_EPICS_AND_TASKS.
• Pass --approve "I_APPROVE_CREATING_EPICS_AND_TASKS" on the create command after approval.

Discover all commands/options:

$FLUXCTL --help
$FLUXCTL <command> --help   # e.g., $FLUXCTL task --help

Quick Reference

# Check if .flux exists
$FLUXCTL detect --json

# Initialize (if needed)
$FLUXCTL init --json

# Show current Flux config
$FLUXCTL config list --json

# Open Flux config in an editor
$FLUXCTL config edit

# List everything (epics + tasks grouped)
$FLUXCTL list --json

# List all epics
$FLUXCTL epics --json

# List all tasks (or filter by epic/status)
$FLUXCTL tasks --json
$FLUXCTL tasks --epic fn-1-add-oauth --json
$FLUXCTL tasks --status todo --json

# View epic with all tasks
$FLUXCTL show fn-1-add-oauth --json
$FLUXCTL cat fn-1-add-oauth              # Spec markdown

# View single task
$FLUXCTL show fn-1-add-oauth.2 --json
$FLUXCTL cat fn-1-add-oauth.2            # Task spec

# What's ready to work on?
$FLUXCTL ready --epic fn-1-add-oauth --json

# Create task under existing epic
$FLUXCTL task create --epic fn-1-add-oauth --title "Fix bug X" --approve "I_APPROVE_CREATING_EPICS_AND_TASKS" --json

# Set task description and acceptance (combined, fewer writes)
$FLUXCTL task set-spec fn-1-add-oauth.2 --description /tmp/desc.md --acceptance /tmp/accept.md --json

# Or use stdin with heredoc (no temp file):
$FLUXCTL task set-description fn-1-add-oauth.2 --file - --json <<'EOF'
Description here
EOF

# Start working on task
$FLUXCTL start fn-1-add-oauth.2 --json

# Mark task done
echo "What was done" > /tmp/summary.md
echo '{"commits":["abc123"],"tests":["npm test"],"prs":[]}' > /tmp/evidence.json
$FLUXCTL done fn-1-add-oauth.2 --summary-file /tmp/summary.md --evidence-json /tmp/evidence.json --json

# Validate structure
$FLUXCTL validate --epic fn-1-add-oauth --json
$FLUXCTL validate --all --json

Common Patterns

"Add a task for X"

1. Find relevant epic:

   # List all epics
   $FLUXCTL epics --json
   
   # Or show a specific epic to check its scope
   $FLUXCTL show fn-1 --json
   

2. Create task:

   $FLUXCTL task create --epic fn-N --title "Short title" --approve "I_APPROVE_CREATING_EPICS_AND_TASKS" --json
   

3. Add description + acceptance (combined):

   cat > /tmp/desc.md << 'EOF'
   **Bug/Feature:** Brief description
   
   **Details:**
   - Point 1
   - Point 2
   EOF
   cat > /tmp/accept.md << 'EOF'
   - [ ] Criterion 1
   - [ ] Criterion 2
   EOF
   $FLUXCTL task set-spec fn-N.M --description /tmp/desc.md --acceptance /tmp/accept.md --json
   

"What tasks are there?"

# All epics
$FLUXCTL epics --json

# All tasks
$FLUXCTL tasks --json

# Tasks for specific epic
$FLUXCTL tasks --epic fn-1-add-oauth --json

# Ready tasks for an epic
$FLUXCTL ready --epic fn-1-add-oauth --json

"Show me my Flux config"

# Full current config as Flux resolves it
$FLUXCTL config list --json

# Single config value
$FLUXCTL config get review.backend --json

# Open .flux/config.json in your editor
$FLUXCTL config edit

"Show me task X"

$FLUXCTL show fn-1-add-oauth.2 --json   # Metadata
$FLUXCTL cat fn-1-add-oauth.2           # Full spec

(Legacy fn-1.2 / fn-1-xxx.2 still works.)

Create new epic (rare - usually via /flux:plan)

$FLUXCTL epic create --title "Epic title" --approve "I_APPROVE_CREATING_EPICS_AND_TASKS" --json
# Returns: {"success": true, "id": "fn-N-epic-title", ...}

ID Format

• Epic: fn-N-slug where slug is derived from title (e.g., fn-1-add-oauth, fn-2-fix-login-bug)
• Task: fn-N-slug.M (e.g., fn-1-add-oauth.1, fn-2-fix-login-bug.2)

Legacy formats fn-N and fn-N-xxx (random 3-char suffix) are still supported.

Notes

• Run $FLUXCTL --help to discover all commands and options
• All writes go through fluxctl (don't edit JSON/MD files directly)
• --json flag gives machine-readable output
• For complex planning/execution, use /flux:plan and /flux:work

Gotchas

• This skill is for quick task, epic, and config operations only. Do not route planning or implementation here when /flux:plan or /flux:work is the real intent.
• fluxctl is bundled inside the plugin cache, not on the global PATH. Recompute PLUGIN_ROOT first instead of assuming which fluxctl works.
• Never edit .flux/ task JSON or markdown files by hand. Use fluxctl so runtime state stays consistent.

---

Update Check (End of Command)

ALWAYS run at the very end of command execution:

PLUGIN_ROOT="${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}}"
[ ! -d "$PLUGIN_ROOT/scripts" ] && PLUGIN_ROOT=$(ls -td ~/.claude/plugins/cache/nairon-flux/flux/*/ 2>/dev/null | head -1)
UPDATE_JSON=$("$PLUGIN_ROOT/scripts/version-check.sh" 2>/dev/null || echo '{"update_available":false}')
UPDATE_AVAILABLE=$(echo "$UPDATE_JSON" | jq -r '.update_available')
LOCAL_VER=$(echo "$UPDATE_JSON" | jq -r '.local_version')
REMOTE_VER=$(echo "$UPDATE_JSON" | jq -r '.remote_version')

If update available, append to output:

---
Flux update available: v${LOCAL_VER} → v${REMOTE_VER}
Update Flux from the same source you installed it from, then restart your agent session.
---