agentsclimarketplace
Sign in

Flow sync status

Skill cofin/flow/skills/flow-sync-status

Use when syncing Beads state to markdown, checking Flow status, refreshing context docs, validating task markers, or reporting ready/blocked Flow work.From its SKILL.md

Install
npx -y skills add cofin/flow --skill flow-sync-status

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 1 command, including `make validate-skills`.

SKILL.md

2.6 KB, 575 tokens by cl100k_base, as published. Nobody here has run it

Flow Sync And Status

Use this lifecycle skill for status dashboards, sync, context refresh, cleanup checks, and drift reporting.

Beads mode: Skip every bd invocation when the SessionStart hook reports Beads Backend: Missing (None) or Disabled via plugin config (useBeads=false). With no backend, /flow:sync is a no-op (announce and exit) and status falls back to spec.md markers. Never halt for missing Beads. See ../flow/references/discipline.md.

Workflow

  1. Read .agents/beads.json before any sync/export decision.
  2. Pull Beads state and notes as the source of truth.
  3. Regenerate synchronized markdown views without changing requirement text.
  4. Detect drift in workflow commands, tech stack, patterns, knowledge chapters, and references.
  5. Report ready, blocked, in-progress, and stale work with clear next actions.

Guardrails

  • /flow:sync ALWAYS writes the reconciled markdown to disk. It is mandatory: regenerate every markdown file in .agents/specs/<flow_id>/ (spec.md, learnings.md, and any other tracked markdown in the flow folder) — not just spec.md — so they all match Beads exactly, and persist them. Sync is never read-only/dry-run and must never finish without writing the markdown.
  • "Sync"/"export" means reconciling markdown ↔ Beads to identical reality on disk — NOT Dolt. NEVER run bd dolt push/bd dolt pull (Dolt remote sync) or bd export (the optional JSONL snapshot) as part of sync. They are out of scope and only run if the user explicitly and separately asks for them.
  • Sync reads backend state; do not close, block, or mutate tasks during status reporting.
  • Do not auto-stage/commit unless policy or the user explicitly allows it.
  • Preserve human-written spec content; only update synchronized task/status regions.
  • Ask before applying context-doc updates when sync detects drift.

Validation

  • Confirm status comes from Beads, not markdown markers.
  • Confirm broken file references, workflow drift, and sync policy decisions are reported.
  • For this repo, run make validate-skills after skill or command sync changes.

References Index

Example

User: "Flow status."

Action: read Beads state, summarize active flows, ready tasks, blockers, recent notes, and whether markdown views need sync.

What ships with it: 1 file

140 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most docs writing skills give in 575 tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • Read beads.json before sync decisions
  • Pull beads state as source of truth
  • Regenerate all synchronized markdown files
  • Report ready blocked and stale work
  • Ask before applying context doc updates
  • Confirm status comes from beads

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.