How does the TDD workflow work with this skill?

The skill automates the creation of a three-part issue chain: RED for writing failing tests, GREEN for the minimal implementation to pass, and REFACTOR for code cleanup.

Beads (bd) is a git-native issue tracker that lives inside your repository, allowing you to track tasks, bugs, and features without leaving your development environment.

How does Beads differ from TodoWrite?

TodoWrite is intended for simple, single-session checklists, whereas Beads is built for complex, multi-session work requiring persistent context and dependency tracking.

Can I use Beads for team collaboration?

Yes. Because Beads is git-native, the issue state is committed to your repository and can be synced across team members using standard git workflows.

Does this skill support parallel development?

Yes, you can launch parallel subagents to create multiple TDD issue chains for different modules simultaneously, with all dependencies automatically linked.

Beads Issue Tracker & TDD Workflow

Name: Beads Issue Tracker & TDD Workflow
Author: dot-do

bydot-do

•

生产力与工作流

Manages git-native issue tracking and Test-Driven Development (TDD) cycles directly within your repository.

Beads is a git-native issue tracker designed for multi-session work and complex dependency management. This skill optimizes Claude's ability to navigate the TDD cycle by creating structured issue chains for RED (failing tests), GREEN (implementation), and REFACTOR phases. It allows developers to maintain persistent context, manage linear and non-linear tasks with dependency graphs, and utilize parallel subagents for large feature development, ensuring high code quality and clear progress tracking throughout the software development lifecycle.