원클릭으로 Manus에서 모든 스킬 실행

flow-sync-status

스타14

포크4

업데이트2026년 6월 24일 15:38

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

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

cofin

cofin/flow

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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

Read .agents/beads.json before any sync/export decision.
Pull Beads state and notes as the source of truth.
Regenerate synchronized markdown views without changing requirement text.
Detect drift in workflow commands, tech stack, patterns, knowledge chapters, and references.
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.

이 저장소의 다른 Skills

같은 저장소

flow-planning

cofin/flow

Use when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.

2026-06-2414

flow-setup

cofin/flow

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.

2026-06-2414

flow

cofin/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.

2026-06-2414

flow-memory-keeper

cofin/flow

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

2026-06-2414

flow-execution

cofin/flow

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.

2026-06-0614

apilookup

cofin/flow

Use when work depends on current external API behavior, SDK docs, framework versions, breaking changes, migration guides, changelogs, release notes, deprecations, or syntax that may have changed.

2026-04-2714

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

Read .agents/beads.json before any sync/export decision.

Pull Beads state and notes as the source of truth.

Regenerate synchronized markdown views without changing requirement text.

Detect drift in workflow commands, tech stack, patterns, knowledge chapters, and references.

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.

name	flow-sync-status
description	Use when syncing Beads state to markdown, checking Flow status, refreshing context docs, validating task markers, or reporting ready/blocked Flow work.