beads-workflow
MUST use when creating, updating, or closing Beads issues via `bd` commands. Use proactively when starting work (bd update --status=in_progress) and completing work (bd close). Trigger: any mention of "issue", "task tracking", "what should I work on", "bd create/ready/close", or when the session hook indicates beads is active. Provides full bd CLI reference and workflow patterns.
What this skill does
# Beads Workflow for SDLC
## Goal
Use the Beads CLI (`bd`) to track work items as git-native files with explicit dependencies. Beads enables autonomous SDLC by making blocking relationships visible — `bd ready` shows what can be worked on now, `bd close` unblocks dependents.
## Dependencies
### Tools
- **`bd` CLI** — Git-native issue tracker. Commands: `bd create`, `bd ready`, `bd close`, `bd dep add`, `bd show`, `bd list`, `bd sync`.
- **Bash** — Runs all `bd` commands.
- **git** — Beads stores work items as files in the repo.
### Connectors
- **Git worktrees** (optional) — Each Bead can map to an isolated worktree for parallel execution.
## Context
### Core Commands
**Finding work:**
```bash
bd ready # Tasks with no blockers (ready now)
bd list --status=open # All open tasks
bd list --status=in_progress # Active work
bd show <bead-id> # Full details with dependencies
bd blocked # All blocked tasks
```
**Creating work:**
```bash
# Priority: 0=critical, 1=high, 2=medium, 3=low, 4=backlog
# Types: task, feature, bug, epic, chore
bd create --title="Implement feature X" --type=task --priority=1
```
**Managing dependencies:**
```bash
# First arg DEPENDS ON second arg
bd dep add <task-that-needs> <task-it-needs>
bd dep remove <task> <dependency>
```
**Completing work:**
```bash
bd close <bead-id> # Unblocks dependents
bd close <id1> <id2> <id3> # Close multiple at once
bd close <bead-id> --reason="Done" # Close with reason
```
**Syncing:**
```bash
bd sync # Sync with git remote
bd stats # Project statistics
bd doctor # Check for issues
```
### Best Practices
1. **Granular tasks** — Each Bead should be implementable in one focused session
2. **Clear dependencies** — Use `bd dep add` to make blocking relationships explicit
3. **Close immediately** — Run `bd close` as soon as verification passes
4. **Sync often** — Run `bd sync` after completing work
5. **Check ready first** — Always start with `bd ready` to find unblocked work
## Process
### Step 0: Load Stored Feedback
```bash
python ${CLAUDE_PLUGIN_ROOT}/scripts/feedback_manager.py autonomous-sdlc show-feedback
```
Apply relevant feedback: **beads_workflow**, **general**.
### Step 1: Architect Creates Feature Graph
Break requirements into Beads with dependencies:
```bash
bd create --title="Database schema for users" --type=task --priority=1 # → beads-abc
bd create --title="User model and repository" --type=task --priority=1 # → beads-def
bd create --title="Auth middleware" --type=task --priority=1 # → beads-ghi
bd create --title="Login/logout endpoints" --type=feature --priority=1 # → beads-jkl
# Dependency chain
bd dep add beads-def beads-abc # Model depends on schema
bd dep add beads-ghi beads-def # Middleware depends on model
bd dep add beads-jkl beads-ghi # Endpoints depend on middleware
```
### Step 2: Find Ready Work
```bash
bd ready # Shows beads-abc (no blockers)
```
When `bd ready` returns multiple tasks, they can be implemented in parallel (no mutual dependencies).
### Step 3: Implement and Close
```bash
# After implementation passes verification
git add -A
git commit -m "feat(beads-abc): implement database schema for users"
bd close beads-abc # Unblocks beads-def
bd sync
```
### Step 4: Worktree Integration (Optional)
Each Bead can map to an isolated worktree. Claude Code provides native worktree isolation via `isolation: "worktree"` on the Task tool — worktree creation and cleanup are automatic:
```python
# Spawn a builder in an isolated worktree for this Bead
Task(
subagent_type="autonomous-sdlc:builder",
description=f"Build beads-abc",
prompt="Implement the task...",
isolation="worktree",
run_in_background=True
)
# On completion: bd close beads-abc
```
## Output
A dependency graph of Beads tracked as git-native files. The graph drives autonomous workflow: `bd ready` determines what to work on, `bd close` cascades unblocking, and `bd sync` shares progress.
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.