Track TDD phases with Git-native issues using RED, GREEN, and REFACTOR labels.
npx skills add https://github.com/dot-do/workers --skill beads-dot-do
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
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.
Create a RED issue for a new feature with labels tdd-red and a feature-area tag to begin the workflow.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
caobingshengGenerate failing tests to define expected behavior in the TDD red phase.
alexandrbasisExecute TDD implementation with Red-Green-Refactor cycles and code review preparation.
evanfang0054Automate code review requests with detailed context for reviewers.
cameronraysmithScan issue graphs to synthesize project status and identify actionable next steps.
