| name | beads-workflow |
| description | 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.
|
| version | 1.0.0 |
| effort | low |
| allowed-tools | ["Bash"] |
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:
bd ready
bd list --status=open
bd list --status=in_progress
bd show <bead-id>
bd blocked
Creating work:
bd create --title="Implement feature X" --type=task --priority=1
Managing dependencies:
bd dep add <task-that-needs> <task-it-needs>
bd dep remove <task> <dependency>
Completing work:
bd close <bead-id>
bd close <id1> <id2> <id3>
bd close <bead-id> --reason="Done"
Syncing:
bd sync
bd stats
bd doctor
Best Practices
- Granular tasks — Each Bead should be implementable in one focused session
- Clear dependencies — Use
bd dep add to make blocking relationships explicit
- Close immediately — Run
bd close as soon as verification passes
- Sync often — Run
bd sync after completing work
- Check ready first — Always start with
bd ready to find unblocked work
Process
Step 0: Load Stored Feedback
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:
bd create --title="Database schema for users" --type=task --priority=1
bd create --title="User model and repository" --type=task --priority=1
bd create --title="Auth middleware" --type=task --priority=1
bd create --title="Login/logout endpoints" --type=feature --priority=1
bd dep add beads-def beads-abc
bd dep add beads-ghi beads-def
bd dep add beads-jkl beads-ghi
Step 2: Find Ready Work
bd ready
When bd ready returns multiple tasks, they can be implemented in parallel (no mutual dependencies).
Step 3: Implement and Close
git add -A
git commit -m "feat(beads-abc): implement database schema for users"
bd close beads-abc
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:
Task(
subagent_type="autonomous-sdlc:builder",
description=f"Build beads-abc",
prompt="Implement the task...",
isolation="worktree",
run_in_background=True
)
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.