flux-sync

Trigger plan-sync to update downstream task specs after code drift.

7|1|Updated Feb 21, 2026

Search Tags:#workflow #development #flux #downstream #task-sync #plan-sync

Ready to run

npx skills add https://github.com/Nairon-AI/flux --skill flux-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flux-sync
Source: https://github.com/Nairon-AI/flux/tree/main/skills/flux-sync
Command: npx skills add https://github.com/Nairon-AI/flux --skill flux-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually aligning downstream task specifications with evolving implementations is error-prone and time-consuming. flux-sync provides a controlled, manual trigger to refresh downstream specs after code changes.

Core Features & Use Cases

Manual trigger to update downstream task specs after drift, ensuring alignment with latest implementation.
Works with both task-level and epic-level scopes, with optional dry-run to preview changes.
Integrates into Flux-based workflows, reducing coordination overhead and rework when specs diverge.

Quick Start

Manually trigger a plan-sync to refresh downstream task specs after drift.

Frequently Asked Questions about flux-sync

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

FAQPage Schema

How do I update downstream task specs after code drift in a Flux workflow?▼

To update downstream task specs after code drift, manually trigger a plan-sync within your Flux workflow. This refreshes task specifications to align with the latest code implementations, reducing manual coordination overhead and preventing rework.

What is the best way to preview downstream spec changes before applying them?▼

The best way to preview downstream spec changes is to run the sync process with an optional --dry-run flag. This allows you to review how task and epic scopes will be updated before committing any actual modifications to the specifications.

Do I need fluxctl installed to synchronize downstream task specifications?▼

Yes, you need fluxctl installed in your plugin environment to synchronize downstream task specifications. The sync mechanism relies on fluxctl to execute the plan-sync operations required for maintaining alignment within Flux workflows.

Can I synchronize specifications for both individual tasks and epics?▼

Yes, you can synchronize specifications for both individual tasks and epics. The sync process supports both task-level and epic-level scopes, allowing you to update downstream specifications comprehensively across different granularities of your workflow.

Why do my downstream task specifications diverge from the actual implementation?▼

Downstream task specifications diverge from the actual implementation due to evolving code changes that occur without corresponding spec updates. Manually triggering a plan-sync after code drift corrects this misalignment and keeps specs current.

When should I manually trigger a plan-sync for my development workflow?▼

You should manually trigger a plan-sync for your development workflow whenever code drift occurs. Using this controlled trigger after implementation changes ensures that downstream specs remain accurately synchronized with the evolving codebase.