skills.rest
SeanChenR
SeanChenRCOMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Enforce test-driven development with unit, integration, and Playwright E2E tests.

Updated Apr 21, 2026
Search Tags:#tdd#quality-assurance#software-engineering#unit-tests#integration-tests#e2e-tests#test-driven-development
One-click install
npx skills add https://github.com/SeanChenR/ghibli --skill tdd-workflow-seanchenr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/SeanChenR/ghibli/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/SeanChenR/ghibli --skill tdd-workflow-seanchenr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to maintain code quality during rapid development, leading to regression bugs and brittle architecture. This skill codifies a strict Test-Driven Development workflow that keeps tests at the forefront of every feature, bug fix, or refactor.

Core Features & Use Cases

  • Enforces writing tests before code across unit, integration, and end-to-end levels to ensure robust coverage.
  • Provides a repeatable process for generating user journeys, validating with RED-GREEN cycles, and tracking progress with checkpoint commits.
  • Supports staged activation criteria and concrete guidelines for test artifacts, review checkpoints, and refactoring safety.

Quick Start

Describe a feature you want, then implement tests first and iterate until all tests pass.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce test-driven development across my team's feature work and refactors?▼

Test-driven development is enforced by codifying a strict workflow that requires writing unit, integration, and Playwright E2E tests before implementation across all features, bug fixes, and refactors to maintain robust code quality.

What is the best way to maintain 80%+ test coverage during rapid software development?▼

To maintain 80%+ test coverage, apply a repeatable process using RED-GREEN cycles and checkpoint commits, ensuring tests are written first and pass before code is merged to prevent regression bugs and brittle architecture.

How do I structure user journeys and test cases for a new feature using TDD?▼

Structure user journeys and test cases by generating them before writing implementation code, then validating the logic through red-green-refactor cycles and tracking progress with git checkpoint commits to guarantee reliable delivery.

Does this TDD workflow support both unit tests and Playwright end-to-end tests?▼

Yes, this TDD workflow explicitly supports writing tests across multiple levels, specifying concrete guidelines for both unit tests and Playwright end-to-end tests to achieve an 80%+ coverage goal.

When should I use a strict test-driven development workflow instead of writing tests later?▼

Use a strict test-driven development workflow when teams struggle with regression bugs and brittle architecture during rapid development, ensuring tests remain at the forefront of feature work to guarantee reliable delivery.

Related Skills

Explore More Software Engineering Skills→
fmflurryfmflurry
171

tdd-workflow

Enforce test-driven development workflows with 80%+ coverage across feature, bug fix, and refactoring tasks.

Community
Intermediate
himanshu231204himanshu231204
2

tdd-workflow

Enforce test-driven development with Git checkpoint commits for each TDD stage.

Community
Advanced
eventua11yeventua11y
1

writing-tests

Automate E2E and unit test setup and execution with Playwright and Vitest.

Official
Intermediate
ps-carvalhops-carvalho

testing

Generate, execute, and report on unit, integration, and E2E tests.

Community
Advanced