Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

openspec-beads-sync

Étoiles3

Forks0

Mis à jour12 mai 2026 à 02:09

Session-start sync ritual. Pulls latest Beads state, lists active OpenSpec changes, shows ready and blocked work, and outputs a one-paragraph state summary. Use at the start of any session before picking up OpenSpec-backed Beads work.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

boardthatpowder

boardthatpowder/BeadSpec

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

name	openspec-beads-sync
description	Session-start sync ritual. Pulls latest Beads state, lists active OpenSpec changes, shows ready and blocked work, and outputs a one-paragraph state summary. Use at the start of any session before picking up OpenSpec-backed Beads work.
license	MIT
compatibility	Requires openspec CLI and bd (beads) CLI.
metadata	{"author":"openspec","version":"1.0","generatedBy":"1.1.1"}

Sync Beads and OpenSpec state at session start.

Input: None.

Steps

Repair worktree Beads runtime
```
if [ -x scripts/setup-worktree-beads.sh ]; then
  scripts/setup-worktree-beads.sh
fi
```
This is local runtime setup only: it links ignored worktree Beads runtime files to the main checkout so all worktrees share the same Dolt database. If it reports that the main checkout is detected, continue.
Pull latest Beads state
```
bd prime
bd dolt pull
```
If bd dolt pull reports no remote, continue with local state and note it in the summary.
Show active OpenSpec changes
```
openspec list
```
Show ready and blocked work
```
bd ready
bd blocked
```
Write state summary

Output one paragraph covering:
- How many OpenSpec changes are active and how many have Beads issues not yet imported
- How many Beads issues are ready to work, in progress, and blocked
- Which change has the most ready work (if any)
- Any blockers that need user attention before work can resume

Guardrails

This skill is read-only for Beads issue state — the setup step may repair ignored local runtime symlinks
If bd ready returns nothing, surface that explicitly so the user knows no work is available
If bd dolt pull fails, note it in the summary and continue — do not stop

Plus depuis ce dépôt

même dépôt

openspec-beads-complete

boardthatpowder/BeadSpec

Change-wide completion workflow. Verify no open or in-progress required Beads issues, run openspec validate and quality gates, close the epic, invoke openspec-archive-change, then follow the session-close protocol. Use when all implementation issues for an OpenSpec change are done.

2026-05-123

openspec-beads-followup

boardthatpowder/BeadSpec

Triage discovered work into in-scope bug, in-scope task, or out-of-scope follow-up. Sets correct type, priority, and dependency linkage in Beads. Does not silently expand the claimed issue's scope.

2026-05-123

openspec-beads-import

boardthatpowder/BeadSpec

Import an approved OpenSpec change into Beads. Creates one epic, one Beads issue per tasks.md entry, infers task-level dependencies by reading each task description, then shows bd ready snapshot. Use after OpenSpec artifacts are approved and before coding starts.

2026-05-123

openspec-beads-scope-change

boardthatpowder/BeadSpec

Handle a spec gap discovered mid-implementation. Updates OpenSpec artifacts first via openspec-continue-change or openspec-sync-specs, validates, then creates and links Beads issues for the new work. Use when implementation reveals missing, contradictory, or changed behavior that must be reflected in OpenSpec before coding continues.

2026-05-123

openspec-beads-work

boardthatpowder/BeadSpec

Single-issue agent execution loop for OpenSpec-backed Beads work. Claim one ready issue, re-read the referenced OpenSpec artifacts, plan, implement scoped changes, run unit tests and openspec validate, then close or update with blockers. Self-contained — no runbook needed.

2026-05-123

ruflo-swarm-dispatch

boardthatpowder/BeadSpec

Use when deciding between built-in Agent parallelism and ruflo-swarm for multi-agent tasks. Default is always the built-in Agent tool. Ruflo swarm is the escalation path for consensus-required or state-sharing tasks only.

2026-05-123

name	openspec-beads-sync
description	Session-start sync ritual. Pulls latest Beads state, lists active OpenSpec changes, shows ready and blocked work, and outputs a one-paragraph state summary. Use at the start of any session before picking up OpenSpec-backed Beads work.
license	MIT
compatibility	Requires openspec CLI and bd (beads) CLI.
metadata	{"author":"openspec","version":"1.0","generatedBy":"1.1.1"}

Sync Beads and OpenSpec state at session start.

Input: None.

Steps

Repair worktree Beads runtime
```
if [ -x scripts/setup-worktree-beads.sh ]; then
  scripts/setup-worktree-beads.sh
fi
```
This is local runtime setup only: it links ignored worktree Beads runtime files to the main checkout so all worktrees share the same Dolt database. If it reports that the main checkout is detected, continue.
Pull latest Beads state
```
bd prime
bd dolt pull
```
If bd dolt pull reports no remote, continue with local state and note it in the summary.
Show active OpenSpec changes
```
openspec list
```
Show ready and blocked work
```
bd ready
bd blocked
```
Write state summary

Output one paragraph covering:
- How many OpenSpec changes are active and how many have Beads issues not yet imported
- How many Beads issues are ready to work, in progress, and blocked
- Which change has the most ready work (if any)
- Any blockers that need user attention before work can resume

Guardrails

This skill is read-only for Beads issue state — the setup step may repair ignored local runtime symlinks
If bd ready returns nothing, surface that explicitly so the user knows no work is available
If bd dolt pull fails, note it in the summary and continue — do not stop