Skill

status-sync

From wb

Monitors beads status and reminds about bd sync at session end or when phases complete.

Install

npx claudepluginhub gvarela/workbench

Tool Access

This skill is limited to using the following tools:

ReadGlobGrepBash(bd:*)

Preview

Reminds about beads synchronization when completing work or ending sessions.

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

159.9k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

159.9k

writing-skills

6 files

Guides TDD-style skill creation: pressure scenarios as tests, baseline agent failures, write docs to enforce compliance, verify with RED-GREEN-REFACTOR.

superpowers

156.0k

Stats

Stars1

Forks0

Last CommitApr 17, 2026

Actions

View Source View Plugin View on GitHub View README

Status Sync Reminder

Reminds about beads synchronization when completing work or ending sessions.

When to Activate

User completes a phase checkpoint

User says "done", "finished", "complete" about implementation work

At session end (before saying work is complete)

Check Current State

bd stats # Overall progress bd ready # What's available bd list --status=in_progress # What's claimed

Drift Indicators

Work done but not synced:

Issues closed in session but bd sync not run

End of session approaching

Phase complete but not closed:

All tasks in a phase done, but beads issue still open

Reminder: bd close [phase-id] --reason "..."

When to Remind

📍 Beads sync reminder: - [X] issues updated this session - Run `bd sync` before ending session Or if phase complete: - Phase [N] appears complete - Run: bd close [phase-id] --reason "Phase N complete"

When NOT to Remind

Minor work in progress (mid-phase)

User explicitly said they'll update later

Already reminded in this session

Just starting work (not ending)

DO NOT

Update files directly

Run commands automatically

Interrupt creative/coding flow unnecessarily

Remind repeatedly for the same issue

Status Sync Reminder

Reminds about beads synchronization when completing work or ending sessions.

When to Activate

User completes a phase checkpoint
User says "done", "finished", "complete" about implementation work
At session end (before saying work is complete)

Check Current State

bd stats                        # Overall progress
bd ready                        # What's available
bd list --status=in_progress    # What's claimed

Drift Indicators

Work done but not synced:

Issues closed in session but bd sync not run
End of session approaching

Phase complete but not closed:

All tasks in a phase done, but beads issue still open
Reminder: bd close [phase-id] --reason "..."

When to Remind

📍 Beads sync reminder:
- [X] issues updated this session
- Run `bd sync` before ending session

Or if phase complete:
- Phase [N] appears complete
- Run: bd close [phase-id] --reason "Phase N complete"

When NOT to Remind

Minor work in progress (mid-phase)
User explicitly said they'll update later
Already reminded in this session
Just starting work (not ending)

DO NOT

Update files directly
Run commands automatically
Interrupt creative/coding flow unnecessarily
Remind repeatedly for the same issue