skills.rest
Dedalus-ERP-PAS
Dedalus-ERP-PASOFFICIAL
Explore all skills by this author →
WebsiteGitHub

tdd

Guide test-driven development with RED-GREEN-REFACTOR cycles and end-to-end tests.

Updated Aug 23, 2026
Search Tags:#workflow#tdd#refactoring#quality-assurance#software-engineering#integration-tests#test-driven-development
One-click install
npx skills add https://github.com/Dedalus-ERP-PAS/hexagone-foundation-skills --skill tdd-dedalus-erp-pas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Dedalus-ERP-PAS/hexagone-foundation-skills/tree/main/skills/tdd
Command: npx skills add https://github.com/Dedalus-ERP-PAS/hexagone-foundation-skills --skill tdd-dedalus-erp-pas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development helps teams deliver high-quality software by focusing on behavior first and enabling safer refactors.

Core Features & Use Cases

  • Structured workflow: Planning, tracer bullets, and iterative RED-GREEN-REFACTOR loops.
  • Guided testing philosophy: Integration-style tests, dependency injection, and testability practices.
  • Use Case: For a bug fix or feature add, write a single end-to-end test to specify expected behavior, then implement just enough code to pass.

Quick Start

Begin with one end-to-end test that defines a behavior, then implement only enough code to pass that test and iterate.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I start test-driven development for a new software feature?▼

Start test-driven development by writing one end-to-end integration test defining expected behavior, then implement just enough code to pass it. Iterate using incremental loops to build out the feature safely.

What is the RED-GREEN-REFACTOR cycle in test-driven development?▼

The RED-GREEN-REFACTOR cycle in test-driven development means writing a failing test, implementing code to make it pass, and then refactoring. It enforces incremental development and enables safer code improvements.

Does test-driven development work for both frontend and backend projects?▼

Yes, test-driven development works across frontend and backend projects regardless of language. It guides planning and tracer bullets to establish end-to-end workflows suitable for any software engineering environment.

How do I use dependency injection to improve testability in integration tests?▼

Use dependency injection to isolate components during integration tests, ensuring tests focus on behavior rather than implementation details. This practice is enforced during the test-driven development workflow.

What's the best way to write tests for a bug fix using test-driven development?▼

The best way to fix bugs using test-driven development is writing a single end-to-end test specifying the expected behavior first. Implement only enough code to pass the test, ensuring the bug is resolved and documented.

When should I use tracer bullets before starting incremental TDD loops?▼

Use tracer bullets during the planning phase to establish an end-to-end workflow skeleton before entering incremental TDD loops. This approach validates architectural decisions early across frontend and backend systems.

Related Skills

Explore More Software Engineering Skills→
leocostaleocosta
4

test-tdd

Automate an isolated red-green-refactor TDD loop with four phases.

Community
Intermediate
PaulKinlanPaulKinlan
2

test-and-validate

Execute automated test suites and manual validation checks on code.

Community
Intermediate
billydeeii136billydeeii136

health

Compute a weighted 0-10 codebase health score and track trends over time.

Community
Intermediate
fcnatrafcnatra

bdd-with-approvals

Create executable BDD specifications and scannable approval tests.

Community
Intermediate