beads

Track TDD phases with Git-native issues using RED, GREEN, and REFACTOR labels.

5|2|Updated Jul 10, 2025

Search Tags:#workflow #tdd #dependencies #beads #labels #issue-tracking #project-management

Ready to run

npx skills add https://github.com/dot-do/workers --skill beads-dot-do

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/dot-do/workers/tree/main/skills/beads
Command: npx skills add https://github.com/dot-do/workers --skill beads-dot-do

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads provides a Git-native issue tracker to coordinate multi-session development using dependency graphs, enabling disciplined TDD workflows (RED, GREEN, REFACTOR) within a project.

Core Features & Use Cases

TDD-phase tracking: RED (failing tests), GREEN (implementing), REFACTOR (cleanup) with explicit dependencies to enforce order.
Dependency management: link issues so GREEN depends on RED and REFACTOR depends on GREEN, keeping work aligned.
Labels and progress: use standard labels like tdd-red, tdd-green, tdd-refactor to filter and surface blockers.

Quick Start

Create a RED issue for a new feature with labels tdd-red and a feature-area tag to begin the workflow.

Frequently Asked Questions about beads

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

FAQPage Schema

How do I track TDD workflow phases like RED, GREEN, and REFACTOR across multiple development sessions?▼

You can track TDD workflow phases across multiple sessions by using Git-native issue tracking to coordinate RED, GREEN, and REFACTOR issues with explicit phase dependencies. This approach enforces development order and keeps work aligned across modules.

What is the best way to manage dependencies between failing tests and implementation issues in a project?▼

Managing dependencies between failing tests and implementation requires linking issues so GREEN depends on RED and REFACTOR depends on GREEN. This dependency graph enforces a disciplined TDD workflow and prevents out-of-order progress.

Can I use standard labels to filter and surface blockers in a multi-session TDD workflow?▼

Yes, you can use standard labels like tdd-red, tdd-green, and tdd-refactor to filter issues and surface blockers in a multi-session TDD workflow. Applying these labels with feature-area tags helps track progress and dependencies.

How do I start a TDD issue tracking workflow for a new software feature?▼

To start a TDD issue tracking workflow for a new feature, create a RED issue for the failing tests and label it with tdd-red and a feature-area tag. This initiates the dependency graph for the subsequent GREEN and REFACTOR phases.

Does Git-native issue tracking work for collaborative software projects with complex module dependencies?▼

Git-native issue tracking is designed for collaborative software projects with complex module dependencies. It coordinates multi-session, TDD-based development workflows by applying explicit phase dependencies across modules and features.

TDD phase tracking is not keeping work aligned across modules, what are the limitations?▼

If TDD phase tracking is not keeping work aligned across modules, ensure you are correctly linking issues so GREEN depends on RED and REFACTOR depends on GREEN. Without these explicit dependency graphs, coordinated progress and tracking across features can break down.