flow-next-sync

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

674|52|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-next-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-next-sync
Source: https://github.com/gmickel/gmickel-claude-marketplace/tree/main/plugins/flow-next/skills/flow-next-sync
Command: npx skills add https://github.com/gmickel/gmickel-claude-marketplace --skill flow-next-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables manual triggering of the plan-sync workflow to reconcile downstream task specifications when implementation drift occurs, keeping task plans aligned with code changes.

Core Features & Use Cases

  • Manual plan-sync trigger: Initiates a drift-aware sync across downstream tasks and epics.
  • Environment validation & reporting: Verifies plugin environment, parses IDs, and reports results clearly.
  • Reuses existing plan-sync agent: Delegates work to the built-in plan-sync subagent without duplicating processes.

Quick Start

Run the flow-next-sync command to start syncing: /flow-next:sync <id> [--dry-run] Examples:

  • /flow-next:sync fn-1
  • /flow-next:sync fn-1.2 --dry-run

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, run the plan-sync command with your target ID. This triggers drift-aware synchronization across tasks and epics, updating specs to match code changes.

What is drift-aware synchronization for task plans?

Drift-aware synchronization is a process that reconciles downstream task specifications when implementation drift occurs. It keeps task plans aligned with code changes by updating specs across tasks and epics.

Can I preview plan-sync changes before applying them to tasks?

Yes, you can preview plan-sync changes by using the dry-run option. This spawns the plan-sync agent to validate input and build the downstream list without applying actual updates to your task specs.

How do I sync downstream tasks for a specific epic ID?

To sync downstream tasks for a specific epic ID, execute the sync command with your target identifier. The skill validates the input, locates the correct source epic, and spawns the sync agent.

Does the plan-sync workflow require a specific directory structure?

Yes, the plan-sync workflow requires the .flow directory to exist in your environment. The skill validates your environment and ensures this directory is present before locating source tasks.

Why are my downstream task specs out of sync with code changes?

Downstream task specs fall out of sync when code changes outpace existing specifications, creating implementation drift. Manually triggering plan-sync reconciles this by updating downstream tasks to match current code.