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.
Best use case
flow-sync-status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when syncing Beads state to markdown, checking Flow status, refreshing context docs, validating task markers, or reporting ready/blocked Flow work.
Teams using flow-sync-status should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/flow-sync-status/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How flow-sync-status Compares
| Feature / Agent | flow-sync-status | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when syncing Beads state to markdown, checking Flow status, refreshing context docs, validating task markers, or reporting ready/blocked Flow work.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Flow Sync And Status Use this lifecycle skill for status dashboards, sync, context refresh, cleanup checks, and drift reporting. ## 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 - Sync reads backend state; do not close, block, or mutate tasks during status reporting. - Do not run export, auto-stage, or Dolt push 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 - [Sync](../flow/references/sync.md) - [Status](../flow/references/status.md) - [Refresh](../flow/references/refresh.md) - [Cleanup](../flow/references/cleanup.md) ## Example User: "Flow status." Action: read Beads state, summarize active flows, ready tasks, blockers, recent notes, and whether markdown views need sync.
Related Skills
flow-memory-keeper
Use at task, phase, flow, sync, archive, finish, revise, or failure checkpoints to keep Flow specs clean, capture learnings and failures, elevate durable patterns, and refine this skill with project-specific nuances
flow
Use when a repository has .agents, when the user asks for Flow lifecycle routing, Beads-backed task memory, spec-first planning, TDD implementation, sync/status, review, finish, archive, or /flow:* help.
flow-setup
Use when initializing Flow in a repo, configuring .agents, installing or checking Beads bd, setting local-only sync policy, or creating first project context files.
flow-planning
Use when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.
flow-execution
Use when implementing Flow tasks from Beads or spec.md, claiming ready work, applying TDD, recording task notes, committing, and syncing after task state changes.
flow-completion
Use when reviewing, finishing, archiving, reverting, validating, or cleaning up Flow work after implementation or phase completion.
vue
Use when editing Vue projects, .vue files, vue.config.js, Vue 3 components, Composition API, <script setup>, SFC state, deployment workflows, or Vue CI configuration.
vite
Use when editing Vite projects, vite.config.ts, vite.config.js, Vite plugins, HMR, asset bundling, frontend build settings, deployment config, or Litestar/Vite integration.
uvicorn
Use when deploying ASGI apps with uvicorn, editing uvicorn CLI commands, Config or Server usage, workers, reload, event loop selection, SSL, lifespan, logging, or development server behavior.
tracer
Use when tracing execution paths, mapping dependencies, understanding unfamiliar code, following data flow, investigating end-to-end behavior, debugging call chains, or deciding which files to read next.
testing
Use when writing or refactoring tests, editing test_*.py, *.test.ts, *.spec.ts, conftest.py, vitest.config.ts, pytest fixtures, mocks, coverage, async tests, anyio, or test failure debugging.
terraform
Use when creating, adopting, refactoring, or operating Terraform, *.tf files, .terraform.lock.hcl, terragrunt.hcl, root modules, backends, state, workspaces, imports, CI plan/apply, tests, or policy checks.