status-sync

Monitors bead statuses and reminds users to sync progress at phase completion or session end.

1|1|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/gvarela/prompts --skill status-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status-sync
Source: https://github.com/gvarela/prompts/tree/main/claude-code/skills/status-sync
Command: npx skills add https://github.com/gvarela/prompts --skill status-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads workflow often stalls when progress isn't synchronized, leaving phase issues open and end-of-session data inconsistent. This skill provides timely reminders to run bd sync and close phases, ensuring the beads state stays accurate.

Core Features & Use Cases

  • Automated reminders at phase completion and session end to sync beads status.
  • Context-aware prompts suggesting bd sync or bd close actions with a brief justification.
  • Works with common beads commands (bd stats, bd ready, bd list) to assess progress and trigger reminders.
  • Use Case: In a multi-phase project, when a phase finishes, the skill prompts the team to run a sync and lock the phase, preventing drift.

Quick Start

Use the status-sync skill to receive reminders whenever a phase completes or a session ends. You don't need to install anything extra; it relies on the built-in beads commands.

Frequently Asked Questions about status-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync beads status and close phases at the end of a workflow session?

To sync beads status, you can use the status-sync skill to receive automated reminders to run bd sync and bd close when a phase completes or a session ends. It checks progress with bd stats and bd list to ensure consistent state.

Why does my beads workflow stall and leave phase issues open between sessions?

Your beads workflow stalls when progress is not synchronized at session handoffs, leaving phase data inconsistent. The status-sync skill solves this by monitoring beads state and prompting you to run bd sync to prevent drift.

How do I get reminders to run bd sync when a project phase completes?

You get reminders to run bd sync by applying the status-sync skill to your beads-driven workflow. It monitors phase checkpoints and generates context-aware prompts suggesting sync actions with a brief justification when a phase finishes.

Do I need to install extra dependencies to monitor beads status and trigger sync reminders?

No, you do not need to install extra dependencies to monitor beads status. The status-sync skill relies on built-in beads commands like bd stats, bd ready, bd list, and bd sync to assess progress and generate contextual reminders.

Will the status-sync skill automatically modify my beads data when a session ends?

No, the status-sync skill will not automatically modify your beads data. It assesses your workflow state and generates contextual reminders for you to manually run bd sync or bd close, ensuring you maintain control over phase closures.

What is the best way to prevent data drift in multi-phase beads workflows?

The best way to prevent data drift in beads workflows is to use the status-sync skill for timely reminders to run bd sync at phase checkpoints and session ends. This ensures your beads state stays accurate without modifying data automatically.