/tracker-sync

Project a flow spec to a tracker (Linear/GitHub/GitLab/Jira) and reconcile body/status/comments two-way — projection, not coordination. NOT plan-sync (/flow-next:sync).

BOOST

gmickel@gmickel

GitHub

From plugin

flow-next

72126 skills21 agents26 commands

> /plugin marketplace add gmickel/flow-next
> /plugin install flow-next@flow-next

Command definition

tracker-sync.md

name: tracker-sync
description: Project a flow spec to a tracker (Linear/GitHub/GitLab/Jira) and reconcile body/status/comments two-way — projection, not coordination. NOT plan-sync (/flow-next:sync).
argument-hint: "[discover|push|pull|reconcile|link|unlink] [<id>]"
disable-model-invocation: true

IMPORTANT: This command MUST invoke the skill `flow-next-tracker-sync`

The ONLY purpose of this command is to call the `flow-next-tracker-sync` skill. You MUST use that skill now.

This is **distinct from `/flow-next:sync`** (= plan-sync, the `flow-next-sync` skill, which updates downstream task specs after implementation drift). `/flow-next:tracker-sync` bridges a spec to an external tracker issue. Do not conflate them.

**Arguments:** $ARGUMENTS

Pass the arguments to the skill. The skill handles the discovery ceremony, link/create/unlink ceremony, and the push/pull/reconcile orchestration.

Read it on GitHub ↗

Stats

Python Bash Rust GraphQL Docker Git GitHub GitLab Markdown Anthropic OpenAI Jira

723

Stars

Forks

Active

Maintenance

Python

Language

MIT

License

1d ago

Last commit

10mo ago

Created

Repo: gmickel/flow-next

Ships withflow-next

Faster than your agent alone. And better. A workflow plugin that takes a bug, idea or ticket to a verified pull request: specs, cross-model review by risk, live QA, receipts in your repo. Claude Code · Codex · Cursor · Droid · Grok Build · OpenCode · Muse Code.

72129 skills21 agents

Get the whole plugin

Stars on GitHub