flux-sync

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.

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.

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.

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.

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.

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.