flow-next-sync

Execute plan-sync drift corrections to update downstream task specs.

Updated Jan 15, 2026

Search Tags:#automation #validation #drift #epic #task #plan-sync #flowctl

Ready to run

npx skills add https://github.com/tiendung/flow-next --skill flow-next-sync-tiendung

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flow-next-sync
Source: https://github.com/tiendung/flow-next/tree/main/skills/flow-next-sync
Command: npx skills add https://github.com/tiendung/flow-next --skill flow-next-sync-tiendung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

Manually run plan-sync for specified epic or task to propagate spec updates.
Supports both task-level and epic-level drift alignment, including dry-run validation.
Handles error states for missing .flow/ and invalid IDs, and reports results clearly.

Quick Start

Trigger a plan-sync for a given epic or task ID to refresh downstream specs.

Frequently Asked Questions about flow-next-sync

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

FAQPage Schema

How do I manually sync downstream task specs after drift?▼

To manually sync downstream task specs after drift, trigger a plan-sync correction for a specified epic or task ID to propagate spec updates across your project.

Can I validate drift corrections before applying changes to downstream tasks?▼

Yes, you can validate drift corrections by running a dry-run plan-sync to preview downstream spec updates and identify potential errors before applying actual changes.

What happens if I run a plan-sync without the .flow/ folder?▼

Running plan-sync without the .flow/ folder triggers an environment check error, halting the synchronization process and guiding you to initialize the required directory structure.

Does plan-sync support both epic-level and task-level drift alignment?▼

Yes, plan-sync supports both epic-level and task-level drift alignment, allowing you to manually propagate spec updates whether the drift originated at the epic or task scope.

Why does my plan-sync fail when using an invalid epic or task ID?▼

Plan-sync fails with invalid IDs because the system enforces strict ID validation to ensure downstream identification and agent-based synchronization only target existing entities.

What is the best way to troubleshoot plan-sync errors during downstream synchronization?▼

The best way to troubleshoot plan-sync errors is to review the detailed reporting provided by the tool, which offers robust error handling and guidance for resolving environment or ID validation failures.