/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).
$ npx -y skills add gmickel/flow-next --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/tracker-sync
Context preview
What this command does when you run it.
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).
Command definition
tracker-sync.mdname: 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>]"
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.
Repeatable agentic engineering. The workflow layer that turns AI coding agents into a disciplined factory: durable specs, fresh-context workers, adversarial cross-model reviews, receipts. Everything in your repo, zero dependencies. Claude Code · Codex · Cursor · Droid.
Other commands on flow-next.
- /audit
Audit `.flow/memory/` entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry
Open command - /capture
Synthesize the current conversation into a flow-next spec at `.flow/specs/<spec-id>.md` — source-tagged, mandatory read-back, no silent overwrite
Open command - /chart
Decision-map discovery for one oversized/unclear idea before capture - ground, chart a frontier, resolve one decision per invocation, brief for capture
Open command - /guide
Prompt-first router that recommends the smallest sufficient flow-next workflow for the current starting state
Open command - /impl-review
John Carmack-level implementation review via RepoPrompt or Codex
Open command - /interview
Interview & refine a spec, task, or spec file in-depth
Open command