sw-build

Implement software work units through a TDD cycle with Git commits.

9|1|Updated Feb 9, 2026

Search Tags:#automation #git #workflow #testing #tdd #development

Ready to run

npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-build

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sw-build
Source: https://github.com/Obsidian-Owl/specwright/tree/main/skills/sw-build
Command: npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-build

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the implementation of software work units using a strict Test-Driven Development (TDD) process, ensuring code quality and verifiable progress.

Core Features & Use Cases

TDD Workflow: Guides the implementation through RED (failing tests), GREEN (passing tests), and REFACTOR stages.
Automated Commits: Creates a commit for each completed task, maintaining a clean and traceable history.
Branch Management: Handles Git branch creation and checkout according to configuration.
Use Case: Implement a new feature by defining acceptance criteria, letting the skill generate tests, write minimal code to pass them, and then refactor, all while ensuring the codebase remains stable.

Quick Start

Use the sw-build skill to implement the next task for work unit 'WU-123'.

Frequently Asked Questions about sw-build

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

FAQPage Schema

How do I automate test-driven development for new software features?▼

Test-driven development for new features is automated by delegating test writing to a tester agent and implementation to an executor agent. This enforces a strict RED, GREEN, and REFACTOR cycle to ensure code quality and verifiable progress for software work units.

What is the best way to manage Git branches during TDD implementation?▼

Git branch management during TDD implementation is handled automatically by creating and checking out branches according to configuration. It commits code per completed task to maintain a clean, traceable history while ensuring all acceptance criteria are met before verification.

How does automated TDD workflow handle acceptance criteria?▼

Automated TDD workflow handles acceptance criteria by generating tests based on them, writing minimal code to pass the tests, and refactoring. The workflow state is updated continuously, ensuring all acceptance criteria are met before handing off to verification.

Do I need pre-defined work units to use automated TDD implementation?▼

Pre-defined work units are needed for automated TDD implementation, as the process implements the next task for a specific work unit identifier. Defining acceptance criteria beforehand lets the agents generate appropriate tests and write minimal code to pass them.

Can I integrate manual code reviews within an automated TDD workflow?▼

Manual code reviews can be integrated after the automated TDD workflow completes its cycle. The skill ensures the codebase remains stable and hands off to verification once all tests pass, providing a clean baseline for any subsequent manual review processes.